Repository navigation
Upgrade CLI logging, diagnostics, and failure handling - #39
Merged
Merged
Conversation
szmyty
marked this pull request as ready for review
October 18, 2026 13:56
Pull Request Summary by devActivityMetricsAchievements
|
3 of 44 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mindcap currently mixes progress with result output, prints raw exception text, repeats every failed asset warning, and can count a partial sync archive as a successful capture. This gives CLI commands consistent timestamped diagnostics, safe error handling, and usable failure summaries.
--verbose,--debug,--quietand optional--log-file(before the command name), preserving capture/sync's existing local flags. JSONL logs append with owner-only permissions; diagnostic sessions restore handlers and close files after each command. Debug failures show sanitized frame locations without source lines or locals. Root/HTTP loggers remain untouched.Dependency: builds on Suno fix #38. Merge #38 first, then this PR. The PR targets main so it needs no manual base change. Logging-only comparison. Bookmark #37 remains separate and unmerged.
Validation on exact tree
384c432f88de98da6049affb328697551299a74c:No real credentials, Chrome profiles, source accounts or media downloads were accessed. Diagnostics can still include identifiers, titles and paths; they are not anonymous exports. Unrecognized-option usage errors may render text even when
--jsonis present; operational JSON results and errors use their documented channels. The cause of the maintainer's live Suno 403s still needs the diagnostic result requested in #38. No runtime dependencies or lockfiles change.GitHub Actions CI run 39132605708 passed on published head
5e818da7069c7891f29c5aa14c260acf1d36d0f2: dependency install/configuration, formatting, lint, full tests, architecture boundaries, wheel/sdist build, package-content validation and clean-tree checks. The published tree matches the locally tested tree exactly.