Skip to content

[pull] main from django:main - #544

Merged
pull[bot] merged 2 commits into
threatcode:mainfrom
django:main
Aug 27, 2026
Merged

pull[bot] merged 2 commits into
threatcode:mainfrom
django:main

Conversation

@pull

@pull pull Bot commented Aug 27, 2026 •

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

viralpraxis and others added 2 commits August 27, 2026 08:52
Many (~70) tests assert a specific row order for querysets whose SQL has no
ORDER BY. SQL standard does not define that order.

On PostgreSQL the rows usually arrive in physical storage order, which
on a freshly loaded table matches insertion order -- so these assertions
pass by coincidence rather than by contract. That breaks when rows are
updated or deleted and the space is reused, or when the planner picks a
different access path such as an index scan. A test like this can start
failing with no change to Django or to the test itself.

The patch made sure that most of these tests do not
rely on unspecified unordered selection order.
…ror.

The fallback TypeError raised by path() and re_path() for an invalid view
did not report the received type, unlike the neighboring errors for an
invalid kwargs argument or a class-based view instance.
@pull pull Bot locked and limited conversation to collaborators Aug 27, 2026
@pull pull Bot added the ⤵️ pull label Aug 27, 2026
@pull
pull Bot merged commit fdfbb71 into threatcode:main Aug 27, 2026
17 of 18 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants