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

container: Check eACL input in setEACL method's implementation #330

Merged

Conversation

cthulhu-rider
Copy link
Contributor

@cthulhu-rider cthulhu-rider commented Apr 10, 2023

Previously `setEACL` method could throw `invalid offset` fault exception
about invalid eACL argument. This message is too generic, may occur in
different places of execution code and doesn't help caller to realize
the reason. To improve user experience, it's worth to check method
arguments before slice instructions.

Pre-check `eACL` slice length in `SetEACL` method implementation and
throw responsive panic message.

Ref nspcc-dev#329.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
`SetEACL` method imposes requirements on the eACL parameter of a generic
byte array type. These requirements should be described in the
documentation as user manual.

Ref nspcc-dev#329.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
@roman-khimov roman-khimov added this to the v0.18.0 milestone Apr 10, 2023
@roman-khimov roman-khimov merged commit cfa470a into nspcc-dev:master Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants