diff options
| author | user <user@clank> | 2026-08-12 23:51:34 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-12 23:51:34 +0200 |
| commit | 8f5dc3904093c402c16eca835528f59fbb9851b3 (patch) | |
| tree | 7d8c04ead940d9645c18fc3bc12acffc66655de1 /docs | |
| parent | cli: survive a dead session, and a flaky terminal (diff) | |
| download | sl0ppi-8f5dc3904093c402c16eca835528f59fbb9851b3.tar.gz sl0ppi-8f5dc3904093c402c16eca835528f59fbb9851b3.tar.xz sl0ppi-8f5dc3904093c402c16eca835528f59fbb9851b3.zip | |
release: 0.1.1, and stop the CLI carrying a second version
Published 0.1.1 with the dead-session and flaky-read fixes.
Also removes the `sl0ppi-cli` line from MANIFEST and the version field from
cli/package.json: the CLI ships as part of the product, so a version of its own
only drifts -- a 0.1.1 release shipped a MANIFEST claiming sl0ppi-cli 0.1.0.
Records the terminal-level flakiness as a known issue with the measurements, so
it is a tracked defect rather than folklore: list-tabs/list-panes fail ~60% of
the time against a detached live session on a 2-vCPU box, ~25% with a client
attached, and the action client blames "no active session" for what is really a
transient enumeration failure.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/roadmap.md | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/docs/roadmap.md b/docs/roadmap.md index fc9b47b..77086ed 100644 --- a/docs/roadmap.md +++ b/docs/roadmap.md @@ -127,6 +127,27 @@ Guard rails worth knowing: --- +## Known issue: sl0ppij CLI actions are racy + +Measured on a 2-vCPU Debian box, against a **live** session: + +| | detached | client attached | +|---|---|---| +| `action list-tabs --json` | ~60% fail | ~25% fail | +| `action list-panes --json` | ~60% fail | ~25% fail | + +Failures are either an empty stdout with exit 0, or `There is no active +session!`. The action client calls `get_active_session()` before it consults +`-s`, so a transient enumeration failure looks like "no session at all". + +The CLI works around it (idempotent reads are retried with backoff, which took +`sl0ppi ls` from failing most runs to 8/8), but the fork should be fixed: any +consumer of `zellij action` on a slow machine will hit this, and most will +conclude their session is dead. + +Not yet investigated: whether it reproduces upstream, and whether it is a +socket-connect timeout or a race in session enumeration. + ## Standing risks **`sl0ppij/target` is a symlink to `~/lol/zellij/target`.** Introduced when the |
