-
Notifications
You must be signed in to change notification settings - Fork 567
Closed
Labels
api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.authgrpcpriority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.status: acknowledgedstatus: blockedResolving the issue is dependent on other work.Resolving the issue is dependent on other work.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Hi, we just pushed the code to production, and one hour after started seeing unexpected UnauthenticatedError exceptions.
cause is GRPC::BadStatus and message is "16:Faraday::ConnectionFailed", .details="Faraday::ConnectionFailed"
Which looks like transient HTTP AUTH connection failure, which should be retriable, and in any case should not be reported as Google::Cloud::UnauthenticatedError.
Also I didn't think Faraday is still in use after update to grpc.
Can you please investigate the issue, as it is out of the expected behavior and I had to hot-patch the production.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.authgrpcpriority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.status: acknowledgedstatus: blockedResolving the issue is dependent on other work.Resolving the issue is dependent on other work.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.