Rotorsoft / act-root
100%

DEFAULT BRANCH: master
Repo Added
Files 117
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH master
branch: master
CHANGE BRANCH
x

coverage: 100.0%. Remained the same
33339638071

push

github

web-flow 
fix(act-pg): exclude the boundary event from created_after (#1603)

Postgres stores `created` at microsecond resolution but hands back a JS
Date, which carries milliseconds. A row stamped ...976999 reads back as
...976, so `created > '...976'` compared the row against its own
timestamp and returned it. InMemory and SQLite both exclude it, so
Postgres was the odd one out, and the documented "scan since last time"
pattern re-delivered the boundary event there and nowhere else. With a
limit it returned the wrong event rather than one extra.

Millisecond is the resolution the contract is expressed in, since that is
all a Date carries, so strictly-after means "at least the next
millisecond". Advancing the bound rather than truncating the column fixes
rows already written at microsecond precision, needs no table rewrite on
an events table, and keeps the comparison a plain range scan on
(created, id).

The store TCK gains the case that would have caught it: both bounds must
exclude the event they are pinned to. Its existing window case is built
as `ts ± 60_000`, so no bound ever landed on an event's own timestamp.
Verified the new case fails on Postgres without this fix and passes on
InMemory and SQLite unchanged.

Closes #1595


Claude-Session: https://claude.ai/code/session_014Vfpx1bDy3t57oHBynvNPF

Co-authored-by: rotorsoft <rotorsoft@outlook.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

4332 of 4332 branches covered (100.0%)

Branch coverage included in aggregate %.

10 of 10 new or added lines in 2 files covered. (100.0%)

9302 of 9302 relevant lines covered (100.0%)

1178.88 hits per line

Relevant lines Covered
9302 RELEVANT LINES 9302 COVERED LINES
1178.88 HITS PER LINE
Source Files on master

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
33339638071 master fix(act-pg): exclude the boundary event from created_after (#1603) Postgres stores `created` at microsecond resolution but hands back a JS Date, which carries milliseconds. A row stamped ...976999 reads back as ...976, so `created > '...976'` com... push web-flow github
100.0
33339147622 master fix(act): revive dates on read instead of re-validating the payload (#1601) * fix(act): revive dates on read instead of re-validating the payload Reading an event ran a throwing z.parse() over its data whenever the schema mentioned a date. All t... push web-flow github
100.0
33276871839 master fix(act): don't quarantine a stream while the database is failing (ACT-1592) (#1593) * fix(act): refund claims a store failure spent, not the handler's retry budget `claim` persists `retry = retry + 1` before any handler runs, and only a confirm... push web-flow github
100.0
33274414677 master fix(act): keep static reaction targets out of the subscribed LRU (ACT-1582) (#1588) * fix(act): keep static reaction targets out of the subscribed LRU A static target is recorded at a +Infinity priority floor so the dynamic resolver path can nev... push web-flow github
100.0
33273496848 master docs(act): one store belongs to one application (#1590) Two Acts built from different registries over one store silently lose reactions: correlation keeps one shared read cursor, and a correlator key with no row of its own is seeded from it, so t... push web-flow github
100.0
33273395274 master fix(act): key the dynamic-lane reports on the declaration, not the target (#1587) `report_once` exists so one misdeclaration costs one log line, but two of its three callers built the key from the resolved target. The documented per-aggregate sha... push web-flow github
100.0
33106512168 master fix(act): normalize the lane name on both sides of the agreement guard (#1586) Two reactions to the same target must declare the same lane, and the build-time guard stored the raw declaration to compare later ones against. An omitted lane and an ... push web-flow github
100.0
33077769791 master fix(act): warn instead of error on self-healing failures (#1580) Error-level logs are routinely wired to paging, and six sites reported events that lose nothing and recover on their own — so healthy operation paged someone. Four are fire-and-for... push web-flow github
100.0
33075268786 master fix(act): explain a failed correlation-lease handback instead of logging it raw (#1578) * fix(act): explain a failed correlation-lease handback instead of logging it raw The handback is best-effort — the lease carries its own expiry, so failing ... push web-flow github
100.0
32896299477 master fix(act): apply the lane guards to dynamic resolutions (#1575) * fix(act): apply the lane guards to dynamic resolutions A build-time guard only ever sees a static `.to({lane})` — a `.to(fn)` lane is a function until an event arrives — so both la... push web-flow github
100.0
See All Builds (1159)