-
Notifications
You must be signed in to change notification settings - Fork 135
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: Remove our implementation of NodeId #1070
Conversation
8ba2045
to
6f35b69
Compare
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.
🚢 Looks good to me! For some reason, I assumed that there would be a lot more changes as a result of this update, but it seems to me like you've covered everything here. One note, is to just update the pr description to "closes #869"
so that the issue will be automatically closed once this pr is merged. Thanks!
I was thinking about that, but decided not to do it because bug also says:
Is that something that should be done as part of this pr before merging (and how?), or something to be done once it's merged (but before closing the bug)? |
@morph-dev Ahh, good catch. Have you run it against portal-hive locally? I'd recommend doing that before merging this pr. Of course, if we go ahead with the merge, we will soon find out if it passes portal-hive, but I think it's better to confirm that it passes portal-hive locally before merging this through |
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.
🥳
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.
LGTM 👍
Which portal-hive tests should I run? I think I ran all of them, and these are the result:
This is similar but slightly worse than results at https://portal-hive.ethdevops.io/. |
Which clients did you run and which tests failed in portal-interop between what clients |
If the test includes ultralight you can ignore it and we are good to merge if it comes up for tests which are trin/fluffy that is concerning |
In second run I used this command: ./hive --sim portal-interop --client fluffy,ultralight,trin These tests failed: |
This is good to merge then |
Wait actually nvm I will look into it more |
What is the fail reason given for GOSSIP blocks from A:trin --> B:fluffy? |
"173": {
"name": "GOSSIP blocks from A:trin --\u003e B:fluffy",
"description": "",
"start": "2023-12-14T16:51:56.389867412+02:00",
"end": "2023-12-14T16:52:11.282737476+02:00",
"summaryResult": {
"pass": false,
"details": "Client B: [\"Error content for block 17510000 (post-shanghai) block body was absent\", \"Error content for block 17510000 (post-shanghai) receipt was absent\"]"
},
"clientInfo": {
"00343e15": {
"id": "00343e15",
"ip": "172.17.0.5",
"name": "fluffy",
"instantiatedAt": "2023-12-14T16:51:57.480046961+02:00",
"logFile": "fluffy/client-00343e15735ccbba69fbeeb4dad3a78139e0d04e06b50603d7a61f54623448c2.log"
},
"d1ebef78": {
"id": "d1ebef78",
"ip": "172.17.0.4",
"name": "trin",
"instantiatedAt": "2023-12-14T16:51:56.87565928+02:00",
"logFile": "trin/client-d1ebef78a56260c20092203a8e2af0f5857024b0e5064cc6a91f8eae656e15dc.log"
}
}
}, |
Ok yeah this looks good to merge we are increasing the timeout in the PR I am waiting to merge on Portal-Hive. |
What was wrong?
We have our own implementation of NodeId, which is no longer needed (see #869)
Closes #869.