Closed pentschev closed 3 weeks ago
and then updating base images used in devcontainers builds for libraries that use UCX
Put up PRs here:
cuml
had already been updated:
It looks to me like everything needed for this is complete. @pentschev I'm going to close this. Please do re-open it if I've misunderstood and there's still something remaining.
Indeed thanks all! 🙏
To update UCX we must change various different repositories. I hope this issue will be useful for future reference, here are the places we must update:
dependencies.yaml
andconda/recipes/ucx-py/meta.yaml
. See https://github.com/rapidsai/ucx-py/pull/1051 for example;dependencies.yaml
andconda/recipes/ucxx/meta.yaml
. See https://github.com/rapidsai/ucxx/pull/240 for example;conda/recipes/versions.yaml
. See https://github.com/rapidsai/integration/pull/712 for example.VERSION
. See https://github.com/rapidsai/ucx-wheels/pull/10 for example.matrix.yaml
, available versions inucx
feature infeatures/src/ucx/devcontainer-feature.json
and the respective feature version in the same file. See https://github.com/rapidsai/devcontainers/pull/338 for example.Notice that we have two different pinnings:
depends_on_ucx_build
: this refers what UCX version should be used to build and must be equal the minimum version we support, for exampleucx==1.15.0
means we build against version 1.15.0 and that's the minimum required version at runtime;depends_on_ucx_run
: this refers what UCX versions we support running, the minimum version should match at least what's defined independs_on_ucx_build
and has no theoretical upper limit, as API/ABI should be compatible, for exampleucx>=1.15.0,<1.18
.