Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

isChownNeeded bad when only user/group (!both) set #1652

Merged
merged 1 commit into from
Oct 4, 2022

Conversation

eikenb
Copy link
Contributor

@eikenb eikenb commented Oct 3, 2022

isChownNeeded returned the wrong result if either (exclusive) user or group were set but not the other. It uses a guard value but only compares both at the start and doesn't take this into account on the final comparison which compares both against the current values.

IE. it always returns true in these cases as the guard value is never going to be the same as an real file value.

Fixes #1651

isChownNeeded returned the wrong result if either (exclusive) user or
group were set but not the other. It uses a guard value but only
compares both at the start and doesn't take this into account on the
final comparison which compares both against the current values.

IE. it always returns true in these cases as the guard value is never
going to be the same as an real file value.
@eikenb eikenb added the bug label Oct 3, 2022
@eikenb eikenb added this to the v0.30.0 milestone Oct 3, 2022
@eikenb eikenb requested a review from a team October 3, 2022 20:31
@eikenb eikenb merged commit 0bb9fc2 into main Oct 4, 2022
@eikenb eikenb deleted the issue-1651-ischown-fix branch October 4, 2022 17:53
@eikenb eikenb modified the milestones: v0.30.0, v0.29.5 Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

unexpected respawn with user set
1 participant