Bug #9990

[Workbench] configurable timeout for API requests

Added by Tom Clegg over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Workbench
Target version:
Start date:
09/08/2016
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-

Subtasks

Task #10060: Review 9990-workbench-client-timeoutResolvedRadhika Chippada


Related issues

Has duplicate Arvados - Story #9974: [Workbench] All receive_timeout to be configurableClosed09/07/2016

Associated revisions

Revision bc8f7abd
Added by Tom Clegg over 4 years ago

Merge branch '9990-workbench-client-timeout' closes #9990

History

#1 Updated by Tom Clegg over 4 years ago

9990-workbench-client-timeout @ a0f073cc

#2 Updated by Tom Clegg over 4 years ago

  • Target version set to 2016-09-28 sprint

#3 Updated by Radhika Chippada over 4 years ago

a0f073cc

  • Wondering if calling "api_client_connect_timeout" as "api_request_connect_timeout" ... might be more intuitive
  • (I noticed there were no tests), so (after merging master) tested manually adding some lag on api server end and the functionality works and timeout errors are received

LGTM

#4 Updated by Tom Clegg over 4 years ago

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

Applied in changeset arvados|commit:bc8f7abd8a5d32ac8c67130b7a490d32089115af.

Also available in: Atom PDF