-
Notifications
You must be signed in to change notification settings - Fork 8
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
Annoying condition messages from rlang (deprecated as_character) logged while using dplyr arrange and group_by functions #62
Comments
Thanks for your excellent issue report incl. a perfect reproducible example! The reason for this "chattiness" is the I have already opened an Since the fix seems to be easy I probably should send a PR myself to Until then there is a workaround to switch off the deprecation infos of
|
Observation:
Output:
I think this is related to the Note that if I run the same code outside the Expected behaviour: |
@tkharrat Good observation, not even my proposed workaround does help here :-(
Currently I do not yet understand how I guess that the signal is thrown and later captured + hidden in I will dig into the issue this weekend (I hope)... |
Issue analysis results (wip):SummaryThe annoying messages are caused by non-standard conditions (sub classes of Standard R does not write non-standard conditions to the console (no output) which explains the different behaviour between a direct call and a call within Analysis details
Possible fixes
Furthermore another option to specify the severity level of non-standard conditions could be introduced (eg. together with new log level functions like "debug" and "trace"). |
Hi, this package is very usefull in a project where I do a lot of |
Oh yes, PRs are always welcome an sorry for not having fixed this annoying issue sooner. Which implementation would you suggest (I am open for discussions!). Currently I still prefer an implementation that changes the current Furthermore perhaps a possiblilty to provide a positive list of all condition classes to be logged would be great. How about this signature and semantics:
with these allowed values for NA = do not log any condition Other suggestions and discussions welcome! |
Your proposal is excellent! I will take some time to propose a PR by this week-end. Have a good day. |
THX a lot for your support! BTW: I am still not sure if it would be more consistent to use NA to log all conditions and "" to log no condition (providing a vector is a white list then)... |
FYI: I have pushed the current implementation to this feature branch: The have refactored the implementation (just to apply my personal coding style) and extended the unit tests... Next steps: I will review the changes in a few days and probably rename the new argument |
Thanks a lot for letting me know! |
Fixed with commit 4fe9478 I am preparing the CRAN release new (planned end of October 2021) |
FYI: Released at CRAN today as version 1.3.1: |
SessionInfo
R version 4.0.3 (2020-10-10)
Platform: x86_64-conda-linux-gnu (64-bit)
Running under: Ubuntu 20.04.1 LTS
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] tryCatchLog_1.2.1 dplyr_1.0.2
loaded via a namespace (and not attached):
[1] rstudioapi_0.13 magrittr_2.0.1 tidyselect_1.1.0 lattice_0.20-41 R6_2.5.0 rlang_0.4.9 fansi_0.4.1
[8] tools_4.0.3 grid_4.0.3 utf8_1.1.4 cli_2.2.0 lambda.r_1.2.4 futile.logger_1.4.3 ellipsis_0.3.1
[15] assertthat_0.2.1 tibble_3.0.4 lifecycle_0.2.0 crayon_1.3.4 Matrix_1.2-18 purrr_0.3.4 formatR_1.7
[22] vctrs_0.3.5 futile.options_1.0.1 glue_1.4.2 compiler_4.0.3 pillar_1.4.7 generics_0.1.0 pkgconfig_2.0.3
Observation:
When using a tryCatchLog or tryCatch function with arrange from dplyr , it throws annoying INFO messages :
library(dplyr)
library(tryCatchLog)
Output :
Expected behaviour:
Do not throw deprecation INFO warnings messages when using
arrange
function fromdplyr
.Postscript :
When using other functions from
dplyr
package such as select or filter .. , it doesn't throw INFO warnings messages and works fine .The text was updated successfully, but these errors were encountered: