-
Notifications
You must be signed in to change notification settings - Fork 9
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
Special evm height handling #645
Special evm height handling #645
Conversation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
@m-Peter I'm not sure how to tests this, but as far as I can see there is already a test for it in |
@@ -82,6 +82,7 @@ const coaFundingBalance = minFlowBalance - 1 | |||
|
|||
const LatestBlockHeight uint64 = math.MaxUint64 - 1 | |||
|
|||
// TODO(janezp): Requester does need to know about special EVM block heights. evmHeight should be uint64. |
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.
That's a good remark 👌
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! 💯
@janezpodhostnik This is generally tested throughout the various E2E test scenarios, so no need for further tests I would say. It's good to go 👍 |
Description
Extracted from #635
I think the API should translate the special heights to actual heights before forwarding to the requester.
For contributor use:
master
branchFiles changed
in the Github PR explorer