diff options
Diffstat (limited to 'docs/next-daemon.md')
| -rw-r--r-- | docs/next-daemon.md | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/docs/next-daemon.md b/docs/next-daemon.md index ef1b868d..5537bf1a 100644 --- a/docs/next-daemon.md +++ b/docs/next-daemon.md @@ -4509,3 +4509,38 @@ After the line, a window that joined late: `--window-clients`; ReleaseSafe `test/daemon.py` 20 cycles and `--window-clients`: all pass. The box soak, ReleaseSafe at both ends: 0 rejoins in six of seven clients, the seventh's the query pane's above. + +After it, the query pane's two: +- **A speculated Enter panicked in `Query.land`** (`f.location_rows[c + + 1]`, `index 1, len 0`: win207-4 after its rejoin). An edit of a frozen + query pane's rows drops them with the text they were of + (`setContentSpan`'s dropped marks), while its items and its current row + stay, and a later search in the pane keeps them so in its `saved` for an + Esc. `land` indexed the rows by the current item all the same; every + other reader of them asks first. In the soak it was line 1 of a live pane + (another view's SPC b b and Esc, and the window's own keys, in another + order than the session took them), which the session never ran: the + input panicked before it was sent. A session's own keys reach it too: + SPC b b, Enter, then `jxd` on the pane's rows and Enter. + - Fix: a current item without its row is none: the keyboard to the + owner, as with no current row. + - Test: Query.zig's "Enter on a frozen query pane's rows after its text + was edited: no row to land on, the keyboard to its owner". Main panics + in it. +- **A window joined from a dump made a `/` query's rows plain where its + session had coloured them** (`pane 21.file.location_rows`, win207-4's + `/r`, unit 4/447: the session's tape had the same host answers). A hit + row's colours are the owner's highlights where a frame painted them, + else the locations cache's: both derived, made by what the process has + drawn and painted, and a joiner has neither. + - Fix: a row's colours are in no digest (Row's own `digest`); a dump + still keeps them. They are how a row looks, not where it points. + - Test: replica.zig's "a client joined from a dump makes a `/` query's + rows as the session does, though only the session has drawn its + owner". Main fails it at `pane 1.file.location_rows`. +- **Gates** (on nopmlypk): Debug `core-test` tty, `replay`, `replicas` + (none diverged or unequal), `test/daemon.py` 20 cycles and + `--window-clients`; ReleaseSafe `test/daemon.py` 20 cycles and + `--window-clients`; the box soak, seed 7, ReleaseSafe at both ends, 21 + min and six clients (late windows and a late terminal among them): no + rejoin, no differing check, no panic. All pass. |
