Repository navigation
Allow maxlag to be explicitly configured instead of hardcoded - #128
Merged
CXuesong merged 1 commit intoOct 12, 2026
Merged
Conversation
The maxlag parameter is explicitly set on _some_ API calls, but the value is hardcoded to 5 seconds. This change introduces a configuration option in SiteOptions to set maxlag on all API calls.
CXuesong
force-pushed
the
feature/configurable-maxlag
branch
from
October 12, 2026 16:09
8a06701 to
69b6683
Compare
Owner
|
Thanks for the PR! I merged the change but it may take a while before I revamp the failing unit test cases and release a new package. |
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 maxlag parameter is explicitly set on some API calls, but the value is hardcoded to 5 seconds.
This change introduces a configuration option in SiteOptions to set maxlag on all API calls.