Skip to content

epoch-rotted client could not recover from fresh READ/WRITE delegation #8

Description

@kn8-codes

Envoy 0.2.4-era clients exposed a stale capability state where one participant could not recover via fresh delegation.

Environment

  • Admin/delegator: macOS, Envoy CLI 0.2.4 (git_commit bbedb403a9363f012e186a4f9e0d76d321cf4628)
  • Affected client: Linux host, Envoy profile default
  • Space: private shared space name redacted

Observed

The affected client could not read past cursor 9 and send failed with:

capability token expired or missing — room admin may need to refresh your role.

An admin delegated object-scoped READ/WRITE to the affected client's DID. Delegation succeeded from the admin side, but the affected client still could not apply/ingest/use the delegated capability. A fresh rejoin was required to restore operation.

Expected

One of:

  • fresh delegation should be discoverable/ingestable by the stale client;
  • envoy diagnose should identify that local state is unrecoverable and recommend rejoin;
  • a repair command should exist, e.g. envoy space repair, envoy capabilities refresh, or documented equivalent.

Impact

The user-facing error suggests an admin refresh/delegation may fix the role. In this case, admin delegation did not fix it, and the required action was rejoin.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions