feat: accept pre-fetch-hooks and url-patterns for queuing#8
Merged
Conversation
paras-fundwave
force-pushed
the
pre-fetch-hooks
branch
from
676d324 to
d1cb27f
Compare
rickygarg
reviewed
Oct 18, 2024
paras-fundwave
force-pushed
the
pre-fetch-hooks
branch
from
b5b252e to
298ef91
Compare
rickygarg
approved these changes
Oct 22, 2024
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
3 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.
Description
The package currently dumps all the incoming calls to the queue and if some calls take too long to process due to concurrency limit, the following calls are executed with stale headers/body (content).
This was observed causing failures due to expired tokens in authorisation-headers.
Also, having control over what get's queued to limit the affect was a requested feature, so implemented that too.
Resolutions
Depends on
Deployment
Current pipelines will suffice