Unhandled Exceptions Connecting to Server
Description
Here is the error when running this from the Windows command line:
R:\canvasData>canvasDataCli sync -c ./config.js
fetching current list of files from API...
an error occured
{ Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code:
'ECONNRESET', syscall: 'read' }
Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
Here is the error when running this from the Linux subsystem for Windows (version info is below):
/mnt/r/canvasData# canvasDataCli sync --level debug -c ./config.js
fs.js:1657
binding.lstat(baseLong);
^ Error: ENOTCONN: socket is not connected, lstat '/mnt/r'
at Object.realpathSync (fs.js:1657:15)
at toRealPath (module.js:164:13)
at Function.Module._findPath (module.js:213:22)
at Function.Module._resolveFilename (module.js:545:25)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.run (/usr/lib/node_modules/canvas-data-cli/lib/cli.js:108:16)
at Object.<anonymous> (/usr/lib/node_modules/canvas-data-cli/bin/canvasDataCli:4:5)
at Module._compile (module.js:652:30)
I had Node.js v 10 installed in the Linux subsystem and received a different error:
/mnt/r/canvasData# canvasDataCli sync -c ./config.js
fetching current list of files from API...
an error occured
{ Error: Client network socket disconnected before secure TLS connection was established
at TLSSocket.onConnectEnd (_tls_wrap.js:1086:19)
at Object.onceWrapper (events.js:273:13)
at TLSSocket.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1092:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
code: 'ECONNRESET',
path: null,
host: 'api.inshosteddata.com',
port: 443,
localAddress: undefined }
Error: Client network socket disconnected before secure TLS connection was established
at TLSSocket.onConnectEnd (_tls_wrap.js:1086:19)
at Object.onceWrapper (events.js:273:13)
at TLSSocket.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1092:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
As an end user I need the source to handle exceptions and provide informative error messages to help diagnose what the cause of the error is and to help identify potential solutions. The desired behavior I would like is for the software that is developed by Instructure to work as intended to facilitate accessing our data programmatically. It would also be great if some of the devs from Instructure would respond to the issues being submitted to the source repository as well.
Additional Information
- Node Version 10.10.0 & 8.11.4
- Platform: Windows 10 (Education license) & Linux Subsystem for Windows (Ubuntu 16.04.5)
- Logs: Adding the debug flag does not appear to have any effect on the logging of the errors