Displaying 8 results from an estimated 8 matches for "r_session".
Did you mean:
_session
2019 Apr 30
2
Background R session on Unix and SIGINT
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 receives
while it is waiting on stdin, and then it triggers it when some input
comes in.... Mayb...
2019 Apr 30
2
Background R session on Unix and SIGINT
...t;csardi.gabor at gmail.com> wrote:
> >
> > 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...
2019 Apr 30
2
Background R session on Unix and SIGINT
...t;>> 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
> >>...
2019 Apr 30
2
[External] Re: Background R session on Unix and SIGINT
...; >>>>> 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(fu...
2019 Apr 30
0
Background R session on Unix and SIGINT
...30, 2019, at 3:44 PM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote:
>
> 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 receives
> while it is waiting on stdin, an...
2019 Apr 30
0
Background R session on Unix and SIGINT
...> wrote:
>>>
>>> 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...
2019 Apr 30
0
[External] Re: Background R session on Unix and SIGINT
...>>>>>
>>>>> 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)
>>>>>...
2019 May 01
0
[External] Re: Background R session on Unix and SIGINT
...;>> 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
>>>>>>>
>>>>...