-
Notifications
You must be signed in to change notification settings - Fork 884
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
[BUG] off-by-one errors in cudf.date_range
#12133
Labels
Milestone
Comments
wence-
added
bug
Something isn't working
Needs Triage
Need team to review and classify
Python
Affects Python cuDF API.
labels
Nov 11, 2022
GregoryKimball
added
1 - On Deck
To be worked on next
and removed
Needs Triage
Need team to review and classify
labels
Nov 19, 2022
This was referenced Feb 27, 2024
rapids-bot bot
pushed a commit
that referenced
this issue
Jul 16, 2024
There are some cupy usages that don't seem _strictly_ necessary (generating starting data, array type conversion) in some APIs. IMO we should prefer using CPU data/the existing data structure/Column ops over cupy when possible closes #12133 Authors: - Matthew Roeschke (https://github.com/mroeschke) Approvers: - Bradley Dice (https://github.com/bdice) URL: #16277
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
[As part of attempting to get to XPASS-zero in the test suite]
If the date range is long enough, and for some frequencies,
cudf.date_range
has a fencepost error in the number of dates it produces.Steps/Code to reproduce bug
Expected behavior
No fencepost error.
The text was updated successfully, but these errors were encountered: