search for: l421

...code identified by the code author." The example here uses Sys.sleep(), which supports and detects user interrupts. The timeout error message is thrown by the R_ProcessEvents(void) function as defined in: * src/unix/sys-unix.c (https://github.com/wch/r-source/blob/trunk/src/unix/sys-unix.c#L421-L453) * src/gnuwin32/system.c (https://github.com/wch/r-source/blob/trunk/src/gnuwin32/system.c#L110-L140) So, they're clearly different implementations on Windows and Unix. Also, for the Unix implementation, the code differ based on preprocessing directive HAVE_AQUA, which could explain why S...

...uses Sys.sleep(), which supports and detects user interrupts. >> >> >> The timeout error message is thrown by the R_ProcessEvents(void) >> function as defined in: >> >> * src/unix/sys-unix.c >> (https://github.com/wch/r-source/blob/trunk/src/unix/sys-unix.c#L421-L453) >> * src/gnuwin32/system.c >> (https://github.com/wch/r-source/blob/trunk/src/gnuwin32/system.c#L110-L140) >> >> So, they're clearly different implementations on Windows and Unix. >> Also, for the Unix implementation, the code differ based on >> preproc...

...; > The example here uses Sys.sleep(), which supports and detects user interrupts. > > > The timeout error message is thrown by the R_ProcessEvents(void) > function as defined in: > > * src/unix/sys-unix.c > (https://github.com/wch/r-source/blob/trunk/src/unix/sys-unix.c#L421-L453) > * src/gnuwin32/system.c > (https://github.com/wch/r-source/blob/trunk/src/gnuwin32/system.c#L110-L140) > > So, they're clearly different implementations on Windows and Unix. > Also, for the Unix implementation, the code differ based on > preprocessing directive HAVE_A...

...;> >>>> >>>> The timeout error message is thrown by the R_ProcessEvents(void) >>>> function as defined in: >>>> >>>> * src/unix/sys-unix.c >>>> >>>> (https://github.com/wch/r-source/blob/trunk/src/unix/sys-unix.c#L421-L453) >>>> * src/gnuwin32/system.c >>>> >>>> (https://github.com/wch/r-source/blob/trunk/src/gnuwin32/system.c#L110-L140) >>>> >>>> So, they're clearly different implementations on Windows and Unix. >>>> Also, for the Unix...

...>> interrupts. >>> >>> >>> The timeout error message is thrown by the R_ProcessEvents(void) >>> function as defined in: >>> >>> * src/unix/sys-unix.c >>> >>> (https://github.com/wch/r-source/blob/trunk/src/unix/sys-unix.c#L421-L453) >>> * src/gnuwin32/system.c >>> >>> (https://github.com/wch/r-source/blob/trunk/src/gnuwin32/system.c#L110-L140) >>> >>> So, they're clearly different implementations on Windows and Unix. >>> Also, for the Unix implementation, the code...

https://bugzilla.mindrot.org/show_bug.cgi?id=2929 Bug ID: 2929 Summary: OpenSSH server should not send the SSH_MSG_EXT_INFO message after rekeying Product: Portable OpenSSH Version: 7.7p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5

setTimeLimit(elapsed=1) causes a timeout error whenever a call takes more than one second. For instance, this is how it works on Windows (R 3.3.1): > setTimeLimit(elapsed=1) > Sys.sleep(10); message("done") Error in Sys.sleep(10) : reached elapsed time limit Also, the error propagates immediately and causes an interrupt after ~1 second; > system.time({ Sys.sleep(10);