Fix configuredMaxSeconds behavior in TrimContextByTimeoutWithCappedDDL
Open
- Dominant language
- Go
- Stars
- 661
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
So that in case of RPC worker invocation timeout, it will return the 4xx errros instead of 5xx errors.
Also, may worth changing the status code from 420 to something else
Contributor guide
Research direction
Start by locating TrimContextByTimeoutWithCappedDDL and tracing how RPC worker invocation timeouts are converted into response errors. Check the existing error-handling tests or entry points around this function; done means timeout cases return 4xx responses consistently, with the intended replacement for status 420 confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100