Skip to content

Logging/stale fetch diagnostics - #247

Merged
parawanderer merged 2 commits into
mainfrom
logging/stale-fetch-diagnostics
Oct 11, 2026
Merged

parawanderer merged 2 commits into
mainfrom
logging/stale-fetch-diagnostics

Conversation

@parawanderer

Copy link
Copy Markdown
Owner
  • Cover more account and fetch related issues in the logs.
  • Update python/README.md removing outdated advice.

parawanderer and others added 2 commits October 11, 2026 14:46
Three places a "map goes stale with no error anywhere" capture had to
be read around silences, seen across #238, #239 and #240:

- A fetch refused while the session answers as healthy (rate limiting,
  flagging) and a session check suppressed by the latch produced the
  same empty log. Both branches now say which one happened.
- A successful fetch logged only a report count, so "the network
  genuinely holds nothing newer" was indistinguishable from "returned
  something fresh". The newest report's age is now logged per
  accessory, on the periodic path the reports come from.
- A restore stalled inside Python (anisette, network) looked exactly
  like one that never started. Start and return are now logged, so a
  cold-start capture shows which side of the call it sits on.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@parawanderer
parawanderer deployed to Android Build October 11, 2026 12:48 — with GitHub Actions Active
@parawanderer
parawanderer deployed to Android Build October 11, 2026 12:48 — with GitHub Actions Active
@parawanderer
parawanderer merged commit eb35c41 into main Oct 11, 2026
9 checks passed

This branch was successfully deployed

1 active deployment
Android Build — 5380da45 Deployed Oct 11, 2026 by parawanderer via build #309
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant