Forward-merge branch-24.03 into branch-24.06

[rapids-bot]

Forward-merge triggered by push to branch-24.03 that creates a PR to keep branch-24.06 up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.

[rapids-bot]

FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the Resolve conflicts option in this PR, follow these instructions https://docs.rapids.ai/maintainers/forward-merger/

IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the /merge comment). Instead, an admin must manually merge by changing the merging strategy to Create a Merge Commit. Otherwise, history will be lost and the branches become incompatible.

[dagardner-nv]

/ok to test

[codecov]

Codecov Report

Merging #463 (e080e77) into branch-24.06 (bd7955e) will decrease coverage by 0.01%.
Report is 1 commits behind head on branch-24.06.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##           branch-24.06     #463      +/-   ##
================================================
- Coverage         73.68%   73.67%   -0.01%     
================================================
  Files               400      400              
  Lines             14275    14275              
  Branches           1113     1114       +1     
================================================
- Hits              10518    10517       -1     
- Misses             3757     3758       +1     

Flag	Coverage Δ
cpp	70.22% <ø> (ø)
py	41.74% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bd7955e...e080e77. Read the comment docs.