The simple example does not work: the driver gets stuck on connecting

[caiiiycuk]

I created an empty project and copied & pasted code from README.md, but whenever I run it, it gets stuck on this:

    // wait until the background initialization of the driver finishes
    client.wait().await?;

Even if the configuration is obviously wrong, it never exits with an error. How can I use it?

Here is my test project: test.zip

[caiiiycuk]

Okay it's duplicate of this #180

[rekby]

Hello, @caiiiycuk.

This problem has a different from #180. The issue is about the example. It might be more understandable really.

Do I right understand about you haven't run a local ydb instance and it was the problem?
Where do you want to see notification about it?

And I agree with the needs for timeout example of connections - I will add those .

[caiiiycuk]

Do I right understand about you haven't run a local ydb instance and it was the problem?

I migrated from AWS to Yandex Cloud, so I use the SDK only to connect to my cloud instance. I do not have any knowledge about deploying YDB locally, etc.

I started with this example, and of course, I did not have a local server. When I ran the example, it got stuck on connecting. I then started trying different credential providers, hoping that some would clearly fail so I could understand if something was working. However, every provider I tried did the same thing—getting stuck on connecting.

Next, I found out how to enable trace logging, but there was no clear error. All I saw was that it kept trying to connect without success. When I set a timeout for the connection, the error message was something like "empty list in endpoint", which didn’t make any sense.

It was really hard to understand whether I was doing things correctly and whether it was working or not. Finally, I used my service account token file (even though, initially, I didn’t know this was possible, as the documentation suggested otherwise), and it magically started working.

Overall, this experience was not great for me. This is probably also because I have little knowledge about YDB...

[caiiiycuk]

I also tried using a wrong credentials provider (from example) with my cloud endpoint, but it also got stuck on connecting—no interruptions due to incorrect credentials. This made me think that the YDB SDK wasn’t working at all.

Accidentally, I tried my endpoint and token from another project, and it magically started working. So, I figured it out incidentally.