You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a change in behavior of os.RemoveAll on tip compared to 1.11.2, on macOS (and Linux, BSDs), caused by CL 146020, in a specific scenario. I can't definitively say whether this change should considered a bug/regression, or if it's a normal intentional new behavior, so marking as NeedsDecision.
Prior to CL 146020, it was possible to use os.RemoveAll to remove an empty directory without read permissions, because its code had a "Simple case" as the first thing it tried:
dmitshur
added
NeedsFix
The path to resolution is known, but the work has not been done.
and removed
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
labels
Dec 12, 2018
There is a change in behavior of
os.RemoveAll
on tip compared to 1.11.2, on macOS (and Linux, BSDs), caused by CL 146020, in a specific scenario. I can't definitively say whether this change should considered a bug/regression, or if it's a normal intentional new behavior, so marking as NeedsDecision.Prior to CL 146020, it was possible to use
os.RemoveAll
to remove an empty directory without read permissions, because its code had a "Simple case" as the first thing it tried:So the Go program https://play.golang.org/p/68OMhP1VS7G printed
temp file was removed: true
.The new
os.RemoveAll
code after CL 146020 tries to read the directory before performing the "simple case", and returns a permission error instead:/cc @ostenbom @ianlancetaylor
The text was updated successfully, but these errors were encountered: