Closed leonerd closed 10 years ago
Still happening occasionally with
Net::Async::HTTP = 0.32 Net::Async::Webservice::S3 = 0.17 SocialFlow::S3 = 0.03+bzr224
I suspect this may be a missing timeout option somewhere along the lines. I think I'll hunt for it by updating the unit tests to assert that a timeout or stall_timeout is definitely supplied to every S3 call.
I believe now fixed by b3dfa361aff4db34085f71cb7d9c662ccb78ea75
Occasionally files will just stall at 0-bytes progress during a tree 'pull', requiring the command to be SIGINT'ed and restarted. I suspect some timeout logic isn't happening in NaHTTP at some critical stage.