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
bpf: remove Map.DeleteWithErrno()
#10058
Conversation
test-me-please |
test-me-please |
20e69bd
to
67477e1
Compare
test-me-please |
@joestringer PTAL, there was an issue with |
67477e1
to
f5b42b9
Compare
test-me-please |
vm provisioning fail, will trigger the tests again |
test-me-please |
f5b42b9
to
7835747
Compare
Rebased against |
test-me-please |
`Map.Delete()` now wraps the underlying errno when returning an error. Therefore, `Map.DeleteWithErrno()` is rendered obsolete as checking for an error of type `syscall.Errno` can now be done using `errors.Is()` or `errors.As()` with the error returned by `Map.Delete()`. Signed-off-by: Robin Hahling <robin.hahling@gw-computing.net>
7835747
to
0d0eb3f
Compare
vm provisioning failed again :( |
test-me-please |
Map.Delete()
now wraps the underlying errno when returning an error.Therefore,
Map.DeleteWithErrno()
is rendered obsolete as checking for an error of typesyscall.Errno
can now be done usingerrors.Is()
orerrors.As()
with the error returned byMap.Delete()
.Fixes #8324
This change is