mathiasandClaude Opus 5.5 52d4bfeeab fix(symlinkguard): flush on handoff and at shutdown; test the handoff ...

PR #180 review (BLOCK) found that moving delivery out of the scan left
two problems:
- An alert waited for deliver's own tick, about one interval. It is
  now flushed as soon as it is handed over, and on each tick after
  that while it is still pending.
- On ctx end deliver returned without draining, so an alert handed over
  just before shutdown was lost even with a healthy ntfy. Watch now
  closes the handoff channel, and deliver drains it and flushes once
  more (bounded by shutdownFlushTimeout) before Watch returns.

The review also showed the tests didn't cover the handoff. The new
tests are each flip-tested red:
- the lifetime test uses a notifier slower than the interval, so a
  blocking handoff fails it
- the overflow-accounting test uses a slow notifier
- a join test checks that Notify is no longer running when Watch
  returns
- a shutdown-flush test, and a prompt-delivery test

Refs #164

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-05 09:45:15 +02:00

..

cmd

test(ingestion): OIDC discovery 502s then 200 against a real issuer (#83)

2026-10-05 06:57:45 +02:00

internal

fix(symlinkguard): flush on handoff and at shutdown; test the handoff

2026-10-05 09:45:15 +02:00

Dockerfile

fix(ci): allow ingestion Dockerfile to fetch internal gitea modules

2026-05-22 12:12:09 +02:00

go.mod

fix(deps): bump x/net and x/text past called vulns

2026-10-05 06:59:31 +02:00

go.sum

fix(deps): bump x/net and x/text past called vulns

2026-10-05 06:59:31 +02:00