Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EPIC] Have clustered advise outputs #417

Open
3 of 5 tasks
Gkrumbach07 opened this issue Jun 14, 2022 · 4 comments
Open
3 of 5 tasks

[EPIC] Have clustered advise outputs #417

Gkrumbach07 opened this issue Jun 14, 2022 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.

Comments

@Gkrumbach07
Copy link
Member

Gkrumbach07 commented Jun 14, 2022

Problem statement

As a user of Thoth adviser, I want to be able to sort and filter through the justifications provided after an advise so that I can find display only the information that is relevant to me.

High-level Goals

  • Justifications and stack info can be grouped into smaller categories
  • Justifications and stack info can have varying levels of visibility.

Proposal description

I want to be able to filter or sort my advise output's justifications and stack info by category and priority through Thamos.

Additional context

For example the justification bellow can have labels attached such as: labels: ["environment", "parameter"]

{
    "link": "https://thoth-station.ninja/j/env",
    "message": "No CUDA used",
    "type": "INFO"
}

This can be queried in an advise, so a user can get all environment justifications.

Acceptance Criteria

@Gkrumbach07 Gkrumbach07 added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 14, 2022
@Gkrumbach07
Copy link
Member Author

/sig user-experience
/priority important-longterm

@sesheta sesheta added sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jun 15, 2022
@codificat
Copy link
Member

/transfer core

@sesheta sesheta transferred this issue from thoth-station/adviser Jun 27, 2022
@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Jun 27, 2022
@sesheta
Copy link
Member

sesheta commented Jun 27, 2022

@Gkrumbach07: This issue is currently awaiting triage.
If a refinement session determines this is a relevant issue, it 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Gkrumbach07
Copy link
Member Author

Gkrumbach07 commented Jul 5, 2022

Justifications that can be clustered easily

  • scorecards
  • environment parameters set or not set
  • solver rules
  • installation errors / solver did not solve specific version of package
  • external links
  • cve info

Each of these groups have seen abundantly in the justification or stack info list. They all can be easily be identified as groups by the pattern of the text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants