Skip to content

docs(client): document new memory_report() fields from #1273 - #511

Merged
jlucaso1 merged 2 commits into
mainfrom
claude/nifty-bohr-x73nah
Aug 11, 2026
Merged

docs(client): document new memory_report() fields from #1273#511
jlucaso1 merged 2 commits into
mainfrom
claude/nifty-bohr-x73nah

Conversation

@jlucaso1

@jlucaso1 jlucaso1 commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Documents four new MemoryReport fields added in oxidezap/whatsapp-rust#1273: inbound_commit_batch, msg_secret_buffer, pending_device_sync, and app_state_key_cache.
  • Notes the new --- Transient retention --- section that Display now prints for the three transient-retention fields, alongside the existing --- In-flight history sync --- section.

Context

PR #1273 was a per-client retention/cache-bounds audit (no bounds changed, no behavior changed) but it did extend Client::memory_report()'s public output so memory_report() could see the largest transient allocation a client holds (the inbound commit batch, up to 4 MiB of decoded protos) plus two other previously-unreported collections. This PR updates api/client.mdx's memory_report field table and Display description to match.

Everything else in #1273 (an internal agent_docs/observability.md audit narrative, new characterization tests, a measurement harness) is engineering-internal and has no separate public-doc surface, so it isn't mirrored here.

Test plan

  • Docs build (mint dev / mint broken-links) — not run in this session; please verify in CI or locally.
  • New field descriptions cross-checked against the PR's diff of src/client.rs, src/client/accessors.rs, and wacore/src/appstate_sync.rs.

Generated by Claude Code


Summary by cubic

Updates api/client.mdx to document four new MemoryReport fields—inbound_commit_batch, msg_secret_buffer, pending_device_sync, and app_state_key_cache—and note the new --- Transient retention --- section in Display output.
Clarifies that inbound_commit_batch is only the largest allocation under default cache sizes (others like history_sync_tasks can exceed it) and that pending_device_sync counts dedup-set entries, not queued work; aligns docs with oxidezap/whatsapp-rust#1273.

Written for commit fce8a05. Summary will update on new commits.

Adds inbound_commit_batch, msg_secret_buffer, pending_device_sync, and
app_state_key_cache to the memory_report() field table, and notes the
new Transient retention section in the Display output.

Ref: oxidezap/whatsapp-rust#1273
@mintlify

mintlify Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
whatsapp-rust 🟢 Ready View Preview Aug 10, 2026, 11:58 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jlucaso1, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 22 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 191e453a-bf1d-4cd9-87c4-be8f7620c70e

📥 Commits

Reviewing files that changed from the base of the PR and between 20d2b5f and fce8a05.

📒 Files selected for processing (1)
  • api/client.mdx

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5f76790438

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread api/client.mdx Outdated
Comment thread api/client.mdx Outdated
Comment thread api/client.mdx Outdated
Inbound_commit_batch's "largest allocation" claim now notes it holds
only under default cache sizing (enlarged history_sync_tasks or other
cache capacity can exceed it). pending_device_sync's description now
makes clear a nonzero count is dedup-set membership, not necessarily a
refresh still queued -- an online-path entry outlives its own refresh
until the next offline drain or teardown removes it.

Addresses review feedback from #511.
@jlucaso1
jlucaso1 merged commit 91954a0 into main Aug 11, 2026
3 checks passed
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.

1 participant