On Tue, Feb 11, 2020 at 2:42 PM Martin Morgan wrote:
>
> (sending again from / to an appropriate email address, sorry for the noise)
>
> Henrik -- I appreciate the ease with which gitea can be deployed in this
> one-off solution but cynically think that a real deployment would introduce
>
(sending again from / to an appropriate email address, sorry for the noise)
Henrik -- I appreciate the ease with which gitea can be deployed in this
one-off solution but cynically think that a real deployment would introduce
significant work, e.g., re-tooling our approach to new package
I wanna revive this old thread.
I've used Gitea for internal git/issue trackers at the UCSF for quite
a while now and it works really well. I've also looked into how easy
it would be to use it for pure code exposure and it's pretty
straightforward. Gitea even has built-in tools for
Hi Qian,
I have modified the GDS file in the SeqArray package.
"annotation/info/AA" should have fewer values than "annotation/info/AC",
since it is a variable-length vector in the new GDS file.
VCF format allows storing variable-length data, so SeqArray also allows
variable-length data.
It's a NOTE, you can't change the affiliation of the authors, so ignore it. The
purpose of the note is to improve readability by enabling display in
fixed-width windows (e.g., in github!) so make changes that are consistent with
improving readability without degrading information.
Martin
On
`sapply()` implies that you expect the result to be _s_implified, which implies
that all your elements are the same length. Sounds like you want to use
`lapply()` instead, to signal that it will *not* be simplified, even if by
chance the elements are the same length.
Martin
On 2/11/20, 3:51
" Avoid sapply(); use vapply()"
Hi, This is a Note I received from BiocCheck()
I tried to change my sapply functions to vapply; however, vapply requires
knowing the exact length of the vector(list), however, my vector length are
not static and variable. Therefore, vapply may not be of use for me
Greetings,
I am developing a Bioconductor package.
After runningBiocCheck:::checkFormatting("CommunityAMARETTO",
nlines=Inf)
I receive
* NOTE: Consider multiples of 4 spaces for line indents, 114
lines(3%) are not.
The majority of the lines being shown are manual pages (pages in man
Hi , I am developing a Bioconductor package.
By runningBiocCheck:::checkFormatting("CommunityAMARETTO", nlines=Inf)
I receive
*NOTE: Consider shorter lines; 10 lines (0%) are > 80*
* characters long.*
However, all these 10 lines belong to Vignette and affiliation part and you
can not
Dear Dr. Zheng & SeqArray maintainer,
I have a Bioconductor package called "GDSArray" that interfaces GDS file nodes
as DelayedArray instances. In this new Bioc devel version of 3.11, this package
failed all platforms. The debugging shows inconsistent dimensions calculated
from different
Thanks,
yes, I checked the build report.
And yes, I am afraid that you are right: it could have simply taken too
much time. It is a package that tries to accomplish many things and I was
warned during the review process that it was probably doing too much. But
on the other hand, I know it is
Hi Daniel,
Could you try adding a new public key?
Because everything on our end is fine.
Best
Nitesh
> On Feb 11, 2020, at 1:09 PM, Danrley Fernandes wrote:
>
> Hi,
> I'm the developer of the package rSWeeP, and I'm trying to clone my
> package's repository on Bioconductor, so I can commit
Hi,
I'm the developer of the package rSWeeP, and I'm trying to clone my
package's repository on Bioconductor, so I can commit changes. I already
have my ssh key register on the Bioconductor credentials for almost a week,
but when I ask to git bash to " git remote add upstream
remember to visit the build report page
http://bioconductor.org/checkResults/devel/bioc-LATEST/artMS/ ; perhaps your
package failed to build, e.g., because one of the 187(!) dependent packages did
not install correctly on the devel builder, or because of transient problems?
Martin Morgan
On
Hello Bioconductor developer community
We wanted to remind you that Bioc2020 registration is open!
Bioc2020 is accepting applications for workshops/talks/poster with the deadline
March 3.
Travel scholarships and Caregiver scholarships are also open with deadline
March 3.
We hope to see you
That does seem odd. Please let us know when you see this again with examples
and I can investigate more.
Lori Shepherd
Bioconductor Core Team
Roswell Park Comprehensive Cancer Center
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
It looks like it did get updated:
http://bioconductor.org/checkResults/release/bioc-LATEST/artMS/
Is showing 1.4.3 which is the expected version correct?
Remember it can take up to 24 hours for the build reports to pick up the new
versions depending on when you pushed changes
Cheers,
Lori
17 matches
Mail list logo
