kartka now reports through crdt_sync_flutter 0.9.1, so the shared ingest reads /kartka (old entry shape included) and kartka's own ingest retires. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3.4 KiB
App errors and slow waits become board tickets
kuhy's rule (2026-11-17): every error, and every wait the user sees over 1 s, in
any of his apps is reported automatically. The board then turns each one into a
ticket that fixes itself. This doc covers the apps' half and the PC ingest. The
board's half is todoImplementer DOCS-errors.md, with the contract in
contracts/app-error.schema.json. The design is kartka's pipeline
(~/src/kartka, docs/DOCS-error-reports.md), made shared.
Pipeline
- Apps report. Each report is one entry (see
app_errors/README.md):- Flutter,
crdt_sync_flutter0.9.0:installAppErrorshooksFlutterError.onErrorandPlatformDispatcher.onError.WaitWatchturns a spinner shown over 1 s intoperf.slow. The device deduplicates (30 s, 20 a minute) and redacts each report, and queues it inSharedPreferences. It uploads to RTDB/<app>/errors/<device>/<id>with the build (versionCode). - Python/Tk,
gatelock0.15.0:gatelock.error_report.installhookssys.excepthook,threading.excepthookand Tk callback errors.watch_stalls(root, rep)reports a frozen Tk loop over 1 s.rep.wait(...)andrep.begin(...)time a wait. - Godot,
godot_dev_tools0.2.0,addons/app_errors: anOS.add_loggerlogger catches script errors andpush_error. A frame over 1 s, orreport_waitover 1 s, becomesperf.slow. Headless runs andAPP_ERRORS_OFF=1write nothing, so a game's own test gates file no tickets. - PC apps (Tk and Godot) append to the local spool
~/.local/state/app-errors-spool/<app>.jsonl. They need no RTDB, because the ingest runs on the same PC.
- Flutter,
- The PC ingests.
app-errors-ingest.timerrunsapp-errors ingestevery 5 min. It reads RTDB through an already seeded crdt-sync session (firebase_backup) and reads the spool. It merges reports by signature (Dart signatures are kartka-identical), deletes what it read, and writes~/.local/state/app-errors/<app>.jsonas a contractreport. - The board files tickets. It scans that folder every 60 s and makes one
ticket per
app:signature(todoImplementerDOCS-errors.md).
app-errors resolve <app> <signature> sets open: false. A later report opens
the error again only when it is a regression: a newer build when both sides
know the build, else a report made after the resolve. The board never calls
resolve on its own, because folder sources have no resolve hook. It tracks
shipped fixes by fixed_build.
Choices made (no questions asked, per the brief)
- kartka moved over on 2026-11-17: the shared ingest reads
/kartkatoo (it parses kartka's older entry shape:sourceId, per-entrybuild), the board'serror_sourcesis[]andkartka-errors.timeris retired. Ticket ids stayed the same: all 134 stored kartka signatures recompute identically. - Tk and Godot use the local spool instead of RTDB: they only run on the PC.
- The Godot reporter is its own addon folder, mounted in every build. It is
not part of
dev_tools, which only loads for--devruns. - Reporting is silent: no text, dialog or notification in any app.
Install and check
scripts/deploy.sh runs app_errors/install.sh. That installs the venv and
~/.local/bin/app-errors, enables the timer, and checks that the timer is
active and the venv imports the live checkout.