Skip to content

CI: apply-in-place - #43

Closed
pcarrier wants to merge 7 commits into
ci-basefrom
apply-in-place
Closed

pcarrier wants to merge 7 commits into
ci-basefrom
apply-in-place

Conversation

@pcarrier

Copy link
Copy Markdown

Fork CI for yas-run/yas apply-in-place.

Since yas-run#54 a command wait that runs out before any command it could
report on has started answers TIMEOUT (NOT_FOUND stays for an exited
terminal or an evicted index). The client_host test still expected
NOT_FOUND, so it failed on main.
Since yas-run#54 the server answers TIMEOUT when a command wait runs out before
any command it could report on has started; wait_terminal_command's
documentation still said NOT_FOUND, which stays for an evicted index or
an exited terminal.
APPLY WRITE_INLINE items take item flag APPLY_ITEM_IN_PLACE (2), offered
with CAPABILITY_APPLY_IN_PLACE (32): the item writes as COMMIT of a
STAGE_IN_PLACE stage does (open with create and truncate through a final
symlink, no temporary, no rename), through one shared write_in_place. An
in-place write onto a directory is CONFLICT with {EISDIR, open} in the
item's ApplyOsErrors entry, as COMMIT's. The flag is INVALID on other item
kinds and with APPLY_ITEM_CREATE_PARENTS; APPLY_ITEM_EXTENDED_FLAGS lists it
beside the v1 baseline's APPLY_ITEM_FLAGS.

yas-client's write_in_place sends it for content within the server's
inline limit and stages the rest, so a write tool call that already spends
a round trip resolving or reading the file takes two in all, not three.
TypeScript codec parity (inPlace) and golden vector
fs.apply.in_place.payload.
Review of yas-run#89: the mode an in-place write gives a file it creates is read
under cfg(unix) alone, so Windows' -D warnings build failed on dead_code
(Stage::mode had atomic_replace to read it). Windows files take their
directory's ACL; say so on the field. Rewrap yas.md's opt-in paragraph at 80
columns.
@github-actions

Copy link
Copy Markdown

Coverage

Crate Lines Functions Regions
alacritty-driver 85.6% (1081/1263) 89.4% (84/94) 89.3% (1746/1955)
browser 25.5% (309/1212) 30.4% (34/112) 27.7% (605/2183)
cli 31.8% (6517/20468) 32.8% (598/1824) 32.9% (9634/29263)
client 62.7% (4448/7089) 65.8% (582/885) 61.2% (5754/9400)
composite-transport 96.3% (526/546) 98.4% (60/61) 96.2% (884/919)
compositor 55.0% (11419/20763) 66.5% (838/1261) 54.8% (15820/28844)
desktop 78.4% (4460/5691) 71.6% (393/549) 75.1% (6211/8267)
edge 63.1% (800/1268) 50.9% (82/161) 58.0% (1043/1799)
fonts 77.3% (1257/1626) 82.7% (129/156) 78.9% (2424/3071)
fssync 86.0% (1609/1872) 85.8% (182/212) 87.0% (2833/3255)
git 70.4% (4462/6334) 68.5% (337/492) 67.3% (6313/9386)
guest 67.3% (6829/10148) 67.0% (488/728) 66.6% (8935/13416)
lsp 78.7% (3573/4542) 80.8% (336/416) 76.7% (5408/7054)
proxy 63.0% (1854/2943) 56.2% (180/320) 63.3% (2860/4521)
runtime-dir 93.6% (117/125) 100.0% (14/14) 94.8% (218/230)
sd-notify 73.9% (68/92) 100.0% (6/6) 83.2% (109/131)
server 70.2% (82689/117737) 72.7% (5982/8229) 68.1% (110312/161883)
ssh 67.2% (708/1054) 75.9% (85/112) 67.2% (1105/1645)
terminal-model 49.9% (314/629) 62.3% (38/61) 50.3% (505/1004)
uplink 94.2% (582/618) 92.6% (50/54) 93.1% (1062/1141)
webrtc-forwarder 33.6% (1321/3932) 44.9% (146/325) 36.0% (2279/6336)
webserver 80.7% (1490/1846) 81.1% (193/238) 83.2% (2551/3067)
website 35.1% (355/1012) 34.4% (53/154) 35.8% (607/1694)
xtask 0.0% (0/5149) 0.0% (0/131) 0.0% (0/9157)
yas 88.5% (27522/31082) 93.6% (2105/2249) 83.6% (43230/51722)
Total 66.0% (164310/249041) 69.0% (12995/18844) 64.3% (232448/361343)

@pcarrier

Copy link
Copy Markdown
Author

yas-run#89 merged.

@pcarrier pcarrier closed this Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant