Refactor #9354
closed
Disable DJANGO_ALLOW_ASYNC_UNSAFE for content app
100%
Description
Plugins will need to adapt their code to be async - and possibly APIs will need to be changed to facilitate this.
Updated by bmbouter about 3 years ago
When do you think plugins need to make this change by? Also what steps does pulpcore need to take to work towards this?
Updated by bmbouter about 3 years ago
Maybe we discuss at the pulpcore meeting? If so, perhaps put it on the agenda?
Updated by dalley about 3 years ago
bmbouter Here's an example: https://github.com/pulp/pulp_rpm/blob/master/pulp_rpm/app/models/repository.py#L424-L459
I don't think it will be difficult but the challenge to make the changes themselves but since it requires API changes it does apply some constraints on how we execute.
Updated by dalley about 3 years ago
Yeah, I think it's just those two methods. https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/publication.py#L461-L483
Updated by pulpbot about 3 years ago
- Status changed from ASSIGNED to POST
Added by dalley about 3 years ago
Updated by dalley about 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|1a8c7c53031f80a1d571f99add06651233e0b8fb.
Updated by pulpbot almost 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Disable DJANGO_ALLOW_ASYNC_UNSAFE for the content app
It's just hiding issues.
closes: #9354 https://pulp.plan.io/issues/9354