fail fast in case of unexpected anwer from grpc #242

New issue

Open

opened 2025-12-28 18:07:32 +00:00 by sami · 2 comments

sami commented

2025-12-28 18:07:32 +00:00

Owner

Originally created by @532910 on GitHub (Dec 5, 2024).

Originally assigned to: @cthulhu-rider on GitHub.

See https://github.com/nspcc-dev/neo-go/issues/3721 for details.

Just like the response for curl http://st1.storage.fs.neo.org:443 is pretty instantaneous, neofs should fail fast in case of unexpected response.

Originally created by @532910 on GitHub (Dec 5, 2024). Originally assigned to: @cthulhu-rider on GitHub. See https://github.com/nspcc-dev/neo-go/issues/3721 for details. Just like the response for `curl http://st1.storage.fs.neo.org:443` is pretty instantaneous, neofs should fail fast in case of unexpected response.

sami added the

bug

labels

2025-12-28 18:07:32 +00:00

sami commented

2025-12-28 18:07:33 +00:00

Author

Owner

@cthulhu-rider commented on GitHub (Dec 5, 2024):

caused by nspcc-dev/neofs-sdk-go@591dd25e7c/client/client.go (L181) gRPC dial option which:

enables blocking until READY conn state (desired)
makes dial to fail immediately on any non-temporary error
but the mentioned error is not temporary according to current gRPC implementation

to solve, we'd need to configure dialer more specifically

@cthulhu-rider commented on GitHub (Dec 5, 2024): caused by https://github.com/nspcc-dev/neofs-sdk-go/blob/591dd25e7c5d9ef6d4239ebe1a3914bd9198ef13/client/client.go#L181 gRPC dial option which: - enables blocking until **READY** conn state (desired) - makes dial to fail immediately on any non-temporary error but the mentioned error is not temporary according to current gRPC implementation to solve, we'd need to configure dialer more specifically

sami commented

2025-12-28 18:07:33 +00:00

Author

Owner

@AnnaShaleva commented on GitHub (Dec 12, 2024):

Ping to this issue.

@AnnaShaleva commented on GitHub (Dec 12, 2024): Ping to this issue.