-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
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 or unhelpful error message in 0.12 and trunk: IndexError: Out of bounds on buffer access (axis 0) #4825
Comments
Seem ok in master (they on don't raise because you have least 1 valid value)
|
either I've made a mistake in simplifying or the above scenario has been fixed in the last 2 days of trunk.
|
did u make build? eg regen the cython code |
I just ran:
Is that correct? |
yep |
I've deleted and refetched and rebuilt the pandas source, nosetests show only skips, no errors, the above still fails. |
can u show |
|
It's running on freshly purpose-built VM with an up-to-date ArchLinux x64, although it also fails on 0.12 in Windows - just that without nightly windows builds and not being able to get pandas to compile with either mingw or Win SDK 7.0 I had to build this VM just for this bug! |
Are you having difficulty reproducing? |
@ruidc I can't reproduce this either. |
Can you reproduce on 0.12 ? |
@ruidc yes, it produces an error for me in 0.12.0, but this no longer occurs on current master. I believe we're putting out either a point release or a new release version very soon. I am, however, going to add this to the test suite. Error was:
|
can you post the full trace back u r getting? |
Thanks, I look forward to Windows binaries from head working again, or an RC binary for 0.13.
|
no this changed from 0.12 |
Fixed...here's the behavior. Anything look odd? None of these raise (well doing
This is a unique index on the selector (effectively like a reindex)
These raise as expected
|
sorry, am away from the office now so can't test the patch until monday From: jreback notifications@github.com @jtratner @ruidc thoughts? |
@jreback that looks fine to me... |
were you able to reproduce in the end? applying this PR, I get the original passing but:
|
updated....was doing something dumb! thanks for the tests
|
Let me know when I can test it again as our data seems to cover a few bases ;) |
the PR is updated |
looks great now, thx! do I close the Issue or should it only be closed when the pull request is closed? |
... also for future reference, were you able to reproduce the problem then? or where did we have the disconnect on not having our results match? |
no.your examples where showing errors; I added them as test cases. This particular indexing point in the code was 'new' and just didn't have all the cases covered, as certain examples 'worked' even when was doing something 'wrong'. So had a false positive before. thanks for the help! |
the thanks is all mine! From: jreback notifications@github.com @ruidc |
The following raises the error
whilst
does not. Or is there something invalid with this code?
The text was updated successfully, but these errors were encountered: