weixin_39801714
weixin_39801714
2021-01-03 04:40

Push timesout...and I've no idea why.

Describe the bug

This is related to #6242

I work in two places, one has no problem pushing. The other will often timeout when pushing. To the point that I often switch using my phone as a hot spot to get around it. This works but its killing my data plan!

Oddly at this place I have plenty of internet speed, its not metered and works good enough to run everything else I need. Ok so sometimes zoom will have a complaint every now and then about the connection but it copes. Amplify on the other hang often hangs and the times out. I don't understand why. At the time it hanged I did a speed test and had an upload speed of 18+Mbps.

It tries to upload the files and then 2 minutes later will error like so:

image

Switch to my phone and no issues. What could it be?

The logical answer is "this is a issue with your setup" but what on earth could that be? Is there anything in the code that might explain this happening? If it zips everything up I don't see how it could timeout, it can't be that big! Plus it works sometimes but not others so its not like there is a firewall here blocking something. Totally puzzled.

Amplify CLI Version

v4.40.1

To Reproduce

Fly to my girl friends house and try to push...

Expected behavior

It works like it does at home...

Desktop (please complete the following information): - OS: the dreaded Windows

Additional context Add any other context about the problem here.

该提问来源于开源项目:aws-amplify/amplify-cli

  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享
  • 邀请回答

7条回答

  • weixin_39801714 weixin_39801714 4月前

    The dodgy connection (which seems to be behaving itself at the mo): image

    Mobile:

    image

    My home one will have to wait until tomorrow :)

    点赞 评论 复制链接分享
  • weixin_39716521 weixin_39716521 4月前

    Were you able to push with the network having no packet loss at the moment right now?

    点赞 评论 复制链接分享
  • weixin_39801714 weixin_39801714 4月前

    yep, pushing again now to test again. If it happens again I'll run the same report, is that best way to narrow this down? I know its a tricky one to get to the bottom of an likely its at my end...but network stuff really isn't a strong point for me :)

    点赞 评论 复制链接分享
  • weixin_39716521 weixin_39716521 4月前

    Yeah, we tried solving for this problem a few months back - https://github.com/aws-amplify/amplify-cli/pull/5158 by chunking down the files to be uploaded to S3 to avoid seeing this issue. But I think we need to come up with a better retry strategy as mentioned by out here - https://github.com/aws-amplify/amplify-cli/issues/4183#issuecomment-624835043 for this problem.

    点赞 评论 复制链接分享
  • weixin_39716521 weixin_39716521 4月前

    Closing this issue - please let us know if you're still seeing this often with a reliable network connection. We're tracking the retry work I mentioned above as a part of this issue - #4183

    点赞 评论 复制链接分享
  • weixin_39989190 weixin_39989190 4月前

    -amplify/amplify-cli mentioned that this may be related to https://github.com/aws-amplify/amplify-cli/issues/4113.

    : I'd be curious if you ran some tests on the three networks (third being your mobile hotspot.) What is the ping / bandwidth of each one? Are you seeing packet loss on any? Try these tools to understand the health of your networks. 1. https://packetlosstest.com/ 2. https://www.speedtest.net/

    点赞 评论 复制链接分享
  • weixin_39716521 weixin_39716521 4月前

    We've seen this issue before and this it's highly probably that this is caused due to Network issues like high latency, packet loss, and congestion as mentioned out here - https://aws.amazon.com/premiumsupport/knowledge-center/s3-socket-connection-timeout-error/

    As suggested, could you please give the above mentioned network tools a try?

    点赞 评论 复制链接分享