-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
R 4.0 #53
Comments
@pcorvalan Great question. I haven't tested on R 4.0. The current tests were on minor versions R 3.5 and dplyr 0.8. I wouldn't expect much to change on R 4.0. Most of the references to stringsAsFactors already involved setting it to I'm not so sure about dplyr 1.0. My advice is taking a look at the changes in the recent release to spot any potential issues, then upgrade in a dev environment see how it goes. If not, then revert and let me know any issues. Happy to help work through it to make sure it works for everyone. |
Fwiw, I just upgraded today to From terminal, I then ran: The Overall, I could have been a bit more organized before doing the upgrade to In minimal initial testing (numerous |
Thanks, @arp3ggio! Appreciate the detail here. Very helpful. Keep me posted if anything pops up. |
Thanks @arp3ggio !! |
Additional background, I'm also using |
I was just trying to use
I did some tracing and the error occurs at line 52 of job_info <- response_parsed %>% xml_ns_strip() %>% xml_find_all("//jobInfo") %>%
map_df(xml_nodeset_to_df) %>% type_convert(col_types = cols()) I had the issue myself the other day with another function of mine as the result of using a posixct in an interval function, but given this issue is the result of the |
@danwwilson After some googling, I think it could be more of a system configuration issue where readr cannot find the Olson database on the system needed to parse datetimes. Could you check out the two similar issues I've linked below and let me know if these explain/solve the issue? Thanks.
|
@StevenMMortimer adding the tzdata to the docker build solved the problem. Thanks a Buch for your help. |
@pcorvalan @arp3ggio @danwwilson The latest release of the package is now on cran (salesforcer 0.1.4). While releasing I tested and built the package on Windows, Ubuntu, and Mac OS X across multiple version of R, namely 3.6.3, 4.0.0, and 4.0.1 (more specifics on the tested configurations are available in cran-comments.md). I didn't encounter any problems with unit tests or installs. As @arp3ggio keenly pointed out, you may have to work through some issues installing the dependencies, but no trouble after that. Please let me know if there are still problems and we can work through them. If there are no lingering issues or I don't hear back in a couple weeks, then I'll close this issue. Other updates made in v0.1.4 are available in NEWS.md Thanks again for your assistance and your patience! 👍 |
Thanks Steven! We upgraded R base in a test machine without any problem. |
Hi Steven,
I would like to ask if you test Salesforcer on R 4.0 environment.
Does Salesforcer have any dplyr package dependency that may be affected if we upgrade to dplyr 1.0?
Saleforcer is a great package!
Thanks!
The text was updated successfully, but these errors were encountered: