Avoid side effect error in setting error handling #15295
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
This made it really hard to debug issues related to connecting to the database.
Locally, using docker-compose, I put in these settings:
These settings were wrong. But the message I got was:
This is a problematic error... yes, it has the real error buried down in there, but that's not what I want it to give.
With this change:
And it still gave me shell_plus.
Several commands are required to work without database access like
collectstatic
, and what's surprising is that this didn't break someone. I expect that's because those commands were never run while getting this type of error, which leads to a secondary error that stops execution when that is not the expectation.ISSUE TYPE
COMPONENT NAME