fix(cron): handle whitespace-only responses (#28151)#28352
Merged
Conversation
Contributor
🔎 Lint report:
|
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Salvage of #28151 by @joe102084.
What: Cron jobs that returned whitespace-only final responses (
" \n\t ") were delivered as blank messages and recorded as successful runs. The empty-response soft-failure guard checkednot final_response(truthy) instead ofnot final_response.strip().How: Strip before both the delivery decision and the soft-failure marker so whitespace-only output is treated the same as empty output. Test added covering the regression.
Original PR: #28151