similar to: readLines function with R >= 3.5.0

>>>>> Michael Lawrence >>>>> on Tue, 12 Jun 2018 19:27:49 -0700 writes: > Hi Jen, This was already resolved for R 3.5.1 by just > disabling buffering on terminal file connections like stdin. and before R 3.5.1 exists, *and* as the change is also not yet available in R patched (!) this means using a version of "R-devel", e.g. for Windows

Dear all, I would like to draw you attention to this question on SO: https://stackoverflow.com/questions/50372043/readlines-function-with-new-version-of-r Based on the OP's code I used the script ####################################### create_matrix <- function() { cat("Write the numbers of vertices: ") user_input <- readLines("stdin", n=1) user_input <-

Hi Michael: I can confirm Martin's comment. I tested my software with r-devel (r74914) and it works, while with r-patched (r74914) it does not work (it hangs, as it did in R 3.5.0). I apologize for it taking so long for me to test this, but is there any chance this fix could make into R 3.5.1? Thanks. Jen. On Wed, Jun 13, 2018 at 6:24 AM, Michael Lawrence <lawrence.michael at gene.com

>>>>> Martin Maechler >>>>> on Mon, 28 May 2018 10:28:01 +0200 writes: >>>>> Ralf Stubner >>>>> on Fri, 25 May 2018 19:18:58 +0200 writes: >> Dear all, I would like to draw you attention to this >> question on SO: >>

Hi Jen, This was already resolved for R 3.5.1 by just disabling buffering on terminal file connections like stdin. Sounds like you might want to be running a web service or something instead though. Michael On Tue, Jun 12, 2018 at 4:46 PM, Jennifer Lyon <jennifer.s.lyon at gmail.com> wrote: > Hi: > > I have also just stumbled into this bug. Unfortunately, I can not > change

Are you sure it's not available in patched? It's definitely in the source since 6/1. Michael On Wed, Jun 13, 2018 at 2:19 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> Michael Lawrence >>>>>> on Tue, 12 Jun 2018 19:27:49 -0700 writes: > > > Hi Jen, This was already resolved for R 3.5.1 by just > >

>>>>> Ralf Stubner >>>>> on Fri, 25 May 2018 19:18:58 +0200 writes: > Dear all, I would like to draw you attention to this > question on SO: > https://stackoverflow.com/questions/50372043/readlines-function-with-new-version-of-r > Based on the OP's code I used the script > ####################################### >

stdin() is not the same as file("stdin"), see the note in ?stdin. Gabor On Mon, 28 May 2018, 10:41 Martin Maechler, <maechler at stat.math.ethz.ch> wrote: > >>>>> Martin Maechler > >>>>> on Mon, 28 May 2018 10:28:01 +0200 writes: > > >>>>> Ralf Stubner > >>>>> on Fri, 25 May 2018 19:18:58 +0200

On 28.05.2018 11:07, G?bor Cs?rdi wrote: > stdin() is not the same as file("stdin"), see the note in ?stdin. In particular stdin() works in an interactive session but not when R -f / Rscript is used, since it does not wait for the user to input anything: $ R -f readLines.R R version 3.5.0 (2018-04-23) -- "Joy in Playing" Copyright (C) 2018 The R Foundation for Statistical

>>>>> Ralf Stubner >>>>> on Mon, 28 May 2018 12:13:57 +0200 writes: > On 28.05.2018 11:07, G?bor Cs?rdi wrote: >> stdin() is not the same as file("stdin"), see the note in ?stdin. Of course it is not the same, otherwise using one for the other had no effect, but you are right: it is *NOT* a solution to the problem > In

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: > > Thanks, I responded to this on bugzilla. > On Wed, Sep 12, 2018 at 9:04 AM Chris

Bug 17432 (https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17432) is still a problem when using pipes for IPC. The bug is evident when calling R from another process and trying to communicate via StdIn. R will buffer the input and not read lines until the buffer is exceeded or StdIn is closed by the sending process. This prevents interactive communication between a calling process and a

Hi: I have a 2.1GB JSON file. Typically I use readLines() and jsonlite:fromJSON() to extract data from a JSON file. When I try and read in this file using readLines() R segfaults. I believe the two salient issues with this file are 1). Its size 2). It is a single line (no line breaks) I can reproduce this issue as follows #Generate a big file with no line breaks # In R >

Thank you for your suggestion. Unfortunately, while R doesn't segfault calling readr::read_file() on the test file I described, I get the error message: Error in read_file_(ds, locale) : negative length vectors are not allowed Jen On Sat, Sep 2, 2017 at 1:38 PM, Ista Zahn <istazahn at gmail.com> wrote: > As s work-around I suggest readr::read_file. > > --Ista > > >

On 28.05.2018 16:38, Martin Maechler wrote: > Then, I now do think this needs to be dealt with as a bug > (but I'm not delving into fixing it!) Ok. Can somebody with write privileges in bugzilla add the bug report? I can also do this myself, if somebody with the required privileges can create a user for me. Greetings Ralf PS: I get an error message from

>>>>> Ralf Stubner >>>>> on Tue, 29 May 2018 11:21:28 +0200 writes: > On 28.05.2018 16:38, Martin Maechler wrote: >> Then, I now do think this needs to be dealt with as a bug >> (but I'm not delving into fixing it!) > Ok. Can somebody with write privileges in bugzilla add the > bug report? I can also do this myself,

Jeroen: Thank you for pointing me to ndjson, which I had not heard of and is exactly my case. My experience: jsonlite::stream_in - segfaults ndjson::stream_in - my fault, I am running Ubuntu 14.04 and it is too old so it won't compile the package corpus::read_ndjson - works!!! Of course it does a different simplification than jsonlite::fromJSON, so I have to change some code, but

It seems that the behavior of readLines() in R 3.5 has changed for non-blocking pipeline. Consider the following R script, which reads from STDIN line by line. ``` con <- file("stdin") open(con, blocking = FALSE) while (TRUE) { ? ? txt <- readLines(con, 1) ? ? if (length(txt) > 0) { ? ? ? ? cat(txt, "\n", file = stdout()) ? ? } ? ? Sys.sleep(0.1) } close(con) ```

The issue is that readLines() tries to seek (for reasons I don't understand) in the non-blocking case, but silently fails for "stdin" since it's a stream. This confused the buffering logic. The fix is to mark "stdin" as unable to seek, but I do wonder why readLines() is seeking in the first place. Anyway, I'll get this into patched ASAP. Thanks for the report.

Hi Folks, BackgrounDRb is a Ruby job server and scheduler. Its main intent is to be used with Ruby on Rails applications for offloading long-running tasks. Since a Rails application blocks while serving a request it is best to move long-running tasks off into a background process that is divorced from http request/response cycle. This new release of BackgrounDRb is also modular and can be used