Skip to content

actionable error: some errors related to rpc calls are missing debug info #766

@daniel-sanche

Description

@daniel-sanche

Looking at the exceptions raised in python-firestore, I found a couple places where custom ValueErrors are raised after failed rpc calls, discarding all the useful server debugging information

These should all use exception chaining to make sure the original error is preserved

Metadata

Metadata

Assignees

No one assigned

    Labels

    api: firestoreIssues related to the googleapis/python-firestore API.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions