CTM-256: use correct time interval when pausing Quicksilver correction monitor#3546
Open
CTM-256: use correct time interval when pausing Quicksilver correction monitor#3546
Conversation
davidangb
requested review from
rjohanek and
snf2ye
and removed request for
a team
davidangb
commented
Jan 12, 2026
| if (config.continueWhenDone) { | ||
| logger.info(s"pausing ${config.completionInterval.toString()} before checking for updated corrections ...") | ||
| context.system.scheduler.scheduleOnce(config.startupDelay, self, CountOutstanding) | ||
| context.system.scheduler.scheduleOnce(config.completionInterval, self, CountOutstanding) |
Contributor
Author
There was a problem hiding this comment.
you can see from the logger.info line which config setting this should be using
davidangb
requested review from
calypsomatic
and removed request for
rjohanek
calypsomatic
approved these changes
Jan 13, 2026
snf2ye
approved these changes
Jan 13, 2026
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.
Ticket: CTM-256
Use the correct time interval (4 hours) when pausing the Quicksilver correction monitor.
I mistakenly used the startup delay (5 minutes) instead.
This has no functional impact; it just causes the monitor to check for newly-available corrections much more frequently than intended.