Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Broadening the exception type from RToolsHCKActionError to RToolsHCKError will now also catch RToolsHCKConnectionError exceptions (including ServerError and EtherError). While this aligns with the PR's goal to handle server exceptions, it changes the behavior for all methods using handle_action_exceptions. Consider whether all connection errors should be uniformly treated as retriable action errors. If some connection errors require different handling, you might need a more nuanced approach that distinguishes between different types of connection failures.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's try to retry requests always and see how this will work in real system