[#340] Fix encode object acl #356
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#356
Loading…
Reference in a new issue
No description provided.
Delete branch ":bugfix/340-flaky_test_put_object_acl"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
close #340
In the process of encode the acl of an object,
we use a map. As a result, when traversing the
map, we can get a different sequence of permissions
each time. Therefore, a list is used instead of a map.
Signed-off-by: Roman Loginov r.loginov@yadro.com
@ -1665,3 +1695,3 @@
}
for key, val := range m {
for _, val := range m.list {
Maybe we can just add the following
after this loop and don't introduce
accessList
?I've been thinking about it, and it will really solve the problem with the test. However, if we imagine a situation where we have several acl records for different users on the same object, then the order of records will still be non-deterministic. As far as I know, in aws s3, records are output (get-object-acl) in the order in which they were added, despite the fact that functionally it doesn't seem to affect anything. If it still doesn't matter to us, then of course it's better to use sorting.
Ok, let's keep current approach. But simplify a little:
0e2819b07f
tod1f4941b63
d1f4941b63
to08dd6aff41