reallocate after repeated token fetch failures#19
Merged
Conversation
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
1 participant
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.
This pull request introduces improved error handling for repeated token fetch failures in the
src/api.tsfile and bumps the package version inpackage.json. The main change is to track consecutive token fetch failures and trigger a reallocation if a threshold is reached, improving reliability when the token service is unavailable.Error handling improvements:
tokenFailurescounter andMAX_TOKEN_FAILURESconstant to track consecutive token fetch failures insrc/api.ts. If fetching the token fails five times in a row, the worker logs an error and callsreallocateMeto trigger reallocation. The counter resets on a successful token fetch. [1] [2]Version update:
0.7.1to0.7.2inpackage.jsonto reflect these changes.