sesheta
commented
2 years ago @TomasTomecek: This issue is currently awaiting triage.
One of the @thoth-station/devs will take care of the issue, and will accept the issue by applying the
triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
goern
Gkrumbach07
Is your feature request related to a problem? Please describe.
Just going through the latest results in my console for https://thoth-station.ninja/search/adviser-220719131518-f9cde332e97c5073/summary and giving you feedback for the output. I separate every point with a \<hr>. Let's go!
There are too many lines on the output, I have no control over the code inside our dependencies.
Could be a single line with multiple dependencies, doesn't need to be a single line for every dep. I also understand this is important for people that install directly from PyPI.
A lot of the
INFOlines could even be suppressed:No $tool usedPlease write which environment, I don't understand what I should change.
I don't care about this and specifically don't have control over CPU in our CI.
I don't understand if there is anything I should change or if Thoth is just telling me that it doesn't take that CVE into account.
Stack report: I like the table in the Web UI with ❌ and ✅: that's easy to read. In the console, there is a lot of text that's hard to parse. Could there e.g. be some score number that would tell the healthiness? So that in console it would only be a single line per project.
That's it! Overall the web interface is easier to read for me, especially the stack report. I also appreciate the Compare tab so that I can see what has changed in the meantime. One thing I'd highlight is that it's hard for me to find any of the points actionable - it's good that I know that information but it's not in my control do anything about it. Examples of actionable items:
"Dependency $XYZ has low health project status and can be replaced with $ASD"
"You are using setup.py style of Python packaging. Please consider migrating to $QWE"
"Option $A in setup.cfg is deprecated, please use $B"