Displaying 3 results from an estimated 3 matches for "r73463".
Did you mean:
r73465
2017 Oct 05
1
socketSelect(..., timeout): non-integer timeouts in (0, 2) (?) equal infinite timeout on Linux - weird
...e 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 reverified that the patch still
> solves the problem on trunk (SVN r73463).
>
> Thanks,
>
> /Henrik
>
> On Sat, Oct 1, 2016 at 1:11 PM, Henrik Bengtsson
> <henrik.bengtsson at gmail.com> wrote:
>> There's something weird going on for certain non-integer values of
>> argument 'timeout' to base::socketSelect(). For such v...
2016 Oct 01
2
socketSelect(..., timeout): non-integer timeouts in (0, 2) (?) equal infinite timeout on Linux - weird
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
2017 Oct 05
0
socketSelect(..., timeout): non-integer timeouts in (0, 2) (?) equal infinite timeout on Linux - weird
...#39;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 reverified that the patch still
solves the problem on trunk (SVN r73463).
Thanks,
/Henrik
On Sat, Oct 1, 2016 at 1:11 PM, Henrik Bengtsson
<henrik.bengtsson at gmail.com> wrote:
> 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...