Repository navigation
Cannot run npm run cover locally #309
Copy link
Copy link
Closed
Labels
🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Milestone
Description
Activity
@stephenplusplus This looks like it's originating from
google-service-accountbut also seems to dive intogtokenso I'm not sure whether it's you or me or something else that's causing this issue but I'm kind of at a loss as to what could cause this. Essentially in therequestlibrary @request.js:930there's a call forself.req.on(...andself.reqis undefined for some reason. Either the request has been discarded or removed or never initiated? Any idea what could have caused this? It's especially weird becausenpm testandnpm run regression-testboth work fine. 😕Will take a look now 🔍 👓 🐛 🔨
I seem to be getting a different stacktrace:
1) BigQuery "before all" hook: Uncaught TypeError: Cannot call method 'on' of undefined at Request.start (/Users/stephen/dev/gcloud-node/node_modules/request/request.js:930:12) at Request.write (/Users/stephen/dev/gcloud-node/node_modules/request/request.js:1689:10) at end (/Users/stephen/dev/gcloud-node/node_modules/request/request.js:687:14) at Object._onImmediate (/Users/stephen/dev/gcloud-node/node_modules/request/request.js:710:7) at processImmediate [as _immediateCallback] (timers.js:345:15)Could I be doing something wrong?
Nm, updated request and get the same thing now.
- added 2 commits that reference this issue
on Nov 24, 2014 - added a commit that references this issue
on Nov 24, 2014 - addedtype: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
on Feb 2, 2015 - addedtriage meI really want to be triaged.I really want to be triaged.🚨This issue needs some love.This issue needs some love.
on Apr 6, 2020 31 remaining items
- added a commit that references this issue
on Feb 3, 2026 - added a commit that references this issue
on Feb 4, 2026 - added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 23, 2026 - added 2 commits that reference this issue
on Feb 24, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Mar 5, 2026 - added a commit that references this issue
on Mar 5, 2026 - added a commit that references this issue
on Mar 5, 2026 - added a commit that references this issue
on Mar 18, 2026
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Well, both
npm run testandnpm run regression-testboth run fine and pass but I cannot generate coverage report usingnpm run cover(which I thought just ran test and regression-test)?Error I see: