8000 Added parameter for configuring timeout for /evaluate. by jnegara · Pull Request #298 · tableau/TabPy · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Added parameter for configuring timeout for /evaluate. #298

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

Merged
merged 10 commits into from
May 22, 2019
Merged

Conversation

jnegara
Copy link
Contributor
@jnegara jnegara commented May 21, 2019

Added support for parameter TABPY_EVALUATE_TIMEOUT in the server config.

When /evaluate is called with some script, if that script takes longer than the number of seconds specified by this parameter the script is terminated and the client received a TimeoutError.

If TABPY_EVALUATE_TIMEOUT is set to a non-float value, or is not present then the timeout length defaults to 30s.

This should close issue #118.

@pep8speaks
Copy link
pep8speaks commented May 21, 2019

Hello @jnegara! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

Line 189:80: E501 line too long (98 > 79 characters)
Line 196:80: E501 line too long (103 > 79 characters)

Line 36:80: E501 line too long (112 > 79 characters)
Line 84:80: E501 line too long (84 > 79 characters)

Line 144:80: E501 line too long (93 > 79 characters)
Line 150:80: E501 line too long (82 > 79 characters)

Line 10:80: E501 line too long (84 > 79 characters)
Line 12:80: E501 line too long (123 > 79 characters)
Line 22:80: E501 line too long (84 > 79 characters)
Line 44:1: W293 blank line contains whitespace

Line 111:80: E501 line too long (105 > 79 characters)
Line 124:80: E501 line too long (107 > 79 characters)

Comment last updated at 2019-05-22 19:17:01 UTC

@0golovatyi 0golovatyi merged commit a44798e into dev May 22, 2019
@0golovatyi 0golovatyi deleted the read-timeout branch May 22, 2019 18:37
0golovatyi added a commit that referenced this pull request Jul 31, 2019
* Added parameter for configuring timeout for /evaluate. (#298)

* Added configurable timeout.

* Added unit test for custom evaluate timeout.

* Fixed evaluation timeout, added integration tests + additional UT.

* Documentation updates.

* Reverting state.ini.

* Updated file path in server-config.md.

* Fixing pep8 issues.

* Improved timeout error messaging.

* Fixed docs, removed debugging prints.

* Returning HTTP code 408 on eval timeout.

* Querying models through /evaluate causes server hang. (#300)

* Made call_subprocess non-blocking.

* Magic?

* Using native coroutines in EvaluationPlaneHandler.

* Updated docs to reflect timeout limitations.

* Resolved markdownlint issue.

* Back to tornado coroutines.

* Fixed pep8 style.

* fixing regex issue where . were not allowed in endpoint path (#305) (#306)

* adding t-test to pre-deployed models (#312)

* adding t-test to pre-deployed models

* fixed pep8 issues

* import error on ttest and updated successful deployment message for sentiment analysis

* fixed md issues

* fixed endpoint name in integration tests

* refactor redundant code and update md

* Add FAQ.md (#325)

* Update README.md

* Create FAQ.md

* Fix models call via /evaluate in HTTPS (#322)

* Fix models call via /evaluate in HTTPS

* Restore state.ini

* Delete 'Supported Configurations' page (#327)

* Upgrade to Tornado 6 (#328)

* remove asyncronous attribute for coroutines

* Remove dependency on jsonschema

* Fix markdown

* Update setup.py

* Add tornado to travis script

* Add tornado to travis script

* Remove tornado-json dependency

* Update VERSION

* Update CHANGELOG

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

Successfully merging this pull request may close these issues.

4 participants
0