Bug #5836

[API] Remote API error messages should make it clear that they are remote.

Added by Misha Zatsman over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Misha Zatsman
Category:
SDKs
Target version:
Start date:
04/28/2015
Due date:
% Done:

100%

Estimated time:
Story points:
0.5

Description

When the API server returns an error indicating that it is out of memory, the go sdk client code returns an error whose Error() method returns "#<NoMemoryError: failed to allocate memory>"

In addition to the actual error message returned by the server, it should also give context to indicate that this error message was returned by the api server, and might as well print the returned status and message too.

As stated in http://blog.golang.org/error-handling-and-go :

It is the error implementation's responsibility to summarize the context. The error returned by os.Open formats as "open /etc/passwd: permission denied," not just "permission denied."

Associated revisions

Revision a4211acb
Added by Tom Clegg over 6 years ago

Merge branch '5836-remote-api-server-errors-made-obvious' closes #5836

History

#1 Updated by Ward Vandewege over 6 years ago

  • Target version set to 2015-05-20 sprint

#2 Updated by Ward Vandewege over 6 years ago

  • Subject changed from Remote API error messages should make it clear that they are remote. to [API] Remote API error messages should make it clear that they are remote.

#3 Updated by Tom Clegg over 6 years ago

  • Status changed from New to In Progress
  • Story points set to 0.5

#4 Updated by Tom Clegg over 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Applied in changeset arvados|commit:a4211acb465bd42869bf2a2f9fad6ff2c5e518e0.

Also available in: Atom PDF