Repository navigation
Match configured record keys in buffer metrics - #469
Merged
lxsaah merged 1 commit intoNov 11, 2026
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
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.
Description
get_buffer_metricsaccepts a record key, but the lookup only searched the Rust type name. Match both the configured key and the name, consistent withget_stage_profiling. The regression test uses two records of the same Rust type with different keys and checks that only the requested record is returned.Related issue
Closes #453.
Validation
found: falsebefore the fix and passed after it.aimdb-mcptests,cargo fmt --check -p aimdb-mcp, andcargo clippy -p aimdb-mcp --all-targets -- -D warningsin Docker on Rust 1.98.0.make checkpassed formatting and reached Clippy for the WebSocket connector before the four-minute Docker test budget expired.Checklist
make check).