Conversation
0xrusowsky
force-pushed
the
daniel/zone-pause-recovery
branch
3 times, most recently
from
September 15, 2026 09:54
36a2c47 to
e1e279f
Compare
0xrusowsky
force-pushed
the
daniel/zone-pause-recovery
branch
from
September 15, 2026 09:57
e1e279f to
abeb1c1
Compare
Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
pull Bot
pushed a commit
to Dustin4444/zones
that referenced
this pull request
Sep 15, 2026
## Summary Foundry's dependency checks block CI in two places: the tracked lockfile points at an old `tempo-std` revision, and Docker copies that lockfile into a source snapshot without the Git metadata needed to validate it. - Align `crates/contracts/foundry.lock` with the existing `tempo-std` submodule revision, `96f882963ce3b0e0abc7ec2b41d03d42457877bb`. - Exclude that lockfile from Docker's build context alongside Git metadata. Docker still compiles the checked-out, pinned submodule sources; regular contract CI continues validating the tracked lockfile against Git. This unblocks contract and Docker builds affecting [tempoxyz#1429](tempoxyz#1429) and [tempoxyz#1443](tempoxyz#1443). ## Validation - Verified both Foundry lockfile entries match their committed submodule revisions. - Reproduced Docker's `fatal: not a git repository` failure with its exact Foundry nightly (`ba4700106baf7c633ec664b27db381a3401cd097`) and a source snapshot without Git metadata. - Excluding the lockfile from that snapshot makes the same `forge build --skip test` command pass (33 Solidity files). - `git diff --check` passed. - Full Docker validation runs in CI; the local sandbox has no Docker daemon. Prompted by: @0xrusowsky --------- Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR makes a finalized Portal pause stop Zone execution without stopping L1 governance.
The producer and followers share the same pause gate: leaders finish at most the in-flight block, followers retain peer blocks without importing them, and neither side signs settlements while paused.
Portal state is initialized before startup and tracked independently of the bounded execution queue. RPC failures fail closed, while
resume()or automatic expiry clears the gate and drains retained work.Settlement retries also reuse a valid anchor until it approaches expiry, giving delayed follower signatures time to reach quorum while still rebuilding and validating the statement against current L1 state.