Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
More robust way to detect atomic move failure. Fixes #5415. #5416
It must have escaped my notice when improving the
@ahorek If you can confirm this works for you locally (I have confirmed it myself on MacOS) it would be a big help!
enebo left a comment
I think we should just put the EXDEV fix in this alone for 188.8.131.52 and then put the rest in after release. All our other string matches have been working for years without complaint and I don't want to add another variable of uncertainty for 184.108.40.206. 220.127.116.11 can hopefully have a little bake and we can have some confidence that the rest of this is solid (which I suspect it is but I am a bit paranoid this week).