• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

umputun / agterm / 44577526131
94%

Build:
DEFAULT BRANCH: master
Ran 19 Nov 2026 05:39PM UTC
Jobs 1
Files 379
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

19 Nov 2026 05:28PM UTC coverage: 94.423% (-0.02%) from 94.44%
44577526131

push

github

umputun
fix(zmx): keep a session's last output when its shell exits

A session whose command prints and exits lost the end of its output when
the terminal was not reading at that moment, as on a Live `session new
--command ... --wait` pane. The attach client returned at the daemon's
hangup with output it had read but not written, and with output still
queued behind the hangup. The daemon made at most one more write per
client at the PTY's EOF, and shutdown freed the rest.

Patch 0007:
- A hangup with the session's socket still in place, a detach or a
  daemon that died, returns as before. After any other the client reads
  the socket to EOF and writes stdout until both are done, reading the
  socket only while stdout keeps up, under one 2 s deadline; on a
  terminal it stops 200 ms short of it so the reset fits under it.
- The client leaves its terminal through loop.leaveTerminal: TCSAFLUSH
  once the terminal has taken the output; otherwise the output is
  flushed and termios restored with TCSANOW, since on macOS TCSAFLUSH
  and the exit's close of the tty wait for a terminal that may never
  read. A reset not taken by the deadline is flushed too. The attach a
  session switch returns through shares the deadline.
- After the hangup a signal ends the client's poll, so its timeout is
  recomputed from the deadline.
- On a shell exit the daemon keeps sending what its clients have not
  read, until none is left or one 2 s deadline shared by all of them
  passes, and takes no new attach, input or command meanwhile. A kill
  ends it at once.

Zig tests run the real daemon and client loops on threads: a reader that
resumes gets the final mark and the whole payload, one that never reads
again ends both on their deadlines, a draining daemon ignores a late
attach, type and run but takes a kill, and a detach returns as before.
leaveTerminal is driven with a recording terminal, the reset write under
signals, and the output queue wait on a macOS pty.

Related to discussi... (continued)

33100 of 35055 relevant lines covered (94.42%)

1962106.93 hits per line

Coverage Regressions

Lines Coverage ∆ File
2
87.97
-1.5% agtermCore/Sources/agtermCore/PresentationStream.swift
2
97.01
-1.49% agtermCore/Sources/AgtermServerKit/ServerActions+Recent.swift
1
97.6
-0.8% agtermCore/Sources/agtermCore/CatalogHub.swift
1
96.71
-0.47% agtermCore/Sources/agtermCore/PasteBundle.swift
1
89.09
-0.36% agtermCore/Sources/AgtermServerKit/ServerStreams.swift
Jobs
ID Job ID Ran Files Coverage
1 44577526131.1 19 Nov 2026 05:39PM UTC 379
94.42
GitHub Action Run
Source Files on build 44577526131
  • Tree
  • List 379
  • Changed 6
  • Source Changed 0
  • Coverage Changed 6
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #44577526131
  • 603e53f0 on github
  • Prev Build on master (#44530108098)
  • Next Build on master (#44582824205)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc