coracle/caravel
1
1
Fork 2
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Relay sync errors stored in DB but never surfaced in UI #32

New Issue
Closed
opened 2026-04-20 11:53:19 +00:00 by userAdityaa · 0 comments
userAdityaa commented 2026-04-20 11:53:19 +00:00
Contributor
Copy Link
Copy Source

Description

When Caravel fails to provision a relay in Zooid, the error is saved in the sync_error column of the relay table (written by command::fail_relay_sync, cleared by command::complete_relay_sync). However, this field is never read or rendered anywhere in the frontend. The relay detail page shows the relay URL as live and the status badge only knows active / inactive, there is no visual indicator that provisioning failed.

### Description When Caravel fails to provision a relay in Zooid, the error is saved in the `sync_error` column of the `relay` table (written by `command::fail_relay_sync`, cleared by `command::complete_relay_sync`). However, this field is never read or rendered anywhere in the frontend. The relay detail page shows the relay URL as live and the status badge only knows `active` / `inactive`, there is no visual indicator that provisioning failed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hodlbod (hodlbod)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coracle/caravel#32
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?