-
Notifications
You must be signed in to change notification settings - Fork 8
fix: max_by min_by #21
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
base: main
Are you sure you want to change the base?
fix: max_by min_by #21
Conversation
|
what do you mean about OK and KO? |
Hi, sorry for not explaining it properly last night — it was really late. By OK, I mean the expected behaviour of the test (we exclude the nulls). By KO, I mean the current incorrect behaviour: the test fails now, but without my changes it “passes” even though the result is not the expected one. The KO test should be removed before merging, since it's the opposite case and only exists to demonstrate the current incorrect behaviour. |
9568fb5 to
a222cdc
Compare
|
hi @dariocurr, I think now we can see better in 1a52b8a we can see the bug solved too in the expected values I need refactor unit test like in your code |
|
sorry again, I fixed in Sail lakehq/sail#1049 and now pass the ibis test, these tests |

I think this is a bug
I have a test to ok and ko
In Spark
