Latest Results
more reviewsbenedikt-bartscher:explicit-event-id-minification cleanupbenedikt-bartscher:improve-compile-perf reviewbenedikt-bartscher:improve-compile-perf reviewbenedikt-bartscher:explicit-event-id-minification fix(cloud): preserve an unreadable hosting config instead of replacing it
Follow-up review caught a regression from the atomic-write change:
`_read_hosting_config` swallowed read errors and returned `{}`, so
`delete_token_from_config` replaced a malformed config with `{}`,
destroying the token and project it could not parse. On main the read and
the write shared one try block, so a parse failure aborted before the
write. Confirmed against a main worktree: main leaves the malformed file
untouched, this branch emptied it.
`_read_hosting_config` now returns `{}` only for a missing file and
propagates read and parse errors. `delete_token_from_config` lets those
reach its existing handler, so an unreadable config is left alone.
`save_token_to_config` keeps its previous fallback of starting from an
empty config, so a corrupt file cannot block re-authenticating.
`token --clear` verified removal through a lookup that treats an
unreadable config as "no token", so it could report success while the
token was still on disk. It now reads the config directly through
`stored_access_token`, which distinguishes absent from unparseable, and
fails on either kind of unconfirmed removal.
The `--print` stdout test mocked the very helper whose debug records
contaminate stdout, so it passed with or without the fix. It now writes a
real config and exercises the lookup; verified it fails without the fix.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Latest Branches
+14%
benedikt-bartscher:explicit-event-id-minification 0%
harsh21234i:fix/wrap-recharts-sankey-6558 +6%
benedikt-bartscher:improve-compile-perf © 2026 CodSpeed Technology