-
Notifications
You must be signed in to change notification settings - Fork 152
[EASY] Use unbuffered alloy provider #3843
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
# Conflicts: # crates/autopilot/src/database/onchain_order_events/ethflow_events.rs # crates/autopilot/src/run.rs # crates/cow-amm/src/registry.rs # crates/shared/src/event_handling.rs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR modifies the web3() function to conditionally choose between buffered and unbuffered Alloy providers based on the configuration. The key change is moving the Alloy provider creation inside the match statement to align with the legacy transport's buffering configuration.
- Restructured provider initialization to use different Alloy providers based on buffering configuration
- Moved Alloy provider creation from after the transport setup to inside the buffering match statement
- Updated variable naming from
transporttolegacyfor clarity
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Description
The following function uses unbuffered legacy web3 transport, while for Alloy it uses a regular provider. This PR fixes that.
services/crates/autopilot/src/run.rs
Lines 106 to 117 in 7fbb222
How to test
N/A