Skip to content

Conversation

rlycx
Copy link
Contributor

@rlycx rlycx commented Oct 16, 2025

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.

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.
@rlycx rlycx requested a review from Qqwy October 16, 2025 12:39
Copy link
Contributor

@Qqwy Qqwy left a 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants