similar to: Inconsistency in creating/opening/closing/destroying (PR#788)

I expected close() to be the opposite of open(), but > # create a connection > con <- file("ex.data") > # open it > open(con, "w") > # close it > close(con) > # re-open it > open(con, "w") Error in open.connection(con, "w") : invalid connection > > con Error in summary.connection(x) : invalid connection > # is obviously

On Wed, 20 Dec 2000 joehl@web.de wrote: > > # creating a file > > cat("sddfasdf", file="tempfile") > > showConnections() > class description mode text isopen can read can write > > con <- file("tempfile", "r") > > readLines(con) > [1] "sddfasdf" > Warning message: > incomplete final line in:

> # creating a file > cat("sddfasdf", file="tempfile") > showConnections() class description mode text isopen can read can write > con <- file("tempfile", "r") > readLines(con) [1] "sddfasdf" Warning message: incomplete final line in: readLines(con, n, ok) > showConnections() class description mode text isopen

help on showConnections explains parameter all logical: if true all connections, including closed ones and the standard ones are displayed. If false only open user-created connections are included. but > # create a file > cat("TITLE extra line", "2 3 5 7", "", "11 13 17", file="ex.data", + sep="\n") >

# Have no other connections opened yet > showConnections() class description mode text isopen can read can write > sink("tempfile") > close(getConnection(3)) > cat("send some output\n") Error in stdout() : invalid connection > sink() Error in sink() : invalid connection > cat("send some output\n") Error in stdout() : invalid connection >

# Have no other connections opened yet > showConnections() class description mode text isopen can read can write > sink("tempfile") > close(getConnection(3)) > cat("send some output\n") Error in stdout() : invalid connection > sink() Error in sink() : invalid connection > cat("send some output\n") Error in stdout() : invalid connection >

help on showConnections explains parameter all logical: if true all connections, including closed ones and the standard ones are displayed. If false only open user-created connections are included. but > # create a file > cat("TITLE extra line", "2 3 5 7", "", "11 13 17", file="ex.data", + sep="\n") >

On Thu, Dec 14, 2017 at 12:17 PM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > On Thu, Dec 14, 2017 at 7:56 PM, Gabriel Becker <gmbecker at ucdavis.edu> > wrote: > > Gabor, > > > > You can grab the connection and destroy it via getConnection and then a > > standard close call. > > Yeah, that's often a possible workaround, but since this

This has nothing to do with on.exit. It is an iteraction between where the warning is signaled in 'file' and your _exiting_ warning handler. This combination has the same issue, tryCatch(file(tempfile(), "r"), warning = identity) showConnections(all = TRUE) as does options(warn=2) file(tempfile(), "r") showConnections(all = TRUE) I haven't looked at the

Gabor, You can grab the connection and destroy it via getConnection and then a standard close call. (it actually lists that it is "closed" already, but still in the set of existing connections. I can't speak to that difference). > tryCatch( + readLines(tempfile(), warn = FALSE)[1], + error = function(e) NA, + warning = function(w) NA + ) [1] NA >

Thanks for tracking this down. Yeah, I should use suppressWarnings(), you are right. Although, readLines() might throw another warning, e.g. for incomplete last lines, and you don't necessarily want to suppress that. TBH I am not sure why that warning is given: ? con <- file(tempfile()) ? open(con) Error in open.connection(con) : cannot open the connection In addition: Warning message: In

Hi, I am making multiple calls to gzfile() via read.table(), e.g. > x <- read.table( gzfile( "xxx.gz" ) ) After i do this many times (I haven't counted, but probably between 50 and 100 times) I get the error message: Error in open.connection(file, "r") : unable to open connection In addition: Warning message: cannot open compressed file 'xxx.gz' however, I

Consider this code. This is R 3.4.2, but based on a quick look at the NEWS, this has not been fixed. tryCatch( readLines(tempfile(), warn = FALSE)[1], error = function(e) NA, warning = function(w) NA ) rm(list=ls(all.names = TRUE)) gc() showConnections(all = TRUE) If you run it, you'll get a connection you cannot close(), i.e. the last showConnections() call prints: ?

Hi all, I'm writing a function that read data from a binary file. I want to close all opened connections, but it failed: > showConnections() description class mode text isopen can read can write 3 "daten/t5_all.mea" "file" "rb" "binary" "opened" "yes" "no" 4 "daten/t5_all.mea"

Hello; I am new to R and trying to read a line from socket connection at a time but at the end of script I am getting "closing unused connection" warning. I am not able to understand how to solve this. I want to read a line from socket and then use read.table/scan on that line but it looks like I am opening multiple connections instead of just one. I think I am doing something wrong or

Hi, I''m trying to create a "runtime-generic" ActiveRecord class, It means I don''t need to know the table or database, before I create my program ruby-rails. So I don''t need to predefine my database in environment.yml file and pre-build classes inherited from ActiveRecord::Base. I write some code, it seems to work. However, I can''t disconnect my

Sirs, According to RFC 2705 (MGCP), these are the parameters that are used in the transactions: ReturnCode, Connection-parameters <-- DeleteConnection(CallId, EndpointId, ConnectionId, [Encapsulated NotificationRequest,] [Encapsulated

On Thu, Dec 14, 2017 at 7:56 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote: > Gabor, > > You can grab the connection and destroy it via getConnection and then a > standard close call. Yeah, that's often a possible workaround, but since this connection was opened by readLines() internally, I don't necessarily know which one it is. E.g. I might open multiple

I noticed the following file descriptor leak when I couldn't remove a package unless I shut down the R session that had loaded and used it. The function that triggered the problem printed the output of a call to parse(). Each time one prints a srcref a connection is opened and not closed. It looks like it happens in as.character.srcref's call to getSrcLines, which has some logic I

On 18/07/2009 8:15 AM, murdoch at stats.uwo.ca wrote: > On 17/07/2009 7:57 PM, Marilyn & Rich Short wrote: >> Hello, >> >> I'm having a problem in R with repeated use of the "load", "save", and >> "close" commands. I'm getting an error message that reads, "Too many >> open files". I'm opening files and