Skip to content

Logging fetcher should provide more detail with status codes  #28

@Qinusty

Description

@Qinusty

#27 (comment) highlights a problem with the clarity of the logging fetcher providing information in the case of an error, we should also look to include the GRPC error name alongside the code or perhaps even the message that the error is wrapped with.

See

log.Printf("FetchBlob completed for %s with status code %d", req.Uris, resp.Status.GetCode())

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions