-
Notifications
You must be signed in to change notification settings - Fork 653
Closed
Labels
api: loggingIssues related to the Cloud Logging API.Issues related to the Cloud Logging API.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.
Description
When the logging library has a failure the callback is never called. The same is true from the promiseified version. Below is basic sample code with garbage credentials, but I have seen the same issue with seemingly valid credentials and unknown failures.
Environment details
- OS: OS X 10.11.6
- Node.js version: 6.9.1
- npm version: 3.10.8
- google-cloud-node version: @google-cloud/logging@0.6.1
Steps to reproduce
var logging = require('@google-cloud/logging')({
projectId: 'projectx',
keyFilename: false
});
var syslog = logging.log('syslog');
var metadata = {
resource: {
type: 'global',
}
};
var entry = syslog.entry(metadata, {
logMsg: 'something happened'
});
syslog.write(entry, function(err, resp) {
console.log(err, resp);
});I've tried stepping through the code to debug the the root cause of the issue but get stuck when grpc starts calling into native code blocks (call.startBatch)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
api: loggingIssues related to the Cloud Logging API.Issues related to the Cloud Logging API.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.