Skip to content

Forward-merge release/26.04 into main#1936

Open
gforsyth wants to merge 3 commits intorapidsai:mainfrom
gforsyth:main-merge-release/26.04
Open

Forward-merge release/26.04 into main#1936
gforsyth wants to merge 3 commits intorapidsai:mainfrom
gforsyth:main-merge-release/26.04

Conversation

@gforsyth
Copy link
Contributor

@gforsyth gforsyth commented Mar 19, 2026

Forward merge fixups for #1935

Note that this PR must be merged with /merge nosquash

…wheels against mix of CTK versions (rapidsai#1862)

The changes from rapidsai#1405 introduced linking against nvJitLink. nvJitLink has versioned symbols that are added in each new CTK release, and some of those are exposed in `libcuvs.so`.

`libcuvs` wheels are built against the latest CTK supported in RAPIDS (CUDA 13.1.1 as of this writing), so when those wheels are used in environments with older nvJitLink, runtime errors like this can happen:

> libcugraph.so: undefined symbol: __nvJitLinkGetErrorLog_13_1, version libnvJitLink.so.13

For more details, see rapidsai/cugraph#5443

This tries to fix that.

Contributes to rapidsai/build-planning#257

* builds CUDA 13 wheels with the 13.0 CTK
* ensures CUDA 13 wheels ship with a runtime dependency of `nvidia-nvjitlink>={whatever-minor-version-they-were-built-against}`

Contributes to rapidsai/build-planning#256

* updates wheel tests to cover a range of CTK versions (we previously, accidentally, were only testing the latest 12.x and 13.x)

Other changes

* ensures conda packages also take on floors of `libnvjitlink>={whatever-minor-version-they-were-built-against}`

## Notes for Reviewers

### How I tested this

This uses wheels from similar PRs from RAPIDS dependencies, at build and test time:

* rapidsai/raft#2971
* rapidsai/rmm#2270
* rapidsai/ucxx#604

### Other Options

1. avoiding those versioned symbols with a build-time shim (rapidsai#1855 does this, but hasn't been successful yet)
2. statically linking libnvJitLink (hasn't been successful yet)

Authors:
  - James Lamb (https://github.com/jameslamb)

Approvers:
  - Gil Forsyth (https://github.com/gforsyth)

URL: rapidsai#1862
@gforsyth gforsyth requested a review from a team as a code owner March 19, 2026 17:13
@gforsyth gforsyth added improvement Improves an existing functionality non-breaking Introduces a non-breaking change labels Mar 19, 2026
@gforsyth gforsyth requested a review from a team as a code owner March 19, 2026 17:13
@gforsyth gforsyth requested a review from jameslamb March 19, 2026 17:13
Resolves rapidsai#1207. Depends on rapidsai/raft#2952
This PR introduces the `cuvs::preprocessing::pca` with `float` support. The following APIs are supported:
`fit`, `transform`, `fit_transform`, `inverse_transform`.

Authors:
  - Anupam (https://github.com/aamijar)
  - Divye Gala (https://github.com/divyegala)

Approvers:
  - Divye Gala (https://github.com/divyegala)

URL: rapidsai#1808
Copy link
Member

@jameslamb jameslamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for beating me to this (the conflicts are all my fault).

@gforsyth
Copy link
Contributor Author

/merge nosquash

@rapids-bot
Copy link

rapids-bot bot commented Mar 20, 2026

Commit history integrity check failed: not all commits from original PR #1935 appear to be present individually in this PR's history. This usually happens if commits were squashed during the manual resolution process. Please ensure all original commits are preserved individually. You can fix this and try the /merge nosquash command again.

@gforsyth gforsyth requested review from a team as code owners March 20, 2026 21:06
@gforsyth gforsyth force-pushed the main-merge-release/26.04 branch from 670dfdd to db94025 Compare March 20, 2026 21:08
@gforsyth
Copy link
Contributor Author

/merge nosquash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Improves an existing functionality non-breaking Introduces a non-breaking change

Projects

Development

Successfully merging this pull request may close these issues.

3 participants