fix(utxorpc): address ai review
Signed-off-by: cryptodj413 <[email protected]>
Signed-off-by: cryptodj413 <[email protected]>
A lower bound on microlens was introduced.
Includes a couple of hacks to flake.nix to force happy < 2.2.1.
CHaP index-state was 2026-02-09 but cardano-node 10.6.3 requires 2026-03-28. Update CHaP to 2026-04-07 and haskell.nix/hackage/stackage to latest.
The new `ConformanceTest` record contains fields for all data formerly used to run a test via `forAllGenesisTest` helper, plus other fields that adjust its evaluation as a test property on a`TestTree`. It is worth noting that a `GenesisTest` is more general than what its name suggests; it is the type representing the "Node-vs-Environment" or point schedule tests. All such `ConformanceTest`s are arranged in `TestSuite`s, a data structure introduced with the goal of eventually exporting them as part of a new sublibrary for the [Conformance Testing of Consensus](https://github.com/tweag/cardano-conformance-testing-of-consensus) (CTC) harness. This data structure is designed to optimize single test lookups, while retaining the necessary structure to be compiled back to a `TestTree`, in such a way that the introduced changes preserve the semantics of the `ouroboros-consensus:test:consensus-diffusion-test` test suite. Those, `TestSuite`s lay out an interface between the internal property test execution and the up-coming CTC harness. To accomplish this, a new `TestKey` data type is introduced in each module as a `key` for the locally defined `TestSuite`, such that each test in the module corresponds to a unique value (nullary constructor) of this type. This means that including a new test in a `TestSuite` requires the extension of `TestKey` by e.g. introducing a new data constructor. These `TestKey` types are aggregated into higher level key types (sums of other test key unary constructors) to reify the nested grouping of the original tasty `TestTree`s by combining them using `mkTestSuite`. The new `SmallKey` constraint is morally equivalent to `Universe.Class.Finite` from the `universe-base` package, but includes a set of measures to prevent *large* finite types from instantiating it. The reason for this is that its `allKeys` method is used for the exhaustive construction of `TestSuite`s via `newTestSuite` and `mkTestSuite`; as implemented, a `TestSuite` is a total map.
- cardano-node: 10.5.4 → 10.6.3 (latest stable, 2026-04-01) - cardano-node-pre: add 10.7.0 pre-release as separate input/output - cardano-cli: 10.3.0.0 → 10.15.1.0 (latest) The 10.7.0 pre-release builds are output as cardano-tools-pre-* alongside the stable cardano-tools-* builds.
Signed-off-by: cryptodj413 <[email protected]>
A lower bound on microlens was introduced.
Includes a couple of hacks to flake.nix to force happy < 2.2.1.
A lower bound on microlens was introduced.
Before version 0.5 of microlens, an Internal module was being used. Now we switch to a module that is explicitly part of the microlens API.
Includes a hack to flake.nix to force happy < 2.2.1.
Update `slack-github-action` configuration for v2 onward
This commit adds a missing strictness annotation in the PerasVotingView record. Co-authored-by: Nicolas BACQUEY <[email protected]> Co-authored-by: Thomas BAGREL <[email protected]> Co-authored-by: Agustin Mista <[email protected]>
This commit implements a model-based test suite for the Peras certificate inclusion rules. This follows the same approach used to test the Peras voting rules. Co-authored-by: Nicolas BACQUEY <[email protected]> Co-authored-by: Thomas BAGREL <[email protected]> Co-authored-by: Agustin Mista <[email protected]>
This commit adds a new PerasCertMaxRounds to the PerasParams record. This parameter is used to decide if a Peras certificate is still valid when considering it for inclusion in a block body. Co-authored-by: Nicolas BACQUEY <[email protected]> Co-authored-by: Thomas BAGREL <[email protected]> Co-authored-by: Agustin Mista <[email protected]>
This commit implements the Peras certficate inclusion rules using the boolean predicate DSL used for the Peras voting rules. This logic is used to decide whether a certificate (the latest one seen) needs to be added to a block body, typically to orchestrate the beginning and end of a cooldown period. Co-authored-by: Nicolas BACQUEY <[email protected]> Co-authored-by: Thomas BAGREL <[email protected]> Co-authored-by: Agustin Mista <[email protected]>
Signed-off-by: Ritesh Pandit <[email protected]>
Before version 0.5 of microlens, an Internal module was being used. Now we switch to a module that is explicitly part of the microlens API.