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

Failing to restore (due timeout?) #3375

Closed
auduchinok opened this issue Sep 26, 2018 · 11 comments · Fixed by #3554
Closed

Failing to restore (due timeout?) #3375

auduchinok opened this issue Sep 26, 2018 · 11 comments · Fixed by #3554

Comments

@auduchinok
Copy link
Contributor

I'm trying to restore https://github.com/thinkbeforecoding/UnoCore using a slow internet connection.
During downloading transitive dependencies it seems to time out and fail and Paket doesn't tell anything about why it cannot restore.
Packages it fails on:
runtime.win10-arm.Microsoft.Net.Native.SharedLibrary
runtime.win10-x64.Microsoft.Net.Native.Compiler
runtime.win10-x86.Microsoft.Net.Native.Compiler
I was able to restore it using PackageReference and it took several minutes for each package.

Any additional info I could provide?

@forki
Copy link
Member

forki commented Sep 27, 2018 via email

@auduchinok
Copy link
Contributor Author

auduchinok commented Sep 27, 2018

It tries to download it three times and then exits with a non-zero code.

@forki
Copy link
Member

forki commented Sep 27, 2018 via email

@auduchinok
Copy link
Contributor Author

It was the first time it was being downloaded on that machine so it couldn't fall back to the packages folder.
My workaround was to create a separate project and to restore these packages using Nuget. Only after me doing that Paket was able to restore the project.

@auduchinok
Copy link
Contributor Author

@forki Can you reproduce it with the solution above by removing the downloaded packages?
Not sure how to repro the slow connection, though. :)

@forki
Copy link
Member

forki commented Sep 28, 2018

no, works for me. even after "paket clear-cache". but these packages are huge!

image

@auduchinok
Copy link
Contributor Author

The thing probably is they still manage to download in just a few seconds while it took me literally several minutes to download each one at that place.

I'm not sure how much edge case is it as people either usually have it in their packages folder or can download it shortly, feel free to close the issue if you feel it is.

@Vidarls
Copy link
Contributor

Vidarls commented Oct 24, 2018

I'm struggling with the same right now, not an issue in my dev environment, but on a CI server with no cache it breaks the build for some of these huge runtime packages.

@forki
Copy link
Member

forki commented Oct 24, 2018

suggestions welcome

@Vidarls
Copy link
Contributor

Vidarls commented Oct 24, 2018

In my case, the package is coming from a public MyGet feed (that seems to be throttled), so the download is taking several minutes to complete (even though it is "just" ~65 MB).

It looks like #3383 could be a viable fix? I can set the required Env variables in the build environment and keep normal timeouts for other builds.

@Vidarls
Copy link
Contributor

Vidarls commented Oct 24, 2018

update, tested the latest prerelease with the changes from #3383, this does solve the issue for me at least.

matthid added a commit that referenced this issue Apr 14, 2019
…ET_STREAMREADWRITE_TIMEOUT basically obsolete

Write into a temporary file and move it at the end, should fix #3418
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants