Project

Profile

Help

Refactor #9354

Disable DJANGO_ALLOW_ASYNC_UNSAFE for content app

Added by dalley about 1 month ago. Updated 10 days ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Plugins will need to adapt their code to be async - and possibly APIs will need to be changed to facilitate this.

Associated revisions

Revision 1a8c7c53 View on GitHub
Added by dalley 10 days ago

Disable DJANGO_ALLOW_ASYNC_UNSAFE for the content app

It's just hiding issues.

closes: #9354 https://pulp.plan.io/issues/9354

History

#1 Updated by bmbouter about 1 month ago

When do you think plugins need to make this change by? Also what steps does pulpcore need to take to work towards this?

#2 Updated by bmbouter about 1 month ago

Maybe we discuss at the pulpcore meeting? If so, perhaps put it on the agenda?

#3 Updated by dalley about 1 month 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.

#5 Updated by dalley 11 days ago

  • Status changed from NEW to ASSIGNED

#6 Updated by pulpbot 11 days ago

  • Status changed from ASSIGNED to POST

#7 Updated by ipanova@redhat.com 11 days ago

  • Sprint/Milestone set to 3.17.0

#8 Updated by dalley 11 days ago

  • Assignee set to dalley

#9 Updated by dalley 10 days ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

Please register to edit this issue

Also available in: Atom PDF