-
Notifications
You must be signed in to change notification settings - Fork 18
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
refactor: move duplicate utils to test utils crate #127
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,6 +6,7 @@ edition = "2021" | |
|
||
[dependencies] | ||
ethportal-api = { git = "https://github.com/ethereum/trin", rev = "2a32224e3c2b0b80bc37c1b692c33016371f197a" } | ||
portal-spec-test-utils-rs = { git = "https://github.com/ethereum/portal-spec-tests", rev = "d1e996d0d4dc2136b3cd38d9e25cdc3a6b74dcd9" } | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm curious, but is storing these constants in a separate repository necessary? Seems to me like we'd like to store them in this repo, to make it easier to add/remove/edit constants, rather than juggling them between multiple repositories. Is there any reason why we couldn't just create a "utils" workspace inside There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @KolbyML I'm still curious about this question There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe we can store it in the simulator folder I will check There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Honestly, I'm using these constants right now in some scripting work I'm doing in trin, so maybe we just store them in |
||
hivesim = { path = "../../../hivesim-rs" } | ||
itertools = "0.10.5" | ||
serde_json = "1.0.87" | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1 @@ | ||
// Execution Layer hard forks https://ethereum.org/en/history/ | ||
pub const SHANGHAI_BLOCK_NUMBER: u64 = 17034870; | ||
pub const MERGE_BLOCK_NUMBER: u64 = 15537394; | ||
pub const LONDON_BLOCK_NUMBER: u64 = 12965000; | ||
pub const BERLIN_BLOCK_NUMBER: u64 = 12244000; | ||
pub const ISTANBUL_BLOCK_NUMBER: u64 = 9069000; | ||
pub const CONSTANTINOPLE_BLOCK_NUMBER: u64 = 7280000; | ||
pub const BYZANTIUM_BLOCK_NUMBER: u64 = 4370000; | ||
pub const HOMESTEAD_BLOCK_NUMBER: u64 = 1150000; | ||
|
||
pub const TEST_DATA_FILE_PATH: &str = "./test-data/test_data_collection_of_forks_blocks.yaml"; |
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.
Why is
portal-hive
tagged to a particular hash ofethportal-api
? If possible I think it's much more preferable to tag to the versionThere 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.
Because ethportal-api has broken in the past and has broken our builds.
Sure that would be a fine change to make in an upcoming PR
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.
I will make an issue for it