fix(ci, signer-aws): increase recursion limit to fix error: queries overflow the depth limit!#3633
Merged
zerosnacks merged 4 commits intomainfrom Feb 2, 2026
Merged
Conversation
error: queries overflow the depth limit!
|
= help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`alloy_signer_aws`)
= note: query depth increased by 130 when computing layout of `{async block@crates/signer-aws/src/signer.rs:120:5: 120:23}`
error: queries overflow the depth limit!error: queries overflow the depth limit!
error: queries overflow the depth limit!error: queries overflow the depth limit!
onbjerg
approved these changes
Feb 2, 2026
onbjerg
reviewed
Feb 2, 2026
…oy into zerosnacks/fix-clippy-issue
3 tasks
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.
Motivation
Fixes CI issue:
This is breaking downstream CI's as
aws-*is pinned to major. I have not fully looked into why this is happening, I can't find reports on the respective repo.To repro:
Solution
Bumps to
#![recursion_limit = "256"]PR Checklist