ydb-platform / ydb-platform/ydb-java-sdk
In async transport initialization readyWatcher will never be called in case of discovery error
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 53
- Forks
- 40
- Avg merge
- 9h 51m
- Merged PRs (30d)
- 7
Description
https://github.com/ydb-platform/ydb-java-sdk/blob/master/core/src/main/java/tech/ydb/core/impl/YdbTransportImpl.java#L87
If discovery fails, discovery.waitReady will throw exception and readyWatcher.run() will never be called.
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
The failure path is in core/src/main/java/tech/ydb/core/impl/YdbTransportImpl.java around line 87; start by reading the async initialization flow around discovery.waitReady and readyWatcher. Run the relevant project tests and verify that discovery errors produce the expected initialization outcome while readyWatcher is still handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100