Fix handling of v2 hashes #18522
Merged
Fix handling of v2 hashes #18522
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bernt-matthias
changed the title
bernt-matthias
added a commit
to bernt-matthias/planemo
that referenced
this pull request
Jul 10, 2024
This was referenced Jul 10, 2024
mvdbeek
reviewed
Jul 10, 2024
mvdbeek
approved these changes
Jul 10, 2024
mvdbeek
requested changes
Jul 10, 2024
|
I only remove it from the function that parses targets from a string (comma separated list of tools and versions) which is used in The remaining code (e.g. the mulled container resolver etc) keeps the build as part of the version. I think that the tests which I added in my first commit show this (the version part of the hash differs when builds are added, i.e. the build is considered as part of the version when computing the hash). Wondering if this got a bit confusing when we merged |
mvdbeek
reviewed
Jul 11, 2024
bernt-matthias
force-pushed
the
topic/v2-hash-fixes
branch
3 times, most recently
from
1c0354c to
727850b
Compare
bernt-matthias
commented
Jul 22, 2024
mvdbeek
reviewed
Aug 26, 2024
mvdbeek
approved these changes
Aug 26, 2024
bernt-matthias
commented
Sep 2, 2024
|
Anything else to do here? |
mvdbeek
reviewed
Sep 2, 2024
bernt-matthias
force-pushed
the
topic/v2-hash-fixes
branch
from
ea3180c to
aa2660f
Compare
mvdbeek
force-pushed
the
topic/v2-hash-fixes
branch
from
aa2660f to
f5310f6
Compare
to verify if the build is considered as part of the version or not
the build information that may be contained in requirement versions is considered as part of the version in some places of the code - mulled container resolvers - mulled-build-tool - [planemo](https://github.com/galaxyproject/planemo/blob/b3e12a334e3d358ce30bf2c8c3f8d5a7a7e08136/planemo/conda.py#L116) in others it isn't: - mulled-hash - mulled-build-files - mulled_build which are the files that use the `target_str_to_targets` function. With this change the build info in version strings is always considered as part of the version. `mulled-build-files` is used in the multi-package-containers repo which led to wrong hashes in up to approx 50 tools (check with `grep "=[^,]*=" combinations/* | wc -l`).
bernt-matthias
force-pushed
the
topic/v2-hash-fixes
branch
from
2f223d0 to
16e7cdf
Compare
an empty set of requirements gives an empty requirement string which was wrongly parsed to an CondaTarget with empty package name This triggered a `conda search ''` which took so much memory that other processes crashed. The fix is to parse an empty list of CondaTargets for an empty target string. In addition we check for empty package name during the creation of the CondaTarget (to make this more easily detectable in the future)
bernt-matthias
force-pushed
the
topic/v2-hash-fixes
branch
from
c57cca2 to
da7926a
Compare
|
If github let's me I will merge this 😆 |
|
This PR was merged without a "kind/" label, please correct. |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added tests first for the mulled container resolvers here 5b3c4bd
Then fixed (and more tests) here: e7bca83
See details in e7bca83
I'm tempted to backport this to 24.1 in order to make this effective in the multi-package-container repo.
How to test the changes?
(Select all options that apply)
License