Bug #13542

No timeout is specified in A.C.R or as a default in the python sdk

Added by Thomas Hickman about 2 years ago. Updated 8 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Thomas Hickman
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

When constructing a new api object, if no http argument is passed into the api function no timeout is used (https://github.com/curoverse/arvados/blob/52be0992a572473171d3fe9f0b4182f67201f052/sdk/python/arvados/api.py#L222). When the api is used in A.C.R (https://github.com/curoverse/arvados/blob/52be0992a572473171d3fe9f0b4182f67201f052/sdk/cwl/arvados_cwl/__init__.py#L804), a http argument is not passed through, so no timeout is used.

Associated revisions

Revision f159fab8
Added by Peter Amstutz almost 2 years ago

Merge branch 'wtsi/python-api-timeout' refs #13542

Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <>

Revision 490f5378 (diff)
Added by Peter Amstutz almost 2 years ago

Add http_timeout to runtimeContext refs #13542

Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <>

History

#2 Updated by Tom Morris about 2 years ago

  • Target version set to To Be Groomed

#3 Updated by Peter Amstutz 8 months ago

  • Status changed from New to Resolved

#4 Updated by Peter Amstutz 8 months ago

  • Target version deleted (To Be Groomed)

Also available in: Atom PDF