search for: renv

Dear R Developers, I am having an issue with the renv package and R 4.0.1, which I suspect is related to base R and not the renv package itself, as with R 3.6.3 such an "error" does not appear. The error is raised by a file.exists() path, and path "C:\Users\J-tel\Documents", which in R 3.6.3 is read correctly, but in R 4.0.1 fails...

...se"). Regards, Yihui On Thu, Jun 11, 2020 at 3:11 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > > Dear Juan, > > I don't see what is the problem from your report. Please try to create a > minimal but complete reproducible example that does not use the renv > package. Perhaps you could use the R debugger (e.g. via > options(error=recover)) to find out what is the argument that > file.exists() has been called with. And then you could try just to call > file.exists() directly with that argument to trigger the problem. > > It may be tha...

Dear Juan, I don't see what is the problem from your report. Please try to create a minimal but complete reproducible example that does not use the renv package. Perhaps you could use the R debugger (e.g. via options(error=recover)) to find out what is the argument that file.exists() has been called with. And then you could try just to call file.exists() directly with that argument to trigger the problem. It may be that the argument has been c...

Hi Juan, For bug reports to R, you should attempt to create a minimally-reproducible example, using only R's builtin facilities and not any other addon packages. Given your report, it's not clear whether the issue lies within renv or truly is caused by a change in R 4.0.0. Also note that you have not supplied a minimally reproducible example. If at all possible, you should be able to supply some code that reproduces the issue -- ideally, one should be able to just copy + paste the code into an R session to see the issue ari...

...ui > > On Thu, Jun 11, 2020 at 3:11 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: >> >> Dear Juan, >> >> I don't see what is the problem from your report. Please try to create a >> minimal but complete reproducible example that does not use the renv >> package. Perhaps you could use the R debugger (e.g. via >> options(error=recover)) to find out what is the argument that >> file.exists() has been called with. And then you could try just to call >> file.exists() directly with that argument to trigger the problem. >&gt...

...ualizar R a una versión más reciente (con la 3.6 es posible que esto te llegue a pasar con más paquetes, la versión actual es 4.3.2). Si por tus requerimientos tienes que seguir usando la 3.6, entonces como dice Eric debes controlar también las versiones de los paquetes, y mejor aún si lo haces con renv (https://rstudio.github.io/renv/articles/renv.html) Emilio Emilio L. Cano Tel: 665 676 225 http://emilio.lcano.com > El 5 dic 2023, a las 4:20, Eric <ericconchamunoz en gmail.com> escribió: > > Es un problema de dependencias, es decir, algunos de los paquetes necesarios para...

...11, 2020 at 3:11 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > >> > >> Dear Juan, > >> > >> I don't see what is the problem from your report. Please try to create a > >> minimal but complete reproducible example that does not use the renv > >> package. Perhaps you could use the R debugger (e.g. via > >> options(error=recover)) to find out what is the argument that > >> file.exists() has been called with. And then you could try just to call > >> file.exists() directly with that argument to trigger...

...0007f992514fdd2 in smtp_address_clone (pool=0x7f992528dce0 <static_system_pool>, src=src at entry=0x7ffd30eace10) at smtp-address.c:632 #2 0x000055f7330916b3 in testsuite_message_set_data (mail=0x55f73486f848) at testsuite-message.c:96 #3 0x000055f7330918b9 in testsuite_message_set_file (renv=renv at entry=0x55f734856ac0, file_path=<optimized out>) at testsuite-message.c:139 #4 0x000055f7330931cc in testsuite_smtp_get (renv=renv at entry=0x55f734856ac0, index=<optimized out>) at testsuite-smtp.c:171 #5 0x000055f73309566c in cmd_test_message_smtp_operation_execute (renv...

...to create such a file $retval = file_path($R::Vars::TMPDIR, $pat . $$ . sprintf("%05d", rand(10**5))); croak "Cannot find unused name for temporary file" if($n++ > 1000); } $retval; } ### * R_system sub R_system { my ($cmd, $Renv) = @_; my $tmpf = R_tempfile(); if($R::Vars::OSTYPE eq "windows") { open(tmpf, "> $tmpf") or die "Error: cannot write to '$tmpf'\n"; print tmpf "$cmd $Renv\n"; close tmpf; $res = system("sh $tmpf");...

Es un problema de dependencias, es decir, algunos de los paquetes necesarios para instalar Shiny no estan aun disponibles en la arquitectura y la version necesaria ... yo lo resolvi haciendo un downgrade de la version del paquete principal que quieres instalar, en este caso Shiny ... asi, si usas una version mas antigua de Shiny, entonces si estaran disponibles los paquetes que necesitas en la

...<- matrix(0, ncol=2, nrow=n) env[,1] <- rdist(n, ...) # first envelope has `x' env[,2] <- r*env[,1] # second envelope has `r*x' # randomize de envelopes, so we don't know which one from # the pair has `x' or `r*x' i <- as.logical(rbinom(n, 1, 0.5)) renv <- env renv[i,1] <- env[i,2] renv[i,2] <- env[i,1] return(renv) # return the randomized envelopes } # example, `x' follows an exponential distribution with E(x) = 10 # we do one million simulations n=1e6) env <- generateenv(r=2, rexp, n=1e6, rate=1/10) mean(env[,1]) # you...

Buenas tardes. Tenía la versión 3.6.0 de R. Quería instalar el paquete edarf, pero decía que no estaba disponible para esa versión. Actualicé R a la versión 4.0.0, que creo que es la última, pero al tratar de reinstalar forestFloor, me dice que no está disponible para la versión 4.0.0. He abierto R 3.6.0 directamente, cliqueo install.packages("forestfloor") y ahora me dice que no está

...is is something we try to keep working in R if possible, to allow > users moving installed packages by moving the installation directories. > If this practice works for you, it is probably fine. Our current workaround kind of works, but when users expect to be able to install packages using renv or other tools that use install.packages to work; our wrapper is not that convenient. > > > Currently, installing a binary package just means unpacking it to the > target directory. Probably you could do this also via binary packages: > build binary packages on a local filesystem,...

I'm running R (currently 4.4.1) on Linux Mint > sessionInfo() R version 4.4.1 (2024-06-14) Platform: x86_64-pc-linux-gnu Running under: Linux Mint 20.3 ...truncated... To install a new R package, is it better to use Linux Mint's pacakge manager (e.g. synaptic, apt-get, or similar), or to install it within R with install.packages("some_new_package")? I've done both over

...know that PKG_LOCKDIR_PREFIX has been set. Package installation just works as expected. I feel the patch has some added value over our workaround: Even if we implement the workaround with a simple wrapper over install.packages(), any third party package that depends on install.packages() (such as renv or others) won't use our workaround. Besides, with this patch merged any other R user benefits from being able to install packages in those filesystems. Any feedback is very much appreciated. Thanks for your time, Sergio [[alternative HTML version deleted]]

...r alone can allow me to reproduce most relevant published analyses. That is, including a link to a reproducible code repository with a list of exact package/versions used and to the exact data used as input are necessary to achieve that degree of completeness. It is non-trivial even with tools like renv and a complete repo to document all of the decisions required to reproduce a published result months or years later... expecting citations and technical discussion alone to catch everything is IMO an unrealistic goal. The paper can only cover the general outline of the work, and should be complete...

...REFIX has been > set. Package installation just works as expected. > > I feel the patch has some added value over our workaround: Even if we > implement the workaround with a simple wrapper over install.packages(), any > third party package that depends on install.packages() (such as renv or > others) won't use our workaround. Besides, with this patch merged any other > R user benefits from being able to install packages in those filesystems. > > Any feedback is very much appreciated. > > Thanks for your time, > > Sergio > > [[alternative HTML vers...

...r alone can allow me to reproduce most relevant published analyses. That is, including a link to a reproducible code repository with a list of exact package/versions used and to the exact data used as input are necessary to achieve that degree of completeness. It is non-trivial even with tools like renv and a complete repo to document all of the decisions required to reproduce a published result months or years later... expecting citations and technical discussion alone to catch everything is IMO an unrealistic goal. The paper can only cover the general outline of the work, and should be complete...

...r alone can allow me to reproduce most relevant published analyses. That is, including a link to a reproducible code repository with a list of exact package/versions used and to the exact data used as input are necessary to achieve that degree of completeness. It is non-trivial even with tools like renv and a complete repo to document all of the decisions required to reproduce a published result months or years later... expecting citations and technical discussion alone to catch everything is IMO an unrealistic goal. The paper can only cover the general outline of the work, and should be complete...

Hi list I just realized that that I don not receive all mails in my mailbox (running dovecot-ee 2.2.23.1-1 on Debian 8). On my frontend servers (running postfix) the queue fills up with mails that cannot be delivered via lmtp to my backend servers. The error message on the frontend is "lost connection with backend while sending data" When I checked the logs on the backend server I found