Repository navigation
Chainweb Revolution - #49
Open
edmundnoble wants to merge 467 commits into
Open
edmundnoble wants to merge 467 commits into
edmundnoble wants to merge 467 commits into
Conversation
Change-Id: Id000000003df0e6228643907b06fda6e13d2dea2
Change-Id: Id00000001b24cc3d269cffcf1b3a67d230747c18
Change-Id: Id000000056296ea25046e7a8b9b001e84c259047
Change-Id: Id0000000ed99ccb169d20e1c82392d7caeaebc07
Change-Id: Id00000004fff1e1eabf1711fa760fc3322b5c6d2
This reverts commit 11d5a11.
Change-Id: Id0000000d4951d048a44b5125ed5989baa634712
Change-Id: Id00000004bbbaefabb706f8ce15ce299b916598c
Change-Id: Id0000000b7c10bea6c1dd66d95c2bcba718a2e52
Change-Id: Id0000000cdc2ae11e7d1dd855f4a9d31f7a8262d
Change-Id: Id0000000faf6a22224ec34917461fad9062c07bd
The old code was not safe; the thread could be lost and not stopped in theory, if PactService was interrupted. Change-Id: Id00000001a7bf815abbbedd23159bd9c11a2bd00
…ntain permissions' Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
The cabal-cache sync step fails intermittently (e.g. S3 access issues), aborting otherwise healthy builds. Mark it continue-on-error so builds proceed from source when the remote cache is unavailable.
The macos-latest runners fail to link with: ld: tapi error: malformed file ... MacOSX27.0.sdk ... unknown architecture arm64e.x1-macos because clang and ld are picked from mismatched toolchains. Probe both xcode-select locations and keep the one that can actually link.
The macOS workflow still pointed at the upstream kadena-cabal-cache bucket with the upstream secret names, so the cache sync failed with exit code 1 on this fork. Point it at community-kda-cabal-cache with the kda_community_* secrets, matching applications.yml.
Make the SPV proof fork error message version-aware via chainweb231Pact, matching master's forkedError. Since the SPV proof expiration window was introduced at the Chainweb231Pact fork, the message now reads 'target header is not in the chain or is out of bounds' for post-231 blocks instead of just 'target header is not in the chain'. This threads the current block height and a HasVersion constraint into checkProofAndExtractOutput and its callers in both the Pact 4 and Pact 5 SPV support, since this branch's HeaderOracle only carries the chain id.
--------- Co-authored-by: KadenaFriend <241389759+kdafriend@users.noreply.github.com>
Updated permissions to allow write access to contents and added a step to generate and commit a freeze file if it doesn't exist. Adjusted conditions for various jobs to always run.
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 includes:
PactService, with automatic migration from the previous version. This comes with a drastic simplification of the data flow between consensus and Pact, which should make future Pact development easier.There's much more to say about the EVM payload provider, but it will require more testing and updating to bring to mainnet, not to mention operational challenges that come with multi-process coordination and changes to the build.