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] Warn if the given environment is not fully solved yet #2308

Open
3 tasks
fridex opened this issue Mar 14, 2022 · 8 comments
Open
3 tasks

[Epic] Warn if the given environment is not fully solved yet #2308

fridex opened this issue Mar 14, 2022 · 8 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fridex
Copy link
Contributor

fridex commented Mar 14, 2022

Is your feature request related to a problem? Please describe.

When we plug a new solver, it might happen that adviser fails to resolve application dependencies as we haven't solved packages yet. We could warn users that we haven't solved the environment yet.

Describe the solution you'd like

Similarly, as we show in metrics percentage of solved software packages, we could show this number to users and warn them that the environment they use is not fully solved yet.

Acceptance Criteria

  • Investigate the alternative method to develop this action.
  • Gather metrics that show the no of solver yet to be solved for an env.
  • Plan a method to get the action as a workflow to display the message.
@fridex fridex added 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. labels Mar 14, 2022
@mayaCostantini
Copy link
Contributor

/sig stack-guidance

@sesheta sesheta added the sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. label Mar 16, 2022
@goern
Copy link
Member

goern commented Mar 17, 2022

/project sig-stack-guidance new

@goern
Copy link
Member

goern commented Mar 17, 2022

/project 39 new

@goern
Copy link
Member

goern commented Mar 17, 2022

/project SIG-Stack-Guidance New

@goern
Copy link
Member

goern commented Mar 17, 2022

sorry for the pollution ;)

@goern
Copy link
Member

goern commented Mar 22, 2022

/project SIG-Stack-Guidance

@codificat
Copy link
Member

/priority backlog
/triage accepted

@sesheta sesheta added priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Mar 23, 2022
@harshad16 harshad16 removed the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Jun 6, 2022
@harshad16 harshad16 changed the title Warn if the given environment is not fully solved yet [Epic] Warn if the given environment is not fully solved yet Jun 6, 2022
@sesheta
Copy link
Member

sesheta commented Sep 4, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 4, 2022
@mayaCostantini mayaCostantini removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 4, 2022
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. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 🔖 Next
Development

No branches or pull requests

6 participants