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
gRPC status errors are suitable for gRPC p2p communication between clients. I don't think we need to work with it it gates. S3 gate defines it's own set of errors so we should use it ubiquitous.
NeoFS API Client will provide generic go errors in the future (nspcc-dev/neofs-api#150) but now we can rely only on text descriptions. So the common pattern should be to parse API error (basically text description) and throw S3 error.
The text was updated successfully, but these errors were encountered:
gRPC status errors are suitable for gRPC p2p communication between clients. I don't think we need to work with it it gates. S3 gate defines it's own set of errors so we should use it ubiquitous.
NeoFS API Client will provide generic go errors in the future (nspcc-dev/neofs-api#150) but now we can rely only on text descriptions. So the common pattern should be to parse API error (basically text description) and throw S3 error.
The text was updated successfully, but these errors were encountered: