Re: [Bioc-devel] [Untrusted Server]Re: [Untrusted Server]Re: strange error in Jenkins build forsingleCellWorkflow

Hi Aaron, Would you mind sharing the code for flushing DLLs? This is a problem that others working with single cells and I have faced. Better yet would anyone know of code that would allow unused DLL to be identified and unloaded? I suspect not as it would require keeping track of the

Re: [Bioc-devel] [Untrusted Server]Re: strange error in Jenkins build forsingleCellWorkflow

Well, inertia won out in the end, and so I've just moved a whole stack of packages into "Suggests" for now. This is probably not a sustainable solution as the workflow can potentially get larger over time; I would prefer to have some formal support for splitting up the workflow into modules

Re: [Bioc-devel] Generic for write to BiocGenerics

I was also about to suggest that we converge on export() but held back because I was obviously biased. I also agree with making the target explicit in the function name. It makes the intent of the code way more obvious. On Mon, Sep 18, 2017 at 3:15 PM, Hervé Pagès wrote: >

Re: [Bioc-devel] Generic for write to BiocGenerics

Hi jo, At the moment probably not much to be gained unless you ran into some conflicts with other "write" methods defined in Bioconductor? Note that the arguments/signature of base::write() don't really help making it a clean generic functions (e.g. weird 'file' default, 'ncolumns' and 'sep'

Re: [Bioc-devel] hook declined to update error

Hi Anand, Each file needs to be smaller than 5Mb. If you have a file larger than 5mb, the pre-receive hook will tell you which file failed. Can you tell me why you are using “—force” or “-f” flag? We don’t allow force pushes to the bioconductor git server. Try without it

Re: [Bioc-devel] hook declined error

Hi Anand, Each file needs to be smaller than 5Mb. If you have a file larger than 5mb, the pre-receive hook will tell you which file failed. Can you tell me why you are using “—force” or “-f” flag? We don’t allow force pushes to the bioconductor git server. Did you submit your SSH key to the

[Bioc-devel] Generic for write to BiocGenerics

Dear all! We are currently implementing mzML write support in `MSnbase` and did implement a `write` method for the S4 objects in `MSnbase`. Now, the question is whether it might not be better to define a `write` S4 generic in `BiocGenerics`? cheers, jo

[Rd] NEWS item about PR#17284

Previous mentions: - https://stat.ethz.ch/pipermail/r-devel/2017-July/074723.html - https://stat.ethz.ch/pipermail/r-devel/2017-August/074737.html The NEWS item corresponding to PR#17284 is in "CHANGES in R-devel". However, fix for PR#17284 is already included in R 3.4.2 beta.

[Bioc-devel] BioCor devel timeout

Dear developers, The package I maintain (BioCor) builds correctly on malbec1 (Linux) and veracruz1 (OS X) in the development but not in tokay1 (Windows machine) server. It timesout. I am not sure what causes this, I don't fetch anything from the website. Last Windows downloadable version is

Re: [R-pkg-devel] Advice on dealing with absent dependencies

http://dirk.eddelbuettel.com/blog/2017/03/22#suggests_is_not_depends For a decent (and long-standing) example in code, see the R Commander. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org __ R-package-devel@r-project.org

Re: [Bioc-devel] Bioconductor failing package MEAL

Hi, It worked. Now I can make pushes. Thanks, Carlos El 14/09/2017 a las 20:23, Turaga, Nitesh escribió: Bioc-git server* (git.bioconductor.org). Ignore the typo. On Sep 14, 2017, at 2:20 PM, ni41435_ca wrote: Hi Carlos Your ID is standardized across all

Re: [Rd] R-devel r73293 and the testthat package

On 17/09/2017 6:25 PM, Will Landau wrote: Hello, Windows R-devel no longer lets me use testthat even though the CRAN checks are pretty much clean. I have copied my session output below. There was a recent change in R-devel that means all packages with compiled code need to be re-installed

Re: [Rd] R-devel r73293 and the testthat package

> On 18 Sep 2017, at 00:25 , Will Landau wrote: > > Hello, > > > Windows R-devel no longer lets me use testthat even though the CRAN checks > are pretty much clean. I have copied my session output below. > > Will Well, there us a reason for the nickname of R-devel:

[Rd] FW: CRAN check errors: drake 4.1.0 on r-devel-linux-x86_64-debian-clang

Hello, The CRAN checks for the drake package (4.1.0) fail for r-devel-linux-x86_64-debian-clang. This happened right when crayon 1.3.4 was released, but I suspect the problem is not with crayon or drake, but with base R-devel. I cannot reproduce the error myself, but I have copied a minimal

[Rd] R-devel r73293 and the testthat package

Hello, Windows R-devel no longer lets me use testthat even though the CRAN checks are pretty much clean. I have copied my session output below. Will R Under development (unstable) (2017-09-16 r73293) -- "Unsuffered Consequences" Copyright (C) 2017 The R Foundation for Statistical Computing

[Rd] Bug: Issues on Windows with SFN disabled

Hello, R appears to assume that Windows drives have short file names (SFN, 8.3) enabled; for example, that "C:/Program Files/..." is addressable as "C:/Progra~1/...". Newer versions of Windows have SFN disabled on non-OS drives, however. This means that if you install R on a non-OS drive, you -