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
Describe the bug, including details regarding any error messages, version, and platform.
dplyr 1.1.0 is being sent to CRAN tomorrow. I reran the revdeps again today and arrow popped up all of a sudden as a new broken revdep. I wish we could give you all more time, but unfortunately there were only 3 new revdep failures detected today, so we plan to continue with the release tomorrow anyways.
There seem to be quite a few test failures, many of which look to be overly strict tests. I've put the full test output in the details section at the very bottom of this issue. I'll also list a few problems I see along with the corresponding NEWS bullet to try and help you out:
Probably related to the fact that joins in dplyr now throw a warning by default if multiple matches are detected. Set multiple = "all" to silence this.
Seems like a possible typo on your end, as semi_join() doesn't have the keep arg and we actually check for empty dots now.
── Error ('test-dplyr-slice.R:145'):slice_*notsupportedwithgroups ─────────
Errorin`slice_min(grouped, n = 5)`:`order_by`isabsentbutmustbesupplied.
slice_min() and friends do better checking for absent arguments so maybe you were expecting a different error message. We also do this error checking in the generic which is before anything on your end can run.
I'm happy to report that - at least as of today - we've fixed all of those! (I also just ran pak::pak("tidyverse/dplyr") and devtools::test() to double check). We're in the process of preparing a CRAN release in the next week or so (if all goes well).
kou
changed the title
dplyr 1.1.0 compatibility
[R] dplyr 1.1.0 compatibility
Jan 27, 2023
Describe the bug, including details regarding any error messages, version, and platform.
dplyr 1.1.0 is being sent to CRAN tomorrow. I reran the revdeps again today and arrow popped up all of a sudden as a new broken revdep. I wish we could give you all more time, but unfortunately there were only 3 new revdep failures detected today, so we plan to continue with the release tomorrow anyways.
There seem to be quite a few test failures, many of which look to be overly strict tests. I've put the full test output in the details section at the very bottom of this issue. I'll also list a few problems I see along with the corresponding NEWS bullet to try and help you out:
A few
distinct()
failures, probably related to:Probably related to the fact that joins in dplyr now throw a warning by default if multiple matches are detected. Set
multiple = "all"
to silence this.Seems like a possible typo on your end, as
semi_join()
doesn't have thekeep
arg and we actually check for empty dots now.slice_min()
and friends do better checking for absent arguments so maybe you were expecting a different error message. We also do this error checking in the generic which is before anything on your end can run.n_distinct()
now errors if 0 inputs are provided, because that is almost always a mistake.Component(s)
R
The text was updated successfully, but these errors were encountered: