-
Notifications
You must be signed in to change notification settings - Fork 584
Port compatible+develop to mesa - 2026.1.23 #18345
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
base: mesa
Are you sure you want to change the base?
Conversation
…g up magic config to testnet-generic debian
…inance patch binance archive issue - release/3.3.0
…own when resovling GQL schema
…config.net_config
This change only adds Deferred to the signature of the method that will populate a root ledger from a genesis ledger.
This method works like a checkpoint, but does not throw an exception if the source and destination backings are different. It will instead ensure that the backing at the destination is what is requested, by migrating the primary database at the destination or avoiding checkpointing the migrated database.
The daemon no longer expects that the genesis ledgers have the same backing as the root ledger; if they differ, either the stable genesis ledger database will be copied and migrated at the destination (if the root ledger should have a converting backing), or the migrated genesis ledger database will not be copied (if the root ledger should have a stable backing).
This change lets us avoid keeping migrated genesis ledger databases around on disk. This does require the daemon to migrate these ledgers whenever it wants to bootstrap from genesis, but this operation should be very infrequent (usually happening at most once during startup, and only if the frontier on disk is sufficiently behind the network).
- added --redirect-to-logs option, so output from nodes are not polluting console output
|
!ci-build-me |
[CI] Fix writing to cache
Pickles: document interface of Impl, with some design choice decisions
…ial-snarked-ledgers-compatible Resolve merge conflicts in 18284 - compatible
|
!ci-build-me |
1 similar comment
|
!ci-build-me |
Pickles: document interface of step
…sly migrate_from_berkeley) be identity function, remove bunch of test that doesn't make sense on mesa
|
!ci-build-me |
|
I think we might want some eyes from @cjjdespres on 106423b as I'm removing tests he implemented here. |
|
This PR should be merged after #18352 is merged so to retain the branching rules. |
|
It's interesting to see this PR needs all those reviewers. I thought we don't have a branch protection rule on |
| } | ||
|
|
||
| (* This function converts Berkeley account to Mesa account *) | ||
| let migrate_from_berkeley ~hardfork_slot (account : Stable.Latest.t) : t = |
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.
I renamed this to migrate_from_berkeley -> migrate_to_mesa because the original name only make sense if we're working on a berkeley branch.
| ; permissions = account.permissions | ||
| ; zkapp = Option.map ~f:Zkapp_account.Hardfork.to_stable_exn account.zkapp | ||
| (* This function converts current account to Mesa account *) | ||
| let migrate_to_mesa ~hardfork_slot:_ |
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.
This is just Fn.id now we've on a mesa branch.
| type t = Zkapp_basic.F.Stable.V1.t V.t | ||
| [@@deriving sexp, equal, hash, compare, yojson, bin_io_unversioned] | ||
|
|
||
| let of_stable (value : Value.Stable.Latest.t) : t = |
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.
I don't think these functions matter any more.
|
!ci-build-me |
|
!ci-build-me |
|
Apparantly CI being green here is a false-positive. Don't merge. |
as title