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
Does git-ftp have breakpoint continuation? When I try to "git ftp push" a large file to the ftp server. if the network is bad, the connection will be disconnected in the middle of the upload. What I need is that when I try to upload again, the upload will continue at the breakpoint , not from the zero. THANKS, and sorry for my bad English.
Environment
Please copy the output of the following commands.
echo"$SHELL":
/bin/bash
uname -a :
Linux ****** 4.15.0-106-generic #107~16.04.1-Ubuntu SMP Thu Jun 4 15:40:05 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
git-ftp version:
git-ftp version 1.0.6
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have found a solution for this, it would be great if you could share it here to help others. Thank you for your question.
Currently this is not supported. But it’s a great idea to have a „saveponits“ to continue later. The problem with this idea is the following. We are using a single curl command to upload the files. And as far as I know there is no way to get the information what files are already upload successfully. So the implementation of this could be difficult.
Nevertheless I marked this feature as a possible enhancement so we might come back to the idea later.
Bug / Enhancement / Question ?
Does git-ftp have breakpoint continuation? When I try to "git ftp push" a large file to the ftp server. if the network is bad, the connection will be disconnected in the middle of the upload. What I need is that when I try to upload again, the upload will continue at the breakpoint , not from the zero. THANKS, and sorry for my bad English.
Environment
Please copy the output of the following commands.
The text was updated successfully, but these errors were encountered: