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

[21.01] Initial fix for quay.io repo query issue #13468

Merged
merged 3 commits into from Mar 2, 2022

Conversation

mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented Mar 2, 2022

Fixes not getting a full list of images in a repo. Without this fix some container images are not resolvable.

I understand there's more to be done, but this is a major fix we should get out ASAP.

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

Fixes not getting a full list of images in a repo. Without this fix some
container images are not resolvable.
Co-authored-by: Sergey Golitsynskiy <sgolitsynskiy@gmail.com>
Copy link
Member

@dannon dannon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed this fixes the resolution issue for me.

@mvdbeek
Copy link
Member Author

mvdbeek commented Mar 2, 2022

Do we know an example repo that was affected by this ? We could add this to the tests then.

@nuwang
Copy link
Member

nuwang commented Mar 2, 2022

On anvil, we were able to replicate with fastqc and multiqc.

Comment on lines 64 to 65
if resolution_cache is not None and cache_key in resolution_cache:
repo_names = resolution_cache.get(cache_key)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't the cache have different repo_names for different namespaces?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so, this would be a problem if we we're using more than one namespace, but so far it's only biocontainers.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, added to #13460 for tracking.

@nsoranzo nsoranzo modified the milestones: 21.05, 22.01 Mar 2, 2022
@nsoranzo nsoranzo merged commit 2d535ed into galaxyproject:release_21.01 Mar 2, 2022
@nsoranzo nsoranzo deleted the quay_io_fix branch March 2, 2022 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants