-
Notifications
You must be signed in to change notification settings - Fork 0
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
Newest version of dplyr (1.1) requires code changes #48
Comments
I have tried to roll back the computer experiencing these issues to 1.0.10 but it fails to build correctly. In the mean time, I am not allowing UGs to use that computer |
From tidyverse/dplyr#6262 or lionel-/lillies@6d0d31f
|
the all.x was apparently never doing anything and causes a critical failure in dplyr 1.1. Paritally addresses #48. However, code is still not ready for new dplyr due to changes in group_by, summarise and the new reframe. See https://dplyr.tidyverse.org/news/index.html
I have managed to install the old version of dply on all the lab computers so I made this low priority. https://dplyr.tidyverse.org/news/index.html Changes I know will affect the code:
|
The all.x is fixed by 4be52ce. The summarize/reframe issue is still outstanding. |
Warning: Returning more (or less) than 1 row per This can be caused by a blank table return. Reproduce: |
Still Happening in Main so haven't closed yet: Loading file... C:\Users\Noelle\AppData\Local\Temp\RtmpknhrcR/86765e9c027e6ce4c27df80c/0.mat Performance checks complete. Run 20240127112732_178.192998468876_1.92546067375806 of Orange1 (#315) saved to disk. |
In dplyr 1.1.0 main fails due to line 316's left_join argument all.x = TRUE
trial_data = dplyr::left_join(x = trial_data_encoded, y = dplyr::select(run_properties$stim_encoding_table, -Repeat_number, -``Delay (s)``), by = "Stim_ID", all.x = TRUE)
It works on the prior 1.0.10 version of dplyr.
In the newer 1.1 version, you get the fatal error:
If you remove the all.x = TRUE argument, the file processes with the additional warnings:
The text was updated successfully, but these errors were encountered: