Skip to content
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

Features/tu async message reset 1 #4804

Merged
merged 4 commits into from
Jan 8, 2025

Conversation

sydhds
Copy link
Contributor

@sydhds sydhds commented Jan 6, 2025

No description provided.

@sydhds sydhds requested a review from Leo-Besancon January 6, 2025 11:02
@sydhds sydhds force-pushed the features/tu_async_message_reset_1 branch from 3047551 to e6d6ec3 Compare January 6, 2025 11:04
Copy link
Collaborator

@Leo-Besancon Leo-Besancon left a comment

Choose a reason for hiding this comment

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

LGTM if the CI passes and the unit-test-srcs repo contains the SC used

Copy link
Collaborator

@Leo-Besancon Leo-Besancon left a comment

Choose a reason for hiding this comment

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

A minor comment, otherwise it's good for me if the CI passes :)

@@ -1143,8 +1143,6 @@ impl Interface for InterfaceImpl {
///
/// # Arguments:
/// data: the string data that is the payload of the event
///
/// [DeprecatedByNewRuntime] Replaced by `get_current_slot`
Copy link
Collaborator

Choose a reason for hiding this comment

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

This is a typo, but still valid info IMO, maybe just replace get_current_slot by generate_event_wasmv1 instead of removing the comment

Copy link
Contributor Author

Choose a reason for hiding this comment

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

wasmv1 is unused so why bother here?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Do what you think is best! I just felt it good to stay consistant (remove it or keep it everywhere), but it's a non issue :)

.set_expectations(|ledger_controller| {
ledger_controller
.expect_get_balance()
.returning(|_| Some(Amount::from_str("200").unwrap()));
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think changing this changed the final state and so changed the generated address

@sydhds sydhds merged commit ce90e00 into mainnet_2_3 Jan 8, 2025
12 checks passed
@sydhds sydhds deleted the features/tu_async_message_reset_1 branch January 8, 2025 09:46
Leo-Besancon pushed a commit that referenced this pull request Jan 17, 2025
* Add send_message_then_reset_bytecode TU

* Code cleanup

* Minor updates

* Update address for sandbox mode
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.

2 participants