-
Notifications
You must be signed in to change notification settings - Fork 0
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: halt-height behavior is not deterministic #305
Conversation
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.
Please add a note in the PR description stating whether we should abandon this change in favor of the cherry-pick source once we upgrade to that point.
CHANGELOG.md
Outdated
@@ -37,6 +37,8 @@ Ref: https://keepachangelog.com/en/1.0.0/ | |||
|
|||
## [Unreleased] | |||
|
|||
* (baseapp) [#305](https://github.com/agoric-labs/cosmos-sdk/pull/305) Make sure we don't execute blocks beyond the halt height. |
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.
Move this to CHANGELOG-Agoric.md
- creating it if #306 doesn't land first.
(Moving our changes to a separate file makes it easier to merge changes from cosmos.)
Also, note that it's a backport of cosmos#16639. This will also make future merges easier.
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.
Done, but I'll wait until #306 merges first.
Port of cosmos#16639 Co-authored-by: yihuang <huang@crypto.com>
a7b31b8
to
762e033
Compare
The backport referenced above has the agd process hang around after halting. Wrote a wrapper utility which scans stderr for the halt application message, interrupts the process, then propagates its error signal. Conventional shell scripting is not up to the challenge of expressing this behavior.
This reverts commit 7b8423a. This commit caused test failures in agoric-sdk. Reverting to land other changes in agoric-sdk. We'll restore the change and try to debug the failure against a smaller diff in the future.
…#305" This reverts commit efcc3b0. We decided to roll back the problematic change (agoric-labs/cosmos-sdk#305).
The backport referenced above has the agd process hang around after halting. Wrote a wrapper utility which scans stderr for the halt application message, interrupts the process, then propagates its error signal. Conventional shell scripting is not up to the challenge of expressing this behavior.
…#305" This reverts commit efcc3b0. We decided to roll back the problematic change (agoric-labs/cosmos-sdk#305).
The backport referenced above has the agd process hang around after halting. Wrote a wrapper utility which scans stderr for the halt application message, interrupts the process, then propagates its error signal. Conventional shell scripting is not up to the challenge of expressing this behavior.
…#305" This reverts commit efcc3b0. We decided to roll back the problematic change (agoric-labs/cosmos-sdk#305).
The backport referenced above has the agd process hang around after halting. Wrote a wrapper utility which scans stderr for the halt application message, interrupts the process, then propagates its error signal. Conventional shell scripting is not up to the challenge of expressing this behavior.
…#305" This reverts commit efcc3b0. We decided to roll back the problematic change (agoric-labs/cosmos-sdk#305).
Port of cosmos#16639 Co-authored-by: yihuang <huang@crypto.com>
Port of cosmos#16639 Co-authored-by: yihuang <huang@crypto.com>
Port of cosmos#16639 Co-authored-by: yihuang <huang@crypto.com>
Description
Refs: Agoric/agoric-sdk#8326
Port (cherry-pick with modifications) of cosmos#16639
Adapt by using
BeginBlock
andpanic
, similar to the adaptation in crypto-org-chain/chain-main#998Adapted the Unit test as well
Once we reach the version of cosmos-sdk (v0.50) with the
FinalizeBlock
semantics (CometBFT v0.38), we can adopt the upstream change more directly.Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change