amesgen
amesgen
@karknu asked whether we could have metrics/counters in the node for interesting Genesis events, for example when ChainSel was starved and when the CSJ dynamo got rotated (currently, these two...
In various common scenarios, the mempool will (re)apply a tx to a ledger state that does not contain all of the necessary inputs (usually because the tx has already been...
In order to construct a `Summary` (which is used to create the `EpochInfo` that is passed to the ledger) from a ledger state, we use `reconstructSummary` (see its call sites):...
On current `main` (44d8867c33102766a6b30e6f6a75e3b0b136d5e7): ```console $ cabal run byron-test -- --quickcheck-replay="(SMGen 3815441042141447428 1971304436672976329,3)" -p '/simple convergence/' Node CoreId (CoreNodeId 0)'s ImmutableDB is leaking file handles 1 /= 0 ``` This...
Also see https://github.com/google/double-conversion/commit/8857767d5b2f5a035321e3712e8cd0008840ba6b Tests also pass fine Happy to add a corresponding CI job if desired
While putting #196 together I noticed this comment: https://github.com/input-output-hk/io-sim/blob/785dc08aec5f08e112ee3a98a2203ce56b47d8e6/io-sim/src/Control/Monad/IOSim/STM.hs#L156-L160 Is this actually true for the code here? This doesn't look like a lazy pattern match to me; forcing the first...
Since https://github.com/IntersectMBO/ouroboros-consensus/pull/1175, the Mempool needs to be able to run all size-related checks (tx byte size, execution units, ref scripts) separately from (namely before) regular tx validation. Currently, this logic...
Not a priority for now, but opening a PR to have a reference Relies on the fact that boosted points all lie on the same chain (which is not true...
Currently, the node always creates snapshots in the format corresponding to the chosen LedgerDB backend, ie in-memory (V2) or LMDB, with lsm-tree replacing LMDB in the near future. It would...