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

fix: explicitly expect one message in timelock execute_execute_proposal #ntrn-129 #96

Merged
merged 5 commits into from
Nov 3, 2023

Conversation

NeverHappened
Copy link
Contributor

@NeverHappened NeverHappened self-assigned this Oct 25, 2023
@NeverHappened
Copy link
Contributor Author

NeverHappened commented Oct 25, 2023

@NeverHappened NeverHappened force-pushed the fix/explicitly-take-one-message-in-timelock branch from 2a0bbd7 to 590a736 Compare October 25, 2023 13:44
@NeverHappened
Copy link
Contributor Author

…fy check for execute_timelock_proposal as well
@NeverHappened
Copy link
Contributor Author

NeverHappened commented Nov 1, 2023

@NeverHappened NeverHappened changed the base branch from main to feat/rust-optimizer-0.14.0 November 1, 2023 15:04
@NeverHappened
Copy link
Contributor Author

@pr0n00gler pr0n00gler changed the base branch from feat/rust-optimizer-0.14.0 to main November 3, 2023 10:23
@pr0n00gler pr0n00gler merged commit 09d3f67 into main Nov 3, 2023
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.

3 participants