-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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(rust,python): Fix possibly incorrect order of columns when using ipc stream with_columns
#14859
fix(rust,python): Fix possibly incorrect order of columns when using ipc stream with_columns
#14859
Conversation
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.
Good catch!
Actually, looks like this now results in a test failure - seems like we'll have to fix the bug or skip this test for now and fix it later. The addition of assert
is good regardless.
f6d7bac
to
60af176
Compare
with_columns
@stinodego the failing tests indicated an actual problem. I've addressed this now. The commits are pretty decent so this can be reviewed on a per-commit basis. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #14859 +/- ##
==========================================
+ Coverage 80.98% 81.01% +0.02%
==========================================
Files 1331 1331
Lines 172525 172752 +227
Branches 2455 2455
==========================================
+ Hits 139720 139955 +235
+ Misses 32337 32329 -8
Partials 468 468 ☔ View full report in Codecov by Sentry. |
@ritchie46 I would like to move this forward and would like to get your input on the following:
|
fn assert_df_eq_passes() { | ||
let df = df!("a" => [1], "b" => [2]).unwrap(); | ||
assert_df_eq!(df, df); | ||
drop(df); // Ensure `assert_df_eq!` does not consume its arguments. |
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.
Does assert_eq
take a ref by default?
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.
I think so, although it is not entirely obvious to me why the implementation of assert_eq
is what it is.
No, it's a fix. |
No description provided.