-
Notifications
You must be signed in to change notification settings - Fork 3
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
Redirect Issues in cli calls #217
Comments
Thanks for reporting this ticket. Does the redirection issue occur with the data node and/or NLP tools? |
It looks like this is specific to the |
I can't reproduce this issue. I used the image [ec2-user@ip-10-41-30-136 date-annotator-example]$ nlp-cli --version
nlp-cli, version 4.3.1
[ec2-user@ip-10-41-30-136 date-annotator-example]$ nlp-cli tool get-tool --annotator_host http://localhost:80/api/v1
{'name': 'date-annotator-example', 'version': '1.2.0', 'license': 'apache-2.0', 'repository': 'github:nlpsandbox/date-annotator-example', 'description': 'Example implementation of the NLP Sandbox Date Annotator API', 'author': 'NLP Sandbox Team', 'author_email': 'team@nlpsandbox.io', 'url': 'https://github.com/nlpsandbox/date-annotator-example', 'type': 'nlpsandbox:date-annotator', 'api_version': '1.2.0'} @jakevc Could you please give it another try? At the level of the code, both the date annotator and the person name annotator, for example, redirect the root path |
Yeah so I tried getting a fresh clone of the date annotator and the same thing happens. I have the data node and the workflow orchestrator running, and then I run
That is successful and I have all the containers running on the same machine:
Okay check, then try and get-tool:
|
Problem description
Some CLI commands fail with redirection issues associated with the route
http://localhost:80/api/v1/ui
. It appears as the intended route ishttp://localhost:80/api/v1
, but is redirectedhttp://localhost:80/api/v1/ui
.Steps to reproduce the issue
Using the nlp-cli version:
Expected behavior
Extra information
The text was updated successfully, but these errors were encountered: