Skip to content
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

SentEval S3 bucket does not exist anymore #59

Closed
devfoo-one opened this issue Jan 30, 2019 · 6 comments
Closed

SentEval S3 bucket does not exist anymore #59

devfoo-one opened this issue Jan 30, 2019 · 6 comments

Comments

@devfoo-one
Copy link

get_transfer_data.bash is not able to get the BINCLASSIF data because the S3 bucket seems to have vanished.

BINCLASSIF='https://s3.amazonaws.com/senteval/senteval_data/datasmall_NB_ACL12.zip'

<Error>
<Code>NoSuchBucket</Code>
<Message>The specified bucket does not exist</Message>
<BucketName>senteval</BucketName>
<RequestId>CD9C211F9430BBDA</RequestId>
<HostId>
A3Uc1f5nbAEl0vTqp5mFPITfxuvPogs5m5dDm/72UaTbZ8tG5TbCJH9K7tm6JJ8T1Y1R7ZgVpXE=
</HostId>
</Error>
@nstfk
Copy link

nstfk commented Jan 31, 2019

Did you find another bucket as I am also looking for the model?

@heartcored98
Copy link

heartcored98 commented Jan 31, 2019

I am suffering same issue :(
I just tried to download dataset with get_transfer_data.bash, here is the list of the downloading status of each dataset

Failed to Download

  • COCO
  • CR
  • MPQA
  • MRPC
  • MR
  • SUBJ

Succeed to Download

  • SICK (OK)
  • SST-binary (OK)
  • SST-fine (OK)
  • SNIL (OK)
  • STS12, 13, 14, 15, 16, Benchmark (OK)
  • TREC (OK)

@devfoo-one
Copy link
Author

Did you find another bucket as I am also looking for the model?

No, unfortunately not.

@DannyMerkx
Copy link

DannyMerkx commented Feb 1, 2019

I am having the same problem, it only seems to affect the data hosted on amazon. I found an old version of Senteval with all the data on one of my VMs, what would be a convenient way to share it with you? The data is about 1.3 gb

@douwekiela
Copy link
Contributor

Should be fixed now, we migrated to a new S3. See 6b13ac2.

@saippuakauppias
Copy link

infersent2 are the same infersent1!
Please, check issue facebookresearch/InferSent#123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants