The link for it in the git lfs help pages is broken.
Hello @Jon Petter Åsen ,
The use of Media adapter is discouraged, and it is not available for download anymore.
Could you please link to the page that still refers to it? Looks like that was an oversight, sorry.
Let me know if you have any questions.
Cheers,
Daniil
https://confluence.atlassian.com/bitbucket/troubleshoot-git-lfs-in-bitbucket-831652519.html
It is referred to under:
If the Media adapter is discontinued, is there any other recommendations when pushing large files (multiple GBs)? Use https instead of ssh?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for pointing to that page, we'll get it fixed soon!
If the Media adapter is discontinued, is there any other recommendations when pushing large files (multiple GBs)? Use https instead of ssh?
No, it shouldn't matter which protocol you use. LFS files are always transferred over HTTPS, no matter what protocol is used for the Git repository itself. We improved transmission of huge files over the last year, so hopefully there will be no issues with that.
So, no special recommendations, it should just work. Let me know if you face any problems.
Cheers,
Daniil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Daniil Penkin ,
I met the same problem when pushing large files (1.2GB, 700MB, etc.) to bitbucket. it was stuck with the following message:
Uploading LFS objects: 88% (7/8), 8.3 GB | 97 MB/s
It kept uploading LFS object until the number jumped to ~15 GB and finally returned an "i/o timeout" error.
However, the total size of files I would like to upload is only ~2.2 GB.
Can you give some suggestions? Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.