This repository has been archived by the owner on Jun 13, 2023. It is now read-only.
Fix not working Fallback Mode when using axios 0.19.0 #15
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
This was referenced Sep 4, 2019
This was referenced Jan 5, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
Since version
0.19.0axios filter out custom properties in config , see axios/axios#164 (comment)It means that
axios-retrycan't store retry number and will try to retry request to Knapsack Pro API infinitely.Because of that Knapsack Pro Fallback Mode never started.
Related:
softonic/axios-retry#89 (comment)
Fix
Workaround for this issue - downgrade to axios
0.18.0Other changes
retryCountnumber for each retried request.3.1.2