#35495: Referencing default django.contrib packages permissions in data 
migrations,
results in a "race condition"
----------------------------+--------------------------------------
     Reporter:  braiam      |                    Owner:  nobody
         Type:  Bug         |                   Status:  closed
    Component:  Migrations  |                  Version:  5.0
     Severity:  Normal      |               Resolution:  duplicate
     Keywords:              |             Triage Stage:  Unreviewed
    Has patch:  0           |      Needs documentation:  0
  Needs tests:  0           |  Patch needs improvement:  0
Easy pickings:  0           |                    UI/UX:  0
----------------------------+--------------------------------------
Changes (by Simon Charette):

 * resolution:   => duplicate
 * status:  new => closed

Comment:

 > I first used the forums to describe my findings, but this seems the best
 channel.

 This is a not a second level support channel.

 [https://docs.djangoproject.com/en/5.0/internals/contributing/bugs-and-
 features/#reporting-bugs-and-requesting-features The first line of the
 Reporting bugs and requesting features documentation states].

 > Check that someone hasn’t already filed the bug or feature request by
 [https://code.djangoproject.com/search searching] or running
 [https://code.djangoproject.com/query custom queries] in the ticket
 tracker.

 Clicking the above links and
 
[https://code.djangoproject.com/query?description=~permissions&status=assigned&status=new&order=id&desc=1
 searching for "permissions"] links to #29843 (''Create permissions using
 migration operations rather than using the post_migrate signal'') which
 details the exact same use case you ran into.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35495#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018fe4f47329-4caf4bd1-2d8e-486b-b57a-a2e779cdb9d8-000000%40eu-central-1.amazonses.com.

Reply via email to