download hangs with too small timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-swiftclient |
New
|
Undecided
|
Unassigned |
Bug Description
I think the cli used to require timeouts to be integers, so maybe this got worse recently, but with small enough timeouts values python-swiftclient seems to hang on download
vagrant@
liarliar [auth 0.006s, headers 0.099s, total 0.343s, 31.151 MB/s]
real 0m1.206s
user 0m0.347s
sys 0m0.521s
vagrant@
liarliar [auth 0.006s, headers 0.089s, total 0.391s, 27.268 MB/s]
real 0m1.252s
user 0m0.337s
sys 0m0.531s
vagrant@
^C Aborted
real 0m6.048s
user 0m0.326s
sys 0m0.423s
Trying to get the stacks for a hung process with https:/ /github. com/tipabu/ python- stack-xray/ blob/master/ python- stack-xray, I triggered a segfault:
[New LWP 49621] 64-linux- gnu/libthread_ db.so.1" . abstimed_ wait_common64 (private=<optimized out>, cancel=true, abstime= 0x7fff04f845d0, op=137, expected=0, futex_word= 0x55a4dda7d760) at ./nptl/ futex-internal. c:57 futex-internal. c: No such file or directory.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
__futex_
57 ./nptl/
No symbol "PyGILState_STATE" in current context.
Thread 1 "swift" received signal SIGSEGV, Segmentation fault. SimpleString) will be abandoned.
0x000055a4dc0dd13f in ?? ()
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(PyRun_
When the function is done executing, GDB will silently stop.
History has not yet reached $1.
[Inferior 1 (process 49620) detached]
Might take a bit to figure out what we're actually waiting on :-/