Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

Corrupt jars files following SocketTimeoutException #4787

Closed
CeylonMigrationBot opened this issue Sep 2, 2015 · 2 comments
Closed

Corrupt jars files following SocketTimeoutException #4787

CeylonMigrationBot opened this issue Sep 2, 2015 · 2 comments
Labels
Milestone

Comments

@CeylonMigrationBot
Copy link

[@tombentley] If a SocketTimeoutException occurs when downloading a jar from a remote repo it seems that the partially transferred file is left of the filesystem. On a subsequent run things break because the zip file is invalid.

[Migrated from ceylon/ceylon-module-resolver#125]
[Closed at 2015-09-02 14:47:08]

@CeylonMigrationBot
Copy link
Author

[@tombentley] Maybe we should write to a foo-1.0.0.jar.part file and rename it when the download is complete. That would also allow us to resume a transfer using a range request.

@CeylonMigrationBot
Copy link
Author

[@FroMage] Fixed. We'll implement partial files and resuming later, it's not a priority since most files are small, and I expect we'll need parallel downloads too later.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants