Assert not null for databases field #95497
Merged
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.
In this PR we try to fix #95496 by asserting that the field
databases
is not null. This will address the NPE which I believe is caused because it's not fully initialized yet. Changing the NPE to a assertion failure will trigger theassertBusy
to retry until everything is properly initialized.I cannot reproduce it locally, so I am not 100% that there is no other issue with the test, but I believe this is a step forward.
Closes: #95496