similar to: R package builder silently continues after unclosed brace

Displaying 20 results from an estimated 200 matches similar to: "R package builder silently continues after unclosed brace"

2020 Jan 25
0
R package builder silently continues after unclosed brace
R CMD build does not actually run any R code, it just puts the files together into a .tar.gz archive. R CMD INSTALL will run the R code, and fail. Gabor On Sat, Jan 25, 2020 at 4:59 PM Andy Manka <andy.manka at gmail.com> wrote: > > > If you start a function in one file but don't close it, the package > will still build if you manage to close it in a later file. Like so:
2003 Sep 28
1
infinite recursion during package installation with methods, setAs
I ran into a problem recently trying to update a package which uses S4 methods using a recent beta of R. I think I can reproduce it with a simple example. I have package called `testpkg' in directory testpkg/. In the R/ subdirectory of testpkg/ I have a file called testpkg.R which contains the following two lines: setClass("testpkg", representation(pts = "list"))
2007 Jul 18
1
possible bug R CMD check: No space(s) allowed after \VignetteDepends{}
R CMD check gives an error when a vignette entry %\VignetteDepends{} has any extra space at the end. Maybe this is by design, but I found it confusing. Changing the function "vignetteMetaRE" in tools package could solve the problem. I.e. vignetteMetaRE <- function(tag) paste("[[:space:]]*%+[[:space:]]*\\\\Vignette", tag,"\\{([^}]*)\\}", sep = "")
2005 Aug 14
1
parse():ing a unclosed string
When parse():ing R code from *file* with a unclosed string, that is, a string that has an open quoation mark, but not a ending one, the string seems to be closed automagically. Is this a "bug"? Example: > code <- "x <- '123"; > parse(text=code) # Gives an error as expected Error in parse(file, n, text, prompt) : parse error >
2020 Sep 11
4
Garbage collection of seemingly PROTECTed pairlist
I want to write an R function using R's C interface that takes a 2-column matrix of increasing, non-overlapping integer intervals and returns a list with those intervals plus some added intervals, such that there are no gaps. For example, it should take the matrix rbind(c(5L, 6L), c(7L, 10L), c(20L, 30L)) and return list(c(5L, 6L), c(7L, 10L), c(11L, 19L), c(20L, 30L)). Because the output is
2013 Mar 04
0
[PATCH 2/2] Btrfs: fix unclosed transaction handler when the async transaction commitment fails
If the async transaction commitment failed, we need close the current transaction handler, or the current transaction will be blocked to commit because of this orphan handler. We fix the problem by doing sync transaction commitment, that is to invoke btrfs_commit_transaction(). Signed-off-by: Miao Xie <miaox@cn.fujitsu.com> --- fs/btrfs/ioctl.c | 4 ++++ 1 files changed, 4
2011 Aug 18
0
[PATCH 3/3] Btrfs: fix unclosed transaction handle in btrfs_cont_expand()
The function - btrfs_cont_expand() forgot to close the transaction handle before it jump out the while loop. Fix it. Signed-off-by: Miao Xie <miaox@cn.fujitsu.com> --- fs/btrfs/inode.c | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 634dd797..ee57b40 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -3510,15
2001 Mar 17
0
OpenSSH_2.5.1p2 hang on log out due to unclosed file handles in forked process
OpenSSH folks, We're run into a problem with OpenSSH_2.5.1p2 servers that we didn't see before, and I can't reproduce with OpenSSH_2.3.0p1 servers. (OpenSSH_2.3.0p1 seems to work correctly) We're seeing this bug on Solaris 2.7 and on Linux 2.2.15 machines. Basically, if you log into a machine, fork a process that leaves stdout, stderr, or stdin open, and try to log out of that
2018 Mar 05
2
Unclosed parenthesis in grep.Rd
Lines 129-131: \code{grep(value = FALSE)} returns a vector of the indices of the elements of \code{x} that yielded a match (or not, for \code{invert = TRUE}. This will be an integer vector unless the input There should be a closing parenthesis after \code{invert = TRUE}
2018 Mar 05
1
Unclosed parenthesis in grep.Rd
There are probably more unmatched parentheses around: detect <- function(file) { text <- paste(readLines(file), collapse = "") nchar(gsub("[^(]", "", text)) != nchar(gsub("[^)]", "", text)) } docs <- list.files("r-source-trunk/src/library", pattern = "\\.Rd$", full.names =
2010 Dec 25
4
[ win32utils-Bugs-28801 ] unclosed handle in Process.setpriority/getpriority
Bugs item #28801, was opened at 2010-12-25 11:02 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=28801&group_id=85 Category: win32-process Group: Code Status: Open Resolution: None Priority: 3 Submitted By: Rafa? Michalski (royaltm) Assigned to: Nobody (None) Summary: unclosed handle in Process.setpriority/getpriority Initial Comment: Using
2017 Nov 16
2
Risks of using "function <- package::function" ?
Large packages sometimes mask each other's functions and that creates a headache, especially for teaching code, since function signatures may depend on which order packages were loaded in. One of my students proposed using the idiom <function> <- <package>::<function> ... in a preamble, when we use just a small subset of functions from a larger package. I like that
2007 Sep 23
3
html help fails for named vector objects (PR#9927)
help(letters, htmlhelp=TRUE) fails. Under the Mac OSX gui, the message is 'Help for the topic "a" was not found.' Under the version documented below, and under Windows, the message is "No documentation for 'a' in specified packages and libraries:" repeated for all the elements of letters, then followed by "you could try
2017 Nov 17
0
Risks of using "function <- package::function" ?
On 16/11/2017 4:53 PM, Boris Steipe wrote: > Large packages sometimes mask each other's functions and that creates a headache, especially for teaching code, since function signatures may depend on which order packages were loaded in. One of my students proposed using the idiom > > <function> <- <package>::<function> > > ... in a preamble, when we use
2007 Apr 11
1
R CMD build fails with try(stop()) in vignette
A vignette in <pkg>/inst/doc with \documentclass[]{article} \begin{document} <<test>>= try(stop('err')) @ \end{document} produces an error with R CMD build <pkg>: ... ** building package indices ... * DONE (testPkg) * creating vignettes ... ERROR Error in try(stop("err")) : err This is not seen with Sweave alone. > sessionInfo() R version 2.5.0
2020 Oct 08
1
Coercion function does not work for the ALTREP object
Hi Gabriel, here is a simple package for reproducing the problem. https://github.com/Jiefei-Wang/testPkg Best, Jiefei On Thu, Oct 8, 2020 at 5:04 AM Gabriel Becker <gabembecker at gmail.com> wrote: > Jiefei, > > Where does the code for your altrep class live? > > Thanks, > ~G > > On Wed, Oct 7, 2020 at 4:25 AM Jiefei Wang <szwjf08 at gmail.com> wrote: >
2017 Nov 17
2
Risks of using "function <- package::function" ?
Obvious? How about "obscurity"? Just directly use pkg::fun if you have name collision. -- Sent from my phone. Please excuse my brevity. On November 16, 2017 4:46:15 PM PST, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >On 16/11/2017 4:53 PM, Boris Steipe wrote: >> Large packages sometimes mask each other's functions and that creates >a headache,
2011 Jul 06
1
including figures in html documentation/help
Dear list members, is it somehow possible to include figures to the html help pages of individueal functions (containing for example a plot produced by that function?) I thought about adding these figures into a 'graphs' subfolder of the package folder and then to somehow insert some sort of html link into the documentation code. I use inlinedocs for creating the documentation. Any
2020 Oct 07
2
Coercion function does not work for the ALTREP object
Hi all, The coercion function defined for the ALTREP object will not be called by R when an assignment operation implicitly introduces coercion for a large ALTREP object. For example, If I create a vector of length 10, the ALTREP coercion function seems to work fine. ``` > x <- 1:10 > y <- wrap_altrep(x) > .Internal(inspect(y)) @0x000000001f9271c0 13 INTSXP g0c0 [REF(2)] I am
2019 Jan 24
0
Possible setClassUnion Unloading Issue
I'm encountering a problem caused by class unions from unloaded packages that are referenced by the still-loaded subclasses. In essence, when the class union is loaded initially, it registers itself as a super class of the component classes in the S4 cache. When the package the class union lives in is unloaded, it does not undo that registration. Here is an MRE of the problems it causes: