-
Notifications
You must be signed in to change notification settings - Fork 112
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
Release gtrendsR 1.4.6 #347
Comments
This will be a release to fix a CRAN issue due to failing tests. https://cran.r-project.org/web/checks/check_results_gtrendsR.html |
What drove the breakage?
|
It was related to a use case where there was no rising data returned by Google. So it was just an unhandled use case in our code. Lines 47 to 82 in cb93d9e
|
I am facing an issue that I do not understand with gtrendsR/inst/tinytest/test_encoding_does_not_change.R Lines 2 to 3 in cb93d9e
This works: kw <- "赤"
res <- gtrends(kw) This fails: tinytest::run_test_file("inst/tinytest/test_encoding_does_not_change.R") Any ideas? PS. It works fine on any Linux distro. |
Yes. It is spelled W. I. N. D. O. W. S. It simply doesn't have the utf-8 support real computers have. Skip the test on that platform, I do these same in some repo. (See e.g. anytime for a bazillion tests and skips because working with timezones on different OSs is only for crazy people ....) Off for a run now, poke me later if this persists, |
I think I even have a utf-8 test somewhere that I skip on Windows. Possibly in Rcpp. |
Prepare for release:
devtools::check(remote = TRUE, manual = TRUE)
devtools::check_win_devel()
rhub::check_for_cran()
revdepcheck::revdep_check(num_workers = 4)
cran-comments.md
Submit to CRAN:
usethis::use_version('patch')
devtools::submit_cran()
Wait for CRAN...
usethis::use_github_release()
usethis::use_dev_version()
The text was updated successfully, but these errors were encountered: