stale-knife-36790
04/08/2020, 12:43 PMadorable-action-51248
04/08/2020, 1:50 PMfaint-table-42725
04/08/2020, 3:52 PMconst gs = require('./crud.js')
to be within the functions? I answered your GH issue with an example of moving the actual @google-cloud/datastore
import within the function within one of the crud.js
methods. Curious if that did not work for you?stale-knife-36790
04/09/2020, 10:52 AMadorable-action-51248
04/09/2020, 11:21 AMstale-knife-36790
04/10/2020, 10:02 AMBuild failed: {"error": {"canonicalCode": "INVALID_ARGUMENT", "errorMessage": "`gen_package_lock` had stderr output:\nnpm ERR! Maximum call stack size exceeded\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /builder/home/.npm/_logs/2020-04-09T12_17_01_397Z-debug.log\n\nerror: `gen_package_lock` returned code: 1", "errorType": "InternalError", "errorId": "F9FB3220"}}
adorable-action-51248
04/10/2020, 10:04 AMstale-knife-36790
04/10/2020, 10:07 AMadorable-action-51248
04/10/2020, 10:13 AMstale-knife-36790
04/10/2020, 10:15 AMadorable-action-51248
04/10/2020, 10:15 AMstale-knife-36790
04/10/2020, 10:18 AMadorable-action-51248
04/10/2020, 10:23 AMstale-knife-36790
04/10/2020, 10:23 AMadorable-action-51248
04/10/2020, 10:23 AMstale-knife-36790
04/10/2020, 10:23 AMadorable-action-51248
04/10/2020, 10:23 AMstale-knife-36790
04/10/2020, 10:25 AMadorable-action-51248
04/10/2020, 10:26 AMstale-knife-36790
04/10/2020, 10:34 AMDiagnostics:
gcp:cloudfunctions:Function (pulumi-test):
error: 1 error occurred:
* creating urn:pulumi:dev::gcp::gcp:cloudfunctions:CallbackFunction$gcp:cloudfunctions/function:Function::pulumi-test: Error waiting for Creating CloudFunctions Function: Error code 3, message: Build failed: Build error details not available
pulumi:pulumi:Stack (gcp-dev):
error: update failed
The Pulumi runtime detected that 34 promises were still active
at the time that the process exited. There are a few ways that this can occur:
* Not using `await` or `.then` on a Promise returned from a Pulumi API
* Introducing a cyclic dependency between two Pulumi Resources
* A bug in the Pulumi Runtime
Leaving promises active is probably not what you want. If you are unsure about
why you are seeing this message, re-run your program with the `PULUMI_DEBUG_PROMISE_LEAKS`
environment variable. The Pulumi runtime will then print out additional
debug information about the leaked promises.
adorable-action-51248
04/10/2020, 10:54 AMstale-knife-36790
04/10/2020, 11:14 AMadorable-action-51248
04/10/2020, 11:34 AMstale-knife-36790
04/10/2020, 11:44 AM{
"name": "gcp",
"main": "index.js",
"dependencies": {
"@pulumi/gcp": "^2.0.0",
"@pulumi/pulumi": "^1.0.0",
"express": "^4.17.1",
"allCrud": "file:."
}
}
(Currently not using 'allCrud' @adorable-action-51248)adorable-action-51248
04/10/2020, 11:45 AMstale-knife-36790
04/10/2020, 12:10 PMadorable-action-51248
04/10/2020, 4:16 PMstale-knife-36790
04/14/2020, 9:04 AMBuild failed: {"error": {"canonicalCode": "INVALID_ARGUMENT", "errorMessage": "`gen_package_lock` had stderr output:\nnpm ERR! Maximum call stack size exceeded\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /builder/home/.npm/_logs/2020-04-14T08_50_30_907Z-debug.log\n\nerror: `gen_package_lock` returned code: 1", "errorType": "InternalError", "errorId": "79DA4BF7"}}
adorable-action-51248
04/14/2020, 9:18 AMstale-knife-36790
04/14/2020, 9:27 AMadorable-action-51248
04/14/2020, 9:28 AMstale-knife-36790
04/14/2020, 9:30 AM