You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There appears to be an issue transferring large files over scp onto an Altis Cloud environment. The result is a transfer that stalls when it reaches 100% on the progress bar, shows the total size in MB as having been transferred in full, but the transfer never actually completes. When attempting to work with the transferred file it may or may not be complete enough. For example, trying to unzip a zip archive that stalled on 100% will result in a "End-of-central-directory signature not found" error.
I'm not sure at what size the problem becomes apparent. I've successfully transferred zips up to 162MB. A zip of 370MB will stall at 100% and not complete. I wonder if this may be related to the available disk space on the target environment.
To reproduce
Create a zip file >= 370MB in size
Transfer it with altis-cli stack scp <from> <to>
Observe that the transfer will stall at 100%, but will never finish, and the transfer itself is not actually complete
The text was updated successfully, but these errors were encountered:
There appears to be an issue transferring large files over scp onto an Altis Cloud environment. The result is a transfer that stalls when it reaches 100% on the progress bar, shows the total size in
MB
as having been transferred in full, but the transfer never actually completes. When attempting to work with the transferred file it may or may not be complete enough. For example, trying to unzip a zip archive that stalled on 100% will result in a "End-of-central-directory signature not found" error.I'm not sure at what size the problem becomes apparent. I've successfully transferred zips up to 162MB. A zip of 370MB will stall at 100% and not complete. I wonder if this may be related to the available disk space on the target environment.
To reproduce
altis-cli stack scp <from> <to>
The text was updated successfully, but these errors were encountered: