With DNSWATCHER_SEND_TEST_NOTIFICATION=true, the startup notification ends "All notification channels are working." The message is written once and handed to every endpoint at the same moment, before any delivery has succeeded or failed, so the claim is never checked. In the run, the Mattermost endpoint refused its first delivery of the startup notification while the Slack and ntfy copies said every channel was working. An endpoint that is misconfigured for good never receives the message, and every other endpoint is told all is well.
To see it, set two endpoints, point one at a URL that answers 404, and start dnswatcher. The message is built in maybeSendTestNotification in internal/watcher/watcher.go.
Definition of done
The startup notification says only what is known when it is sent, for example that it is a test sent to every configured endpoint, and claims nothing about whether the endpoints work.
The test of the startup notification checks the new text.
Model: opus-5-5
Found in the trial run for https://git.eeqj.de/sneak/dnswatcher/issues/149.
With `DNSWATCHER_SEND_TEST_NOTIFICATION=true`, the startup notification ends "All notification channels are working." The message is written once and handed to every endpoint at the same moment, before any delivery has succeeded or failed, so the claim is never checked. In the run, the Mattermost endpoint refused its first delivery of the startup notification while the Slack and ntfy copies said every channel was working. An endpoint that is misconfigured for good never receives the message, and every other endpoint is told all is well.
To see it, set two endpoints, point one at a URL that answers 404, and start dnswatcher. The message is built in `maybeSendTestNotification` in `internal/watcher/watcher.go`.
## Definition of done
- The startup notification says only what is known when it is sent, for example that it is a test sent to every configured endpoint, and claims nothing about whether the endpoints work.
- The test of the startup notification checks the new text.
Model: opus-5-5
clawbot
added this to the 1.0 milestone 2026-10-02 07:35:34 +02:00
Implemented in #241: the startup notification now ends by saying it is a test notification sent to every configured notification endpoint, and its test checks the whole message.
Model: opus-5-5
Implemented in https://git.eeqj.de/sneak/dnswatcher/pulls/241: the startup notification now ends by saying it is a test notification sent to every configured notification endpoint, and its test checks the whole message.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found in the trial run for #149.
With
DNSWATCHER_SEND_TEST_NOTIFICATION=true, the startup notification ends "All notification channels are working." The message is written once and handed to every endpoint at the same moment, before any delivery has succeeded or failed, so the claim is never checked. In the run, the Mattermost endpoint refused its first delivery of the startup notification while the Slack and ntfy copies said every channel was working. An endpoint that is misconfigured for good never receives the message, and every other endpoint is told all is well.To see it, set two endpoints, point one at a URL that answers 404, and start dnswatcher. The message is built in
maybeSendTestNotificationininternal/watcher/watcher.go.Definition of done
Model: opus-5-5
Implemented in #241: the startup notification now ends by saying it is a test notification sent to every configured notification endpoint, and its test checks the whole message.
Model: opus-5-5