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.

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

Fix warning when dependencies.yaml doesn't exist #35

Merged

Conversation

KyleFromNVIDIA
Copy link
Contributor

The warning was accidentally being issued with a tuple instead of a string. Fix.

The warning was accidentally being issued with a tuple instead of
a string. Fix.
@KyleFromNVIDIA KyleFromNVIDIA requested a review from a team as a code owner May 17, 2024 18:40
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.

blegh thank you for fixing this! Sorry I didn't write a test case for it in #33 .

@jameslamb jameslamb added bug Something isn't working non-breaking Introduces a non-breaking change labels May 17, 2024
@KyleFromNVIDIA KyleFromNVIDIA merged commit ca51a32 into rapidsai:main May 17, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working non-breaking Introduces a non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants