summaryrefslogtreecommitdiff
path: root/docs/next-daemon.md
Commit message (Collapse)AuthorAge
* docs/next-daemon.md: phase 6's upgrade by re-exec: the decisions at its ↵Gabriel Schneider2026-10-29
| | | | | | forks, what was found, the gates here and on the FreeBSD box, the startup A/B, and what is not done Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: Phase 5 part B terminal notes: what crosses and where ↵Gabriel Schneider2026-10-29
| | | | | | | | in the stream, the authority's steps batched, deltas in flight against the version last sent, the replica's terminal the authority's to the row, what a step reads sent before it, and the numbers ReleaseFast, 20 seeds of three clients at 30, 80 and 207 ms, the shell running a TUI, a session with clears and 8 MB of yes: no divergence, every terminal the authority's at quiescence and 23,508 deltas each the authority's screen at its version (and with a filled heap). Under the flood 72-76 deltas a second a replica (one in flight would be 4.8 at 207 ms), 10 KB/s of deltas and 101 KB/s of units a peer, encode a frame 15-16 us at three peers and 13-15 at one, apply 34-37 us p50. Bench 200x60: yes 65 KB/s a peer, apply 65-72 us (was 2.4 ms); varied text 356 KB/s, apply 0.47-0.49 ms. Local A/B against main within its runs; against base page-down and wheel are main's since. What is not done: kitty images, the units' bytes under a flood, the first text-mode step after a flood sending its history, a stale view slot the rollback copy follows (part A's), echo prediction. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: phase 2 on main with views and phase 5 part A: a slice ↵Gabriel Schneider2026-10-29
| | | | | | a len cuts, the drawn views' selections, and the gates again Co-Authored-By: Claude Opus 5.5 <[email protected]>
* dump: savePane puts back only the fields it changes, not a copy of the whole ↵Gabriel Schneider2026-10-29
| | | | | | 88 KB pane, and makes its empty undo history only for a slim record; the notes say what the small close after a big one measures Co-Authored-By: Claude Opus 5.5 <[email protected]>
* dump: a session's dump keeps every view, the ones not live parked again by ↵Gabriel Schneider2026-10-29
| | | | | | load; a session revived for one client is its live view alone, as view 0 Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: phase 2's upgrade (what a user loses: ZON dumps; the ↵Gabriel Schneider2026-10-29
| | | | | | store checked on a copy of a real one), the web shell, and the closes measured again Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: phase 2's gates and measurementsGabriel Schneider2026-10-29
| | | | Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: phase 2 notes (the walker dump, crossing builds, load ↵Gabriel Schneider2026-10-29
| | | | | | and revive, what the design missed); the GUI's Restore test keeps the dump's serial Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: Phase 5 part A notes: the copy put back where it was, ↵Gabriel Schneider2026-10-29
| | | | | | | | speculation checked against the authority's tape, each client in its own view, what release builds read unwritten, and the numbers Three clients typing 100 inputs a seed at 30, 80 and 207 ms RTT, a view each: no divergence and every replica on the authority's digest at quiescence (Debug 12 seeds, ReleaseFast with a filled heap 20, ReleaseFast timed 20, and 20 in one shared view). ReleaseFast, p50/p99: a speculative apply 35-54/168-183 us, a copy (1.3 MB) 75-94/198-447 us, a rollback 342-569/818-1561 us, the worst a tenth of a frame; rollbacks per input 31%, 76% and 129%, nearly all for another client's unit first, which views do not change (they change what a rollback shows); 2-7% mispredictions, every one a message's HH:MM:SS read in another second. rollback-bench: a typical session's copy 980 KB in 0.044 ms, put back in 0.036; a big one's 1.49 MB in 0.071, 0.051. What proved wrong (a 100 KB copy, rare mispredictions), what is not done (transport, the view's events at once, echo prediction, a single-threaded epoch), and fs.py's mounted-startup hang still on main, shown with main's own binary. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: Phase 5 groundwork notes: the replica socket's ↵Gabriel Schneider2026-10-29
| | | | | | | | decisions, the round trips locally, through the relay and to FreeBSD, and open points 3 and 5 decided (walker copy for rollback and for join, no fork) A ping through `ssh -L` to a session on the FreeBSD box costs its RTT (median 205 to 210 ms against a TCP connect's 206 to 208) and a hello two (411 to 476 ms: ssh confirms the channel before it forwards a byte); through the relay at 30, 80 and 207 ms they are the RTT plus 0.3 ms. A rollback copy is about 80 KB (typical) or 96 KB (big) once file texts and undo snapshots are pinned, 0.02 to 0.045 ms; a fork of 1 GB stalls the authority 13 to 20 ms here and 20 on FreeBSD, and every page it writes while the child lives costs ~1.3 us more, so a join takes the same walker copy and a worker streams it. The tty A/B against phase 1's tip is within its A/A runs. Still open marks points 3 and 5 decided. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* views: a terminal shown in a view shorter than it is passed down to its ↵Gabriel Schneider2026-10-29
| | | | | | | | | | | | cursor, a shell's prompt never out of sight, an arrow in the gutter where rows are above; a name drafted in a tag is the view's that opened it A terminal takes the size of the view that typed into it last; a shorter view used to show its top rows, the prompt below them cut. It now passes over as many as keep the cursor's row in sight, as tmux pans a bigger window in a smaller client: `Pane.pan` (per view, derived) is made in the step's sync and again when a view is drawn out of turn (views.unpark), by terminal.panFor (0 in the view that sizes it, in one tall enough, or folded), and read where the body's rows start: `Pane.scroll`, the body walk in tty mode, the visible cursor. One view never pans: the view that sizes a terminal returns 0 at its first test. A `.name` prompt (a file's name drafted in its tag) is the view's that opened it (`Pane.prompt_view`): another view's step, where that pane has not the keyboard, no longer drops it; its view closing does. views-pan.snap: a shell sized for a 24-row view, its last lines and prompt in a 12-row one under the arrow, then typed into from the short view and sized for it. A unit test: the short view's frame has the cursor's row, and the line on it, inside the pane. docs: the notes, the reference. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: phase 4's gates and perf (every cell inside its A/A), ↵Gabriel Schneider2026-10-29
| | | | | | and what is not done; ponytail marks for the shortcuts left (a paste shared by every terminal, a second window's hit test, one display density per process) Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs: views in the guide and reference (a session attached already takes ↵Gabriel Schneider2026-10-29
| | | | | | another view, up to four; Detach lets one go); phase 4 notes in docs/next-daemon.md; tty: Screen.hungUp reads a test terminal's fd as the test build has it Co-Authored-By: Claude Opus 5.5 <[email protected]>
* screen_state.zig: a terminal crosses to a replica as its screen's state, ↵Gabriel Schneider2026-10-29
| | | | | | ghostty's own records by content address, a delta a screen of row hashes and the blobs the peer lacks, history fetched by absolute row Co-Authored-By: Claude Opus 5.5 <[email protected]>
* tty: a flooded pane's output is drawn a frame a tick at most, two of its ↵Gabriel Schneider2026-10-29
| | | | | | reads queued at most, so it costs no frame a 4 KB read and holds no key or echo behind it Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: Phase 1 notes: the forks decided, what the census ↵Gabriel Schneider2026-10-29
| | | | | | | | | | | | | | | missed, what is deferred, and the gate's numbers How the tape and the walker came out (a tree at the host boundary, the replay a mode of the same binary, three replicas, digests per field), the annotations the walker needed (`len` besides local, derived and authority), the render-time writes moved into the step, the clock and host facts taped, the unit tests that had passed on a stale frame, and the two per-frame costs the A/B found and that are gone (the geometry key fed field by field, the paint-ahead worker started inside the render). The gate's numbers close it. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* daemon.zig: a forked session takes its stub's death, a SIGKILL too, as the ↵Gabriel Schneider2026-10-29
| | | | | | | | | | | | | | | | | | terminal's HUP and detaches PR_SET_PDEATHSIG (FreeBSD: PROC_PDEATHSIG_CTL) in the session child, cleared again at Detach so the stub's own exit then is no hangup; a stub dead before it was set hangs up at once. It is the HUP the signal thread already takes (blocked in every thread, sigwaited), and setsid does not touch it. An --attach stub is no parent of its session: one killed so still leaves the session drawing until the terminal closes or Detach. test/daemon.py kills a session's stub outright under a shell that keeps the terminal (on FreeBSD the session leader's exit revokes it), waits for the session to put the terminal back and detach, and attaches it again; without the death signal it times out. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* test/fs.py: a new +Pager each run, its colours through the theme until ↵Gabriel Schneider2026-10-29
| | | | | | | | | | | | | | | Filter, SYSTEMD_PAGER read by the shell, and no pager of the caller's Since 046979b8 (committed 2026-10-22) `pardes -` makes a new +Pager for each paged text, one already there keeping its page, and maps its colours through the theme as a terminal's until Filter shows them as sent; the test still expected one +Pager refilled and the colour as given. coreutils 9.12's printenv quotes a value with a blank on a terminal, so the shell prints SYSTEMD_PAGER instead. And a session's shells no longer inherit the caller's pagers: a PAGER naming the user's own pardes-gui ran instead of the binary under test. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* 9p_io.zig: a session's liveness is a flock on its socket's .lock, not a ↵Gabriel Schneider2026-10-29
| | | | | | | | | | | | | | | | | | | connect, which FreeBSD refuses to a full listen queue as to a dead socket The owner holds `<socket>.lock` flocked from before it binds until after it unlinks (claim, release; the fatal-signal path unlinks it too). The startup sweep, the registry sweep, a registry entry's replacement and `taken` ask that lock: held is live, free is dead. They unlink only while holding it, so no new owner comes between the judging and the unlink, and two starters of one name are told apart by who took it. A socket with no lock, a pardes from before the locks, is still judged by a connect. The daemon's own start was already decided by its flock. The sweep test gains a live session whose socket refuses connects on every system (bound, not listening, its lock held) and a dead one's free lock, which goes with it; it passes on the FreeBSD box now. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: FreeBSD notes, for phase 5 (building, deploying and ↵Gabriel Schneider2026-10-29
| | | | | | running on the box, what differs there, what 207 ms costs) Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs: the daemon, Detach, --attach and Adopt; phase 3 notes in ↵Gabriel Schneider2026-10-29
| | | | | | | | docs/next-daemon.md building.typ's detached sessions are the daemon and its sessions; the guide, cheatsheet and reference say what Detach, a closing terminal, --attach of each kind and Adopt do, and that attaching from another machine waits for phase 5. docs/next-daemon.md records the forks taken (sessions register and are not the daemon's children, and why; how it starts; masters; Adopt as a word; the stub's signals and job control; --detach; the Attach word; the harness switch), the known gaps, and the termios trap. Co-Authored-By: Claude Opus 5.5 <[email protected]>
* docs/next-daemon.md: the daemon and multi-client design, argued 2026-10-29 ↵Gabriel Schneider2026-10-29
(deterministic replicated core, kakoune-style views, one daemon per user, phases) Co-Authored-By: Claude Opus 5.5 <[email protected]>