StreamGroupInfo.Lag can be null #2902
Merged
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
mgravell
approved these changes
Jul 21, 2025
make tests async
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.
In the special case where consumer group lag is unavailable XINFO GROUPS lag is reported as null from redis.
The Lag property on StreamGroupInfo is long?, so the type is correct.
StreamGroupInfoProcessor.ParseItem parses the value as a long and defaults to 0 not null
This is a bug-fix on that issue, it does contain some code duplication, but that is probably just my skill level.
Make some tests for this, probably not in the right place but that is how it is.