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

Extraction API giving 403 Forbidden #7

Closed
parmeshashwath opened this issue Apr 3, 2019 · 5 comments
Closed

Extraction API giving 403 Forbidden #7

parmeshashwath opened this issue Apr 3, 2019 · 5 comments

Comments

@parmeshashwath
Copy link

I loaded the pre-trained model and trying the predict in interactive mode the sample function given in Input.java. However, The Extraction API (https://ff655m4ut8.execute-api.us-east-1.amazonaws.com/production/extractmethods) used in the code is giving the 403 Forbidden. Can you please help if I am missing something

@urialon
Copy link
Contributor

urialon commented Apr 3, 2019

Hi Parmesh,
Thank you for letting us know.
You are not missing anything, this is indeed a problem caused by the migration of our AWS services.
It will be solved in 24 hours.

Sorry for the inconvenience,
Uri

@urialon
Copy link
Contributor

urialon commented Apr 3, 2019

Hi Parmesh,
Please try again now. Everything is supposed to work.

@parmeshashwath
Copy link
Author

Hi Uri
It works now . Thanks a lot for fixing it. This is a great project and will add a great value. Thanks for open-sourcing this.
But can we have the extractor API code also as part of this code base? So that we can run this code2seq without any external dependencies.

@urialon
Copy link
Contributor

urialon commented Apr 3, 2019

The extractor API is exactly the same as the JavaExtractor, which is included in the codebase, but wrapped in a class that makes it a Lambda function in AWS. This way, manual examination (interactive mode) could be performed faster and easier.
The alternative would be to run a Java process on the user's machine, in parallel with the user's Python process, which would be cumbersome, require communication between the processes and require opening ports.
I hope that this downtime of the extraction API won't happen again. This API is running for over a year and has never been down before.

@parmeshashwath
Copy link
Author

Great. It makes sense. Thanks Again

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

2 participants