-
Notifications
You must be signed in to change notification settings - Fork 3
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
push: unexpected error - 'NoneType' object is not iterable #29
Comments
same
|
Can reproduce. |
I am taking a look. Introduced in iterative/dvc#9538 . In all the other remote filesystems, we expect an error to be raised and ignored when checking for So the dir However in GdriveFilesystem, |
I am pretty sure that this is the issue becaus of wrong remote location. I am also experiencing similar issue with
|
To an update here: you can track the progress in the linked issue in iterative/PyDrive2#283 and we hope to get it resolved by early next week. |
You can manually go and create folders |
@satyajitghana , |
@rnoxy Please post full verbose log for the error you are getting. |
I have used recent I have observed that Here is some example log (unfortunatelly I cannot give more details):
So the output the "1 file added" is not true :-( When I try to use but I have double checked that the Here are some logs from
|
@efiop , let me add that when I tried to copy the file to the old location (v2 format)
i.e. without I think the |
@efiop , I am not 100% sure, but probably this is the problem (see dvc-data package): |
and this (for |
the |
@rnoxy can you share the contents of the i.e. something along the lines of
This error:
indicates that the specified dataset was created in DVC 2.x (since it is reported as an It sounds like the problem may be that the specified file at that git tag was just not pushed to the remote in the first place. |
Can you also confirm whether or not the tag (This would also cause the behavior you are seeing here, where you have pushed the file to 3.0 cache, but the tag still points to the 2.x version of a .dvc file which was never pushed to 2.x cache) |
|
No, the error means the problem with current dvc See my note that I copied the file from |
This is a DVC 2.x output, meaning DVC (even in 3.0) will push and pull it to the legacy remote location. DVC 3.x data has an additional
It sounds like there is a bit of confusion over the deprecated behavior in 3.x. DVC 3.x still uses the legacy cache/remote location (without As long as |
@antortjim, can you please try installing |
First of all, thank you all for looking into the issue
I confirm I don't get the error and the files I added with |
Bug Report
Description
I just installed dvc 3.0.0 in a mamba environment in an existing git repository. I wish to upload the large files to a google drive repository
Reproduce
Expected
I expected to be taken to the Google login page or maybe that it would simply work, since I already have another environment with dvc working and able to push/pull from another remote (it's a separate project). Instead I get this error
Environment information
Ubuntu 22.04.2 LTS
Python 3.10 (Mamba environment)
dvc 3.0.0
gdrive 0.1.5
Output of
dvc doctor
:Additional Information (if any):
The text was updated successfully, but these errors were encountered: