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

Wrong project url entries in python_package_metadata_project_url table #2566

Open
fridex opened this issue Jan 31, 2022 · 6 comments
Open

Wrong project url entries in python_package_metadata_project_url table #2566

fridex opened this issue Jan 31, 2022 · 6 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@fridex
Copy link
Contributor

fridex commented Jan 31, 2022

Describe the bug

Check one of the postgres dumps available. More precisely, check the content of the python_package_metadata_project_url table. It holds project_url in the wrong format:

image

To Reproduce
Steps to reproduce the behavior:

  1. Check database content
  2. Check content of python_package_metadata_project_url table
  3. Check entries in project_url column
  4. See the error

Expected behavior

It might be nice to parse project_url when inserting data into the database and have project_url really a URL that can be used and accessed. A new column introduced might show the type of the URL (as parsed). An entry in the database might then be:

id type project_url
1 source https://github.com/google/flatbuffers

instead of:

id project_url
1 Source, https://github.com/google/flatbuffers
@fridex fridex added kind/bug Categorizes issue or PR as related to a bug. triage/needs-information Indicates an issue needs more information in order to work on it. labels Jan 31, 2022
@mayaCostantini
Copy link
Contributor

/assign

@sesheta
Copy link
Member

sesheta commented Jun 2, 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 Jun 2, 2022
@sesheta
Copy link
Member

sesheta commented Jul 2, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 2, 2022
@sesheta
Copy link
Member

sesheta commented Aug 1, 2022

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta
Copy link
Member

sesheta commented Aug 1, 2022

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.

@sesheta sesheta closed this as completed Aug 1, 2022
@mayaCostantini mayaCostantini reopened this Aug 2, 2022
@mayaCostantini
Copy link
Contributor

/remove lifecycle-rotten
/sig stack-guidance
/lifecycle frozen

@sesheta sesheta added sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

4 participants