You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Broken SVN external can freeze primary graph updates #1119
The SVN observer currently produces one aggregate process/parser outcome. Any nonzero svn status exit or uncertain parse rejects the full observation. If one materialized external is broken, otherwise complete primary-working-copy edits cannot trigger graph synchronization until that external recovers.
This is a residual from the SVN auto-watch design in #1113.
Suggested direction
Track primary and external completeness/contributions separately. Preserve each incomplete external's last acknowledged contribution while allowing a complete primary observation to synchronize, and keep the external retry pending. Add real file/directory external fixtures with external-only failure.
Thanks for separating this from the primary SVN observer work. I have classified it as a 0.9.2-rc follow-up task linked to #1113/#1127. Because #1127 currently claims a broken external cannot block primary synchronization, the PR review will treat this as a correctness blocker unless that claim and external participation are removed from the initial scope. The fixture needs independent primary and external completeness plus retry state.
Thank you for separating primary working-copy progress from a broken external. I have no new resolution or scope decision to report; the external-failure claim still needs to match the behavior and coverage actually delivered.
Activity
DeusData commentedon Jul 16, 2026
Thanks for separating this from the primary SVN observer work. I have classified it as a 0.9.2-rc follow-up task linked to #1113/#1127. Because #1127 currently claims a broken external cannot block primary synchronization, the PR review will treat this as a correctness blocker unless that claim and external participation are removed from the initial scope. The fixture needs independent primary and external completeness plus retry state.
DeusData commentedon Oct 19, 2026
Thank you for separating primary working-copy progress from a broken external. I have no new resolution or scope decision to report; the external-failure claim still needs to match the behavior and coverage actually delivered.