Thanks to you both -- I see it now on Ubuntu. A typo in the code for
restoring the SIGINT handler in the timeout cleanup was installing the
wrong handler. Fixed in R-devel and R-patched.
Best,
luke
On Fri, 14 Sep 2018, Kevin Ushey wrote:
FWIW I can reproduce on macOS with R 3.5.1. A smaller e
FWIW I can reproduce on macOS with R 3.5.1. A smaller example:
system2("ls", timeout = 5); x <- sample(1:1E8)
If I try to interrupt R while that sample call is running, R itself is closed.
Best,
Kevin
On Fri, Sep 14, 2018 at 10:53 AM Emil Bode wrote:
>
> I hope it's not too specific in my
I hope it's not too specific in my setup...
I've tried with system2 added on the first line, so:
Example.R:
system2('ls', timeout=5)
cat('Start non-interruptable functions\n')
sample_a <- sample(1:1e7)
sample_b <- sample(1:2e7)
matching <- match(sample_a, sample_b)
cat('Finished\n')
Sys.sleep(10)
The actual bug corresponding to this thread is:
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17470
On Fri, Sep 14, 2018 at 9:22 AM Jennifer Lyon wrote:
>
> Michael:
>
> I don't see any comments on Bug 17432
> (https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17432) later than June
> 1
Michael:
I don't see any comments on Bug 17432 (
https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17432) later than June
1, 2018. Would you please supply a link pointing to the followup to this
discussion on bugzilla?
Thanks.
Jen.
> On Thu Sep 13 14:14:46 CEST 2018 Michael Lawrence wrote:
>
I can't reproduce this. Can you be more precise: exactly where are you
putting the system2 call and exactly where are you sending the
interrupt signal with ^C?
Best,
luke
On Fri, 14 Sep 2018, Emil Bode wrote:
Hi all,
I found some strange behaviour, which I think is a bug. Could someone make
Hi all,
I found some strange behaviour, which I think is a bug. Could someone make an
account for me on Bugzilla or pass on my report?
The problem:
When pressing Ctrl-C when a file is sourced in R, run from Terminal (macOS),
sometimes the entire session is ended right away, while I just want to
Hello all,
Currently, the default behavior for system.file() is to return "" for
faulty paths.
I've found this behavior to be difficult when debugging, since it passes
the empty path onto other functions. I initially wrote in errors myself
(with code like `if(path == "") stop(“Path not found”)`)
On 14/09/2018 3:22 AM, Witold E Wolski wrote:
Dear Community,
I have an Rmarkdown vignette with optional child documents.
Since all markdown files in the vingette folder are build when
executing R CMD build
I did place the child documents in
/inst/ParametrizedReportChid/
so they are excluded fro
>
> on Thu, 13 Sep 2018 23:33:41 -0700 writes:
> Hello Core Team, I sent this patch over a year ago. It
> looks like it was sent in response to another user's
> complaint which echoed some of my own observations about
> problems in the documentation for 'text'. Did a
Dear Community,
I have an Rmarkdown vignette with optional child documents.
Since all markdown files in the vingette folder are build when
executing R CMD build
I did place the child documents in
/inst/ParametrizedReportChid/
so they are excluded from the build.
I do reference them from the markd
11 matches
Mail list logo
