Title: Categorize remote-fetch failures and surface a "rate limited" pill instead of silent blanks #36

New issue

Open

opened 2026-05-23 20:55:25 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-05-23 20:55:25 +00:00

Owner

Originally filed by @coilysiren on 2026-05-15T03:18:15Z - https://github.com/coilysiren/repo-recall/issues/165

Problem

When a gh call fails, the dashboard renders the affected remote-state columns as blank. There is no way to tell whether the repo genuinely has no PRs/issues/CI, the repo is unauthenticated, the repo is missing, or GitHub rate-limited us. All four states look identical to the user.

Where

src/ingest/github/{issues,pulls,ci_runs}.rs - failures collapse into None with a debug! log.
src/display/routes/templates.rs - no failure-state pill in the existing PILL bundles.
Proposed

Distinguish failure modes at the ingest boundary by inspecting gh exit code + stderr (404 vs 401/403 vs 403+rate-limit headers vs other). Surface the categorized state up to the dashboard as a discriminated enum (e.g. RemoteFetchState::{Ok, Missing, Unauthorized, RateLimited, Error}) and render a "rate limited, paused" pill instead of a silent blank when relevant.

_Originally filed by @coilysiren on 2026-05-15T03:18:15Z - [https://github.com/coilysiren/repo-recall/issues/165](https://github.com/coilysiren/repo-recall/issues/165)_ Problem When a gh call fails, the dashboard renders the affected remote-state columns as blank. There is no way to tell whether the repo genuinely has no PRs/issues/CI, the repo is unauthenticated, the repo is missing, or GitHub rate-limited us. All four states look identical to the user. Where src/ingest/github/{issues,pulls,ci_runs}.rs - failures collapse into None with a debug! log. src/display/routes/templates.rs - no failure-state pill in the existing PILL bundles. Proposed Distinguish failure modes at the ingest boundary by inspecting gh exit code + stderr (404 vs 401/403 vs 403+rate-limit headers vs other). Surface the categorized state up to the dashboard as a discriminated enum (e.g. RemoteFetchState::{Ok, Missing, Unauthorized, RateLimited, Error}) and render a "rate limited, paused" pill instead of a silent blank when relevant.

coilysiren referenced this issue

2026-05-23 20:55:29 +00:00

Document the full usage surface (browser, agent-via-HTTP, MCP App, demo, dev loops) #65

coilysiren added the

label

2026-05-31 01:55:03 +00:00

coilysiren added

and removed

labels

2026-05-31 07:01:14 +00:00