Skip to content

Fix pty test in vscode integrated terminal - #4

Closed
abernardeau-wallix wants to merge 5 commits into
nextfrom
fix/vscode-pty-test
Closed

abernardeau-wallix wants to merge 5 commits into
nextfrom
fix/vscode-pty-test

Conversation

@abernardeau-wallix

Copy link
Copy Markdown
Collaborator

No description provided.

vanackere and others added 5 commits September 11, 2026 20:27
Refresh a host checkout's index on the host, after waiting out the
second `reset --hard` stamped it in, so no entry is left racily clean.
Otherwise the guest re-hashes every file on its first git command, over
virtio-fs, on every job.
Vendor ipstack 1.0.1 with a patch that resets a guest-bound flow whose
retransmissions are exhausted, instead of leaving it Established with a
permanent hole that stalls the guest for the rest of the job. Hold a
segment for six retransmissions (63s, up from the default three / 7s) so
a switch the host briefly fails to schedule no longer costs the flow.
A read-only share keeps its DAX windows across REMOVEMAPPING rather than
tearing each one down: the mapping cannot be written through, and the next
SETUPMAPPING replaces it in place. This drops nearly half the host mmaps
of a guest reading a large source tree. The read-write path instead merges
a batch's adjacent ranges into one mmap.
A share's window now maps only regular files at or above a size floor
(`dax=inode`) rather than every file: the guest mounts the share dax=inode and
the host flags the qualifying entries, since small files never repay a
mapping's cost. `vk run --dax`, x-virtkit.dax and [executor.vm] dax take
<size>:always for the old behaviour and <size>:inode=<min> to move the floor.
@abernardeau-wallix abernardeau-wallix changed the title Fix vscode pty test Fix pty test in vscode integrated terminal Sep 12, 2026
@abernardeau-wallix
abernardeau-wallix changed the base branch from main to next September 12, 2026 21:56
@vanackere
vanackere force-pushed the next branch 2 times, most recently from e51f414 to ad32833 Compare September 15, 2026 11:48
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.

2 participants