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!

@rlycx
Copy link
Contributor Author

rlycx commented Oct 23, 2025

@OpsBotPrime merge

@OpsBotPrime
Copy link
Contributor

Rebased as 54f9dd9, waiting for CI …

OpsBotPrime added a commit that referenced this pull request Oct 23, 2025
Approved-by: rlycx
Priority: Normal
Auto-deploy: false
@OpsBotPrime
Copy link
Contributor

CI job 🟡 started.

@OpsBotPrime
Copy link
Contributor

The build failed ❌.

If this is the result of a flaky test, then tag me again with the retry command. Otherwise, push a new commit and tag me again.

@rlycx
Copy link
Contributor Author

rlycx commented Oct 23, 2025

@OpsBotPrime retry

Approved-by: rlycx
Priority: Normal
Auto-deploy: false
@OpsBotPrime
Copy link
Contributor

Rebased as 156f0b9, waiting for CI …

@OpsBotPrime
Copy link
Contributor

CI job 🟡 started.

@OpsBotPrime OpsBotPrime merged commit 156f0b9 into master Oct 23, 2025
5 of 7 checks passed
@rlycx rlycx deleted the rly/fix-misleading-error branch October 23, 2025 12:46
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.

3 participants