Bug #5327

[SDK] CLI tools should catch socket errors like "Connection refused"

Added by Peter Amstutz over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
SDKs
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
0.5

Description

Common SDK errors like "connection refused" should be reported to the user in a friendly fashion instead of resulting in a crash and a stack trace.

History

#1 Updated by Peter Amstutz over 4 years ago

  • Story points set to 0.5

#2 Updated by Peter Amstutz over 4 years ago

  • Description updated (diff)

#3 Updated by Brett Smith over 4 years ago

  • Target version changed from Bug Triage to Arvados Future Sprints

I feel like it would be helpful to define a bigger picture strategy for catching and reporting SDK exceptions in our CLI tools. There's a lot that can go wrong besides socket errors, and it seems like if we figure out our desired approach, we can apply that consistently across all kinds of handleable exceptions without much extra effort.

#4 Updated by Brett Smith over 4 years ago

  • Category set to SDKs

And this may be out of scope, but given that patterns are starting to emerge in our tools, it doesn't seem totally unreasonable to start abstracting out a CLIToolBase class or something like that, which other tools can derive from. Having a common source for our common tasks like command-line parsing and error handling is starting to feel worthwhile.

Also available in: Atom PDF