Merge pull request #5362 from IntersectMBO/mw/fix-targets-sync
Fix initial syncing targets
Fix initial syncing targets
This patch ensures that when a node starts syncing from scratch in bootstrap peers mode that it has only up to 2 active connections to bootstrap relays. Co-authored-by: coot <[email protected]>
Various small changes
Fixed #5346
Clairify LedgerPeersConsensusInterface.
Adds `pkgs.releaseTools.aggregate` derivations so all components in a given sub-group can be built with a single command: nix build .\#hydraJobs.x86_64-linux.x86_64-w64-mingw32.all nix build .\#hydraJobs.x86_64-linux.ghc982.all nix build .\#hydraJobs.x86_64-linux.all nix build .\#hydraJobs.aarch64-darwin.all Sub-groups (cross-compilation targets and compiler variants) are detected by checking that their values contain nested attrsets rather than derivations directly, which distinguishes them from the native job categories (packages, checks, …). Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Fixed #5346
Add a new constructor to `TraceTxSubmissionInbound` to record when txids are announced by a peer, carrying the list of txids and the absolute time of receipt. This enables consumers to reconstruct the peer metric state from the trace (matching announced txids against later mempool submission results) and to model time-window expiry correctly. Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Updated comments and added type signatures in `Governor.Monitor.connections` - it makes it easier to track where `RepromoteDelay` is coming from.`
add scoreAcceptDecrement which rewards peers that deliver TXs that gets accepted. Reduce scoreRate to a slow trickle Ensure that the delay penalty stings by mapping it to between 10ms and interTxSpace for any peer with a positive score.
tx-submission demo
connection-manager: added a comment in includeInboundConnectionImpl
Local socket access right warnings
No semantic changes: avoid `>=>`, or use `<$>` instead of `>>=`.
Add basic counter test. Add property that check for leaks in shared state.
No semantic changes: avoid `>=>`, or use `<$>` instead of `>>=`.