What to try first
- Confirm you opened the intended workspace.
- Confirm the space name is valid and already exists.
- Retry after the current operation finishes (or close other Rinne instances).
- If integrity is mentioned, run verify. If cleanup or staged trash is mentioned, run gc.
- If it’s an OS error, check permissions and free disk space.
Errors are part of normal operation — Rinne stops early when it can’t guarantee a correct result. It prints a clear message and exits with a structured code so you can fix the cause and retry safely.
Rinne does not guess or auto-create state on failure. For example, a missing space stays an error — you create and manage spaces explicitly so history remains predictable.
Exit codes
v0.9.6 uses a unified exit-code set across CLI commands. Desktop workflows map cancellation and failure states to the same categories where applicable.
| Code | Name | Meaning |
|---|---|---|
0 | Success | The command completed successfully. |
1 | Failure | General command failure. |
2 | UsageError | Invalid arguments, invalid option combinations, or command usage errors. |
3 | BusyOrLocked | Another operation is running or the workspace lock is held. |
4 | NotFound | Required workspace, space, snapshot, path, or stored object was not found. |
5 | SafetyBlocked | The command stopped because a safety condition was not satisfied. |
6 | CheckFailed | Integrity, validation, verification, or precondition checks failed. |
99 | Fatal | Unexpected fatal error. |
130 | Canceled | The operation was canceled, including Ctrl+C style cancellation. |
Common causes
- Workspace not opened / workspace not found
- You’re outside the intended workspace, or required workspace metadata is missing.
- Space not found
- The specified space does not exist (Rinne won’t create it automatically).
- Busy / locked
- Another operation is running, or a lock is held.
- Ignored by rinneignore
- The selected file or directory is excluded by
rinneignore.json, so a scoped save cannot include it. - Permission / path issues
- Access denied, read-only files, or OS path limitations.
- Storage / I/O errors
- Disk full, device errors, unstable drives, or interrupted reads.
- Integrity problems
- Verification failed, or snapshot metadata / stored content could not be validated.
Reporting
If you’re stuck, include the full error message and the exact command line when reporting an issue.
Early Access note: messages may evolve as Rinne adds features. The v0.9.6 exit-code categories are intended to remain script-friendly. The principle stays the same: stop early when correctness can’t be guaranteed.