-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
gdrive: raises unexpected error - name: drive version: v2 (again) #7949
Comments
Seems like an issue with pyinstaller hook added in #5619 I the latest
However, in the previous build (
|
Issue appears to come from latest Pyinstaller release -> pyinstaller/pyinstaller#6789 |
@daavoo should we merge the bump (5.2) and release the new version? See also this iterative/PyDrive2#197 (comment) and iterative/PyDrive2#197 (comment) Those might be relevant, maybe we can do something on the This issue I think is causing this https://stackoverflow.com/questions/73025023/dvc-pull-returns-error-configuration-error-failed-to-authenticate-gdrive-remo problem. |
I wonder, why does it work on a local machine, but not on GitHub actions? Maybe it is possible to create a workaround until this is fixed? My GitHub actions job runs
|
I'm running on Windows 10, and had the same error message when running dvc pull. py -m pip install 'dvc[gdrive]'
py -m pip install pydrive2 And after this dvc pull worked fine again. |
That definitely changed the error message.
|
@sorenwacker Were you able to resolve that new one? Looks like a simple misconfiguration issue. Upgraded to pyinstaller 5.2 seems to solve this. Releasing 2.14.0 ASAP, please give it a try and let us know if that fixes it for you. |
@efiop I am not sure where to look for a misconfiguration. This is my current workflow:
|
It seems to be working now. |
Here is a minimal setup that works:
|
@sorenwacker In your first workflow, I don't see Great to hear it works for you now 🙂 Thanks for the feedback! |
Hey |
We reverted to pyinstaller 5.0 (thanks @daavoo ) for now. No time to look into this deeper, so going to close it for now. |
This appears to be broken again (w/pyinstaller 5.6) from discord context: https://discord.com/channels/485586884165107732/485596304961962003/1041680983482695751
We probably need explicit pyinstaller hooks for this library in either DVC or pydrive2 (or we need to contribute an actual fix upstream in pyinstaller's hook) .deb build logs for 2.34.1 https://github.com/iterative/dvc-s3-repo/actions/runs/3449002686/jobs/5756539961
|
this should be resolved by the linked pydrive patch once it is merged (and dvc-gdrive is updated) |
Should note that we will probably continue to see the
warning in the future, but it should no longer matter for us. The warning is generated due to an outdated pyinstaller.contrib hook for |
Can I have the requirements.txt file that I can use on my python 3.9 so that I get started with solving an isssue |
Bug Report
Description
As reported here, the latest version (2.11.0) of dvc on Ubuntu 22.04 LTS still has the bug reported in issue #5618.
Downgrading dvc to 2.10.2 allows the push to work properly.
Reproduce
On an existing repository using gdrive, add some files then try to push them.
With extra verbosity:
Expected
The push to succeed without errors.
Environment information
Output of
dvc doctor
:This is running with python 3.10.4 in a virtual environment set up with
direnv
.The text was updated successfully, but these errors were encountered: