Environment details
- OS: Google App-Engine
- Node.js version: 8
- npm version: 6.7.0
@google-cloud/logging version: 4.2.0
Steps to reproduce
- ?
- ?
<rejected> TypeError: Cannot read property 'length' of undefined
at BundleExecutor.schedule (/app/node_modules/@google-cloud/logging/node_modules/google-gax/build/src/bundling.js:319:43)
at status.call (/app/node_modules/@google-cloud/logging/node_modules/google-gax/build/src/bundling.js:443:30)
at Canceller.call (/app/node_modules/@google-cloud/logging/node_modules/google-gax/build/src/api_callable.js:78:27)
at Bundleable.call (/app/node_modules/@google-cloud/logging/node_modules/google-gax/build/src/bundling.js:442:20)
at funcWithAuth.then.then.apiCall (/app/node_modules/@google-cloud/logging/node_modules/google-gax/build/src/api_callable.js:312:23)
at <anonymous> at process._tickCallback (internal/process/next_tick.js:189:7)
Hello @seriousManual,
Yes and no. I made a fix https://github.com/googleapis/gax-nodejs/pull/424 in exactly the place where it fails so it should not fail anymore (we’ll release the new version of that package today). When all the dependency chain upgrades, the error condition should stop happening.
As for what causes the error - i.e. what causes the undefined value to be passed to logging - I don’t have an answer I’m confident in. One idea is that it might be doing that if it gets an object with circular references, but it makes me think there should be another explanation, given that all these bug reports started coming from several people at the same time. @stephenplusplus can I ask you to take a deeper look at what’s going on (why this undefined value appears there)?
Same here, haven’t seen the issue on our development system for a while now!
Thank you!