[VOL-5222] - Upgrade golang version for VOLTHA jobs
.gitreview
VERSION
----------
o post-release tasks. Repository tagged and banched.
o Add missing newlines at EOF.
o go.mod syntax does not allow *-dev suffix so update
master VERSION from v5.5.0-dev to v5.5.0. Community
can introduce a dev version when needed.
go/*.pb.og
vendor/*.go
-----------
o invoke make mod-update to regenerate go.sum and friends.
o lint clenaups: find . -name '*.go' -print | xargs -n1 gofmt -s -e -w
Change-Id: I3da80c0ce5600679b388e309bfa4702f1ec3212b
diff --git a/vendor/google.golang.org/grpc/internal/transport/http2_client.go b/vendor/google.golang.org/grpc/internal/transport/http2_client.go
index f0c72d3..10b5461 100644
--- a/vendor/google.golang.org/grpc/internal/transport/http2_client.go
+++ b/vendor/google.golang.org/grpc/internal/transport/http2_client.go
@@ -629,13 +629,13 @@
// NewStream errors result in transparent retry, as they mean nothing went onto
// the wire. However, there are two notable exceptions:
//
-// 1. If the stream headers violate the max header list size allowed by the
-// server. In this case there is no reason to retry at all, as it is
-// assumed the RPC would continue to fail on subsequent attempts.
-// 2. If the credentials errored when requesting their headers. In this case,
-// it's possible a retry can fix the problem, but indefinitely transparently
-// retrying is not appropriate as it is likely the credentials, if they can
-// eventually succeed, would need I/O to do so.
+// 1. If the stream headers violate the max header list size allowed by the
+// server. In this case there is no reason to retry at all, as it is
+// assumed the RPC would continue to fail on subsequent attempts.
+// 2. If the credentials errored when requesting their headers. In this case,
+// it's possible a retry can fix the problem, but indefinitely transparently
+// retrying is not appropriate as it is likely the credentials, if they can
+// eventually succeed, would need I/O to do so.
type NewStreamError struct {
Err error