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

start f35-py310 ingestion #2479

Closed
goern opened this issue Mar 31, 2022 · 9 comments · Fixed by #2525
Closed

start f35-py310 ingestion #2479

goern opened this issue Mar 31, 2022 · 9 comments · Fixed by #2525
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@goern
Copy link
Member

goern commented Mar 31, 2022

SSIA

@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Mar 31, 2022
@goern
Copy link
Member Author

goern commented Mar 31, 2022

/kind feature
/priority important-soon
/triage needs-information

@sesheta sesheta added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/needs-information Indicates an issue needs more information in order to work on it. labels Mar 31, 2022
@goern
Copy link
Member Author

goern commented Mar 31, 2022

/triage accepted

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Mar 31, 2022
@harshad16
Copy link
Member

We should wait on this.
currently there is still some of the package to be solved:https://grafana.datahub.redhat.com/dashboard/db/thoth-knowledge-graph-content-metrics?refresh=30s&orgId=1&panelId=37&fullscreen

we were blocked by: #2484
and are blocked by: #2493

@goern
Copy link
Member Author

goern commented Apr 5, 2022

so we put it on this or the next milestone?

@fridex
Copy link
Contributor

fridex commented Apr 5, 2022

On the last SIG stack guidance call, we decided to postpone ingestion until the cluster is more stable.

@goern
Copy link
Member Author

goern commented Apr 7, 2022

@harshad16 @fridex could you create a tracker issue to outline what we need to do to get to a more stable state? what are the metrics we are using? which components need improvement?

@codificat
Copy link
Member

/sig devsecops

@sesheta sesheta added the sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. label Apr 25, 2022
@goern
Copy link
Member Author

goern commented Apr 26, 2022

what is the current state of this?

@harshad16
Copy link
Member

This PR would fix this: #2525
and it is ready for review

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/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. triage/accepted Indicates an issue or PR is ready to be actively worked on. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants