Intermittent errors
See original GitHub issueEnvironment
- Node Version: 6.11.0
- Eslint-Watch Version: 3.1.0
- Eslint Version: 3.19.0
Basic Description of the problem
I run your plugin , but when I save a file, I get the following error, intermittently (1 out of every 2 saves) :
/Users/davestewart/Sites/dev/vue-element/node_modules/eslint-watch/src/formatters/simple-detail.js:29
results.forEach(function (result) {
^
TypeError: Cannot read property 'length' of undefined
at /Users/davestewart/Sites/dev/vue-element/node_modules/eslint-watch/src/formatters/simple-detail.js:33:10
at Array.forEach (native)
at simpleDetail (/Users/davestewart/Sites/dev/vue-element/node_modules/eslint-watch/src/formatters/simple-detail.js:29:11)
at lintFile (/Users/davestewart/Sites/dev/vue-element/node_modules/eslint-watch/src/watcher.js:92:16)
at FSWatcher.changeEvent (/Users/davestewart/Sites/dev/vue-element/node_modules/eslint-watch/src/watcher.js:111:9)
at emitOne (events.js:96:13)
at FSWatcher.emit (events.js:188:7)
at FSWatcher.<anonymous> (/Users/davestewart/Sites/dev/vue-element/node_modules/chokidar/index.js:196:15)
at FSWatcher._emit (/Users/davestewart/Sites/dev/vue-element/node_modules/chokidar/index.js:238:5)
at FSWatcher.<anonymous> (/Users/davestewart/Sites/dev/vue-element/node_modules/chokidar/lib/fsevents-handler.js:204:14)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! Vue-Element-Starter@1.0.0 lintw: `esw client/* -w --ext .js --ext .vue --quiet`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the Vue-Element-Starter@1.0.0 lintw script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/davestewart/.npm/_logs/2017-06-14T10_41_03_258Z-debug.log
How to reproduce it
- Command:
esw client/* -w --ext .js --ext .vue --quiet
- Save file
- Watch crashes
More info
Since writing this, strangely, the bug has now stopped (I was having it all morning, and haven’t worked on it since).
But the problem seemed to be results
being null in your code.
Any ideas? I don’t want to waste your time on this, but I am curious, as it was a real thing 😮
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Intermittent fault - Wikipedia
An intermittent fault, often called simply an "intermittent", (or anecdotally "interfailing") is a malfunction of a device or system that occurs at ...
Read more >Definition of intermittent error - PCMag
An error that occurs sporadically, not consistently. It is the most difficult type of problem to diagnose and repair. Advertisement ...
Read more >Troubleshooting Tips: Isolating Intermittent Faults
From my experience, intermittent faults are most commonly hardware related either damaged product or a problem with the installation. Software or firmware are ......
Read more >What is an Intermittent Error? - Computer Hope
An intermittent error is an error that randomly occurs. These errors are commonly difficult to resolve because of the difficulty in ...
Read more >Intermittent problems - IBM
An intermittent problem is a problem that occurs for a short time, and then goes away.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@davestewart There could be some defensive coding done around the
simple-detail-formatter
so that way this error isn’t what is displayed. But I am wondering if this issue is related to #115. Either way, I am glad it is working for you now. 😃 I’ll keep this issue in mind as I make the fixes for #115This should be fixed in the latest release.