-
Notifications
You must be signed in to change notification settings - Fork 303
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: Added an error message with column name when Series to pyarrow conver… #1622
fix: Added an error message with column name when Series to pyarrow conver… #1622
Conversation
…sion fails. Allows for easier debugging.
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use -- conventional-commit-lint bot |
…-conversion' into fix/clearer-error-during-pyarrow-conversion
Do we have any evidence that this problem affects other conversions besides Does a similar problem occur with:
If YES do we need to have similar error handling behavior on lines 376-379? |
Good point. I would say yes. The Try block should cover lines 376 to 380. |
The content of this PR has been incorporated in the following PR: #1836 |
Closed by the merger of #1836 |
Thanks! |
…sion fails. Allows for easier debugging.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #1621 🦕