search for: socketselect

There's something weird going on for certain non-integer values of argument 'timeout' to base::socketSelect(). For such values, there is no timeout and you effectively end up with an infinite timeout. I can reproduce this on R 3.3.1 on Ubuntu 16.04 and RedHat 6.6, but not on Windows (via Linux Wine). # 1. In R master session > con <- socketConnection('localhost', port = 11001, server =...

Fixed in 73470 Best, Tomas On 10/05/2017 06:11 AM, Henrik Bengtsson wrote: > I'd like to follow up/bump the attention to this bug causing the > timeout to fail for socketSelect() on Unix. It is still there in R > 3.4.2 and R-devel. I've identified the bug in the R source code - the > bug is due to floating-point precisions and comparison using >=. See > PR17203 (https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17203) > for details and a patch. I...

I'd like to follow up/bump the attention to this bug causing the timeout to fail for socketSelect() on Unix. It is still there in R 3.4.2 and R-devel. I've identified the bug in the R source code - the bug is due to floating-point precisions and comparison using >=. See PR17203 (https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17203) for details and a patch. I've just reverif...

...e i have to read and write both text and binary data (each binary data package will be preceeded by a header line). When experimenting, i encountered some problems (with R-2.0.1 under different Linuxes (SuSE and Gentoo)). Since the default mode for socket connections is non-blocking, i first tried socketSelect() in order to see whether the socket is ready for reading: # Server: s <- socketConnection(port=2222, server=TRUE, open="w+b") writeLines("test", s) writeBin(1:10, s, size=4, endian="big") # Client, variation 1: s <- socketConnection(port=2222, server=FALSE, op...

I'm trying to use snow in my dual-core (hopefully later this is going to run in a cluster). So, at this moment I create a cluster using SOCK connection (MPI in the future). However when I try to use clusterApplyLB I got "Error in socketSelect(socklist) : not a socket connection". Any ideas ? Do you know if that is going to be an isuue too when I swith from SOCK to MPI ? Sample code is attached. Thanks. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ParallelLikelihood.R UR...

...socketConnection(server=TRUE, open="a+b", port=31415, blocking=FALSE); 2. And in another instance I do the following: s2 <- socketConnection(open="a+b", port=31415, blocking=FALSE); And so I have two processes communicating with sockets. Now, say on s1, I use socketSelect(list(s1),,0) # Session 1 and it returns FALSE, so nothing is there. Then on s2 I send data with writeBin("Hi", con=s2, size=1) # Session 2 and now socketSelect(list(s1),,0) # Session 1 -> TRUE returns TRUE, so I can read two bytes readBin(s1, what=raw(), n=3, size=1) #...

...g the RBaseX client, I had issues with the authentication process. It eventually turned out that a short break had to be inserted in this process between sending the credentials to the server and requesting the status. Tomas Kalibera put me on the right track by drawing my attention to the 'socketSelect' function. I don't know exactly the purpose of this function is (the function itself is documented, but I can't find any information for which situations this function should be called.) but it sufficed to call this function once between sending and requesting. I have two questions...

...I had issues with the > authentication process. It eventually turned out that a short break > had to be inserted in this process between sending the credentials to > the server and requesting the status. Tomas Kalibera put me on the > right track by drawing my attention to the 'socketSelect' function. I > don't know exactly the purpose of this function is (the function > itself is documented, but I can't find any information for which > situations this function should be called.) but it sufficed to call > this function once between sending and requesting. &...

I am writing a function to make a multi-part form request with binary data. I am running R 1.8.1 on Linux ReadHat. The sockectConnection is initialized with open="a+b" and blocking=TRUE. After writing the Post request using writeChar and writeBin and flushing the connection I use socketSelect to check if the socketConnection is availabe for reading. This call consistently takes 15 seconds or so (15.01 seconds; checked using system.time). After this the response is read using readChar no problem. However, when I perform the same operation using an HTML form the whole operation takes a...

...",path," HTTP/1.1\nHost: ",host, "\nReferer:\nContent-type: application/x-www-form-urlencoded\nContent- length: ", len,"\nConnection: Keep-Alive\n\n",dat,sep="") fp <- socketConnection(host=host,port=80,server=FALSE,blocking=TRUE) write(request,fp) socketSelect(list(fp)) # Wait until results are ready readLines(fp) close(fp) So my question is why do I get lines that are split up by hexadecimal characters (e.g. element 13 -- 'a1'-- splits what should be one line: lines 12 + 14)? Am I misunderstanding what is needed to correctly read from...

Hello R people, I have created a '.csv' file of 100 rows by 20 columns whose each cell contains a random numbers between 0 & 1, thru a Java program. Once that is created a signal (just a letter) is send to the port of a socket connection at "localhost", which was earlier started by an "R" session. Now the "R" reads the '.csv' file into a data

...sign text html latex example sink text html latex example missing link(s): capture.output slice.index text html latex example slotOp text html latex socketSelect text html latex example solve text html latex example sort text html latex example source text html latex missing link(s): demo split...

...with format.POSIXct(). * On Windows, detectCores() in package parallel now detects processors in all processor groups, not just the group R is running in (impacts particularly systems with more than 64 logical processors). Reported by Arunkumar Srinivasan. * On Windows, socketSelect() would hang with more than 64 sockets, and hence parallel::clusterApplyLB() would hang with more than 64 workers. Reported by Arunkumar Srinivasan. * as(1L, "double") now does coerce (PR#17457). * lm.influence(), influence.measures(), rstudent() etc now work...

...with format.POSIXct(). * On Windows, detectCores() in package parallel now detects processors in all processor groups, not just the group R is running in (impacts particularly systems with more than 64 logical processors). Reported by Arunkumar Srinivasan. * On Windows, socketSelect() would hang with more than 64 sockets, and hence parallel::clusterApplyLB() would hang with more than 64 workers. Reported by Arunkumar Srinivasan. * as(1L, "double") now does coerce (PR#17457). * lm.influence(), influence.measures(), rstudent() etc now work...

...with format.POSIXct(). * On Windows, detectCores() in package parallel now detects processors in all processor groups, not just the group R is running in (impacts particularly systems with more than 64 logical processors). Reported by Arunkumar Srinivasan. * On Windows, socketSelect() would hang with more than 64 sockets, and hence parallel::clusterApplyLB() would hang with more than 64 workers. Reported by Arunkumar Srinivasan. * as(1L, "double") now does coerce (PR#17457). * lm.influence(), influence.measures(), rstudent() etc now work...

...uation of expression and collection of results, wrapping a common use of sapply() for simulation purposes. o rev() is now a generic function, with default and dendrogram methods. o serialize() and unserialize() functions are available for low-level serialization to connections. o socketSelect() allows waiting on multiple sockets. o sort(method = "quick", decreasing = TRUE) is now implemented. o sort.list() has methods "quick" (a wrapper for sort(method = "quick", index.return = TRUE) and "radix" (a very fast method for small integers)....

...uation of expression and collection of results, wrapping a common use of sapply() for simulation purposes. o rev() is now a generic function, with default and dendrogram methods. o serialize() and unserialize() functions are available for low-level serialization to connections. o socketSelect() allows waiting on multiple sockets. o sort(method = "quick", decreasing = TRUE) is now implemented. o sort.list() has methods "quick" (a wrapper for sort(method = "quick", index.return = TRUE) and "radix" (a very fast method for small integers)....

...(omd) was of the form c(bottom, left, top, right) like par(oma) and par(omi)] o formatC() did not check its 'flag' argument, and could segfault if it was incorrect. (PR#7686) o Contrasts needed to be coerced to numeric (e.g. from integer) inside model.matrix. (PR#7695) o socketSelect() did not check for buffered input. o Reads on a non-blocking socket with no available data were not handled properly and could result in a segfault. o The "aovlist" method for se.contrast() failed in some very simple cases that were effectively not multistratum designs, e.g....

...(omd) was of the form c(bottom, left, top, right) like par(oma) and par(omi)] o formatC() did not check its 'flag' argument, and could segfault if it was incorrect. (PR#7686) o Contrasts needed to be coerced to numeric (e.g. from integer) inside model.matrix. (PR#7695) o socketSelect() did not check for buffered input. o Reads on a non-blocking socket with no available data were not handled properly and could result in a segfault. o The "aovlist" method for se.contrast() failed in some very simple cases that were effectively not multistratum designs, e.g....