fix: correctly parse migration poll response; use dict not Response a… - #2739
Open
reachsridhard wants to merge 4 commits into
Open
fix: correctly parse migration poll response; use dict not Response a…#2739reachsridhard wants to merge 4 commits into
reachsridhard wants to merge 4 commits into
Conversation
…nd robust key checks
Author
|
@m1n0 Could you please take another look when you have a chance? I’d appreciate your feedback and review. Thanks for your time! |
|
Author
|
@Niels-b , Could you please take another look when you have a chance? |
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
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.



Description
Responsevsdictand an incorrect logical condition in SodaCloud.migration_poll_status() when parsing the migration status response from Soda Cloud.response["migration"](treating theResponseobject as a dict) and used anandcondition that could let through malformed JSON. This could cause runtime errors or incorrect polling behavior.Problem being solved
"state" not in response["migration"]instead of using the parsedresponse_body_dict.andinstead ofor, which could allow the code to proceed even when keys were missing.Expected impact on downstream packages/services
Changes
response_body_dict(the parsed JSON dict).orso that any missing key is treated as a parse failure.response_body_dictis notNonebefore checking keys.Before (problematic):