coder

mirror of https://github.com/coder/coder.git synced 2026-06-03 21:18:24 +00:00

Files

T

Cian Johnston 2d7dd73106 chore(httpapi): do not log context.Canceled as error (#22933 )

A cursory glance at Grafana for error-level logs showed that the
following log line was appearing regularly:

```
2026-03-11 05:17:59.169 [erro]  coderd: failed to heartbeat ping  trace=xxx  span=xxx  request_id=xxx ...
    error= failed to ping:
               github.com/coder/coder/v2/coderd/httpapi.pingWithTimeout
                   /home/runner/work/coder/coder/coderd/httpapi/websocket.go:46
             - failed to ping: failed to wait for pong: context canceled
```

This seems to be an "expected" error when the parent context is canceled
so doesn't make sense to log at level ERROR.


NOTE: I also saw this a bit and wonder if it also deserves similar
treatment:

```
2026-03-11 05:10:53.229 [erro]  coderd.inbox_notifications_watcher: failed to heartbeat ping  trace=xxx  span=xxx  request_id=xxx ...
    error= failed to ping:
               github.com/coder/coder/v2/coderd/httpapi.pingWithTimeout
                   /home/runner/work/coder/coder/coderd/httpapi/websocket.go:46
             - failed to ping: failed to write control frame opPing: use of closed network connection
```

2026-03-11 09:48:07 +00:00

httpapiconstraints

refactor(coderd/httpapi): remove database, dbauthz and rbac imports (#9481 )

2023-09-04 19:39:14 +03:00

httperror

refactor: untangle workspace creation from http logic (#19639 )

2025-08-29 14:17:33 +01:00

authz_slim.go

chore: avoid depending on rbac in slim builds (#17959 )

2025-05-22 19:48:23 +10:00

authz.go

chore: bring back x-auth-checks with a length limit (#19928 )