Trial run of the finished image against real targets before tagging 1.0 #149

New Issue

2026-09-21T09:18:32+02:00

clawbot commented

2026-09-21 09:18:32 +02:00

Before 1.0 is tagged, someone has to run the finished thing and read what it does. The last such run was in March, before the dashboard, notification retry, shutdown drain and the nameserver failure work existed.

This is a test-and-report task, not a code change. It runs after #104 and #105 are on next.

What to do

Build the image from current next and run it for at least 30 minutes against 10 to 20 real targets (a mix of apex domains and hostnames, including at least one that does not exist and one with a certificate close to expiry if one can be found), with notifications pointed at a local listener you start yourself so every delivery can be read. Use short intervals so several cycles complete. Restart it once in the middle.

Read the whole log and every notification. Check the dashboard and /api/v1/status against what the log says happened.

Definition of done

One comment on this issue: what was run (one line), then only the defects found. Each defect is either fixed by a linked PR or filed as its own issue with a definition of done, full URL given.
If nothing is wrong, the comment is one line saying so.
DNS is never mocked; the run uses live DNS.

Model: fable-5-1

Before 1.0 is tagged, someone has to run the finished thing and read what it does. The last such run was in March, before the dashboard, notification retry, shutdown drain and the nameserver failure work existed. This is a test-and-report task, not a code change. It runs after https://git.eeqj.de/sneak/dnswatcher/issues/104 and https://git.eeqj.de/sneak/dnswatcher/issues/105 are on `next`. ## What to do Build the image from current `next` and run it for at least 30 minutes against 10 to 20 real targets (a mix of apex domains and hostnames, including at least one that does not exist and one with a certificate close to expiry if one can be found), with notifications pointed at a local listener you start yourself so every delivery can be read. Use short intervals so several cycles complete. Restart it once in the middle. Read the whole log and every notification. Check the dashboard and `/api/v1/status` against what the log says happened. ## Definition of done - One comment on this issue: what was run (one line), then only the defects found. Each defect is either fixed by a linked PR or filed as its own issue with a definition of done, full URL given. - If nothing is wrong, the comment is one line saying so. - DNS is never mocked; the run uses live DNS. Model: fable-5-1

clawbot added this to the 1.0 milestone 2026-09-21 09:18:32 +02:00

clawbot referenced this issue

2026-09-21 09:19:29 +02:00

Review toward 1.0: identify and file all next steps #144

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/dnswatcher#149