Skip to content

Wrong version assigned on updates #93

@fridex

Description

@fridex

Describe the bug

See the following endpoint that lists data for versions. It states that elyra in version=3.5.1 (on UBI 8 Python 3.8) has a dependency on click<8,>=7.1.1. However linked versions in the database are (based on API endpoint):

"versions": [
    "7.1.1",
    "7.1.2",
    "8.0.4"
]

I suspect this wrong version assigned in the database is caused by a release of click==8.0.4. For some reason, revsolver assigns click==8.0.4 as a dependency of elyra==3.5.1 even though it does not respect the version specifier. I'm not sure if revsolver is really the issue maker, but the corresponding solver document that solved elyra==3.5.1 on UBI 8 Python 3.8 has no click==8.0.4 stated (and click in that version might not be even released at the time of solving).

To Reproduce

I see this issue for the second time. Not sure how to reproduce it directly except for waiting for package releases and check timestamps for things that are happening in the system (or run revsolver locally against a local database dump without new releases). The issue might be caused by some incosystency (maybe environment markers?) that create this issue from time to time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/stack-guidanceCategorizes an issue or PR as relevant to SIG Stack Guidance.

    Type

    No type

    Projects

    Status

    📋 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions