umputun / agterm / 37034045107
94%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 180
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
coverage: 93.704%. Remained the same
37034045107

push

github

web-flow 
fix(split): re-apply the divider when the split's length changes (#692)

* fix(split): re-apply the divider when the split's length changes

Halving a wide window in one step left one pane of a left/right split
at zero width. SwiftUI's HSplitView redistributes a resize by its own
rule: once the new split length drops below the second pane's current
width, the primary pane gets nothing and the second takes the whole
split. Shrinking in small steps never crosses that point, and a plain
NSSplitView stays proportional. The model kept the stored ratio, and
the zero-width pane was never resized, so its pty kept the old column
count.

SplitProbeView already re-applied the stored ratio when the safe-area
inset changed under the split. It now records the axis length next to
the inset and re-arms on a change in either, from layout() and from
the split's resize notification, with the same deferred apply and the
same skip while a divider drag is live.

Measured in an isolated Debug instance, 1600 to 800 points wide in one
window.resize: before, 84/84 columns became 84/70 with the left pane
stale; after, 34/34, and 49/118 became 19/48 at ratio 0.3. Widening
back returns the original widths.

The report's Magnet case hides the right pane and the reason for that
difference is unknown. Re-applying the stored ratio restores either
pane, so the fix does not depend on it.

Hosted tests cover shrink/grow/shrink cycles at 0.5 and 0.3 with the
primary pane forced to zero, the layout entry, a suspended probe, and
a divider drag after a resize. The new SplitRatioUITests case halves a
left/right split through window.resize and reads both panes' pty
widths. It fails on the unfixed accessor with 84/70 and passes with
the fix.

Related to #691

* docs: hosted tests can be blocked along with the XCUITest runner

The runner note said hosted agtermTests are unaffected. On 2026-10-02
the hosted suite stalled before its first test case while the UI
runner timed out enabling automatio... (continued)

14629 of 15612 relevant lines covered (93.7%)

2613882.51 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37034045107.1 180
93.7
GitHub Action Run
Source Files on build 37034045107