search for: caughts

Dear R-devel community, There appears to be an inconsistency in R C API about the exceptions that can be raised from C code. Mapping of R C funs to corresponding R functions is as follows. error -> stop warning -> warning REprintf -> message Rprintf -> cat Rprint/cat is of course not an exception, I listed it just for completeness. The inconsistency I would like to report is

Thank you Luke for prompt reply. Is it possible then to request a new function to R C API "message" that would equivalent to R "message" function? Similarly as we now have C "warning" and C "error" functions. Best, Jan On Sun, Sep 15, 2019 at 5:25 PM Tierney, Luke <luke-tierney at uiowa.edu> wrote: > > On Sun, 15 Sep 2019, Jan Gorecki wrote:

The following example involves a function whose on.exit() expression both generates an error and catches the error. The body of the function also generates an error. When calling the function wrapped in a tryCatch, should that tryCatch's error function be given the error from the body of the function, since the one from the on.exit has already been dealt with? Currently the outer tryCatch

On Sun, 15 Sep 2019, Jan Gorecki wrote: > Dear R-devel community, > > There appears to be an inconsistency in R C API about the exceptions > that can be raised from C code. > Mapping of R C funs to corresponding R functions is as follows. > > error -> stop > warning -> warning > REprintf -> message This is wrong: REpintf is like cat with file = stderr().

You can file it as a wishlist item in the bug trackign system. Without a compelling case or a complete and well tested patch or both I doubt it will rise to the top of anyone's priority list. Best, luke On Sun, 15 Sep 2019, Jan Gorecki wrote: > Thank you Luke for prompt reply. > Is it possible then to request a new function to R C API "message" > that would equivalent to

One of my servers has recently started giving an error every time I run "aide --check". I ran it manually twice today with the same results. The second time, I added the -V flag, but that didn't give me anything useful. The system is currently running CentOS 5.3. Nothing on the system has changed recently (that I am aware of). The Aide database hasn't been updated in a few

Hello, I'm in the process of creating a JIT and I've run into a problem with exception handling. The situation I'm in is that my program will JIT functions, which will call native C++ functions (part of the run-time support). These native functions can throw exceptions. However, I don't actually want to handle these exceptions in the JITted functions. There are already try/catch

https://bugzilla.samba.org/show_bug.cgi?id=11561 Bug ID: 11561 Summary: [PATCH] Show progress information when SIGINFO is caught on platforms that have it Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

Package: xcp-squeezed Version: 1.3.2-9 Severity: important When trying to start a guest I get: # xe vm-start name-label=squeeze-2 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Failure("The ballooning daemon is not running") If I then manually run "/etc/init.d/xcp-squeezed

hi, i am getting an error when calling the impute.knn function (see the screenshot below). what is the problem here and how can it be solved? screenshot: ################## *** caught segfault *** address 0x513c7b84, cause 'memory not mapped' Traceback: 1: .Fortran("knnimp", x, ximp = x, p, n, imiss = imiss, irmiss, as.integer(k), double(p), double(n), integer(p),

Dear all, I just installed the "Short Summer" R update last week. Now, my R Studio doesn't open anymore! --> <p>R encountered a fatal error. </p> The session was terminated. and my R terminal doesn't close properly --> *** caught illegal operation *** I restarted my Mac OS Sierra 10.12.6 and reinstalled both R 3.4.2 and the latest R studio but the problem

In a context where exceptions are caught, I ran the fragment: cerr << "allocating" << endl; char* arr[100]; for (int jj = 0; jj < 10; ++jj) { cerr << "jj = " << jj << endl; arr[jj] = new char[2000000000]; sleep (30); } sleep (10); for (int jj = 0; jj < 10; ++jj) delete[] arr[jj]; cerr

How about going back to earlier versions if you don't need the latest ones? On Thu, Oct 26, 2017 at 12:59 PM, Klaus Michael Keller < klaus.keller at graduateinstitute.ch> wrote: > Dear all, > > I just installed the "Short Summer" R update last week. Now, my R Studio > doesn't open anymore! > > --> <p>R encountered a fatal error. </p> The

I have been retooling an S4 class definition to include another slot and have found that the methods::validObject function (defined in methods/R/SClasses.R) in R-devel throws an error that isn't caught internally (and thus not controllable by 'test' argument) when retrieving a non-existent slot. The offending line of code is shown below: > validObject function (object, test =

Been trying to get Passenger installed and setup to run a rails app. Everytime I goto eaa.mysite.com in Firefox the web browser goes out to the Internet instead of serving up the website. Why does this occur? Below is part of the configuration for apache2.conf: ======================================================= # Setup a virtual host for the rails apps to run in. <VirtualHost *:80>

https://bugzilla.samba.org/show_bug.cgi?id=9502 Summary: Deamon deadlock at stop (SIGINT caught) Product: rsync Version: 3.0.7 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: jurij at ocslab.com

I read at a number of places that if my puppet master is behind a proxy which requires authentication puppet module command does not work despite setting the global parameters http_proxy, https_proxy on bash the command throws an error [root@centos-razor ~]# puppet module install saz/dnsmasq --force Notice: Preparing to install into /etc/puppetlabs/puppet/modules ... Notice: Downloading from

Hi Nyx, > I'm in the process of creating a JIT and I've run into a problem with > exception handling. The situation I'm in is that my program will JIT > functions, which will call native C++ functions (part of the run-time > support). These native functions can throw exceptions. However, I don't > actually want to handle these exceptions in the JITted functions.

Hello R Community, I've been run the following codes. However, I've been getting an unusual segfault that I'm unable to trace its origin. Please give me a light to decipher the "caught segfault" Thanks for you attention. Bernardo. > options(STERM='iESS', editor='emacsclient') > rm(list = ls()) > > source("fgenIGLD.R") #RNG

A bunch of controllers were not extending ActionController::TestCase, and instead were just using the basic test/unit testcase, so we were not getting some of the rails baked-in stuff. Signed-off-by: Jason Guiditta <jguiditt at redhat.com> --- src/test/functional/host_controller_test.rb | 2 +- src/test/functional/nic_controller_test.rb | 2 +-