Replies: 2 comments 3 replies
-
Hi @codifryed,
That would be helpful, especially since coolero will often run a different liquidctl version than what the user might otherwise manually install.
Good as well.
I'm not sure how much extra info we're talking about, but either way it's a reasonable and useful feature. As long as you don't mind the extra option on your end...
That's a great idea: in fact, in the past I've had to read the gkraken and coolero sources to check a few bug reports because I need to see which APIs were being called, and in which order.
I think analyzing a potential liquidctl issue in isolation will almost always be a bit easier: besides which liquidctl version the user might be running underneath coolero, the lower-level dependencies might also differ from what we would normally assume, given our different default distribution method the our projects. That said, your ideas are a huge improvement and, with them, we might be able to deal with some problems without having to ask the user to install and learn how to use liquidctl separately. And that's obviously positive for those coolero users. Thanks for thinking and looking into this! |
Beta Was this translation helpful? Give feedback.
-
So I made some changes that will go out with the next Coolero release.
I'm open to any input you may have and hopefully this makes diagnosing issues with liquidctl & Coolero easier. :) PR for reference: https://gitlab.com/coolero/coolero/-/merge_requests/54 |
Beta Was this translation helpful? Give feedback.
-
Hi 👋,
So I see a lot of people posting bugs who are using Coolero, and while it's great more people are getting involved, I sometimes noticed they were not providing helpful information. I'm thinking of adding some features to Coolero to help with debugging situations like:
Some ideas:
coolero --version
-> will also output the version of liquidctl being used. (Can also output more info here if desired)--debug-liquidctl
option that will output liquidctl debug info (normal--debug
outputs a lot of info that's useless for liquidctl debugging)Now perhaps most of these aren't really needed and people should just be advised against coolero at all when submitting issues to liquidctl. (could be clearer and also fine), but I just wanted to see what you think and if there's any way I can help funnel people & improve bug reports coming from people using coolero.
Beta Was this translation helpful? Give feedback.
All reactions