Documentation

Assert that a notification is AcquiredEb with the expected point.

Assert that a notification is AcquiredEbTxs with the expected point.

Run tests for each database implementation.

Generate a LeiosEb with the given number of transactions.

Generate a random EbHash (32 random bytes). With 256 bits of randomness, collisions are practically impossible.

Generate a random LeiosPoint.

Generate a LeiosPoint and LeiosEb together with the given number of transactions.

Generate a random RbHash (32 random bytes). With 256 bits of randomness, collisions are practically impossible.

Generate a random SlotNo.

Generate random max sized tx (16k).

Generate a random TxHash (32 random bytes).

Max sized tx (16k) with all zeros.

Create a test LeiosEb with the given number of transactions.

Create a simple test EbHash from a seed byte.

Create the test groups for a given database implementation.

Create a test LeiosPoint.

Create a simple test TxHash from a seed byte.

Property: complete EB (all txs inserted) returns Just with correct tx data.

Property: EB with body but no txs returns Nothing.

Property: EB with only a point announced (no body) returns Nothing.

Property: EB with partial txs (at least one missing) returns Nothing.

Property: inserting an EB body and looking it up returns the correct txs.

Property: looking up a non-existent EB returns empty list.

Property: multiple inserted points all appear in scan results.

Property: inserting a point and then scanning should return it.

Property: inserting tx bytes and retrieving them returns the correct data. With the normalized schema, txs are inserted into a global txs table by TxHash, and retrieval JOINs with that table.

Property: retrieving from non-existent EB returns empty list.

Names of the tables and indexes in a database file.

A dummy announcing RB hash for DB tests that don't care about its value.

Test that the notification contains the correct AcquiredEb data.

Test that a subscriber who subscribes after an insertion does not receive the past notification.

Test that multiple insertions yield multiple notifications in order.

The same EB content can be forged at multiple slots; the DB must track each LeiosPoint independently and emit one AcquiredEbTxs per (slot, hash) when the closure completes, regardless of how many slots reference the same hash. Conflating the slots loses a notification.

Test that multiple subscribers each receive the notification.

Test that no AcquiredEbTxs notification is produced when only some transactions have been inserted via rwInsertTxs.

Test that completed EBs are not re-notified when subsequent unrelated transactions are inserted.

Re-inserting a tx that is _referenced_ by an already-completed EB must not re-fire AcquiredEbTxs. This is the practical case where the previous 'no re-notification' check (which only used an unrelated tx) lets a bug through: the completion predicate any (\e -> eteTxHash e `elem` insertedTxHashes) matches again on any subsequent batch containing an EB-referenced tx, since the 'all txs present' clause remains true once the EB is complete. The voting layer treats the duplicate AcquiredEbTxs as a fatal AlreadyKnown from addVote.

Test that a AcquiredEbTxs notification is produced when all transactions are inserted via rwInsertTxs.

Test that a single subscriber receives a notification when rwInsertEbBody is called.

The immutable schema lacks the volatile-only tables; the tooling that DBTruncater runs on both files must still work on it.

A file that exists without a schema, as a crash between creating the file and applying the schema leaves it.

Convert DiffTime to a bucket label.

Measure the time of an IO action and return the result with DiffTime.

Create a fresh database and run an action with it. Ensures proper cleanup for SQLite databases.

Create a fresh SQLite database and hand its paths to the action, which truncateLeiosDbAfterSlot needs. The database is torn down -- writes flushed, threads stopped, connections closed -- before the directory is removed; a still-open connection makes the removal flaky (a hard failure on Windows, where deleting an open WAL is a sharing violation).

Paths for both partition files in a fresh temporary directory, which is removed afterwards. Nothing is created at the paths.

Database creation strategy for different implementations.

A reader and a writer onto the same database -- what every caller outside these tests now holds, since reads and writes no longer share a connection.