Re: [Django] #31866: Proxy model is ignored when referenced in select_for_update's 'of' parameter

[Django]

#31866: Proxy model is ignored when referenced in select_for_update's 'of'
parameter
-+-
 Reporter:  Daniel Hillier   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  proxy| Triage Stage:
  select_for_update  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Daniel Hillier):

 Created branch with failing tests here:
 https://github.com/danifus/django/tree/b31866

-- 
Ticket URL: 
Django 
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/065.36da4fbe8047d274e04ab33af671ae2b%40djangoproject.com.

[Django] #31866: Proxy model is ignored when referenced in select_for_update's 'of' parameter

[Django]

#31866: Proxy model is ignored when referenced in select_for_update's 'of'
parameter
-+-
   Reporter:  Daniel |  Owner:  nobody
  Hillier|
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.1
  layer (models, ORM)|   Keywords:  proxy
   Severity:  Normal |  select_for_update
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When referring to a proxy model as a FK in a `select_for_update()` call,
 the proxy model's table is silently omitted from the `FOR UPDATE` clause
 in the resulting SQL.

 Also, if a model has a FK to a proxy model, the `FieldError` that is
 supposed to be raised when an any inappropriate field is found in a
 `select_for_update()` call will crash with `AttributeError: 'NoneType'
 object has no attribute 'name'` .

 Tested with postgres but I don't think this is specific to that db.

-- 
Ticket URL: 
Django 
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/050.b7356049d5b6a4a06700e1dcd9075004%40djangoproject.com.

Re: [Django] #31864: Session data cannot be decoded during the transition to Django 3.1.

[Django]

#31864: Session data cannot be decoded during the transition to Django 3.1.
--+
 Reporter:  felixxm   |Owner:  felixxm
 Type:  Bug   |   Status:  closed
Component:  contrib.sessions  |  Version:  3.1
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Mariusz Felisiak ):

 In [changeset:"c21bbe0883772ea91993eabac6c91ff575a81912" c21bbe08]:
 {{{
 #!CommitTicketReference repository=""
 revision="c21bbe0883772ea91993eabac6c91ff575a81912"
 [3.1.x] Fixed #31864 -- Fixed encoding session data during transition to
 Django 3.1.

 Thanks אורי for the report.
 Backport of 99abfe8f4d3caebcd73548f5bf9e4755bdfed318 from master
 }}}

-- 
Ticket URL: 
Django 
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/065.4a1125949a606079311879eaf802f384%40djangoproject.com.

Re: [Django] #31864: Session data cannot be decoded during the transition to Django 3.1.

[Django]

#31864: Session data cannot be decoded during the transition to Django 3.1.
--+
 Reporter:  felixxm   |Owner:  felixxm
 Type:  Bug   |   Status:  closed
Component:  contrib.sessions  |  Version:  3.1
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by GitHub ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"99abfe8f4d3caebcd73548f5bf9e4755bdfed318" 99abfe8]:
 {{{
 #!CommitTicketReference repository=""
 revision="99abfe8f4d3caebcd73548f5bf9e4755bdfed318"
 Fixed #31864 -- Fixed encoding session data during transition to Django
 3.1.

 Thanks אורי for the report.
 }}}

-- 
Ticket URL: 
Django 
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/065.f16dc7e23776b58952cfaccae33548eb%40djangoproject.com.

Re: [Django] #31865: Missing variable in admin template

[Django]

#31865: Missing variable in admin template
---+--
 Reporter:  Christian Ullrich  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  3.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham):

 The logging comes from dc5b01ad05e50ccde688c73c2ed3334a956076b0 (if DEBUG
 is True).

 I haven't looked into the details but I'd suggest accepting this issue.

-- 
Ticket URL: 
Django 
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/068.59fff524235bb10f9f6a46ba051c3c62%40djangoproject.com.

Re: [Django] #31863: FK field caching behavior change between 1.11.x and 2.x

[Django]

#31863: FK field caching behavior change between 1.11.x and 2.x
-+-
 Reporter:  Gert Burger  |Owner:  Gert
 |  Burger
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Gert Burger):

 * has_patch:  0 => 1


Comment:

 Can someone please double check the fields on the ticket and PR, not sure
 if I got them right.

 https://github.com/django/django/pull/13281/

-- 
Ticket URL: 
Django 
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/068.a93b6c68bc99d9d4e3dedab13c0a8a58%40djangoproject.com.

Re: [Django] #31831: AlterOrderWithRespectTo() with ForeignKey crash when _order is included in Index().

[Django]

#31831: AlterOrderWithRespectTo() with ForeignKey crash when _order is included 
in
Index().
+-
 Reporter:  KyuJoo Han  |Owner:  Iuri de Silvio
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  3.0
 Severity:  Normal  |   Resolution:
 Keywords:  migrations  | Triage Stage:  Ready for checkin
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by felixxm):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
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/064.4c9cbed962c4ae5f9309a34d61e7c55d%40djangoproject.com.

Re: [Django] #31865: Missing variable in admin template

[Django]

#31865: Missing variable in admin template
---+--
 Reporter:  Christian Ullrich  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  3.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Carlton Gibson):

 Hi.

 First pass, I'd say this is deliberately leveraging the DTL's behaviour of
 allowing context variables to be undefined. I wouldn't be logging these:
 `django.template.base.VariableDoesNotExist`, they're expected.

 So, again first pass, do you really want your logging turned up that high?

-- 
Ticket URL: 
Django 
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/068.d3b5a128528b7a1af779aa57bf7a8edf%40djangoproject.com.

[Django] #31865: Missing variable in admin template

[Django]

#31865: Missing variable in admin template
-+
   Reporter:  Christian Ullrich  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  3.1
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 The `admin/nav_sidebar.html` template appears to be missing an assignment
 to `show_changelinks` where it includes `app_list.html`:

 {{{
 {% include 'admin/app_list.html' with app_list=available_apps %}
 }}}

 This leads to megabytes of log spam for every admin page visited with the
 sidebar on:

 {{{
 2020-08-07 09:06:49,882 [DEBUG   ] (django.template) Exception while
 resolving variable 'show_changelinks' in template
 'admin/change_list.html'.
 Traceback (most recent call last):
   File "[python]\lib\site-packages\django\template\base.py", line 829, in
 _resolve_lookup
 current = current[bit]
   File "[python]\lib\site-packages\django\template\context.py", line 83,
 in __getitem__
 raise KeyError(key)
 KeyError: 'show_changelinks'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "[python]\lib\site-packages\django\template\base.py", line 835, in
 _resolve_lookup
 if isinstance(current, BaseContext) and getattr(type(current), bit):
 AttributeError: type object 'RequestContext' has no attribute
 'show_changelinks'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "[python]\lib\site-packages\django\template\base.py", line 843, in
 _resolve_lookup
 current = current[int(bit)]
 ValueError: invalid literal for int() with base 10: 'show_changelinks'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "[python]\lib\site-packages\django\template\base.py", line 848, in
 _resolve_lookup
 raise VariableDoesNotExist("Failed lookup for key "
 django.template.base.VariableDoesNotExist: Failed lookup for key
 [show_changelinks] in [{'True': True, 'False': False, 'None': None},}}}

-- 
Ticket URL: 
Django 
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/053.8c1f426156346e3a3f4bfeea3f6fc956%40djangoproject.com.