If the initial conversion fails and a retry is attempted, the requests are all made with a "size": 0
This seems to be because data is saved into git-lfs-migrate.mapdb. When that data is reused in git.lfs.migrate.GitConverter#createRemoteFile the main body of that function is skipped so the size never gets set to anything other than zero.
Bitbucket.org's implementation of LFS asserts that the uploaded file matches in both OID and size.
If the initial conversion fails and a retry is attempted, the requests are all made with a
"size": 0
This seems to be because data is saved into
git-lfs-migrate.mapdb
. When that data is reused ingit.lfs.migrate.GitConverter#createRemoteFile
the main body of that function is skipped so the size never gets set to anything other than zero.Bitbucket.org's implementation of LFS asserts that the uploaded file matches in both OID and size.