Skip to content

Report project exception messages in the enrollment worker failure line - #18

Closed
pablo-ur-fixer wants to merge 1 commit into
macintog:mainfrom
pablo-ur-fixer:pr/worker-error-detail
Closed

pablo-ur-fixer wants to merge 1 commit into
macintog:mainfrom
pablo-ur-fixer:pr/worker-error-detail

Conversation

@pablo-ur-fixer

Copy link
Copy Markdown

When the enrollment worker stops on a CatacombBridgeError, journald only shows classes=FprintWorkerError>PersistenceOperationError>CatacombBridgeError reason=unclassified. A nonzero prepare status, an interleaved service event, a changed connection generation and a malformed reply all look identical, which made a real first-enrollment failure on bridgeOS 24P6005 impossible to attribute (see #17).

This adds a detail= JSON list to the enrollment stopped line carrying the messages of the project's own exception chain only: classes whose module starts with t2_, printable ASCII, 120 characters per message, at most six messages. Raw bridge replies, OS errors and identifiers never reach the line.

Tests: new tests/test_fprint_enrollment_worker_report.py; full suite passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_013Z5eh5T2UPSQnihyoB12TP

The enrollment worker logged only the exception class names and an
authorization reason, so a Catacomb persistence failure appeared as
"classes=...>CatacombBridgeError reason=unclassified" and could not be
told apart from the other bridge checks. Add a JSON "detail=" list with
the messages of exceptions raised by t2_* modules along the cause chain.
Those messages are fixed strings; foreign exceptions are dropped and the
text is bounded to printable ASCII, so the line still carries no
identifiers or raw bridge replies.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Z5eh7nvcZfcnceC8vskKu
@macintog

macintog commented Nov 4, 2026

Copy link
Copy Markdown
Owner

Thanks for this. We're closing it as superseded, along with the rest of the stack: T2Touch is moving its Touch ID support into Omarchy itself. #17 has the details, the answers to your questions, and what we've recorded from these fixes for that work, with credit.

@macintog macintog closed this Nov 4, 2026
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.

2 participants