You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing lazy validation, pandera bubbles up the first SchemaError observed. However, in the error handling function, the error data is explicitly deleted (for the case of not duplicating data when lazy=True).
The result is that in the case of lazy=False validations, the error message does not include the input dataframe.
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandera.
(optional) I have confirmed this bug exists on the main branch of pandera.
Note: Please read this guide detailing how to provide the necessary information for us to reproduce your bug.
Code Sample, a copy-pastable example
Minimal test that should pass when the bug is fixed:
Describe the bug
When doing lazy validation, pandera bubbles up the first
SchemaError
observed. However, in the error handling function, the error data is explicitly deleted (for the case of not duplicating data whenlazy=True
).The result is that in the case of
lazy=False
validations, the error message does not include the input dataframe.Note: Please read this guide detailing how to provide the necessary information for us to reproduce your bug.
Code Sample, a copy-pastable example
Minimal test that should pass when the bug is fixed:
Expected behavior
e.data
should have theinvalid_df
dataframe in itDesktop (please complete the following information):
The text was updated successfully, but these errors were encountered: