If the batch operation fails, fall back to individual#358
Merged
Conversation
Contributor
|
It'd be cool if a 404/410 response (indicating that the server doesn't even try to implement this) could turn off the |
Contributor
There was a problem hiding this comment.
Why is this declared inside the function like this?
Contributor
Author
There was a problem hiding this comment.
Because it's not needed outside the function.
rubyist
added a commit
that referenced
this pull request
Jun 15, 2015
If the batch operation fails, fall back to individual
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.
The batch endpoint is still "experimental" and a server may not yet support it. It is off by default in the client, but if gets turned on it should fall back to individual processing if the batch processing throws an error.