Skip to content
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

chore(engine): Migrate To Alloy #241

Merged
merged 4 commits into from
May 1, 2024
Merged

Conversation

refcell
Copy link
Collaborator

@refcell refcell commented Apr 30, 2024

Description

Note

This should be merged after #240

Migrates engine module types to Alloy.

Metadata

Fixes #232

@refcell refcell added A-engine Area: Engine API K-chore Kind: general fixes not relating to a bug M-port Meta: Ports code to new implementations labels Apr 30, 2024
@refcell refcell requested a review from ncitron April 30, 2024 20:21
@refcell refcell self-assigned this Apr 30, 2024
@refcell refcell changed the title chore(engine): Migrate To Ally chore(engine): Migrate To Alloy Apr 30, 2024
@refcell refcell mentioned this pull request Apr 30, 2024
Base automatically changed from refcell/chore/l1-alloy-port to alloy May 1, 2024 09:17
Copy link
Contributor

@ncitron ncitron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Feel free to merge once conflicts are resolved

.map(|log| UserDeposited::try_from(log).unwrap())
.collect::<Vec<UserDeposited>>();

// TODO: Optimize this to batch requests.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just want to note that this should be a high priority. Perf was pretty significantly effected by not batching these when I was first testing it out.

Copy link
Collaborator Author

@refcell refcell May 1, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was fortunately mistaken here - the alloy_rpc_types::Log does contain the hydrated block information, which is the object returned by the provider's get_logs method. I had confused this with the alloy_primitives::Log type. Fixing it right now and will push the fix :)

@refcell refcell force-pushed the refcell/chore/engine-alloy-port branch from ca41e5a to 783b18f Compare May 1, 2024 14:19
@refcell refcell merged commit eb829a9 into alloy May 1, 2024
5 checks passed
@refcell refcell deleted the refcell/chore/engine-alloy-port branch May 1, 2024 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-engine Area: Engine API K-chore Kind: general fixes not relating to a bug M-port Meta: Ports code to new implementations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants