ydb-platform / ydb-platform/ydb-python-sdk
feature: Report about timeout reason while connect to topic
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 102
- Forks
- 75
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
If set bad connection params to driver it will reconnect forever.
Topic writer will receive timeout error by retry policy but no contains details.
It will be good to include last driver error in timeout error, for example as: raise TimeoutError from exc.
P.S. may be do it in driver and return same exception from call - for all method, not for topics only
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
Trace the driver reconnect path and topic writer retry/timeout handling described in the issue. Check how the last driver error is propagated and whether the same behavior should apply through the driver's call; done means timeout errors retain the underlying cause without changing unrelated retry behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100