Skip to content

Conversation

@DSharifi
Copy link
Contributor

closes #1185

@DSharifi DSharifi self-assigned this Sep 25, 2025
@DSharifi DSharifi linked an issue Sep 25, 2025 that may be closed by this pull request
@DSharifi DSharifi marked this pull request as ready for review September 25, 2025 18:31
Copy link
Collaborator

@netrome netrome left a comment

Choose a reason for hiding this comment

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

Nice stuff!

Copy link
Contributor

@kevindeforth kevindeforth left a comment

Choose a reason for hiding this comment

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

Thank you.
I would like to see some more state added before the migration call (at least what we have in the pytest we are about to delete, but even better if we were to resolve #415 with this PR)

Copy link
Contributor

@kevindeforth kevindeforth left a comment

Choose a reason for hiding this comment

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

I think there are still a few details to work out s.t. we don't lose test coverage compared to the pytests.

Copy link
Contributor

@kevindeforth kevindeforth left a comment

Choose a reason for hiding this comment

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

Thanks for all the work. I think we are getting close to merge, but there are still a few things we need to look at.

Hard blockers for me right now are the following:

  • concerning large key event timeout #1186 (comment)
  • use of DomainId::legacy_ecdsa_id() in non-backwards compatibility tests #1186 (comment)
  • slight regression testing the upgrade functionality of the current contract #1186 (comment)

Ok(())
}

pub async fn sign_and_validate(
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice refactor, I like that we are breaking the logic out into smaller, re-usable functions!
Could we add a doc comment for this function?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This function already existed before. Seems like the diff is getting messed up because of re-ordering. Feel free to create an issue to document.

Copy link
Contributor

Choose a reason for hiding this comment

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

Feel free to create an issue to document.

I think the effort of opening an issue and following it with a PR is not justified for a doc comment that could be added as a broken-window fix.

But this was never a blocker for this PR, so, if you are happy without the comment, we don't need one.

) -> anyhow::Result<()> {
let status = submit_sign_request(request, contract).await?;

tokio::time::sleep(std::time::Duration::from_secs(3)).await;
Copy link
Contributor

Choose a reason for hiding this comment

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

Out of scope for this PR, but could we open an issue to get rid of this sleep?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, feel free to create cone.

@DSharifi
Copy link
Contributor Author

Thank for the very in depth review. I believe all these hard blockers have been addressed now.

395126c

  • use of DomainId::legacy_ecdsa_id() in non-backwards compatibility tests #1186 (comment)

b23d8e8

  • slight regression testing the upgrade functionality of the current contract #1186 (comment)

9209917

Copy link
Contributor

@kevindeforth kevindeforth left a comment

Choose a reason for hiding this comment

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

Thanks!

Ok(())
}

pub async fn sign_and_validate(
Copy link
Contributor

Choose a reason for hiding this comment

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

Feel free to create an issue to document.

I think the effort of opening an issue and following it with a PR is not justified for a doc comment that could be added as a broken-window fix.

But this was never a blocker for this PR, so, if you are happy without the comment, we don't need one.

@DSharifi DSharifi added this pull request to the merge queue Sep 29, 2025
Merged via the queue into main with commit aa93413 Sep 29, 2025
9 checks passed
@DSharifi DSharifi deleted the 1185-rewrite-test_update_to_current-as-a-sandbox-integration-tests branch September 29, 2025 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rewrite test_update_to_current as a sandbox integration tests

4 participants