[Django] #29046: possible race condition with manager logic

25 views

Skip to first unread message

Django

unread,

Jan 22, 2018, 4:48:37 PM1/22/18

to django-...@googlegroups.com

i tried a lot to explain this weird behaviour, but since it happens
sometimes and doenst at other times i think that its due to some weird
race condition.

Please have a look at the travis build logs:
https://travis-ci.org/kakulukia/django-undeletable
https://travis-ci.org/kakulukia/django-undeletable/builds/331788403 (build
#23)

Most of the time django 1.11 under python2 is failing.
So please could someone with more knowledge about django manager magic
have a look at my module?

git clone https://github.com/kakulukia/django-undeletable.git
git checkout cookiecutter-version
make init2
pipenv shell
pip install django=1.11.9
make test

BTW: The django sources have been uploaded to pypi resulting in a python2
pip trying to install django 2 which aint working. Is there a workaround?
Why are the sources uploaded to pypi?

--
Ticket URL: <https://code.djangoproject.com/ticket/29046>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,

Jan 22, 2018, 4:53:18 PM1/22/18

to django-...@googlegroups.com

#29046: possible race condition with manager logic
-------------------------------------+-------------------------------------

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Description changed by Andy Grabow:

Old description:

> Hi,
>
> i tried a lot to explain this weird behaviour, but since it happens
> sometimes and doenst at other times i think that its due to some weird
> race condition.
>
> Please have a look at the travis build logs:
> https://travis-ci.org/kakulukia/django-undeletable
> https://travis-ci.org/kakulukia/django-undeletable/builds/331788403
> (build #23)
>
> Most of the time django 1.11 under python2 is failing.
> So please could someone with more knowledge about django manager magic
> have a look at my module?
>
> git clone https://github.com/kakulukia/django-undeletable.git
> git checkout cookiecutter-version
> make init2
> pipenv shell
> pip install django=1.11.9
> make test
>
> BTW: The django sources have been uploaded to pypi resulting in a python2
> pip trying to install django 2 which aint working. Is there a workaround?
> Why are the sources uploaded to pypi?

New description:

Hi,

i tried a lot to explain this weird behaviour, but since it happens
sometimes and doenst at other times i think that its due to some weird
race condition.

Please have a look at the travis build logs:
https://travis-ci.org/kakulukia/django-undeletable
https://travis-ci.org/kakulukia/django-undeletable/builds/331788403 (build
#23)

Most of the time django 1.11 under python2 is failing.
So please could someone with more knowledge about django manager magic
have a look at my module?

git clone https://github.com/kakulukia/django-undeletable.git
git checkout cookiecutter-version
make init2
pipenv shell
pip install django=1.11.9
make test

In the last 4 years of me using that module in different projects, this
bug never happend. This might be due to the striped to the basics version
of this unittest compared to a project with multiple other modules to load
before actually executing any ORM logic. Just a guess.

BTW: The django sources have been uploaded to pypi resulting in a python2
pip trying to install django 2 which aint working. Is there a workaround?
Why are the sources uploaded to pypi?

--
Ticket URL: <https://code.djangoproject.com/ticket/29046#comment:1>

Django

unread,

Jan 23, 2018, 1:02:52 PM1/23/18

to django-...@googlegroups.com

#29046: possible race condition with manager logic
-------------------------------------+-------------------------------------

Reporter: Andy Grabow | Owner: nobody

Type: Bug | Status: closed

Component: Database layer | Version: 2.0
(models, ORM) |

Severity: Normal | Resolution: needsinfo
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 Tim Graham):

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

Comment:

Please see TicketClosingReasons/UseSupportChannels for ways to get help
debugging your code. If you confirm a bug in Django, please reopen the
ticket with details. A ticket should provide a very minimal project to
reproduce the problem rather than a larger project with a lot of unrelated
details. Thanks.