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.

Sign up for GitHub

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

Jump to bottom

[BUG] deprecated warnings should be enabled #14819

Open
karthikeyann opened this issue Jan 22, 2024 · 0 comments
Open

[BUG] deprecated warnings should be enabled #14819

karthikeyann opened this issue Jan 22, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@karthikeyann
Copy link
Contributor

karthikeyann commented Jan 22, 2024 •
edited
Loading

Describe the bug
deprecated warnings are disabled by default in build.sh. Dev containers have them enabled.
in rapids-compose also, it's disabled by default in bash-utils.sh

PR #14771 fixes deprecated warnings introduced when #14202 merged. These warnings didn't showup during development (used rapids-compose)

Expected behavior
deprecated warnings should be enabled by default.
deprecated APIs usage are typically removed from unit tests, benchmarks and wrapper APIs as well.

Environment overview (please complete the following information)

  • Environment location: Bare-metal, rapids-compose
  • Method of cuDF install: from source

Additional context
#14771 (comment)
@karthikeyann karthikeyann added bug Something isn't working Needs Triage Need team to review and classify labels Jan 22, 2024
@bdice bdice removed the Needs Triage Need team to review and classify label Mar 4, 2024
@mroeschke mroeschke mentioned this issue Jul 17, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
libcudf
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bdice @karthikeyann