NCBI FTP - The `fromNcbi` throws error all the time
The fromNcbi
throws error all the time.
root@24a5c8782ad1:~# node server/ncbi-integration/fromNcbi
info: from ncbi check was finished in 13 ms
[xmldom error] invalid doc source
@#[line:0,col:undefined]
error: Unhandled Rejection at Promise: Promise {
<rejected> Error: xml parse error
at fs.readFile (/home/xpub/server/ncbi-integration/fromNcbi.js:101:16)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:511:3) }
error: Reason: message=xml parse error, stack=Error: xml parse error
at fs.readFile (/home/xpub/server/ncbi-integration/fromNcbi.js:101:16)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:511:3)
info: connection terminated
After reverting the code for the process does not exist issue, the error looks like below.
root@daac7b9e4874:~# node server/ncbi-integration/fromNcbi
info: from ncbi check was finished in 12 ms
[xmldom error] invalid doc source
@#[line:0,col:undefined]
(node:816) UnhandledPromiseRejectionWarning: Error: xml parse error
at fs.readFile (/home/xpub/server/ncbi-integration/fromNcbi.js:89:16)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:511:3)
(node:816) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:816) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.