Merge pull request #500 from cardano-foundation/fix/496-channel-close-continuation
fix(channel): require close-init continuation
fix(channel): require close-init continuation
ci(gateway): publish container image
Signed-off-by: Eric Torreborre <[email protected]>
Switch to unsafe vector indexing
chore(electron): upgrade from 24.2.0 to 41.3.0
- Elab.hs: fix copy-paste error in binary arithmetic op elab (rhs hole was unified against lhsTy instead of rhsTy); rename evalBinaryArithmethicOpElabProblem to evalBinaryArithmeticOpElabProblem (typo) - Elab.hs: elaborate `metrics` as List Text (was Text); add Str elab case - Elab/Typing.hs, Resolve.hs, Unify.hs: add List Ty to support metrics type - Interp.hs: guard avg/min/max against empty instant vector; fix rate to error on single-point timeseries instead of dividing by zero - Interp/Value.hs: use showFFloat in Show instance for Scalar to avoid scientific notation in JSON output - TimeseriesServer.hs: fix minimumRetentionMillis units (seconds → ms); remove unused RecordWildCards pragma; align sleep delay with Monitoring.hs - Acceptors/Utils.hs: align new imports with surrounding import block
The crate's job has been "the Balius-owned wire schema", but the name "balius-proto" advertised protobuf as the only thing it carries. `balius-core` is a roomier name for what is really the foundational types crate for the runtime <-> WASM interface — protobuf today, more things possibly later. The schema module also gets nested: `balius_proto::cardano` becomes `balius_core::proto::v0::cardano`. The `v0` segment makes the versioning explicit: this schema is wire-compatible with utxorpc-spec 0.17 by construction (the entire point of this PR), so it is frozen for pre-BigInt worker compat. A future breaking change to the schema goes under `proto::v1`, leaving `v0` consumers untouched. Mechanical changes: - Crate dir balius-proto/ -> balius-core/ - Package name -> balius-core; description updated - src/cardano.rs -> src/proto/v0/cardano.rs (plus new mod.rs files) - Workspace member + all 3 dependent Cargo.tomls updated (balius-runtime, balius-sdk, examples/asteria-tracker) - Import paths: balius_proto::cardano -> balius_core::proto::v0::cardano across balius-sdk, balius-runtime, examples/asteria-tracker - Doc/comment references updated No behavior change. cargo check --workspace --tests clean; 2/2 wire-compat tests in balius-core; 9/9 lib tests in balius-runtime (incl. all 8 u5c convert tests); e2e::faucet_claim still passes; only the pre-existing u5c-chainsync::wallet_balance stale-wasm failure remains. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
This allows more control on the dependency between jobs to ensure that the snapshot tests start as soon as possible (since they're the longest), while other jobs are spread between the remaining workflows. Signed-off-by: KtorZ <[email protected]>
Signed-off-by: KtorZ <[email protected]>
This somehow messes up with MacOS; and it's anyway unnecessary for both MacOS and Windows. We only install extra tools on Linux, so that's only where this becomes useful. Signed-off-by: KtorZ <[email protected]>