coder/agent/proto
Spike Curtis 92b2e26a48
feat: send log limit exceeded in response, not error (#12078)
When we exceed the db-imposed limit of logs, we need to communicate that back to the agent.  In v1 we did it with a 4xx-level HTTP status, but with dRPC, the errors are delivered as strings, which feels fragile to me for something we want to gracefully handle.

So, this PR adds the log limit exceeded as a field on the response message, and fixes the API handler to set it as appropriate instead of an error.
2024-02-09 16:17:20 +04:00
..
agent.pb.go feat: send log limit exceeded in response, not error (#12078) 2024-02-09 16:17:20 +04:00
agent.proto feat: send log limit exceeded in response, not error (#12078) 2024-02-09 16:17:20 +04:00
agent_drpc.pb.go chore: remove tailnet from agent API and rename client API to tailnet (#11303) 2024-01-02 10:02:45 +04:00
compare.go fix: fix MetricsAggregator check for metric sameness (#11508) 2024-01-09 15:21:30 +04:00
compare_test.go fix: fix MetricsAggregator check for metric sameness (#11508) 2024-01-09 15:21:30 +04:00
version.go feat: check agent API version on connection (#11696) 2024-01-23 14:27:49 +04:00