Fix flushInterval in context module #272
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
|
@knolleary while you are at it can you fix line 23 which picks the large or 0 or the (configured value || 30) which means it can be configured to less than 30, which I don't think we want. |
|
@hardillb it works as desired. If
I assume it was done like this to prevent negative values being applied. |
|
Hmm, OK. Still think 30 should be the minimum, but won't hold this up. |
hardillb
approved these changes
Aug 5, 2024
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 context module was not honouring the flushInterval - instead, every write to context was triggering a flush.
This ensure the module picks up the flushInterval (default 30s) properly.