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.

cli refusing to run

See original GitHub issue

The server and UI work perfectly. When trying to set up the cli, i build the binary but the cli doesn’t run.

i can run ./zally --help and pull up the help message. But cannot get anything else work. Not a problem with Go, as I can get other CLIs to work.

Attaching terminal output. Terminal Saved Output.txt

Issue Analytics

State:
Created 5 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

2reactions

upasanachatterjeecommented, Jun 6, 2018

ah that works perfectly thank you so much! I could swear I tried running the CLI on localhost:8000 but that must have been what I missed

0reactions

maxim-tschumakcommented, Jun 6, 2018

But for some reason, when I just build and run the server using ./gradlew clean build and ./gradlew bootRun, and then cd to where the CLI is located, CLI works fine.

This is good 😃

If I run the docker compose script ./build-and-run.sh I get both the server and the UI up and running. If I then cd to my go folder where the code for the CLI is located and try to run that, I get the errors that I mentioned in my very first post.

In this case (docker-compose), Zally Server runs on port 8000 (--linter-service "http://localhost:8000").