-
Notifications
You must be signed in to change notification settings - Fork 19
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
Two links Permission denied! #7
Comments
same problem |
Thanks for pointing it out! It seems that it is not downloading through the |
thank you very much!!!
…------------------ 原始邮件 ------------------
发件人: "chail/patch-forensics" ***@***.***>;
发送时间: 2022年1月20日(星期四) 上午7:28
***@***.***>;
***@***.******@***.***>;
主题: Re: [chail/patch-forensics] Two links Permission denied! (#7)
Thanks for pointing it out! It seems that it is not downloading through the gdown tool, but you can open the link directly in the browser to download it. I've also added alternate links to the download script; they are provided as celebahq_image_list.txt and celeba_list_eval_partition.txt
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
There is a problem in the'Data Processing' stage. The specific command is 'cd resources && bash download_resources_data.sh'. If executed directly, it will report an error that I have no access to it. According to the content of 'download_resources_data.sh', I found two Google links inside. The cloud disk link is in the 403 status, and there is no permission to download, which causes the bash command to report an error. These two links are ‘https://drive.google.com/uc?id=0B4qLcYyJmiz0U25vdEVIU3NvNFk’ and ‘https://drive.google.com/uc?id=0B7EVK8r0v71pY0NSMzRuSXJEVkk’. This may have an impact on the follow-up steps, can you check it?
Thanks!
The text was updated successfully, but these errors were encountered: