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.

Should print id of daemon that is processing the request

See original GitHub issue

Yesterday, the daemon seemed stuck while builing Quarkus (it was actually downloading artifacts from a very slow source). Another daemon was present so it was not immediately obvious which one was affected (e.g. for jstack or for stopping/killing).

I think it would come handy if the client would print the pid of the daemon that is processing the request.

PS: I could have probably pressed + to see what’s going on but nevertheless I do think this would be helpful.

Issue Analytics

State:
Created 3 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

ppalagacommented, Jan 8, 2021

+1 for myself. I’d also vote for using shorter daemon IDs. UUIDs are too long to display. E.g. a random Base64 string of length 6 would encode 6 * 6 = 36 bits, which would be more than enough for our use case. WDYT, @gnodet ?

0reactions

ppalagacommented, Jan 8, 2021

OK, hex-encoded int would have 8 characters that sounds acceptable too. We’d have to abs() it so that it can’t be negative.

I’ve used the String.format("%08x") which does not add any - sign.

+1, Math.abs() wouldn’t work anyway