fix typo: reword synch to sync
Home /
Input Output /
hydra
Nov 17, 3-4 PM (0)
Nov 17, 4-5 PM (0)
Nov 17, 5-6 PM (0)
Nov 17, 6-7 PM (0)
Nov 17, 7-8 PM (0)
Nov 17, 8-9 PM (0)
Nov 17, 9-10 PM (0)
Nov 17, 10-11 PM (0)
Nov 17, 11-12 AM (0)
Nov 18, 12-1 AM (0)
Nov 18, 1-2 AM (0)
Nov 18, 2-3 AM (0)
Nov 18, 3-4 AM (0)
Nov 18, 4-5 AM (0)
Nov 18, 5-6 AM (0)
Nov 18, 6-7 AM (0)
Nov 18, 7-8 AM (0)
Nov 18, 8-9 AM (0)
Nov 18, 9-10 AM (0)
Nov 18, 10-11 AM (0)
Nov 18, 11-12 PM (0)
Nov 18, 12-1 PM (0)
Nov 18, 1-2 PM (0)
Nov 18, 2-3 PM (0)
Nov 18, 3-4 PM (0)
Nov 18, 4-5 PM (0)
Nov 18, 5-6 PM (0)
Nov 18, 6-7 PM (0)
Nov 18, 7-8 PM (0)
Nov 18, 8-9 PM (0)
Nov 18, 9-10 PM (0)
Nov 18, 10-11 PM (0)
Nov 18, 11-12 AM (0)
Nov 19, 12-1 AM (0)
Nov 19, 1-2 AM (0)
Nov 19, 2-3 AM (0)
Nov 19, 3-4 AM (0)
Nov 19, 4-5 AM (0)
Nov 19, 5-6 AM (0)
Nov 19, 6-7 AM (0)
Nov 19, 7-8 AM (0)
Nov 19, 8-9 AM (0)
Nov 19, 9-10 AM (0)
Nov 19, 10-11 AM (0)
Nov 19, 11-12 PM (0)
Nov 19, 12-1 PM (0)
Nov 19, 1-2 PM (0)
Nov 19, 2-3 PM (0)
Nov 19, 3-4 PM (0)
Nov 19, 4-5 PM (0)
Nov 19, 5-6 PM (0)
Nov 19, 6-7 PM (0)
Nov 19, 7-8 PM (0)
Nov 19, 8-9 PM (0)
Nov 19, 9-10 PM (0)
Nov 19, 10-11 PM (0)
Nov 19, 11-12 AM (0)
Nov 20, 12-1 AM (0)
Nov 20, 1-2 AM (0)
Nov 20, 2-3 AM (0)
Nov 20, 3-4 AM (0)
Nov 20, 4-5 AM (0)
Nov 20, 5-6 AM (0)
Nov 20, 6-7 AM (0)
Nov 20, 7-8 AM (0)
Nov 20, 8-9 AM (0)
Nov 20, 9-10 AM (1)
Nov 20, 10-11 AM (0)
Nov 20, 11-12 PM (0)
Nov 20, 12-1 PM (0)
Nov 20, 1-2 PM (0)
Nov 20, 2-3 PM (0)
Nov 20, 3-4 PM (0)
Nov 20, 4-5 PM (0)
Nov 20, 5-6 PM (0)
Nov 20, 6-7 PM (0)
Nov 20, 7-8 PM (0)
Nov 20, 8-9 PM (0)
Nov 20, 9-10 PM (0)
Nov 20, 10-11 PM (0)
Nov 20, 11-12 AM (0)
Nov 21, 12-1 AM (0)
Nov 21, 1-2 AM (0)
Nov 21, 2-3 AM (0)
Nov 21, 3-4 AM (1)
Nov 21, 4-5 AM (0)
Nov 21, 5-6 AM (0)
Nov 21, 6-7 AM (0)
Nov 21, 7-8 AM (0)
Nov 21, 8-9 AM (0)
Nov 21, 9-10 AM (0)
Nov 21, 10-11 AM (0)
Nov 21, 11-12 PM (0)
Nov 21, 12-1 PM (0)
Nov 21, 1-2 PM (0)
Nov 21, 2-3 PM (0)
Nov 21, 3-4 PM (0)
Nov 21, 4-5 PM (0)
Nov 21, 5-6 PM (0)
Nov 21, 6-7 PM (0)
Nov 21, 7-8 PM (0)
Nov 21, 8-9 PM (0)
Nov 21, 9-10 PM (0)
Nov 21, 10-11 PM (0)
Nov 21, 11-12 AM (0)
Nov 22, 12-1 AM (0)
Nov 22, 1-2 AM (0)
Nov 22, 2-3 AM (0)
Nov 22, 3-4 AM (1)
Nov 22, 4-5 AM (0)
Nov 22, 5-6 AM (0)
Nov 22, 6-7 AM (0)
Nov 22, 7-8 AM (0)
Nov 22, 8-9 AM (0)
Nov 22, 9-10 AM (0)
Nov 22, 10-11 AM (0)
Nov 22, 11-12 PM (0)
Nov 22, 12-1 PM (0)
Nov 22, 1-2 PM (0)
Nov 22, 2-3 PM (0)
Nov 22, 3-4 PM (0)
Nov 22, 4-5 PM (0)
Nov 22, 5-6 PM (0)
Nov 22, 6-7 PM (0)
Nov 22, 7-8 PM (0)
Nov 22, 8-9 PM (0)
Nov 22, 9-10 PM (0)
Nov 22, 10-11 PM (0)
Nov 22, 11-12 AM (0)
Nov 23, 12-1 AM (0)
Nov 23, 1-2 AM (0)
Nov 23, 2-3 AM (0)
Nov 23, 3-4 AM (0)
Nov 23, 4-5 AM (0)
Nov 23, 5-6 AM (0)
Nov 23, 6-7 AM (0)
Nov 23, 7-8 AM (0)
Nov 23, 8-9 AM (0)
Nov 23, 9-10 AM (0)
Nov 23, 10-11 AM (0)
Nov 23, 11-12 PM (0)
Nov 23, 12-1 PM (0)
Nov 23, 1-2 PM (0)
Nov 23, 2-3 PM (0)
Nov 23, 3-4 PM (0)
Nov 23, 4-5 PM (0)
Nov 23, 5-6 PM (0)
Nov 23, 6-7 PM (0)
Nov 23, 7-8 PM (0)
Nov 23, 8-9 PM (0)
Nov 23, 9-10 PM (0)
Nov 23, 10-11 PM (0)
Nov 23, 11-12 AM (0)
Nov 24, 12-1 AM (0)
Nov 24, 1-2 AM (0)
Nov 24, 2-3 AM (0)
Nov 24, 3-4 AM (0)
Nov 24, 4-5 AM (0)
Nov 24, 5-6 AM (0)
Nov 24, 6-7 AM (0)
Nov 24, 7-8 AM (0)
Nov 24, 8-9 AM (35)
Nov 24, 9-10 AM (0)
Nov 24, 10-11 AM (0)
Nov 24, 11-12 PM (0)
Nov 24, 12-1 PM (0)
Nov 24, 1-2 PM (0)
Nov 24, 2-3 PM (2)
Nov 24, 3-4 PM (0)
40 commits this week
Nov 17, 2025
-
Nov 24, 2025
fix flaky e2e spec: do not wait for node synced as it reconnects fast enough and it never becomes unsynced
Deploying to gh-pages from @ cardano-scaling/hydra@83f795ef3193ef1f35fb9d1867c7fc71ffa1d91e 🚀
handle node synced status in visualize logs module
add haddock to the offline chain tick producer
document new synchronization polciy
fix flaky e2e specs
> by waiting for node to be synced before submitting new txs
fix: adjust e2e assertion delays to prevent node from becoming unsynced when sending new txs
fix e2e specs for node state now initializing in catching up
by waiting for the node to be in sync before: - waiting for nodes to be connected - sending init client input
tune waiting time in scenario based on how long it takes to sync
init node state as catching up
clean up review comment
> as it is safe to use OverloadedRecordDot with sum types
fix: e2e scenario
> by refactoring the cluster connection to node using different delay depending on backend (blockfrost/direct)
fix: make tui to compile
add node state synced status transition property
update tui to handle new server outputs and client message
fix: golden spec files
refactor: introduce synced status type
wait on network inputs while node is catching up
> ignoring network messages during catch-up could result in unsigned in-flight snapshots, as etcd would still consider them delivered.
fix: make hydra-node compile
> this allow tests to run with failures
track current slot also while node state is catching up
remove known tip from tick, tick observed and node state
Add NodeUnsynced and NodeSynced types
define unsynced policy based on cp
> use it to refine the e2e scenario
do not reject inputs in api layer
> they already rejected by the logic