Skip to content

[pull] canary from vercel:canary - #1323

Merged
pull[bot] merged 4 commits into
code:canaryfrom
vercel:canary
Aug 21, 2026
Merged

[pull] canary from vercel:canary#1323
pull[bot] merged 4 commits into
code:canaryfrom
vercel:canary

Conversation

@pull

@pull pull Bot commented Aug 21, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

icyJoseph and others added 4 commits August 20, 2026 23:46
… settle (#97648)

This is a follow-up to #96116

If we're waiting a long time for your filesystem to settle, we should
show you the last modified path, so at least you can have an idea of why
this is happening.
…inks (#97395)

Another attempt at cleanup, similar to
#96955.

We need different information to write symlinks or junction points (most
notably, if it's a directory or not) than we get when reading symlinks.

We were trying to use the same data structure for both, but this lead us
to always call `get_type()` as part of reading a link, which was just
silly.

This also meant that `write_link` had to handle `NotFound` and
`Invalid`. `NotFound` is somewhat reasonable (just delete the file), but
`Invalid` is awkward.
@pull pull Bot locked and limited conversation to collaborators Aug 21, 2026
@pull pull Bot added the ⤵️ pull label Aug 21, 2026
@pull
pull Bot merged commit b2e835d into code:canary Aug 21, 2026
4 of 6 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants