mysql: check for error when getting subtrees #3173
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.
treeTX.getSubtrees iterates over a set of rows from
database/sql
, but it was failing to check the error status after exiting the for loop that iterates over them.On our log deployment (Let's Encrypt Oak), this is causing mistaken error messages of
preload did not get all tiles
when the real error should be propagated from mysql (in our case, max_statement_time exceeded).We're in the middle of trying to remediate a significant availability from for get-sth-consistency, and getting this landed and deployed would help eliminate a source of noise in our investigation.