Files
PaperClipAI/ui/src/components/ConnectionStatusBanner.tsx
T
39279aa34f feat(ui): shared error, connectivity and query foundation for disconnects (#15754)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - The board reads API data and keeps the current task on screen.
> - A restart or temporary network failure can interrupt those reads.
> - Separate page error handlers can hide cached data or expose raw
server codes.
> - The app needs one connection state, readable error copy and a
consistent read policy.
> - This change provides that foundation and moves affected read
surfaces onto it.
> - The dependent write layer in #17960 preserves edits and submissions
across the same failures.

## Linked Issues or Issue Description

**What happened?**

Temporary API failures could replace loaded content with errors.
Different surfaces handled the same outage differently. Some showed raw
server codes. A successful query to an unrelated service could also
falsely report that Paperclip had recovered.

**Expected behavior**

Keep cached content visible. Show one connection banner during sustained
trouble. Confirm recovery through the Paperclip health probe or its
WebSocket. Retry transient reads and show readable errors for permanent
failures.

**Steps to reproduce**

1. Open a populated task or workspace page.
2. Interrupt API requests with a 503 or a dropped connection.
3. Keep an unrelated external request in flight.
4. Confirm that cached content remains and that the external result
cannot clear the outage.
5. Restore the API and check that reads refresh.

The write layer first merged into this feature branch in #15769 now has
its own dependent PR, #17960. This PR contains the shared foundation and
read changes. Merge this PR first.

## What Changed

- Classify API errors and provide readable error copy, including
non-JSON proxy responses and Retry-After handling.
- Use one connection store and health probe with bounded backoff.
Confirm recovery from the server health probe or live-updates WebSocket.
- Pause reads while disconnected, retry transient errors, and refresh
active reads after recovery.
- Keep cached data visible through shared query views and affected page,
panel and plugin read surfaces.
- Add one app-level connection banner and support the pending-write
count consumed by the dependent write layer.
- Add a query-error rendering guard. Call it directly from the existing
CI step. Update development documentation.

## Verification

- Historical-chat lookup now follows the same ready/stale roster state
as rendering. Three regressions fail before the fix; the six new cases
pass after it, including working Retry, fresh data, no-cache error,
permanent 403 and company isolation. All six focused query/recovery
suites pass 200 tests. Final-commit CI passes and Apex is 5/5 with no
unresolved findings. Canary Dry Run initially refused a preview version
that was already on npm. It passed after one rerun with fresh registry
metadata; no check was disabled.

- Integrated current master and retained both transcript interest
registration and connectivity reporting on socket open. The seven
focused recovery/query suites pass 288 tests, and UI typecheck and
production build pass. All 9,451 UI tests across 799 files pass on the
merge commit. Final-commit CI passes and Apex is 5/5 with no unresolved
findings.

- Current head `70d9335d732219352ef0f98414439766bbcb33df`: all hosted CI
checks pass. Apex is **5/5** on that head with no unresolved findings.
The branch has no merge conflict. GitHub still requires code-owner
approval.

- The foundation passes 9,430 UI tests in 804 files. After integrating
current master page paths, 190 focused page tests pass.
- Two unrelated-success regressions fail before the latest fix. With the
fix, 62 focused UI tests, all six guard tests and UI TypeScript pass.
- The composed foundation and write layer pass **9,505 UI tests in 808
files**, UI TypeScript, a production UI build, and query-error, token
and map guards.
- A real Chromium journey on the composed source injects a 503 during
title save. The loaded task stays visible; one reconnect banner appears;
the edit saves after recovery; another task stays unchanged; the saved
title survives reload.
- Full recursive local checks were not repeated because Runner
compilation exhausted local disk during another repair. Hosted checks
must pass before merge. No new staging deployment is claimed.

- Latest review follow-up: a cached CaseDetail now survives a failed
HTTP 429 refresh. Its page regression fails before the fix and passes
after it. Eighty focused foundation tests, UI TypeScript, build and
guards pass after that change.
- Earlier CI evidence is retained: several foundation jobs received a
runner shutdown signal together. The write-layer head also failed an
unchanged Runner descriptor close test with `provider_transport_failed`.
The same Runner source passed that suite in the foundation run. New CI
runs cover the updated heads; no check or assertion was weakened.

## Risks

- Shared retry defaults change the time before transient read errors
appear. Permanent errors still fail promptly.
- ApiError.message now contains readable copy. Callers that compare raw
codes must use ApiError.code.
- Cache success can come from another service or local data. It must not
confirm Paperclip recovery.
- Durable writes are reviewed separately in #17960. This PR does not
change database or mutation contracts.

## Model Used

Anthropic Claude Opus 5.5 (`claude-opus-5-5`) produced the original work
with tool use. OpenAI Codex, GPT-6 family, assisted with restoration,
integration, tests and review fixes. The Codex session does not expose
its exact serving model ID or context window size.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

---------

Co-authored-by: devinfoley <139239+devinfoley@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Paperclip <noreply@paperclip.ing>
Co-authored-by: Amy (Opus) <claude@users.noreply.github.com>
2026-10-27 21:22:07 -07:00

137 lines
5.2 KiB
TypeScript
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
import { useEffect, useRef, useState, useSyncExternalStore } from "react";
import { useConnectivity, type ConnectivityStatus } from "@/lib/connectivity";
/** Trouble must last this long before the banner appears, so one blip never flickers. */
export const BANNER_SHOW_DELAY_MS = 2_000;
/** How long "Back online" stays after a recovery the user saw. */
export const BACK_ONLINE_VISIBLE_MS = 3_000;
export type ConnectionBannerView = "hidden" | "reconnecting" | "offline" | "back_online";
/**
* Which banner to show. Reconnecting/offline only after `BANNER_SHOW_DELAY_MS`
* of continuous trouble; "Back online" only after an outage the banner showed.
*/
export function connectionBannerView(input: {
status: ConnectivityStatus;
troubleSince: number | null;
recoveredAt: number | null;
shownForOutage: boolean;
now: number;
}): ConnectionBannerView {
if (input.status !== "online") {
const troubleFor = input.troubleSince === null ? 0 : input.now - input.troubleSince;
if (troubleFor < BANNER_SHOW_DELAY_MS) return "hidden";
return input.status;
}
if (input.shownForOutage && input.recoveredAt !== null && input.now - input.recoveredAt < BACK_ONLINE_VISIBLE_MS) {
return "back_online";
}
return "hidden";
}
export function pendingWritesCopy(count: number): string | null {
if (count <= 0) return null;
return count === 1
? "1 change will send when you’re back online."
: `${count} changes will send when you’re back online.`;
}
// Full-page reconnect screens (CloudAccessGate before the board opens) already
// say the same thing; the banner stays hidden while one is mounted.
let suppressors = 0;
const suppressionListeners = new Set<() => void>();
function setSuppressors(next: number) {
suppressors = next;
for (const listener of [...suppressionListeners]) listener();
}
function subscribeSuppression(listener: () => void) {
suppressionListeners.add(listener);
return () => {
suppressionListeners.delete(listener);
};
}
/** Hide the banner while the calling component is mounted. */
export function useSuppressConnectionBanner(active = true) {
useEffect(() => {
if (!active) return;
setSuppressors(suppressors + 1);
return () => setSuppressors(suppressors - 1);
}, [active]);
}
/**
* The single app-level connection indicator. Replaces per-surface
* outage errors: while the server is unreachable, loaded content stays on
* screen and this banner explains why nothing is updating.
*/
export function ConnectionStatusBanner() {
const { status, troubleSince, recoveredAt, pendingWrites } = useConnectivity();
const [now, setNow] = useState(() => Date.now());
const shownForOutage = useRef(false);
const suppressed = useSyncExternalStore(subscribeSuppression, () => suppressors > 0, () => false);
const view = connectionBannerView({ status, troubleSince, recoveredAt, shownForOutage: shownForOutage.current, now });
if (!suppressed && (view === "reconnecting" || view === "offline")) shownForOutage.current = true;
// Re-render when the view can next change: when the show delay elapses, or
// when "Back online" should disappear.
useEffect(() => {
let wakeAt: number | null = null;
if (status !== "online" && troubleSince !== null && view === "hidden") {
wakeAt = troubleSince + BANNER_SHOW_DELAY_MS;
} else if (view === "back_online" && recoveredAt !== null) {
wakeAt = recoveredAt + BACK_ONLINE_VISIBLE_MS;
}
if (wakeAt === null) return;
const timer = window.setTimeout(() => setNow(Date.now()), Math.max(0, wakeAt - Date.now()));
return () => window.clearTimeout(timer);
}, [status, troubleSince, recoveredAt, view]);
// Keep `now` current when the connectivity state changes.
useEffect(() => {
setNow(Date.now());
}, [status, troubleSince, recoveredAt]);
useEffect(() => {
if (view === "hidden" && status === "online") shownForOutage.current = false;
}, [view, status]);
if (view === "hidden" || suppressed) return null;
return <ConnectionStatusMessage view={view} pendingWrites={pendingWrites} />;
}
/** The banner's presentation, for a view that is not hidden. */
export function ConnectionStatusMessage({
view,
pendingWrites = 0,
}: {
view: Exclude<ConnectionBannerView, "hidden">;
pendingWrites?: number;
}) {
const pending = view === "back_online" ? null : pendingWritesCopy(pendingWrites);
const message = view === "back_online"
? "Back online."
: view === "offline"
? "You’re offline. Reconnecting when your network is back…"
: "Connection interrupted. Reconnecting automatically…";
// Fixed, not in flow: the desktop shell is exactly `h-dvh` with clipped
// overflow, so an in-flow banner would push the board's bottom off screen.
// The top offset includes the safe-area inset so a notch cannot hide it.
return (
<div className="pointer-events-none fixed inset-x-0 top-(--connection-banner-top) z-(--z-120) flex justify-center px-2">
<div
role="status"
aria-live="polite"
data-connection-status={view}
className="rounded-full border border-border bg-muted px-4 py-1.5 text-center text-sm text-muted-foreground shadow-sm"
>
{message}
{pending ? <> {pending}</> : null}
</div>
</div>
);
}