appear segmentfault when calling current_timestamp()
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 425
- Forks
- 163
- Avg merge
- 10h 51m
- Merged PRs (30d)
- 3
Description
background :
- i'm learning BR of TiDB, and use tikv-client to get TSO.
- however, when i used example of
pd.current_timestampto do, i got an error.
help info :
- you can access my code at segmentfault path, and run
cargo run -- backup table -t 123 -s ./to reproduce the error - after debug, i saw something happened on grpc part of tikv-client.
hopefully, anyone gives me any advise.
Contributor guide
No contributing guide indexed for this repository
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 with components/pd_client/src/lib.rs at line 17 and run cargo run -- backup table -t 123 -s ./ from the linked reproduction. Inspect the gRPC failure shown during debugging and trace whether it produces a segmentation fault; done means the crash is reproduced, its cause is identified, and the current_timestamp path works without the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100