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.

Sign up for GitHub

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

Jump to bottom

Incomplete link name in python_interpreter table #2626

Open
mayaCostantini opened this issue Apr 21, 2022 · 4 comments
Open

Incomplete link name in python_interpreter table #2626

mayaCostantini opened this issue Apr 21, 2022 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. 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

@mayaCostantini
Copy link
Contributor

Bug description

Some values in the link column of the python_interpreter table seem cropped / incomplete:

Screenshot from 2022-04-21 14-35-51

Steps to Reproduce

Explore the python_interpreter data from a recent database dump.

Additional context

Dump name: pg_dump-22-04-13-00-03-43
@mayaCostantini mayaCostantini added the kind/bug Categorizes issue or PR as related to a bug. label Apr 21, 2022
@mayaCostantini
Copy link
Contributor Author

/priority critical-urgent

@sesheta sesheta added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Apr 21, 2022
@sesheta
Copy link
Member

sesheta commented Jul 20, 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 Jul 20, 2022
@codificat
Copy link
Member

based on review today, assigning
/sig stack-guidance

and updating
/remove-priority critical-urgent
/priority important-soon

next step is to check if this is a problem nowadays

@sesheta sesheta added sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Aug 8, 2022
@codificat
Copy link
Member

/triage accepted
/remove-lifecycle stale

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 8, 2022
@codificat codificat moved this to 📋 Backlog in Planning Board Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. 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
Planning Board
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@codificat @sesheta @mayaCostantini