Project

Profile

Help

Refactor #9354

closed

Disable DJANGO_ALLOW_ASYNC_UNSAFE for content app

Added by dalley about 1 year ago. Updated 10 months ago.

Status:
CLOSED - CURRENTRELEASE
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.

Actions #1

Updated by bmbouter about 1 year ago

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

Actions #2

Updated by bmbouter about 1 year ago

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

Actions #3

Updated by dalley about 1 year 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.

Actions #5

Updated by dalley 12 months ago

  • Status changed from NEW to ASSIGNED
Actions #6

Updated by pulpbot 12 months ago

  • Status changed from ASSIGNED to POST
Actions #7

Updated by ipanova@redhat.com 12 months ago

  • Sprint/Milestone set to 3.17.0
Actions #8

Updated by dalley 12 months ago

  • Assignee set to dalley

Added by dalley 12 months ago

Revision 1a8c7c53

Disable DJANGO_ALLOW_ASYNC_UNSAFE for the content app

It's just hiding issues.

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

Actions #9

Updated by dalley 12 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #10

Updated by pulpbot 10 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF