search for: l134

...sEvents(). At the end, there is a code snippet - if (R_interrupts_pending) onintr(); - which is Windows specific and could be another important difference between Windows and Unix. This function is defined in: * src/main/errors.c (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) The do_setTimeLimit() function controls global variables cpuLimitValue 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 (...

...ntry=0x0, ret= > ret at entry=0x0) > ? ? at proto.c:668 > > I debugged this issue and noticed that the appliance logs from?commandrvf?are > truncated, leading to parse failure (missing utf-8 additional bytes): > https://github.com/libguestfs/libguestfs/blob/master/python/handle.c#L134 > UnicodeDecodeError: 'utf-8' codec can't decode byte 0x84 in position 0: invalid > start byte So I thought we'd fixed this in: https://github.com/libguestfs/libguestfs/commit/0ee02e0117527b86a31b2a88a14994ce7f15571f This is specifically a Python API problem or would it aff...

...=0x7fffffffd8f0, xdrp=xdrp at entry=0x0, ret=ret at entry=0x0) at proto.c:668 I debugged this issue and noticed that the appliance logs from commandrvf are truncated, leading to parse failure (missing utf-8 additional bytes): https://github.com/libguestfs/libguestfs/blob/master/python/handle.c#L134 UnicodeDecodeError: 'utf-8' codec can't decode byte 0x84 in position 0: invalid start byte -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libguestfs/attachments/20230212/973ad8ab/attachment.htm>

...;> if (R_interrupts_pending) onintr(); - which is Windows specific and >> could be another important difference between Windows and Unix. This >> function is defined in: >> >> * src/main/errors.c >> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) >> >> >> The do_setTimeLimit() function controls global variables cpuLimitValue >> 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_se...

...to suggest replacing all use of sscanf/strtoul with new nbdkit_parse_* functions, but we would need a lot of them and they still wouldn't cover all the clever uses we make of sscanf, eg: https://github.com/libguestfs/nbdkit/blob/cfbbe17ee21a9a47a96a5ac7f4321d20ed90cad9/filters/error/error.c#L134 So I still think the right way to solve this is to fix C2x / POSIX so it mandates what is possibly already the glibc behaviour. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v...

...is a code snippet - > if (R_interrupts_pending) onintr(); - which is Windows specific and > could be another important difference between Windows and Unix. This > function is defined in: > > * src/main/errors.c > (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) > > > The do_setTimeLimit() function controls global variables cpuLimitValue > 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 define...

On 9/19/19 10:26 AM, Richard W.M. Jones wrote: > This filter can be used to transparently reopen/retry when a plugin > fails. The connection is closed and reopened which for most plugins > causes them to attempt to reconnect to their source. > > For example if doing a long or slow SSH copy: > > nbdkit -U - ssh host=remote /var/tmp/test.iso \ > --run 'qemu-img

...; - which is Windows specific and >>>> could be another important difference between Windows and Unix. This >>>> function is defined in: >>>> >>>> * src/main/errors.c >>>> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) >>>> >>>> >>>> The do_setTimeLimit() function controls global variables cpuLimitValue >>>> and elapsedLimitValue, which are checked in R_ProcessEvents(), but >>>> other than setting the timeout limits I don't think it's involved i...

...ts_pending) onintr(); - which is Windows specific and >>> could be another important difference between Windows and Unix. This >>> function is defined in: >>> >>> * src/main/errors.c >>> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) >>> >>> >>> The do_setTimeLimit() function controls global variables cpuLimitValue >>> and elapsedLimitValue, which are checked in R_ProcessEvents(), but >>> other than setting the timeout limits I don't think it's involved in >>> the r...

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

...16> %I47, <4 x i32> <i32 undef, i32 2, i32 undef, i32 6> %I129 = insertelement <4 x i16> %Shuff67, i16 %Sl109, i32 2 %B130 = add i32 %3, %E38 %FC131 = sitofp i32 %3 to float %Sl132 = select i1 %Sl42, i64 %L24, i64 %L5 %Cmp133 = icmp eq <2 x i1> %I99, %Shuff20 %L134 = load i32, i32* %PC78 store i32 %L104, i32* %1 %E135 = extractelement <8 x i1> zeroinitializer, i32 4 br i1 %E135, label %CF254, label %CF260 CF260: ; preds = %CF264 %Shuff136 = shufflevector <1 x i32> %Shuff59, <1 x i32> %Shuff...

...ight 1994-97, NCR Corporation (c) Copyright 1987-97, MetaWare Incorporated cc -I. -I. -g -DHAVE_CONFIG_H -I./popt -c receiver.c -o receiver.o NCR High Performance C Compiler R3.0c (c) Copyright 1994-97, NCR Corporation (c) Copyright 1987-97, MetaWare Incorporated w "receiver.c",L134/C9(#257): '=' encountered where '==' may have been intended. No errors 1 warning cc -I. -I. -g -DHAVE_CONFIG_H -I./popt -c cleanup.c -o cleanup.o NCR High Performance C Compiler R3.0c (c) Copyright 1994-97, NCR Corporation (c) Copyright 1987-97, MetaWare Incorporated...