Closed mjsteinbaugh closed 3 years ago
The ## Warning: call dbDisconnect() when finished working with a connection
warning is strange as I make sure to close all connections with on.exis(dbDisconnect(con))
. Also, I can not reproduce this warning locally on my computer.
For the second one, that seems to come from curl.
What puzzles me is that you can't suppress these even with suppressWarnings
and suppressMessages
. Seems to be some low level functionality then (e.g. in C++/C code of the curl package)?
I will have a closer look at the code in ensembldb
to see if I can do something there...
Weird right? I've seen this call dbDisconnect()
warning pop up intermittely with AnnotationHub before (see https://github.com/Bioconductor/AnnotationHub/issues/1), and it seems to be persisting in the latest release of Bioconductor. I don't think this is due to any of the underlying code in ensembldb.
Seems like this is safe to close too. Thanks!
Hi, I'm writing a wrapper for
ensDbFromGtf
in my AcidGenomes package (seemakeEnsDbFromGFF
code for details).I'm having trouble suppressing some unwanted connection messages:
Any tips for improving this and removing the unwanted warnings?
Best, Mike