search for: l509

...during parsing" (that is why are variables assigned to an environment) ? We are otherwise aware that the error is not occurring in the R console, but can be traced to a call to R_ParseVector() in R's C API:( https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509 ). Our specific setup is calling an embedded R from Python, using the cffi library. An error on end was the first possibility considered, but the puzzling specificity of the error (as shown below other parsing errors are handled properly) and the difficulty tracing what is in happening in R_ParseV...

...en trying to use syslinux to update the MBR would fail. PS D:\> D:\syslinux64.exe -a -m -f -i D: Writing MBR: Access is denied. Did not successfully update the MBR; continuing... PS D:\> echo $LASTEXITCODE 0 The issue here is in line https://repo.or.cz/syslinux.git/blob/HEAD:/win/syslinux.c#l509 eventhough we fail to update MBR but we still exit with 0. Need to have exit(1) to indicate that operation has failed. https://repo.or.cz/syslinux.git/blob/HEAD:/win/syslinux.c#l513 can have exit(1) aswell. thanks, Pradhap

...> >> Best, >> Tomas >> >> >> We are otherwise aware that the error is not occurring in the R console, >> but can be traced to a call to R_ParseVector() in R's C API:( >> https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509 >> ). >> >> Our specific setup is calling an embedded R from Python, using the cffi >> library. An error on end was the first possibility considered, but the >> puzzling specificity of the error (as shown below other parsing errors are >> handled properly) and th...

...an embedded R. Best, Laurent > Best, > Tomas > > > We are otherwise aware that the error is not occurring in the R console, > but can be traced to a call to R_ParseVector() in R's C API:( > https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509 > ). > > Our specific setup is calling an embedded R from Python, using the cffi > library. An error on end was the first possibility considered, but the > puzzling specificity of the error (as shown below other parsing errors are > handled properly) and the difficulty tracing wha...

...s signaled via return value to ParseVector() Best, Tomas > > We are otherwise aware that the error is not occurring in the R > console, but can be traced to a call to R_ParseVector() in R's C > API:(https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509). > > Our specific setup is calling an embedded R from Python, using the > cffi library. An error on end was the first possibility considered, > but the puzzling specificity of the error (as shown below other > parsing errors are handled properly) and the difficulty tracing what...

...ific bits of IR. When testing this, it is extremely cumbersome to write a test pass which does this in interesting and yet controllable and comprehensible ways. Let's look at a concrete example: https://github.com/llvm-project/llvm-project/blob/master/llvm/unittests/IR/PassManagerTest.cpp#L481-L509 Here we have over 20 lines of code spent testing that the correct set of things happened the correct number of times. I had to write a long comment just to explain what these numbers mean. And I still never understand whether a change in the numbers really means a good or bad thing. Now, we *have...

...t; >>> > >>> We are otherwise aware that the error is not occurring in the R > console, > >>> but can be traced to a call to R_ParseVector() in R's C API:( > >>> > https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509 > >>> ). > >>> > >>> Our specific setup is calling an embedded R from Python, using the cffi > >>> library. An error on end was the first possibility considered, but the > >>> puzzling specificity of the error (as shown below other parsing...

...t; Best, > Tomas > >> >> We are otherwise aware that the error is not occurring in the R >> console, but can be traced to a call to R_ParseVector() in R's C >> API:(https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509). >> >> Our specific setup is calling an embedded R from Python, using >> the cffi library. An error on end was the first possibility >> considered, but the puzzling specificity of the error (as shown >> below other parsing errors are handled properly)...

Hi again, Beside R_ParseVector()'s possible inconsistent behavior, R's handling of zero-length named elements does not seem consistent either: ``` > lst <- list() > lst[[""]] <- 1 > names(lst) [1] "" > list("" = 1) Error: attempt to use zero-length variable name ``` Should the parser be made to accept as valid what is otherwise possible

...t;> Tomas >>> >>> >>> We are otherwise aware that the error is not occurring in the R console, >>> but can be traced to a call to R_ParseVector() in R's C API:( >>> https://github.com/rpy2/rpy2/blob/master/rpy2/rinterface_lib/_rinterface_capi.py#L509 >>> ). >>> >>> Our specific setup is calling an embedded R from Python, using the cffi >>> library. An error on end was the first possibility considered, but the >>> puzzling specificity of the error (as shown below other parsing errors are >>>...

...' encountered where '==' may have been intended. No errors 1 warning cc -I. -I. -g -DHAVE_CONFIG_H -I./popt -c flist.c -o flist.o NCR High Performance C Compiler R3.0c (c) Copyright 1994-97, NCR Corporation (c) Copyright 1987-97, MetaWare Incorporated w "flist.c",L509/C7(#257): '=' encountered where '==' may have been intended. w "flist.c",L711/C7(#257): '=' encountered where '==' may have been intended. w "flist.c",L945/C26(#257): '=' encountered where '==' may have been intend...

...can be included in the next release. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1282423 [2] http://lists.mindrot.org/pipermail/openssh-unix-dev/2015-December/034617.html [3] http://unix.stackexchange.com/q/251194/121504 [4] https://github.com/openssl/openssl/blob/master/include/openssl/pem.h#L509 -- You are receiving this mail because: You are watching the assignee of the bug.