-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
BUG: Fixed grow_buffer to grow when capacity is reached #12504
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
Conversation
67aa639
to
3d1078e
Compare
for count in range(1, 101): | ||
try: | ||
read_empty_header(count) | ||
except pandas.parser.CParserError as e: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
import the exception (I think its actually imported already though)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
scratch that. Why are you catching an exception here at all? These should always be empty frames. In fact you can construct the expected frame and compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough. Done.
499d9c5
to
2f8a608
Compare
2f8a608
to
8ba3dd0
Compare
Tests are passing. Should be good to merge, given how simple the fix was. |
thank you sir! |
Could you also close the associated issue? It doesn't seem to have been closed with the commit you made. |
hmm, |
Addresses issue in #12494 by allowing
grow_buffer
to grow the size of the parser buffer when buffer capacity is achieved. Previously, you had to exceed capacity for this to occur, but that was inconsistent with theend_field
check later on when handling the EOF terminator, where reached capacity was considered a buffer overflow.