feat: Improve error handling and logging in Redis worker #31
Conversation
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
- Downgrade specific Redis errors to info level logging - Handle 'BUSYGROUP Consumer Group name already exists' as informational message
laojianzi
changed the title
fetchTask method
appleboy
added a commit
that referenced
this pull request
Aug 23, 2025
- Add handling for Redis 'no message' errors in fetchTask - Log a specific info message when no messages are available, then continue retrying fix #31 Signed-off-by: appleboy <[email protected]>
appleboy
added a commit
that referenced
this pull request
Aug 23, 2025
- Add handling for Redis 'no message' errors in fetchTask - Log a specific info message when no messages are available, then continue retrying fix #31 Signed-off-by: appleboy <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have a minor suggestion: when the stream has no messages, perhaps it's better not to continuously output error logs. This could help reduce unnecessary log clutter. What are your thoughts on this?