-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck in 'Uploading LFS objects' #1
Comments
It's normal that it gets stuck for a couple seconds, IIRC it needs some feedback from the bucket to be able to write B/s. I assume this is not what you're experiencing. If you can run Also, which S3 provider do you use? Maybe there running more up-to-date API. |
It's possible that you error was related to the usePathStyle option of the s3 client, especially if you use a different hosting provider. @jheiselman allowed to change this option. In addition to my previous message, you can also try changing it. |
I just run into a similar issue and the error log may be help:
My
Update: From further debugging I found the environment variables are not correctly set, hard-code the values to replace
Update 2: Turns out the error on clone is expected and should be manually fixed afterwards with corrected LFS settings. I just filed a PR to address the ENV issue. |
Thanks for debugging this issue @phoenixlzx. I'll assume the error indeed came from an ill-defined environment. I've added error handling in the last version of the package for this case. If that was not your issue @lordcoppetti, fell free to reopen an issue with more detail. |
I've been trying to use the tool recently, so my env:
I have an S3 bucket configured with programmatic access which I tested through boto and python3 and works fine, can upload to the bucket so no networking issues either.
My environment variables are set as described.
However when I run test.sh it gets stuck in:
Uploading LFS objects: 0% (0/2), 1.0 MB | 0 B/s
So my way of reproducing is only running test.sh with a env file with the variables set there.
Do you know why this could be or where to dig into the code? Thanks!
The text was updated successfully, but these errors were encountered: