Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Webui is "started" even when explicitly disabled

See original GitHub issue

Expected behaviour:

No log messages about webui

Actual behaviour:

2020-01-08 18:09:58 INFO     web_server                    Web interface available at http://127.0.0.1:3539

Config:

web_server:
  bind: 0.0.0.0
  port: 3539
  web_ui: no

Probably just a simple logging issue?

Issue Analytics

State:
Created 4 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

2reactions

gazpachokingcommented, Jan 8, 2020

I guess ‘web server’ is fine for the general web server. But then it would be nice to have messages for each app on the web server that was started. e.g.

2020-01-08 18:09:58 INFO     web_server                    Web server started at http://127.0.0.1:3539
2020-01-08 18:09:58 INFO     web_server                    API available at http://127.0.0.1:3539/api
2020-01-08 18:09:58 INFO     web_server                    Web-ui available at http://127.0.0.1:3539/

1reaction

gazpachokingcommented, Jan 11, 2020

This is what it looks like now if you start the web server with all possible apps running:

2020-01-11 11:25:08 INFO     web_server                    Web server started at http://192.168.0.143:5050
2020-01-11 11:25:08 INFO     web_server                    API available at http://192.168.0.143:5050/api
2020-01-11 11:25:08 INFO     web_server                    WebUI (v1) available at http://192.168.0.143:5050/v1/
2020-01-11 11:25:08 INFO     web_server                    WebUI (v2) available at http://192.168.0.143:5050/

Not sure if other log messages need to be tweaked as well, or maybe levels moved down to debug or something.