Skip to content

zed version produces error output when spicedb is unavailable #554

@tstirrat15

Description

@tstirrat15

This is likely a regression that we introduced when we introduced retry logic:

Image

We try to connect to the running instance of SpiceDB, and if it isn't available we retry three times. We log on failed retries and this looks weird. We should probably skip the retries and silently fail in this case - otherwise it's just noise.

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