-
Notifications
You must be signed in to change notification settings - Fork 54
fix(dapi): getStatus cache invalidation #2155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
10c5832
fix(dapi): getStatus cache invalidation
shumkov 5c3b4fa
Merge branch 'v1.4-dev' into fix/dapi/get-status-cache
QuantumExplorer 3c3fedd
fix: potential double cache cleanup
shumkov c62880e
chore: enchance logging
shumkov f345597
test: update BlockchainListener test
shumkov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potential for multiple timeouts—ensure a single scheduled cache cleanup
Each time
getStatusHandlergenerates a newcachedResponse, a newcleanCacheTimeoutis set without clearing any existing timeout. This could lead to multiple timeouts running concurrently, causing redundant executions ofcleanCache.To prevent multiple scheduled timeouts, clear any existing timeout before setting a new one:
Committable suggestion
🛠️ Refactor suggestion
Consider using 'setInterval' for consistent cache cleanup
Using
setIntervalcan simplify the cache cleanup mechanism by consistently invalidating the cache every three minutes, regardless of cache usage patterns.Implement
setIntervalto schedule regular cache cleanups:Modify the
cleanCachefunction to retain the interval:function cleanCache() { cachedResponse = null; - // cancel scheduled cache cleanup - if (cleanCacheTimeout !== null) { - clearTimeout(cleanCacheTimeout); - cleanCacheTimeout = null; - } logger.trace({ endpoint: 'getStatus' }, 'cleanup cache'); }This approach ensures the cache is invalidated regularly without the need to manage timeouts manually.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rabbit misunderstood logic. We cleanup cache by block or in 3 mintues after it was generated by a user request. Interval doesn't work for our case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shumkov, thank you for the clarification. I apologize for the misunderstanding. I now understand that the cache is cleaned up by block or in 3 minutes after it was generated by a user request, so using an interval doesn't fit your requirements.
(・・?)
✏️ Learnings added