Chat handlers returned raw contract errors (SQL fragments, gRPC status details, host paths) to the browser. Every 5xx/transport failure in internal/webui/chat.go now answers with a plain sentence in the gateway's wording and logs the real cause via the injected logger's ErrorContext; the SSE error frame on stream-open failure gets the same treatment. Safe 400 validation messages and the 404 'session not found' are unchanged. New table-driven tests in internal/webui/chat_errors_test.go prove a contract fake whose error embeds a SQL fragment produces a sanitised body and SSE frame, and that the cause lands in the server log; they fail against the old handlers. Verified: go test -short ./internal/webui/... ok, task check exit 0 (fmt, proto:check, db:check, vet, golangci-lint 0 issues, build, go test ./..., pnpm test 102 pass, vue-tsc typecheck).
Chat handlers returned raw contract errors (SQL fragments, gRPC status details, host paths) to the browser. Every 5xx/transport failure in internal/webui/chat.go now answers with a plain sentence in the gateway's wording and logs the real cause via the injected logger's ErrorContext; the SSE error frame on stream-open failure gets the same treatment. Safe 400 validation messages and the 404 'session not found' are unchanged. New table-driven tests in internal/webui/chat_errors_test.go prove a contract fake whose error embeds a SQL fragment produces a sanitised body and SSE frame, and that the cause lands in the server log; they fail against the old handlers. Verified: go test -short ./internal/webui/... ok, task check exit 0 (fmt, proto:check, db:check, vet, golangci-lint 0 issues, build, go test ./..., pnpm test 102 pass, vue-tsc typecheck).
Chat handlers returned raw contract errors to the browser, which can
carry SQL fragments, gRPC status details or host paths. Each 5xx and
transport failure now answers with a plain sentence in the gateway's
wording and logs the real cause through the injected logger's
ErrorContext. The SSE error frame on stream-open failure gets the same
treatment. Safe 400 validation messages and the 404 'session not found'
are unchanged.
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.
Chat handlers returned raw contract errors (SQL fragments, gRPC status details, host paths) to the browser. Every 5xx/transport failure in internal/webui/chat.go now answers with a plain sentence in the gateway's wording and logs the real cause via the injected logger's ErrorContext; the SSE error frame on stream-open failure gets the same treatment. Safe 400 validation messages and the 404 'session not found' are unchanged. New table-driven tests in internal/webui/chat_errors_test.go prove a contract fake whose error embeds a SQL fragment produces a sanitised body and SSE frame, and that the cause lands in the server log; they fail against the old handlers. Verified: go test -short ./internal/webui/... ok, task check exit 0 (fmt, proto:check, db:check, vet, golangci-lint 0 issues, build, go test ./..., pnpm test 102 pass, vue-tsc typecheck).