search for: l1736

...Value and elapsedLimitValue, which are checked in R_ProcessEvents(), but other than setting the timeout limits I don't think it's involved in the runtime checks. The do_setTimeLimit() is defined in: * src/main/sysutils.c (https://github.com/wch/r-source/blob/trunk/src/main/sysutils.c#L1692-L1736) Unfortunately, right now, I've got little extra time to troubleshoot this further. /Henrik On Wed, Oct 26, 2016 at 2:22 AM, Berend Hasselman <bhh at xs4all.nl> wrote: > >> On 26 Oct 2016, at 04:44, Henrik Bengtsson <henrik.bengtsson at gmail.com> wrote: >> .........

...ed in R_ProcessEvents(), but >> other than setting the timeout limits I don't think it's involved in >> the runtime checks. The do_setTimeLimit() is defined in: >> >> * src/main/sysutils.c >> (https://github.com/wch/r-source/blob/trunk/src/main/sysutils.c#L1692-L1736) >> >> >> Unfortunately, right now, I've got little extra time to troubleshoot >> this further. >> >> /Henrik >> >> On Wed, Oct 26, 2016 at 2:22 AM, Berend Hasselman <bhh at xs4all.nl> wrote: >>> >>>> On 26 Oct 2016, at...

...on read_metadata_vorbiscomment_ from stream_decoder.c, at various locations where we short circuit the computation, we also set `obj->num_comments` accordingly. For example: https://git.xiph.org/?p=flac.git;a=blob;f=src/libFLAC/stream_decoder.c;h=e0f1b14d30dd548268a88e4341af3f38290816e3;hb=HEAD#l1736 https://git.xiph.org/?p=flac.git;a=blob;f=src/libFLAC/stream_decoder.c;h=e0f1b14d30dd548268a88e4341af3f38290816e3;hb=HEAD#l1741 https://git.xiph.org/?p=flac.git;a=blob;f=src/libFLAC/stream_decoder.c;h=e0f1b14d30dd548268a88e4341af3f38290816e3;hb=HEAD#l1752 https://git.xiph.org/?p=flac.git;a=blob;f=s...

...ue, which are checked in R_ProcessEvents(), but > other than setting the timeout limits I don't think it's involved in > the runtime checks. The do_setTimeLimit() is defined in: > > * src/main/sysutils.c > (https://github.com/wch/r-source/blob/trunk/src/main/sysutils.c#L1692-L1736) > > > Unfortunately, right now, I've got little extra time to troubleshoot > this further. > > /Henrik > > On Wed, Oct 26, 2016 at 2:22 AM, Berend Hasselman <bhh at xs4all.nl> wrote: >> >>> On 26 Oct 2016, at 04:44, Henrik Bengtsson <henrik....

...setting the timeout limits I don't think it's involved in >>>> the runtime checks. The do_setTimeLimit() is defined in: >>>> >>>> * src/main/sysutils.c >>>> >>>> (https://github.com/wch/r-source/blob/trunk/src/main/sysutils.c#L1692-L1736) >>>> >>>> >>>> Unfortunately, right now, I've got little extra time to troubleshoot >>>> this further. >>>> >>>> /Henrik >>>> >>>> On Wed, Oct 26, 2016 at 2:22 AM, Berend Hasselman <bhh at xs4all...

...>> other than setting the timeout limits I don't think it's involved in >>> the runtime checks. The do_setTimeLimit() is defined in: >>> >>> * src/main/sysutils.c >>> >>> (https://github.com/wch/r-source/blob/trunk/src/main/sysutils.c#L1692-L1736) >>> >>> >>> Unfortunately, right now, I've got little extra time to troubleshoot >>> this further. >>> >>> /Henrik >>> >>> On Wed, Oct 26, 2016 at 2:22 AM, Berend Hasselman <bhh at xs4all.nl> wrote: >>>>...

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);