Skip to content

fix(notifications): treat offline as a connection state, not an error - #3706

Draft
setchy wants to merge 1 commit into
mainfrom
feat/connection-status-offline
Draft

setchy wants to merge 1 commit into
mainfrom
feat/connection-status-offline

Conversation

@setchy

@setchy setchy commented Nov 17, 2026

Copy link
Copy Markdown
Member

Summary

A paused notification query means there is no connectivity, not that a fetch failed. This adds an explicit offline status so the tray and notifications view stop presenting the offline-to-online transition as an error.

  • Status gains offline; deriveStatus returns it when the query is paused.
  • The notifications view renders the existing OFFLINE Oops for offline.
  • The tray only maps error to the -1/red sentinel, so a paused query no longer flashes red.

Part of the OpenSpec change smooth-connection-recovery (PR 1 of 3).

Test plan

  • pnpm test for the affected suites
  • pnpm check
  • pnpm lint:check

Notes

This is the base of a stacked series. The recovery hold and retry PRs build on it.

A paused notification query means there is no connectivity, not that a fetch failed. Derive an explicit offline status so the tray and notifications view do not present the offline/reconnect transition as an error.
@github-actions github-actions Bot added the bug Something isn't working label Nov 17, 2026
@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Development

Successfully merging this pull request may close these issues.

1 participant