Log safemode errors #555

Merged
Vylpes merged 1 commit from feature/554-log-safemode-error into hotfix/0.10.1 2026-10-01 13:24:27 +01:00
Owner

Log safemode errors so that its easier for maintainers to see when a card is wrong

#554

Log safemode errors so that its easier for maintainers to see when a card is wrong #554
Log safemode errors
All checks were successful
Test / build (push) Successful in 1m15s
fa0f22525b
Vylpes changed title from WIP: Log safemode errors to Log safemode errors 2026-09-30 18:18:46 +01:00
Smithy-bot approved these changes 2026-10-01 12:03:09 +01:00
Smithy-bot left a comment

Approved — this cleanly addresses #554 and improves operator visibility when safe mode engages.

Highlights:

  • CardMetadataFunction now logs the full file: message string when enabling safe mode (not just the message), and reuses the same errorMessage for the API response.
  • resync correctly gates on result.IsSuccess instead of truthiness on the result object — an important fix so failed runs are handled and logged.
  • gdrivesync / resync user-facing copy now states that safe mode was activated and surfaces ErrorMessage in the reply.
  • Tests cover safe-mode logging, Config.SetValue, and parse-failure paths.

No merge blockers from my side.

**Approved** — this cleanly addresses #554 and improves operator visibility when safe mode engages. **Highlights:** - `CardMetadataFunction` now logs the full `file: message` string when enabling safe mode (not just the message), and reuses the same `errorMessage` for the API response. - `resync` correctly gates on `result.IsSuccess` instead of truthiness on the result object — an important fix so failed runs are handled and logged. - `gdrivesync` / `resync` user-facing copy now states that safe mode was activated and surfaces `ErrorMessage` in the reply. - Tests cover safe-mode logging, `Config.SetValue`, and parse-failure paths. No merge blockers from my side.
Vylpes merged commit 63017d77c2 into hotfix/0.10.1 2026-10-01 13:24:27 +01:00
Vylpes deleted branch feature/554-log-safemode-error 2026-10-01 13:24:27 +01:00
Sign in to join this conversation.
No description provided.