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

Treekin #51551

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Treekin #51551

wants to merge 4 commits into from

Conversation

mwaldl
Copy link
Contributor

@mwaldl mwaldl commented Oct 22, 2024

Add runtime dependency libgfortran3 to meta,yaml file. This resolves the runtime error "treekin: error while loading shared libraries: libgfortran.so.3: cannot open shared object file: No such file or directory".

Further clean up might be needed, including adding libgfortran as dependency during build.

Copy link
Contributor

coderabbitai bot commented Oct 22, 2024

📝 Walkthrough
📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request introduces modifications to the meta.yaml file for the treekin package. The primary change is the update of the build number from 4 to 5. Additionally, a new section called run_exports has been added under the build section, which includes a reference to a subpackage myrecipe with a maximum pinning constraint. A new runtime requirement specifying libgfortran with a version constraint of =3 has also been included under the run section. Furthermore, the indentation for the run section has been corrected to align with YAML formatting standards. No other alterations to the logic, error handling, or control flow have been made in this update.

Possibly related PRs

  • 2024.4 #50977: This PR updates the meta.yaml file and emphasizes the importance of specifying run_exports, which is directly related to the changes made in the main PR regarding the introduction of a run_exports section.

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@martin-g
Copy link
Contributor

martin-g commented Oct 23, 2024

@bgruening @aliciaaevans This PR fails with:

13:51:51 �[36mBIOCONDA DEBUG�[0m Found: LintMessage(recipe=Recipe "treekin", check=<class 'bioconda_utils.lint.check_build_help.should_use_compilers'>, severity=<Severity.ERROR: 30>, title='The recipe requires a compiler directly', body="\nSince version 3, `conda-build` uses a special syntax to require\ncompilers for a given language matching the architecture for which\na package is being build. Please use:\n\n    requirements:\n       build:\n         - {{ compiler('language') }}\n\nWhere language is one of `c`, `cxx`, `fortran`, `go` or\n`cgo`. You can specify multiple compilers if needed.\n\nThere is no need to add `libgfortran`, `libgcc`, or\n`toolchain` to the dependencies as this will be handled by\nconda-build itself.", start_line=33, end_line=34, fname='recipes/treekin/meta.yaml', canfix=False)�[0m

but the recipe properly uses - {{ compiler("cxx") }} and - {{ compiler("fortran") }}.

In addition the linting error probably should mention rust too.

@mwaldl
Copy link
Contributor Author

mwaldl commented Oct 28, 2024

@martin-g @bgruening @aliciaaevans Does the linter fail because libgfortran is defined as a runtime dependency?
The build dependency is properly defined as - {{ compiler("fortran") }}, however it appears to also be required at runtime. Any suggestions on how to resolve this?

recipes/treekin/meta.yaml Outdated Show resolved Hide resolved
@martin-g
Copy link
Contributor

@mwaldl According to https://github.com/bioconda/bioconda-utils/blob/5910a1009b8b783eb4a3e1a9b15ab71b9794899a/bioconda_utils/lint/check_build_help.py#L13-L47 it is not allowed to use libgfortran as a dependency.
Let's try with - compiler("fortran") as a run dependency!

recipes/treekin/meta.yaml Outdated Show resolved Hide resolved
@martin-g
Copy link
Contributor

Now it fails with

09:30:20 BIOCONDA DEBUG Found: LintMessage(recipe=Recipe "treekin", check=<class 'bioconda_utils.lint.check_build_help.compilers_must_be_in_build'>, severity=<Severity.ERROR: 30>, title='The recipe requests a compiler in a section other than build', body="\nPlease move the `{{ compiler('language') }}` line into the\n`requirements: build:` section.", start_line=33, end_line=34, fname='recipes/treekin/meta.yaml', canfix=False)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants