search

editorconfig-checker / editorconfig-checker.javascript

A tool to verify that your files are in harmony with your .editorconfig
https://editorconfig-checker.github.io/
MIT License
71 stars 10 forks source link

editorconfig-checker should return non-zero if download fails #201

Closed bufferoverflow closed 4 years ago

bufferoverflow commented 4 years ago

Using editorconfig-checker within ci should give non-zero if download fails.

node version: lts/erbium -> v12.16.1

$ editorconfig-checker -exclude 'site|node_modules'
(node:124) UnhandledPromiseRejectionWarning: FetchError: request to https://github.com/editorconfig-checker/editorconfig-checker/releases/download//2.1.0/ec-linux-amd64.tar.gz failed, reason: connect ETIMEDOUT 140.82.121.4:443
    at ClientRequest.<anonymous> (/builds/siemens/api/node_modules/node-fetch/lib/index.js:1455:11)
    at ClientRequest.emit (events.js:315:20)
    at TLSSocket.socketErrorListener (_http_client.js:426:9)
    at TLSSocket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:124) 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: 1)
(node:124) [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.
Done in 130.04s.
github-actions[bot] commented 7 months ago

:tada: This issue has been resolved in version 1.5.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket: