Skip to content

Vanrossem integration: dep bumps + stubs#3

Open
Jimbo4350 wants to merge 6 commits into
masterfrom
jmillar/vanrossem-integration
Open

Vanrossem integration: dep bumps + stubs#3
Jimbo4350 wants to merge 6 commits into
masterfrom
jmillar/vanrossem-integration

Conversation

@Jimbo4350
Copy link
Copy Markdown

Summary

  • Bumps deps for cardano-node 11.0 (ouroboros-network 1.1, ouroboros-consensus 3.0.1, cardano-ledger-conway >= 1.22.1).
  • Gets the branch compiling on top of the new ledger / network APIs by stubbing call sites that hit removed/restructured upstream APIs. Every stub is tagged TODO vanrossem for follow-up.

Mechanical (no behavior change):

  • Transaction.hs: switch to Ledger.Tx Ledger.TopTx <Era> (new TxLevel kind on Tx); getTransactionId now uses Ledger.txIdTx @<Era> directly.
  • Cardano.hs: Ledger.fromTxSeq txstxs ^. Ledger.txSeqBlockBodyL.

Stubbed (revisit before merging to master):

  • Script.hsLedger.Alonzo.TimelockScript constructor removed; all native-script paths + mkBinaryPlutusScript (era kind change) stubbed.
  • Metadata.hstranslateAlonzoTxAuxData / upgradeTxAuxData removed; fromAlonzoMetadata / fromBabbageMetadata stubbed.
  • Point.hsouroboros-network now ships an overlapping ToJSON (Point block) instance; local instance removed. JSON output shape needs verification.
  • MonadOuroboros.hsOuroboros.Network.NodeToClient no longer exists in ouroboros-network 1.1; broken imports stripped, NodeToClientVersion kept as a local placeholder, withChainSyncServer body is error "TODO".
  • Hydra.hsdecodePartialTransaction fails with a TODO (new TxLevel parameter made the decCBOR call ambiguous).

Test plan

  • cabal build all -j4 — green locally (lib + test + exe link).
  • Resolve each TODO vanrossem against the new cardano-ledger / ouroboros-network APIs.
  • Address -Wincomplete-patterns in Kupo.Data.Cardano.foldBlock (production build uses -Werror).
  • Run unit tests.

@Jimbo4350 Jimbo4350 force-pushed the jmillar/vanrossem-integration branch from e55ebb7 to 9eab27d Compare May 27, 2026 21:44
@Jimbo4350 Jimbo4350 force-pushed the jmillar/vanrossem-integration branch from 9eab27d to e0a078c Compare May 27, 2026 21:47
@Jimbo4350 Jimbo4350 force-pushed the jmillar/vanrossem-integration branch 3 times, most recently from 3666e00 to 39c71f6 Compare May 29, 2026 02:08
Jimbo4350 added 3 commits May 29, 2026 16:37
Open the listening socket ourselves (with SO_REUSEADDR) and close it in a
bracket around Warp.runSettingsSocket rather than letting Warp.runSettings
manage it. The close then runs on every exit path, including async cancel,
so the port is freed before the next e2e stage rebinds it; fixes intermittent
EADDRINUSE when kupo is restarted on the same port.
Set managerIdleConnectionCount = 0 so each request opens a fresh connection.
The e2e tests restart kupo on the same port between stages, and reusing a
connection pooled from the previous instance caused intermittent failures.
…anager

Same fix as the e2e manager (managerIdleConnectionCount = 0) so the
state-machine suite never reuses a connection pooled from a prior kupo
instance on the same port.
@Jimbo4350 Jimbo4350 force-pushed the jmillar/vanrossem-integration branch from 49f043e to c2a5b09 Compare May 29, 2026 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant