Handle log_rpc on_timeout calls correctly
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 342
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 52
Description
Environment
(Required) Please provide the output of bin/observer -V. If this test also involves a version change for obproxy, please also provide the output of obproxy -V.
Mapping relationship for the properties on the right side: "Target Branch" and "Iteration".
Description
This issue concerns the correct handling of log_rpc on_timeout calls.
Steps to Reproduce
The issue is consistently reproducible (必现).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by collecting the required output from bin/observer -V, and obproxy -V if the test involves an obproxy version change. Reproduce the reported log_rpc on_timeout behavior and trace how the timeout call is handled. Done means the call is handled correctly and the issue is no longer reproducible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100