Skip to content

fix(xreadgroup): dont parse number props - #3133

Merged
nkaradzhov merged 1 commit into
redis:masterfrom
nkaradzhov:xreadgroup-claim-numbers
Nov 19, 2025
Merged

nkaradzhov merged 1 commit into
redis:masterfrom
nkaradzhov:xreadgroup-claim-numbers

Conversation

@nkaradzhov

Copy link
Copy Markdown
Collaborator

Waiting for GA release to be ready

@nkaradzhov
nkaradzhov force-pushed the xreadgroup-claim-numbers branch 2 times, most recently from 9b1d32d to 300646b Compare November 19, 2025 11:37

@jit-ci jit-ci Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ The following Jit checks failed to run:

  • secret-detection-trufflehog
  • static-code-analysis-semgrep-pro

#jit_bypass_commit in this PR to bypass, Jit Admin privileges required.

More info in the Jit platform.

Initially, there was a bug in the server where the two additional props were
returned as string instead of number. This should now be fixed in the GA, so
no need to parse to Number anymore.
@nkaradzhov
nkaradzhov force-pushed the xreadgroup-claim-numbers branch from 300646b to 722d4c0 Compare November 19, 2025 11:54
@nkaradzhov
nkaradzhov marked this pull request as ready for review November 19, 2025 12:16
@nkaradzhov
nkaradzhov merged commit a245ef4 into redis:master Nov 19, 2025
17 checks passed
@nkaradzhov
nkaradzhov deleted the xreadgroup-claim-numbers branch November 19, 2025 12:18
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