Skip to content

fix(client): expose MEMORY STATS fields added in Redis 7.4 - #3416

Open
abhijeet117 wants to merge 1 commit into
redis:masterfrom
abhijeet117:fix/memory-stats-reply-fields
Open

fix(client): expose MEMORY STATS fields added in Redis 7.4#3416
abhijeet117 wants to merge 1 commit into
redis:masterfrom
abhijeet117:fix/memory-stats-reply-fields

Conversation

@abhijeet117

@abhijeet117 abhijeet117 commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Summary

Redis 7.4 added four top-level fields to MEMORY STATS: overhead.db.hashtable.lut, overhead.db.hashtable.rehashing, db.dict.rehashing.count and allocator.muzzy (object.c emits each via addReplyBulkCString + addReplyLongLong). MemoryStatsReply did not declare them, so consumers needed casts to reach these values. They are now typed as numbers in server reply order, following the existing added-in comments convention.

Testing

Compile-time regression test indexes all four fields on the client-facing reply type; it fails on master with TS7053 and passes after the fix. Verified against Redis 7.4 source; parser spec, type tests, build and lint run locally; Docker-backed integration tests run in CI.

Checklist

  • bug reproduced before fix
  • root cause identified
  • bug fixed
  • tests passed

@PavelPashov

Copy link
Copy Markdown
Contributor

@abhijeet117 Thanks for the PR. We’ll review it when we have capacity.

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