Closed levaid closed 3 years ago
Thank you for your report!
Unfortunately this is a known bug, due to emBERT module. The transformers
package is not pinned and the API has broken in the newer versions. We will provide a workaround soon, to keep things going until the new version of emBERT is released.
The bug only affects the REST API, so in the meantime we recommend using emtsv through CLI or build an own docker image without or with a modified version of emBERT.
This is why I was surprised - the CLI version that I have used a few days did not throw any errors, I wanted to try to REST API because I sometimes have problems with input formatting, and the REST API does not need to cold start after every try.
Thank you for the quick reply!
I've run into this same problem, but going from :latest to a versioned one made the docker container at least useable (for example: docker pull mtaril/emtsv:4.0.1, docker run --rm -p5000:5000 -it mtaril/emtsv:4.0.1)
My further question is: would it be possible to set a default GET page for / ? It could return some version string for example, or possibly a Swagger UI for testing the API? (I just get an Internal Server error on a simple GET for http://localhost:5000)
Thanks!
My further question is: would it be possible to set a default GET page for / ? It could return some version string for example, or possibly a Swagger UI for testing the API? (I just get an Internal Server error on a simple GET for http://localhost:5000)
This is an offtopic question here. It would need a separate issue.
The lastest sources actually returns a basic WebUI for GET /
. This would be the current intended behavior. If you gen an internal server error, please see the logs for details. It is definitely not the intended behavior, but possible due to this bug.
There are efforts on rewriting xtsv according to the user feedback. Some of the planned new features include Swagger UI.
New docker release is out! Thx to @mittelholcz https://hub.docker.com/repository/docker/mtaril/emtsv
Please test and if the issue persists, please reopen the issue. Thank you for your patience!
Hello,
I wanted to start the latest docker image with the given command to run it through Rest API, and I got a pretty long traceback to the emBERT module. This is my full terminal output: