Repository navigation
fix(test): box large execute_tool_call future - #437
Merged
Merged
Conversation
Dependency bumps in the release PR grow the execute_tool_call future past clippy's large_futures threshold, failing lint under -D warnings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The release PR (#426) bumps dependencies (e.g. rmcp 1.8 → 1.9) in
Cargo.lock, which grows theexecute_tool_callfuture intesty.rsto 16,440 bytes. That tripsclippy::large_futures(viaclippy::pedantic) and fails the Lint job under-D warnings.This boxes the future as clippy suggests.
Verified locally with #426's
Cargo.lock: the warning reproduces without this change, andcargo clippy/cargo clippy --all-targets --all-featuresare clean with it.🤖 Generated with Claude Code