-
Notifications
You must be signed in to change notification settings - Fork 177
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
Implement starknet_getMessageStatus #2184
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2184 +/- ##
==========================================
- Coverage 75.40% 75.29% -0.11%
==========================================
Files 106 107 +1
Lines 11237 11392 +155
==========================================
+ Hits 8473 8578 +105
- Misses 2128 2166 +38
- Partials 636 648 +12 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
235811c
to
7322767
Compare
d31039e
to
4f6fd6d
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.
Just one question
8ebd0b7
to
8020f6a
Compare
3d9de48
to
907ce49
Compare
fix hash function and tests lint lint
ff047a5
to
e16cab2
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.
I think there is some repetition around the ethereum client which can be removed.
With regards to migration, it is going to be quite large (@kirugan) and since this has to do with Hashing, it can potentially take quite some time (I would expect it to take several hours) but it will be faster than resyncing the whole chain.
I would prefer to sync from scratch and create a new snapshot so we can avoid adding this migration (if we have time). The rpc may be down if this is not planned well, as an upgrade would block Juno until the migration is complete which cannot stopped.
Co-authored-by: Aneeque <[email protected]> Signed-off-by: Rian Hughes <[email protected]>
The user chooses not to provide eth node therefore they are expected to understand the consequences. Also, there is already an error message is someone tries to request `starknet_getMessageStatus` without providing an eth-node.
Since it is only used in one place there is no need to have a variable for it.
The above changes LGTM |
Signed-off-by: Kirill <[email protected]>
closes #2178