We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Prerequirements: tarantoolctl rocks install http 2.0.1 tarantoolctl rocks install tracing
tarantoolctl rocks install http 2.0.1
tarantoolctl rocks install tracing
Run: tarantool formatter.lua, tarantool publisher.lua in separate terminal window, tarantool client.lua in separate terminal window.
tarantool formatter.lua
tarantool publisher.lua
tarantool client.lua
Last one fails with
LuajitError: client.lua:85: Print string error: {"status":595,"reason":"Couldn't connect to server"} fatal error, exiting the event loop
while tarantool formatter.lua still logs
started entering the event loop GET /format?helloto=world
tarantool publisher.lua logs only
entering the event loop
and there are some traces in Jagger:
The text was updated successfully, but these errors were encountered:
Seems like the reason is missing httpd:start() in publisher.lua app.init() in README
httpd:start()
publisher.lua
app.init()
Sorry, something went wrong.
Fix publisher HTTP server example
894dc4b
Closes #11
d208cd7
This patch fixes example in readme.md. Before this patch we didn't start http server - this patch adds missing command. Closes #11
Successfully merging a pull request may close this issue.
Prerequirements:
tarantoolctl rocks install http 2.0.1
tarantoolctl rocks install tracing
Run:
tarantool formatter.lua
,tarantool publisher.lua
in separate terminal window,tarantool client.lua
in separate terminal window.Last one fails with
while
tarantool formatter.lua
still logstarantool publisher.lua
logs onlyand there are some traces in Jagger:
![image](https://user-images.githubusercontent.com/20455996/107195824-e6d30500-6a02-11eb-8c35-db3b06e8c1e4.png)
The text was updated successfully, but these errors were encountered: