dvc: Unable to pull from gdrive, file identified as malware

Hi, I started following the hands-on tutorial and pushed an example file to my gdrive and tried to retrieve it using dvc pull, and I get the following error.

<HttpError 403 when requesting *www.googleapis.com link* returned "This file has been identified as malware or spam and cannot be downloaded". Details: "[{'domain': 'global', 'reason': 'abuse', 'message': 'This file has been identified as malware or spam and cannot be downloaded'}]">

The gdoc documentation specifies an argument acknowledgeAbuse=true to pass to override this error but I don’t think I can pass it through the DVC wrapper.

Is this issue known ? Any way to bypass this ? Thanks

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 1
Comments: 21 (8 by maintainers)

Commits related to this issue

fs: add acknowledge_abuse parameter Related #62 Pre-requisite for https://github.com/iterative/dvc/issues/7832 — committed to iterative/PyDrive2 by efiop 2 years ago
fs: add acknowledge_abuse parameter Related #62 Pre-requisite for https://github.com/iterative/dvc/issues/7832 — committed to iterative/PyDrive2 by efiop 2 years ago
fs: add acknowledge_abuse parameter Related #62 Pre-requisite for https://github.com/iterative/dvc/issues/7832 — committed to iterative/PyDrive2 by efiop 2 years ago
fs: add acknowledge_abuse parameter Related #62 Pre-requisite for https://github.com/iterative/dvc/issues/7832 — committed to iterative/PyDrive2 by efiop 2 years ago
fs: add acknowledge_abuse parameter Related #62 Pre-requisite for https://github.com/iterative/dvc/issues/7832 — committed to iterative/PyDrive2 by efiop 2 years ago
fs: add acknowledge_abuse parameter Related #62 Pre-requisite for https://github.com/iterative/dvc/issues/7832 — committed to iterative/PyDrive2 by efiop 2 years ago
fs: gdrive: add gdrive_acknowledge_abuse Fixes https://github.com/iterative/dvc/issues/7832 — committed to efiop/dvc by efiop 2 years ago
fs: gdrive: add gdrive_acknowledge_abuse Fixes https://github.com/iterative/dvc/issues/7832 — committed to iterative/dvc by efiop 2 years ago

Most upvoted comments

dvc 2.14.0 is out with gdrive_acknowledge_abuse config option. Please give it a try

$ dvc remote modify myremote gdrive_acknowledge_abuse true

+11

efiop on Jul 22, 2022

dvc 2.14.0 is out with gdrive_acknowledge_abuse config option. Please give it a try
$ dvc remote modify myremote gdrive_acknowledge_abuse true

maybe it makes sense to add it to the hands on tutorial

aliahari on Dec 14, 2022

$ dvc doctor
DVC version: 2.10.2 (conda)
---------------------------------
Platform: Python 3.10.4 on Windows-10-10.0.22000-SP0
Supports:
        gdrive (pydrive2 = 1.10.1),
        webhdfs (fsspec = 2022.5.0),
        http (aiohttp = 3.8.1, aiohttp-retry = 2.4.6),
        https (aiohttp = 3.8.1, aiohttp-retry = 2.4.6)
Cache types: hardlink
Cache directory: NTFS on C:\
Caches: local
Remotes: gdrive
Workspace directory: NTFS on C:\
Repo: dvc, git

M-Puig on Jun 1, 2022

@peterbonnesoeur Edit the <python_env>/lib/python3.10/site-packages/pydrive2/files.py & set the acknowledgeAbuse=True. Check this - https://github.com/iterative/PyDrive2/pull/62

bajaj on Jul 20, 2022

It is happening consistently with my main google account, with which I never used googleAPI previously. Didn’t try with other accounts, just moved away from gdrive

M-Puig on Jun 7, 2022

@M-Puig Is this happening consistently for you or is it intermittent?

The gdoc documentation specifies an argument acknowledgeAbuse=true to pass to override this error but I don’t think I can pass it through the DVC wrapper.

@iterative/dvc It seems like it should be easy for someone to contribute a PR to add this to the config options, but where would they need to do it?

dberenbaum on Jun 6, 2022

Just the one on the dvc.org here I used the conda install

M-Puig on May 31, 2022