Skip to content

Harden S3_PING remove() and removeAll() error handling - #663

Merged
rhusar merged 1 commit into
jgroups-extras:mainfrom
rhusar:s3-ping-remove-followups
Oct 8, 2026
Merged

rhusar merged 1 commit into
jgroups-extras:mainfrom
rhusar:s3-ping-remove-followups

Conversation

@rhusar

@rhusar rhusar commented Oct 8, 2026

Copy link
Copy Markdown
Member
  • remove(): log with String.format including the failed key instead of relying on a JGroups message bundle key
  • removeAll(): catch Throwable in the outer block so an Error does not escape into the view change; keep stack traces of per-object delete failures; fix misleading trace messages
  • Tests: assert on S3 invocations and logged errors, cover Error during listing, per-object delete failures and remove(); handle Object methods in the client proxy

- remove(): log with String.format including the failed key instead of
  relying on a JGroups message bundle key
- removeAll(): catch Throwable in the outer block so an Error does not
  escape into the view change; keep stack traces of per-object delete
  failures; fix misleading trace messages
- Tests: assert on S3 invocations and logged errors, cover Error during
  listing, per-object delete failures and remove(); handle Object methods
  in the client proxy

Signed-off-by: Radoslav Husar <rhusar@ibm.com>
@rhusar
rhusar merged commit 2b1b1b5 into jgroups-extras:main Oct 8, 2026
17 of 18 checks passed
@rhusar
rhusar deleted the s3-ping-remove-followups branch October 8, 2026 06:35
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.

1 participant