similar to: GUI's and R background processes

On Feb 10, 2005, at 7:38 PM, George W. Gilchrist wrote: > Today I was running a graduate level stats lab using R and we > encountered a > major problem while using the current build of the Cocoa GUI: > >> From the GUI: >> system.time(pbinom(80, 1e5, 806/1e6)) > [1] 14.37 4.94 30.29 0.00 0.00 >> > >> From the command line on the same machine: >>

Thank you for the feedback and confirmations. Interesting to see that it's also reproducible on macOS expect for Spencer; that might indicate a difference in builds. BTW, my original post suggested that timeout error was for sure detected while running Sys.sleep(10). However, it could of course also be that it is only detected after it finishes. For troubleshooting, the

On unix, unless event polling is enabled Sys.sleep just waits in a select() call (with a SIGINT handler in place) so the elapsed time isn't checked until after the select call is complete. Rstudio uses event polling, and in particular sets R_wait_usec to 10000, which means event and interrupt checks happen during a Sys.seep call. The R GUI on macOS doesn't seem to do this (but my lldb

Hi All, I tried my best to figure out how to deal with the freezing R console but with no luck. I followed the instructions of calling R_ProcessEvents() regularly but still couldn't work it out (the callings were removed from the below C code). I am using R-2.8.1 on Windows XP service pack 3. The Rtools is version 2.9. I have the following C code: void rx(int *n, int *m, int *rxmax,int

Hi All, I realize that this is not a really nice reprex, but anyone has an idea why a background R session would "remember" an interrupt (SIGINT) on Unix? rs <- callr::r_session$new() rs$interrupt() # just sends a SIGINT #> [1] TRUE rs$run(function() 1+1) #> Error: interrupt rs$run(function() 1+1) #> [1] 2 It seems that the main loop somehow stores the SIGINT it

On Mon, 31 Oct 2016, Henrik Bengtsson wrote: > Thank you for looking into this Luke. > > On Thu, Oct 27, 2016 at 9:26 AM, <luke-tierney at uiowa.edu> wrote: >> On unix, unless event polling is enabled Sys.sleep just waits in a >> select() call (with a SIGINT handler in place) so the elapsed time >> isn't checked until after the select call is complete.

Yeah, I get that they are async. What happens is that the background process is not doing anything when the process gets a SIGINT. I.e. the background process is just listening on its standard input. AFAICT for an interactive process such a SIGINT is just swallowed, with a newline outputted to the terminal. But apparently, for this background process, it is not swallowed, and it is triggered

Unfortunately --interactive also makes the session interactive(), which is bad for me, as it is a background session. In general, I don't want the interactive behavior, but was wondering if I could send as SIGINT to try to interrupt the computation of the background process, and if that does not work, then I would send a SIGKILL and start up another process. It all works nicely, except for

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

OK, I managed to create an example without callr, but it is still somewhat cumbersome. Anyway, here it is. Terminal 1: mkfifo fif R --no-readline --slave --no-save --no-restore < fif Terminal 2: cat > fif Sys.getpid() This will make Terminal 1 print the pid of the R process, so we can send a SIGINT: Terminal 3: kill -INT pid The R process is of course still running happily. Terminal 2

I have been working on this issue for almost 5 days and can not get past this error. Puppet Dashboard is installed via RPM from puppetlabs. I have tried versions 1.2.12, 1.2.9 and am currently on 1.2.1. Regardless of the version, I get the same exact error every time I run rake RAILS_ENV=production db:migrate. (in /usr/share/puppet-dashboard) rake aborted! no such file to load --

I''m having trouble getting puppet dashboard (1.2.21) to run on apache. i installed puppetmaster-passenger and puppet-dashboard package. It didn''t create user puppet-dashboard automatically as stated in the installation guide, so i created one manually and chowned all files under /puppet-dashboard. when testing with webrick everything works fine (as root). when i try with

Puppet Dashboard 1.2.13 is a maintenance and bugfix release of Puppet Dashboard. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.13.tar.gz Debian packages are available at https://apt.puppetlabs.com RPM packages are available at https://yum.puppetlabs.com See the Verifying Puppet Download section at:

This is a maintenance release of Puppet Dashboard. This release resolves issues #10198, #10270, and #10543. More details below. This release is available for download at: http://downloads.puppetlabs.com/dashboard/ We have included Debian and RPM packages as well as a tarball. See the Verifying Puppet Download section at: http://projects.puppetlabs.com/projects/puppet/wiki/Downloading_Puppet

I''ve almost gotten PE running -- Based on tips from a recent Webinar, I''ve started on a minimal RHEL 6 system, and have installed the PE 2.03 packages. Once I set up /etc/ hosts (DNS will come later), I started the PE services. Given past problems (possibly just me), I was pleasantly surprised that the puppet-enterprise-updater script was so accommodating as I remembered which

followed the instruction for installing dashboard, and created user mysql -pmy_password -e "CREATE DATABASE dashboard CHARACTER SET utf8;CREATE USER ''dashboard''@''localhost'' IDENTIFIED BY ''my_password''; GRANT ALL PRIVILEGES ON dashboard.* TO ''dashboard''@''localhost'';" however, I keep getting

Hello, I am currently trying to get the puppetdb dashboard and the puppet dashboard working on the same system. Puppet dashboard is working great but after "successfully" installing puppetdb following puppet''s opensource instructions the puppetdb dashboard just doesn''t seem to exist (according to some sites I should be able to get to it by going to

I am using Ubuntu 10.04 and ruby-enterprise (not ubuntu ruby) and installed puppet via gem. How can I install puppet-dashboard if I don''t see a gem available and if I use the ubuntu package, i get the whole slop of ruby packages sucked in (which i am trying to avoid)? # dpkg -i puppet-dashboard_1.1.0-1_all.deb Selecting previously deselected package puppet-dashboard. (Reading database

I''ve installed Puppet and am installing Dashboard on CentOS 6. I''m running into an ''undefined method'' when installing the dashboard. To install Puppet Open Source, I ran: > rpm -ivh

Howdy, I''ve been getting this issue for about a month in dashboard. All our nodes poll on a cronjob between 00:00 and 01:00 daily, but one node has been getting this as a failed task for a while, with the yaml files building up on the server. Outside of this one cronjob, other puppet runs on the same node are running just fine. The backtrace on dashboard is: Importing report