ray-packages v2.9.3

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
opencensus	0.11.4-1.1.13
openjdk	21.0.2+13
protobuf	25.3
ray-packages	2.9.3

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by source code inspection shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by source code inspection but not in the meta.yaml:

• joblib
• torchvision
• diffusers
• azure-storage-blob
• typing_extensions
• cupy
• scikit-learn
• jupytext
• retry
• docker-py
• google-api-python-client
• jinja2
• cryptography
• xgboost
• mpi4py
• aws-requests-auth
• tqdm
• pyspark
• paramiko
• aliyun-python-sdk-core
• pytorch-lightning
• dask
• lightgbm
• pygithub
• numpy
• matplotlib
• botocore
• mashumaro
• arm_pyart
• pytest
• pytorch
• anyscale
• gpy
• locust
• pyvmomi
• python-kubernetes
• tensorflow
• boto3
• horovod
• xarray

Packages found in the meta.yaml but not found by source code inspection:

• ray-tune
• ray-air
• ray-default
• ray-rllib
• ray-data
• protobuf
• ray-client
• opentelemetry-api
• typing-extensions
• opentelemetry-sdk
• async-timeout
• ray-serve
• opentelemetry-exporter-otlp
• ray-train

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/8014707074, please use this URL for debugging.}

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[mattip]

Well, this is a new error. All the runs are failing with

warning  libmamba Problem type not implemented SOLVER_RULE_STRICT_REPO_PRIORITY

when trying to create an environment with

mamba install --update-specs --yes --quiet --channel conda-forge \
    --strict-channel-priority \
    pip mamba conda-build boa conda-forge-ci-setup=4 'conda-build>=24.1'

[mattip]

Or is that only a warning, and the real problem is that the build cannot install python3.10, even when building for python3.8?

Looking for: ['python=3.10', 'pip', 'mamba', 'conda-build', 'boa', \
              'conda-forge-ci-setup=4', "conda-build[version='>=24.1']"]

Could not solve for environment specs
The following packages are incompatible
├─ boa is installable with the potential options

[h-vetinari]

ray-packages-feedstock/conda-forge.yml

Line 5 in 505c882

conda_build_tool: mambabuild

is conflicting with the switch to conda-build by default in conda-smithy 3.31. However, 3.31 was just marked as broken, so rerendering again should fix it.

@conda-forge-admin, please rerender

[h-vetinari]

is conflicting with the switch to conda-build by default in conda-smithy 3.31.

Ah, and the fact that boa requires conda-build <24.1, see conda-forge/boa-feedstock#79

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/ray-packages-feedstock/actions/runs/8015660329.

[mattip]

The line conda_build_tool: mambabuild came in as part of the OSXarm migration. Should it be deleted only here or as part of a wider effort?

[h-vetinari]

Should it be deleted only here or as part of a wider effort?

It shouldn't be incompatible per se, it just runs into the conflict between boa and the demanded conda-build version. For how to handle it, better chime in on the conda-smithy issue, or open a separate one.

[h-vetinari]

bazel-out/k8-opt/bin/external/local_config_python/_python3/_python3_include/Python.h:44:10: fatal error: crypt.h: No such file or directory
   44 | #include <crypt.h>
      |          ^~~~~~~~~

This needs a host-dep on

- libxcrypt  # [linux and py<39]

due to conda-forge/linux-sysroot-feedstock#52.

For windows, AFAICT, the reason is:

  ERROR: no such package '@rules_perl//perl': error running 'git fetch origin refs/heads/*:refs/remotes/origin/* refs/tags/*:refs/tags/*' while working with @rules_perl:
  fatal: full write to remote helper failed: Broken pipe

[mattip]

Stack overflow thinks the windows failure is connected to the git version. I wonder if something changed with the windows git version, or if it would make sense to get git from conda-forge on windows.

[mattip]

locally, the problem does not manifest.