You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stacktrace when pausing program in debug mode in GoLand:
runtime.gopark at proc.go:337
runtime.selectgo at select.go:327
google.golang.org/grpc.(*ClientConn).WaitForStateChange at clientconn.go:508
google.golang.org/grpc.DialContext at clientconn.go:316
github.com/ydb-platform/ydb-go-sdk/v3/internal/dial.(*dialer).dial at dialer.go:78
github.com/ydb-platform/ydb-go-sdk/v3/internal/dial.(*dialer).dial-fm at dialer.go:77
github.com/ydb-platform/ydb-go-sdk/v3/internal/driver/cluster/balancer/conn.(*conn).take at conn.go:88
github.com/ydb-platform/ydb-go-sdk/v3/internal/driver/cluster/balancer/conn.(*conn).Invoke at conn.go:217
github.com/ydb-platform/ydb-go-genproto/Ydb_Discovery_V1.(*discoveryServiceClient).ListEndpoints at ydb_discovery_v1_grpc.pb.go:36
github.com/ydb-platform/ydb-go-sdk/v3/internal/discovery.(*client).Discover at discovery.go:61
github.com/ydb-platform/ydb-go-sdk/v3/internal/dial.(*dialer).discover at discovery.go:18
github.com/ydb-platform/ydb-go-sdk/v3/internal/dial.(*dialer).connect at dialer.go:63
github.com/ydb-platform/ydb-go-sdk/v3/internal/dial.Dial at dialer.go:37
github.com/ydb-platform/ydb-go-sdk/v3.New at connection.go:124
main.main at main.go:17
runtime.main at proc.go:225
runtime.goexit at asm_amd64.s:1371
- Async Stack Trace
runtime.rt0_go at asm_amd64.s:226
The text was updated successfully, but these errors were encountered:
Bug Report
YDB GO SDK version:
v3.2.7
Environment
Windows 10
go version go1.17.2 windows/amd64
Current behavior:
When trying to create new connection with ydb.New(...), program freezes.
Expected behavior:
It should create new connection and continue program.
Steps to reproduce:
Related code:
Output:
(it doesn't print 2 and doesn't return any error)
Other information:
Stacktrace when pausing program in debug mode in GoLand:
The text was updated successfully, but these errors were encountered: