Unable to to pass option to bloop script about bloop

[Duhemm]

I think that bloop -- compile -p root should work as a workaround.

[leszekgruchala]

That was quick! Thank you, helped.

[Duhemm]

Yes please! There are some issues with messages being lost between the server and the client, that could also be the cause. In that case, restarting the server usually helps.

You can also add --verbose to test to have bloop show the tests that it discovered.

[jvican]

What was the way we decided to solve this issue? Forwarding CLI arguments from the nailgun server to the underlying app?

[olafurpg]

I think I fixed this with alias bloop = ng bloop.Cli @jvican

[jvican]

I have the same alias and this problem still occurs in my machine. I'll fix this in a follow-up PR.

[Duhemm]

I have

alias bloop="~/.bloop/bloop-ng.py bloop.Cli --"

And commands such as

bloop run -p blabla --args arg0 --args arg1

work fine.

[jvican]

alias bloop="~/.bloop/bloop-ng.py bloop.Cli --"

The -- at the end does the trick. However, I wonder if we can fix this in a more fundamental way. I'd like to avoid the need of -- altogether.

[jvican]

python2 nailgun/pynailgun/ng.py compile -p frontend should work out of the box with #175. This is more intuitive because what the user can easily assume that the bloop CLI is the equivalent of running the python script python2 nailgun/pynailgun/ng.py, without any nailgun-specific implementation detail.

[jvican]

Note that, from now on, in case you want to modify one of the nailgun flags (port, server, filearg, show version), you will indeed need to use -- like python2 nailgun/pynailgun/ng.py --nailgun-port=1717 -- compile -p frontend (and this, knowing how CLI parsers work, is intuitive).

But the cool thing with #175 is that it won't require you to add -- for the simplest and most likely use cases.

[jvican]

This is already fixed, thanks to all who chimed in. 🎉