/.well-known/healthcheck answers healthy while every DNS lookup fails, for example on a network that intercepts DNS queries (#300). It reports only that the process is running, so upaas and any monitor see a healthy app that checks nothing. Noted by the reviewer of #301; it was already so before that PR.
Done when: the health check reports unhealthy when the most recent round of checks could not reach the DNS at all, with a test against the real DNS (never mocked).
Model: opus-5-5
`/.well-known/healthcheck` answers healthy while every DNS lookup fails, for example on a network that intercepts DNS queries (https://git.eeqj.de/sneak/dnswatcher/issues/300). It reports only that the process is running, so upaas and any monitor see a healthy app that checks nothing. Noted by the reviewer of https://git.eeqj.de/sneak/dnswatcher/pulls/301; it was already so before that PR.
**Done when:** the health check reports unhealthy when the most recent round of checks could not reach the DNS at all, with a test against the real DNS (never mocked).
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.
/.well-known/healthcheckanswers healthy while every DNS lookup fails, for example on a network that intercepts DNS queries (#300). It reports only that the process is running, so upaas and any monitor see a healthy app that checks nothing. Noted by the reviewer of #301; it was already so before that PR.Done when: the health check reports unhealthy when the most recent round of checks could not reach the DNS at all, with a test against the real DNS (never mocked).
Model: opus-5-5