-
Notifications
You must be signed in to change notification settings - Fork 19
Description
If I manually set mountpoint it is ok.
But if I select Data Stream - Refresh Stream List, there are exception:
(node:24180) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be of type string or an instance of Buffer. Received an instance of Promise
at NtripCasterResponse.end (_http_outgoing.js:773:13)
at V1Processor.printSourcetable (/root/mycaster/node_modules/@ntrip/caster/build/transport/server/ntrip.js:508:22)
at V1Processor.acceptClient (/root/mycaster/node_modules/@ntrip/caster/build/transport/server/ntrip.js:483:29)
at V1Processor.accept (/root/mycaster/node_modules/@ntrip/caster/build/transport/server/ntrip.js:444:28)
at HttpRequestProcessor.accept (/root/mycaster/node_modules/@ntrip/caster/build/transport/server/ntrip.js:422:66)
at NtripTransport.accept (/root/mycaster/node_modules/@ntrip/caster/build/transport/server/ntrip.js:216:75)
at Server. (/root/mycaster/node_modules/@ntrip/caster/build/transport/server/ntrip.js:124:54)
at Server.emit (events.js:314:20)
at parserOnIncoming (_http_server.js:863:12)
at NtripHTTPParser.parserOnHeadersComplete (_http_common.js:126:17)
(Use node --trace-warnings ... to show where the warning was created)
(node:24180) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:24180) [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.
Error only on V1Processor.
Easy fixed - just copy printSourcetable (with async-await) from V2Processor.