Yo Eight
Yo Eight
I believe there is a misunderstanding on how the node discovery works. Yes, in your case it will only resolve one. As I said earlier > We used to support...
@lbodor You’ve chosen the only gRPC client that explicitly performs DNS resolution through lookup queries. While the Python client is officially maintained by the company, it’s not directly managed by...
@lbodor as soon as that PR get merged, I'll cut a new release right after.
@lbodor The feature is available in the 5.4.2 release.
> Chiming in — we’re also encountering this issue. It does seem like the feature-flagged behavior might make sense as the default going forward. That said, enabling it by default...
Apologies for missing your earlier comment, @marcuslyth — I just saw it now. My recollection of why we went in that direction is a bit hazy, but I believe the...
If you’re referring to the fact that the connection string hostname is `foobar:1234`, but the `InetSocketAddress` we retain later only reflects the resolved IP, like `10.20.30.40:1234`, then you’re correct —...
@antonmos This PR addresses that issue: https://github.com/kurrent-io/KurrentDB-Client-Java/pull/328 Thank you and @marcuslyth for bringing that issue to light.
Thank you @samansmink for your insight. Personally, the CLion instructions never worked for me. I don't see what else I should do beside starting CLion in the `duckdb` directory directly...
I have a similar configuration and my extension files are part of the project according to CLion. Yet, CLion can't seem to find my include files properly as shown below: