Error encountered while attempting to view coverage report
dominicbarnes opened this issue · 0 comments
dominicbarnes commented
I opened zuul in "local" mode and was working on inspecting the coverage report. Once I navigated down to an individual file, the server crashed with the following error:
TypeError: Cannot read property 'text' of undefined
at /home/dominic/Github/dominicbarnes/deku-time/node_modules/istanbul-middleware/node_modules/istanbul/lib/report/html.js:210:45
at Array.forEach (native)
at annotateStatements (/home/dominic/Github/dominicbarnes/deku-time/node_modules/istanbul-middleware/node_modules/istanbul/lib/report/html.js:193:33)
at HtmlReport.Report.mix.writeDetailPage (/home/dominic/Github/dominicbarnes/deku-time/node_modules/istanbul-middleware/node_modules/istanbul/lib/report/html.js:428:9)
at Object.render (/home/dominic/Github/dominicbarnes/deku-time/node_modules/istanbul-middleware/lib/core.js:211:16)
at /home/dominic/Github/dominicbarnes/deku-time/node_modules/istanbul-middleware/lib/handlers.js:67:14
at Layer.handle [as handle_request] (/home/dominic/Github/dominicbarnes/deku-time/node_modules/istanbul-middleware/node_modules/express/lib/router/layer.js:95:5)
at next (/home/dominic/Github/dominicbarnes/deku-time/node_modules/istanbul-middleware/node_modules/express/lib/router/route.js:131:13)
at Route.dispatch (/home/dominic/Github/dominicbarnes/deku-time/node_modules/istanbul-middleware/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/home/dominic/Github/dominicbarnes/deku-time/node_modules/istanbul-middleware/node_modules/express/lib/router/layer.js:95:5)
/home/dominic/Github/dominicbarnes/deku-time/node_modules/http-proxy/lib/http-proxy/index.js:119
throw err;
^
Error: socket hang up
at createHangUpError (_http_client.js:252:15)
at Socket.socketOnEnd (_http_client.js:344:23)
at emitNone (events.js:91:20)
at Socket.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:934:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
I've reproduced it consistently, you can try it out on my repo:
- clone
npm install
npm start
- open the tests in the browser (let them finish)
- navigate through the coverage report (ie:
src/
->index.js
)