fix: do not retry on 501 #197
Merged
Conversation
This file contains 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
The other SDK cores skip retry for 501, so the Node core should behave the same way.
|
@padamstx What happened to Travis? |
We are working on it, not sure what happened, but updates when we have them. |
padamstx
force-pushed
the
update-retry-config
branch
from
a20e5e8 to
abad001
Compare
pyrooka
force-pushed
the
update-retry-config
branch
from
66f76f8 to
903e649
Compare
ibm-devx-sdk
pushed a commit
that referenced
this pull request
May 2, 2022
## [2.17.14](v2.17.13...v2.17.14) (2022-05-02) ### Bug Fixes * do not retry on 501 ([#197](#197)) ([5cb9081](5cb9081))
|
🎉 This PR is included in version 2.17.14 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
The other SDK cores skip retry for
501,so the Node core should behave the same way.
Checklist
npm testpasses (tip:npm run lint-fixcan correct most style issues)