wget in download_igb_large.sh returns ERROR 403
a1bc2def6g opened this issue · comments
Hi thanks for bringing this to our attention. As a temporary solution could you please replace the igb-public-awsopen
with igb-public
. I will confirm the paths and update the scripts.
Verified this this other bucket is currently working.
(base) arpan@arpanet ~ % wget https://igb-public.s3.amazonaws.com/igb_large/processed/paper/node_feat.npy
--2024-05-26 00:29:02-- https://igb-public.s3.amazonaws.com/igb_large/processed/paper/node_feat.npy
Resolving igb-public.s3.amazonaws.com (igb-public.s3.amazonaws.com)... 52.219.102.244, 16.12.65.252, 16.12.65.52, ...
Connecting to igb-public.s3.amazonaws.com (igb-public.s3.amazonaws.com)|52.219.102.244|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 409600000000 (381G) [application/octet-stream]
Saving to: ‘node_feat.npy’
node_feat.npy 0%[ ] 24.64M 19.2MB/s
Thanks! Your solution is work!
Confirmed that it works now.
(base) arpan@arpanet ~ % wget https://igb-public-awsopen.s3.amazonaws.com/igb_large/processed/paper/node_label_19.npy
--2024-06-16 16:32:47-- https://igb-public-awsopen.s3.amazonaws.com/igb_large/processed/paper/node_label_19.npy
Resolving igb-public-awsopen.s3.amazonaws.com (igb-public-awsopen.s3.amazonaws.com)... 52.218.180.155, 52.218.180.67, 52.92.149.145, ...
Connecting to igb-public-awsopen.s3.amazonaws.com (igb-public-awsopen.s3.amazonaws.com)|52.218.180.155|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 400000000 (381M) [binary/octet-stream]
Saving to: ‘node_label_19.npy.1’
node_label_19.npy.1 16%[==> ] 63.11M 35.0MB/s