-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Update table2asn to 1.28.1179 #51951
Conversation
📝 WalkthroughWalkthroughThe pull request includes updates to two main files: In Possibly related PRs
Suggested labels
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
recipes/table2asn/build.sh (1)
6-7
: LGTM! Consider standardizing indentation.The changes to use double brackets and force copy are good improvements. However, consider using spaces instead of tabs for indentation to follow common shell scripting conventions.
- cp -f mac.table2asn ${PREFIX}/bin/table2asn + cp -f mac.table2asn ${PREFIX}/bin/table2asnrecipes/table2asn/meta.yaml (1)
Line range hint
39-41
: Consider updating skip-lints documentation.The skip-lints section indicates this package shouldn't be noarch. It would be helpful to add a comment explaining why these lints are skipped (e.g., because of platform-specific binaries).
extra: skip-lints: - - should_be_noarch_generic - - should_not_be_noarch_source + - should_be_noarch_generic # Package contains platform-specific binaries + - should_not_be_noarch_source # Package contains platform-specific binaries🧰 Tools
🪛 yamllint
[error] 1-1: syntax error: found character '%' that cannot start any token
(syntax)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
recipes/table2asn/build.sh
(2 hunks)recipes/table2asn/meta.yaml
(1 hunks)
🔇 Additional comments (6)
recipes/table2asn/build.sh (2)
Line range hint 18-24
: LGTM! The RPATH modifications look correct.
The change to double brackets is a good improvement. The RPATH modifications are properly handled for both Darwin and non-Darwin systems, ensuring the correct linking of the bzip2 library.
9-9
: 🛠️ Refactor suggestion
Verify single file matching for wildcard pattern.
While adding the -f
flag is good, using the wildcard pattern *.table2asn
could be problematic if multiple matching files exist. This could lead to unpredictable behavior in which file gets copied.
Consider being more specific with the file name or add a check to ensure only one file matches:
- cp -f *.table2asn ${PREFIX}/bin/table2asn
+ # Ensure only one file matches
+ table2asn_files=( *.table2asn )
+ if [ ${#table2asn_files[@]} -ne 1 ]; then
+ echo "Error: Expected exactly one table2asn file, found ${#table2asn_files[@]}"
+ exit 1
+ fi
+ cp -f "${table2asn_files[0]}" "${PREFIX}/bin/table2asn"
recipes/table2asn/meta.yaml (4)
Line range hint 17-19
: LGTM: Appropriate dependency pinning strategy.
The run_exports
section correctly pins the package with max_pin="x"
, which is appropriate for this type of tool where minor version updates shouldn't break compatibility.
🧰 Tools
🪛 yamllint
[error] 1-1: syntax error: found character '%' that cannot start any token
(syntax)
Line range hint 21-24
: Verify if runtime dependencies need updates.
The host requirements remain unchanged. Given this is a version update, please verify if any of the dependencies (libidn11
, zlib
, bzip2
) require version updates.
#!/bin/bash
# Description: Check for any dependency changes in the new version's documentation
curl -sL "https://ftp.ncbi.nlm.nih.gov/asn1-converters/versions/2024-10-23/by_program/table2asn/DOCUMENTATION/table2asn_readme.txt" | grep -i "requirement\|depend\|version"
🧰 Tools
🪛 yamllint
[error] 1-1: syntax error: found character '%' that cannot start any token
(syntax)
2-3
: Verify the package version and checksum.
The version has been updated to 1.28.1179. Let's verify the Linux checksum against the source.
#!/bin/bash
# Description: Verify the Linux package checksum
# Download the file and compute its checksum
curl -sL "https://ftp.ncbi.nlm.nih.gov/asn1-converters/versions/2024-10-23/by_program/table2asn/linux64.table2asn.gz" | sha256sum
11-12
: Verify the macOS source configuration.
The macOS-specific URL and checksum have been updated. Let's verify the checksum.
Describe your pull request here
Please read the guidelines for Bioconda recipes before opening a pull request (PR).
General instructions
@BiocondaBot please add label
command.@bioconda/core
in a comment.Instructions for avoiding API, ABI, and CLI breakage issues
Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify
run_exports
(see here for the rationale and comprehensive explanation).Add a
run_exports
section like this:with
...
being one of:{{ pin_subpackage("myrecipe", max_pin="x") }}
{{ pin_subpackage("myrecipe", max_pin="x.x") }}
{{ pin_subpackage("myrecipe", max_pin="x.x") }}
(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin="x.x.x") }}
(in such a case, please add a note that shortly mentions your evidence for that){{ pin_subpackage("myrecipe", max_pin=None) }}
while replacing
"myrecipe"
with eithername
if aname|lower
variable is defined in your recipe or with the lowercase name of the package in quotes.Bot commands for PR management
Please use the following BiocondaBot commands:
Everyone has access to the following BiocondaBot commands, which can be given in a comment:
@BiocondaBot please update
@BiocondaBot please add label
please review & merge
label.@BiocondaBot please fetch artifacts
You can use this to test packages locally.
Note that the
@BiocondaBot please merge
command is now depreciated. Please just squash and merge instead.Also, the bot watches for comments from non-members that include
@bioconda/<team>
and will automatically re-post them to notify the addressed<team>
.