Richer workspace-sync failure logging in software-factory#5259
Merged
Conversation
On a failed sync, emit a structured, attributed trace — the pushed/pulled/ deleted/conflict counts, the realm-server JSON:API error payload, and any skipped conflicting paths — instead of "see prior log lines". This leaves a usable record on the factory's own log channel without scraping the CLI's interleaved progress output, and it's always on (no flag), so it works whether or not anyone anticipated the failure. Replaces the forensic intent of the dropped --halt-on-sync-error flag without sacrificing pull-recovery. CS-11575 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
backspace
approved these changes
Jun 17, 2026
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
2 participants
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.
During my software factory test runs I got a 500 server error when using the atomic write endpoint. I didn't succeed in reproducing this but I want to add informative logging in case that happens again.