-
Notifications
You must be signed in to change notification settings - Fork 1
Clarify consumer log message when chunk reservation expired #18
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
Conversation
The original message was a "todo"/future idea from when opsqueue was more actively being developed. It has a high severity and it sounds actionable to users reading the logs, whereas there isn't really any way they can change the handling. This is a little misleading, so this commit changes the message to be clearer about what's going on.
Qqwy
left a comment
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.
Good change 👍
One thing you could consider however, is whether this should be turned into a debug notice or be kept on info. Since if this message is printed, it is quite likely that the chunk size is too large in a particular usage scenario.
Up to you!
|
@OpsBotPrime merge |
|
Rebased as 54f9dd9, waiting for CI … |
Approved-by: rlycx Priority: Normal Auto-deploy: false
|
CI job 🟡 started. |
|
The build failed ❌. If this is the result of a flaky test, then tag me again with the |
|
@OpsBotPrime retry |
Approved-by: rlycx Priority: Normal Auto-deploy: false
|
Rebased as 156f0b9, waiting for CI … |
|
CI job 🟡 started. |
The original message was a "todo"/future idea from when opsqueue was more actively being developed. It has a high severity (error level) and it sounds actionable to users reading the logs, whereas there isn't really any way they can change the handling (because that's deep opsqueue magic). This commit changes the message to be clearer about what's going on.