Skip to content

fix(cli): stop watch after terminal sync failures - #47

Merged
hhhjin merged 1 commit into
hjinco:mainfrom
algiadev8:fix/cli-watch-terminal-sync-stop
Sep 30, 2026
Merged

hhhjin merged 1 commit into
hjinco:mainfrom
algiadev8:fix/cli-watch-terminal-sync-stop

Conversation

@algiadev8

Copy link
Copy Markdown
Contributor

Summary

When synch watch hit a terminal sync condition, the sync loop could stop while the CLI kept running and waiting for a signal. That left users with a live watch process but no further sync activity; remote vault and storage quota stops also had no CLI explanation.

This change makes the sync engine report terminal stop reasons to the CLI. synch watch now prints the reason and exits with status 1 for remote vault unavailability, sync history mismatch, or remote storage quota exhaustion. Transient connection failures continue to retry with backoff. SIGINT/SIGTERM handling starts after initial connection and sync, so a stalled startup does not swallow Node's default signal termination.

Validation

  • pnpm -C apps/cli typecheck
  • git diff --check

@hhhjin
hhhjin merged commit a06b5f6 into hjinco:main Sep 30, 2026
4 checks passed
@algiadev8
algiadev8 deleted the fix/cli-watch-terminal-sync-stop branch October 6, 2026 01:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants