Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TransferUtility hangs in WAITING_FOR_NETWORK #70

Closed
corbt opened this issue Oct 20, 2015 · 5 comments
Closed

TransferUtility hangs in WAITING_FOR_NETWORK #70

corbt opened this issue Oct 20, 2015 · 5 comments
Labels
bug Something isn't working question General question

Comments

@corbt
Copy link

corbt commented Oct 20, 2015

I noticed that on flaky connections TransferUtility uploads sometimes were stalling forever.

I've managed to reproduce the issue by doing the following:

  1. Begin an upload with TransferUtility
  2. Turn wifi off for an extended period of time (5-10 minutes)
  3. Turn wifi back on

During the time that wifi is off, the transfer remains in the WAITING_FOR_NETWORK state indefinitely, as expected. However, on turning wifi back on (and confirming connectivity in other apps, etc), the transfer does not resume as expected.

I've also noticed this behavior (transfer stuck waiting eternally) on flaky networks, which is why I began investigating it in the first place. The transfer is never resumed -- I left one waiting for several days, actually, and it didn't ever resume.

@fosterzhang fosterzhang added the question General question label Oct 20, 2015
@fosterzhang
Copy link
Contributor

Thanks for reporting this issue. We are researching this issue and will get back to you ASAP.

@jitendraramoliya
Copy link

Fosterzhand, Please! provide solution on this issue ASAP.

@fosterzhang fosterzhang added the bug Something isn't working label Dec 10, 2015
@fosterzhang
Copy link
Contributor

The service stops itself after a period of inactivity, say no active transfers. When network is off, all transfers are on hold, and the service thinks it should stop itself. However it'd better stay active till the network comes back. I'll fix it in the next release.

@fosterzhang
Copy link
Contributor

This has been fixed in v2.2.10 release. Please check out the release notes.

@corbt
Copy link
Author

corbt commented Jan 7, 2016

Great, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question General question
Projects
None yet
Development

No branches or pull requests

3 participants