added a retry mechanic to PostJsonHelper to avoid 400 error issues#130
Merged
added a retry mechanic to PostJsonHelper to avoid 400 error issues#130
Conversation
aslisabanci
previously approved these changes
Aug 3, 2022
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.
In some instances, the
/compileandpublishendpoints may fail with a 400 error if interacted with too quickly or based off of the order of operations in a stateful operation. In order to get around this quickly, this fix simply allows for thepublishandcompileendpoints to retry once, which may fix some state problems that affect user use cases. Not a long term solution, but should work for the moment.