-
Notifications
You must be signed in to change notification settings - Fork 186
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
Bump roxygen2 version #2510
Bump roxygen2 version #2510
Conversation
|
@MichaelChirico thanks for the pointer. I looked at the diff and found the problem:
|
Thanks for the pointer; filed something that works in r-lib/roxygen2#1573. |
Thank you, both, for getting to the bottom of this so quickly and for filing a fix! |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2510 +/- ##
==========================================
+ Coverage 98.53% 98.55% +0.02%
==========================================
Files 125 126 +1
Lines 5609 5762 +153
==========================================
+ Hits 5527 5679 +152
- Misses 82 83 +1 ☔ View full report in Codecov by Sentry. |
Can confirm that devel-roxygen2 fixes the issue. The new warning in the examples looks legit, though, and something we should deal with. |
Can you point to the warning? I'm seeing various issues & can't figure out what's the problem, exactly. Maybe we're seeing something different, though. |
I see: > ### Name: get_r_string
> ### Title: Extract text from 'STR_CONST' nodes
> ### Aliases: get_r_string
>
> ### ** Examples
>
> ## Don't show:
> if (requireNamespace("withr", quietly = TRUE)) (if (getRversion() >= "3.4") withAutoprint else force)({ # examplesIf
+ ## End(Don't show)
+ tmp <- withr::local_tempfile(lines = "c('a', 'b')")
+ expr_as_xml <- get_source_expressions(tmp)$expressions[[1L]]$xml_parsed_content
+ writeLines(as.character(expr_as_xml))
+ get_r_string(expr_as_xml, "expr[2]") # "a"
+ get_r_string(expr_as_xml, "expr[3]") # "b"
+
+ # more importantly, extract strings under R>=4 raw strings
+ ## Don't show:
+ }) # examplesIf
> tmp <- withr::local_tempfile(lines = "c('a', 'b')")
> expr_as_xml <- get_source_expressions(tmp)$expressions[[1L]]$xml_parsed_content
Error in file(con, "r") :
(converted from warning) cannot open file '/var/folders/xr/v_vddzvs33q5wg7jv9mr__4h0000gn/T//Rtmpk8Dcx3/file640749057d03': No such file or directory
Run `rlang::last_trace()` to see where the error occurred.
ℹ Loading lintr
> rlang::last_trace()
<error/rlang_error>
Error:
! No such file or directory
---
Backtrace:
▆
1. └─devtools::run_examples(run_donttest = TRUE, run_dontrun = TRUE)
2. └─base::lapply(...)
3. └─pkgload (local) FUN(X[[i]], ...)
4. └─base::source(tmp, echo = !quiet, local = env, max.deparse.length = Inf)
5. ├─base::withVisible(eval(ei, envir))
6. └─base::eval(ei, envir)
7. └─base::eval(ei, envir)
8. ├─(if (getRversion() >= "3.4") withAutoprint else force)(...) at /Rtmpk8Dcx3/file6407739f7efc.R:8:1
9. │ └─base::source(...)
10. │ ├─base::withVisible(eval(ei, envir))
11. │ └─base::eval(ei, envir)
12. │ └─base::eval(ei, envir)
13. └─lintr::get_source_expressions(tmp)
14. └─lintr:::read_lines(filename) at lintr/R/get_source_expressions.R:69:5
15. ├─base::withCallingHandlers(...) at lintr/R/utils.R:182:3
16. └─base::readLines(file, warn = TRUE, ...)
17. └─base::file(con, "r") |
Hmm I'm not seeing that. Maybe transient. Closing + reopening to see if 7.3.1 gets picked up by CI yet. |
#2518 proves (IINM) the issue is not related to {roxygen2}, since running with {pkgload} skips the The new error might then be related to the {pkgload} update. Anyway, merging this. |
No longer relevant after #2519 merge |
Re-documenting with the new version of
{roxygen2}
(7.3.0) seems to generate a non-parsableNAMESPACE
file.I am wondering if this is a bug upstream.