Re: [R-pkg-devel] Failed: Future File Timestamp Check

2025-02-04 Thread Simon Urbanek
Josiah, that test tests the accuracy of the system clock by querying https://worldtimeapi.org/api/timezone/etc/UTC so my guess would be that you have either network or proxy issues which cause that request to fail by providing garbage instead of the actual response. The call to test yourself

Re: [R-pkg-devel] Additional issue clang-ASAN, gcc-ASAN

2025-02-04 Thread Zhian Kamvar
Thank you, Uwe for tagging me in. Huge thank you to Ivan for the detailed analysis. This reflects what Max Coulter found in https://github.com/thibautjombart/adegenet/issues/363. I just merged in https://github.com/thibautjombart/adegenet/issues/363 yesterday and I believe that should fix the issue

Re: [R-pkg-devel] Failed: Future File Timestamp Check

2025-02-04 Thread Josiah Parry
Thanks, Duncan! It is produced before preparing the tarball. It’s just a way to automate defining many 100ish functions that have the same structure. l run the script manually when I want to update definitions. There is not any auto-magical process that creates a file before the build or instal

Re: [R-pkg-devel] Failed: Future File Timestamp Check

2025-02-04 Thread Duncan Murdoch
One question is when that file is produced. Do you produce it before preparing the tarball, or is it produced as part of the installation process? Duncan Murdoch On 2025-02-04 6:27 p.m., Josiah Parry wrote: The file was written using writeLines() but it is just a normal R script with normal

Re: [R-pkg-devel] Failed: Future File Timestamp Check

2025-02-04 Thread Jeff Newmiller via R-package-devel
That was clear to me, and changes nothing about my comments. On February 4, 2025 3:27:34 PM PST, Josiah Parry wrote: >The file was written using writeLines() but it is just a normal R script >with normal function definitions and is included in the R/ directory. The >source code is just programmat

Re: [R-pkg-devel] Failed: Future File Timestamp Check

2025-02-04 Thread Josiah Parry
The file was written using writeLines() but it is just a normal R script with normal function definitions and is included in the R/ directory. The source code is just programmatically generated. On Tue, Feb 4, 2025 at 14:54 Jeff Newmiller wrote: > Packages are supposed to work when mounted in a

Re: [R-pkg-devel] Failed: Future File Timestamp Check

2025-02-04 Thread Jeff Newmiller via R-package-devel
Packages are supposed to work when mounted in a read-only filesystem... using writeLines seems like a very bad idea since you can't assume the package install is writeable when it is run, and running code from tmp is a security hole. If you absolutely cannot think of a way around running code f

[R-pkg-devel] Failed: Future File Timestamp Check

2025-02-04 Thread Josiah Parry
I'm running R CMD check for my package {calcite} (source: https://github.com/r-arcGIS/calcite) which is failing due to what *looks* like a bug. R CMD check fails at "checking for future file timestamps" I get this error: ...Error in if (abs(unclass(now_local) - unclass(now)[1]) > 300) missing va

Re: [R-pkg-devel] [SPAM Warning!]Re: CRAN Debian error installation time

2025-02-04 Thread Dirk Eddelbuettel
On 4 February 2025 at 16:16, Graeme Hickey wrote: | Having spent the best part of a month troubleshooting an almost | identical issue, I came across Dirk's blog post here: https:// | dirk.eddelbuettel.com/blog/2023/10/31/. He discusses how to throttle the number | of threads, and exports 2 handy

Re: [R-pkg-devel] [SPAM Warning!]Re: CRAN Debian error installation time

2025-02-04 Thread Graeme Hickey
Having spent the best part of a month troubleshooting an almost identical issue, I came across Dirk's blog post here: https://dirk.eddelbuettel.com/blog/2023/10/31/. He discusses how to throttle the number of threads, and exports 2 handy functions in the RcppArmadillo package, which you can use wit

Re: [R-pkg-devel] Vignette build issue on Debian platform

2025-02-04 Thread Graeme Hickey
Thank you, Jisca. I learned something new. Unfortunately the NOTE was not being triggered by this, but rather somehow the package was using OpenMP. I found the trick was to throttle the number of OpenMP threads courtesy of Dirk Edubuettel's post here: https://dirk.eddelbuettel.com/blog/2023/10/31/.

Re: [R-pkg-devel] Additional issue clang-ASAN, gcc-ASAN

2025-02-04 Thread Iñaki Ucar
On Tue, 4 Feb 2025 at 12:56, Uwe Ligges wrote: > > > > On 04.02.2025 12:46, Iñaki Ucar wrote: > > @Ivan: Excellent anaylsis as always. > > > > @Bernd: So what can **you** do about it? You are using adegenet > > correctly as Ivan pointed out, so IMHO CRAN should have requested > > adegenet's mainta

Re: [R-pkg-devel] Additional issue clang-ASAN, gcc-ASAN

2025-02-04 Thread Uwe Ligges
On 04.02.2025 12:46, Iñaki Ucar wrote: @Ivan: Excellent anaylsis as always. @Bernd: So what can **you** do about it? You are using adegenet correctly as Ivan pointed out, so IMHO CRAN should have requested adegenet's maintainer to fix this. But since it's your package that is on the line here,

Re: [R-pkg-devel] Additional issue clang-ASAN, gcc-ASAN

2025-02-04 Thread Iñaki Ucar
@Ivan: Excellent anaylsis as always. @Bernd: So what can **you** do about it? You are using adegenet correctly as Ivan pointed out, so IMHO CRAN should have requested adegenet's maintainer to fix this. But since it's your package that is on the line here, I would put that example inside a dontrun{

Re: [R-pkg-devel] Additional issue clang-ASAN, gcc-ASAN

2025-02-04 Thread Ivan Krylov via R-package-devel
В Sun, 2 Feb 2025 22:56:47 + Bernd.Gruber пишет: > READ of size 16 at 0x518000697ff0 thread T0 > #0 0x7f2e873ccfdf in bytesToDouble > /tmp/RtmpNNPUz9/R.INSTALL3cef1f2b1bd39c/adegenet/src/snpbin.c:225:19 > #1 0x7f2e873ceca5 in snpbin2freq > /tmp/RtmpNNPUz9/R.INSTALL3cef1f2b1bd39c/adegenet/