Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

firestore: handle transient connection errors #10350

Open
Kavantix opened this issue Jun 8, 2024 · 0 comments
Open

firestore: handle transient connection errors #10350

Kavantix opened this issue Jun 8, 2024 · 0 comments
Assignees
Labels
api: firestore Issues related to the Firestore API. triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@Kavantix
Copy link

Kavantix commented Jun 8, 2024

Client

Firestore

Environment

Cloud Run

Go Environment
n/a

Expected behavior

Reading any document from cloud run should always succeed without connection issues, general firebase admin sdk documentation states it should handle any connection resets

Actual behavior

The syscall.ECONNRESET and syscall.ECONNREFUSED errors are not handled but instead passed as error to the caller.
This gives a message like:

rpc error: code = Unavailable desc = error reading from server: read tcp [fddf:3978:feb1:d745::c001]:55980->[2a00:1450:4001:81c::200a]:443: read: connection reset by peer

Notes

@Kavantix Kavantix added the triage me I really want to be triaged. label Jun 8, 2024
@product-auto-label product-auto-label bot added the api: firestore Issues related to the Firestore API. label Jun 8, 2024
@bhshkh bhshkh added the type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: firestore Issues related to the Firestore API. triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants