Cannot create custom recipe about fastdeploy

[bedapudi6788]

@Timopheym thanks for the detailed bug report. I will test this and get back to you.

Meanwhile, you can use notaitech/fastdeploy-recipe:fastPunct_en

Example usage:

docker run -it -p 8080:8080 notaitech/fastdeploy-recipe:fastPunct_en

curl -d '{"data": ["thanks for the detailed bug report"]}' -H "Content-Type: application/json" -X POST http://localhost:8080/sync
# {"prediction": ["Thanks for the detailed bug report."], "success": true}

[bedapudi6788]

timeout is configurable via the enviorment variable TIMEOUT.

example, for 20 minute timeout,

docker run -e TIMEOUT=720 -it -p 8080:8080 notaitech/fastdeploy-recipe:fastPunct_en

Or, /async endpoint might be better for processing longer texts.

[Timopheym]

Thanks for the container, but fortune does not like me.

(base) ➜  ~ docker ps
CONTAINER ID        IMAGE                                      COMMAND                  CREATED              STATUS              PORTS                              NAMES
95d042041742        notaitech/fastdeploy-recipe:fastPunct_en   "bash _run.sh"           About a minute ago   Up About a minute   0.0.0.0:8080->8080/tcp             youthful_hugle

And while calling curl and using requests lib I am getting timeout error...

def get_punct(text: str) -> [str]:
    r = requests.post('http://localhost:8080/sync', json={"data": [text]})
    return r.json()
# {'success': False, 'reason': 'timeout'}

Don't really understand why, and how to debug it. Can I somehow get into the container and see any logs?
Now I see only

2020-07-28:21:06:05,413 WARNING  [_app.py:55] 82020-07-28-21-04-05-411-86be0c48-0105-4f44-b207-c3fd00f7663c timedout, with timeout 120.0

UPDATE: Nevermind. It happens for "long" text (230 ch) and for short text I was able to get results...

Is there any way to process long texts? I can write a logic to recursively pass text after the first recognized dot, but It looks like overkill... And might not work for some cases.
My test text is about 27 498 chars long.

[bedapudi6788]

@Timopheym I think the reason for the original error message is a typo.

example.pkl     predictor.py    requiremets.txt

this should be requirements.txt instead of requiremets.txt

Let me know if this solves the issue.

[bedapudi6788]

Closing the issue for now. Feel free to re-open if necessary.