Mark an unreachable host in the session list instead of raising a toast #4

Merged
natsukium merged 1 commit from fix/quiet-unreachable-hosts into main 2026-10-14 14:26:29 +09:00
Owner

A sleeping laptop on the roster made the toast for its listing timeout appear on every refresh. That meant every time the session list opened and on every reconnect.

  • A failed listing is now stored per host and shown in the session list. The host's row under "New session on" says unreachable, with the gateway's error as the row's title.
  • A later successful listing clears the mark.
  • Failures from an attach or create still appear on the status line.

Checked in a browser with an unreachable ssh host on the roster. No toast appeared in about 46 s, which covers the restore and one open of the session list. The host's row read "over ssh · unreachable".

A sleeping laptop on the roster made the toast for its listing timeout appear on every refresh. That meant every time the session list opened and on every reconnect. - A failed listing is now stored per host and shown in the session list. The host's row under "New session on" says `unreachable`, with the gateway's error as the row's title. - A later successful listing clears the mark. - Failures from an attach or create still appear on the status line. Checked in a browser with an unreachable ssh host on the roster. No toast appeared in about 46 s, which covers the restore and one open of the session list. The host's row read "over ssh · unreachable".
A host that cannot be listed is usually a laptop that is asleep, which is
the ordinary state of a roster rather than news. Each refresh (every
open of the session list, every reconnect) raised the same timeout as a
toast over the terminal, so one sleeping machine meant dismissing it
again and again.

The failure is now kept per host and shown on that host's row under
"New session on", the place a user looks when deciding where to open a
session, with the gateway's reason as the row's title. A later
successful listing clears it. Failures from something the user did
(attaching, creating) still go to the status line.
natsukium deleted branch fix/quiet-unreachable-hosts 2026-10-14 14:26:29 +09:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
natsukium/felis-web!4
No description provided.