Ömer Toraman
10/19/2021, 4:32 PM<https://blabla.com/dev>
when you run npx start --stage dev
?Thomas Ankcorn
10/19/2021, 5:10 PMJulien Goux
10/20/2021, 7:34 AMJulien Goux
10/20/2021, 7:34 AMJulien Goux
10/20/2021, 7:43 AMJoseph Dan Alinsug
10/20/2021, 12:27 PM0.46
, I was wondering if the option minify
on sst Function was removed or at a different place. I couldn't it find on Function.d.ts
Ross Coundon
10/20/2021, 1:33 PMif (!scope.local) {
console.log(`Adding epsagon layer from ${process.env.EPSAGON_LAYER_ARN}`);
const epsagon = LayerVersion.fromLayerVersionArn(this, 'EpsagonLayer', process.env.EPSAGON_LAYER_ARN);
scope.addDefaultFunctionLayers([epsagon]);
scope.addDefaultFunctionEnv({
EPSAGON_TOKEN: process.env.EPSAGON_TOKEN,
EPSAGON_APP_NAME: process.env.EPSAGON_APP_NAME,
NODE_OPTIONS: '-r epsagon-frameworks --enable-source-maps',
});
}
It's deployed via seed and I see the console.log inside the if block with the correct layer ARN but no layer is added to any of the functions. What could be going on?Ömer Toraman
10/20/2021, 4:33 PMMike McCall
10/21/2021, 4:24 AMError: Cannot use e "__Schema" from another module or realm.
Tomasz Sobczyk
10/21/2021, 10:18 AMRoss Coundon
10/21/2021, 11:26 AMError: listen EADDRINUSE: address already in use :::12577
at Server.setupListenHandle [as _listen2] (net.js:1320:16)
at listenInCluster (net.js:1368:12)
at Server.listen (net.js:1454:7)
at Function.listen (/Users/rosscoundon/Documents/GitHub/wheres_my_tech/node_modules/express/lib/application.js:618:24)
at Server.listen (/Users/rosscoundon/Documents/GitHub/wheres_my_tech/node_modules/@serverless-stack/cli/node_modules/@serverless-stack/core/dist/runtime/server.js:78:18)
at startRuntimeServer (/Users/rosscoundon/Documents/GitHub/wheres_my_tech/node_modules/@serverless-stack/cli/scripts/start.js:311:10)
at Object.module.exports [as start] (/Users/rosscoundon/Documents/GitHub/wheres_my_tech/node_modules/@serverless-stack/cli/scripts/start.js:154:9)
Waiting for the debugger to disconnect...
fatal error: all goroutines are asleep - deadlock!
goroutine 1 [semacquire]:
sync.runtime_Semacquire(0x0)
runtime/sema.go:56 +0x25
sync.(*WaitGroup).Wait(0xc000180000)
sync/waitgroup.go:130 +0x71
main.runService(0x1)
<http://github.com/evanw/esbuild/cmd/esbuild/service.go:138|github.com/evanw/esbuild/cmd/esbuild/service.go:138> +0x4cb
main.main()
<http://github.com/evanw/esbuild/cmd/esbuild/main.go:200|github.com/evanw/esbuild/cmd/esbuild/main.go:200> +0x1eb
goroutine 34 [chan receive]:
main.runService.func1()
<http://github.com/evanw/esbuild/cmd/esbuild/service.go:66|github.com/evanw/esbuild/cmd/esbuild/service.go:66> +0x4b
created by main.runService
<http://github.com/evanw/esbuild/cmd/esbuild/service.go:64|github.com/evanw/esbuild/cmd/esbuild/service.go:64> +0x212
goroutine 35 [chan receive]:
main.(*serviceType).sendRequest(0xc0001be140, {0x13f20a0, 0xc0029c4480})
<http://github.com/evanw/esbuild/cmd/esbuild/service.go:163|github.com/evanw/esbuild/cmd/esbuild/service.go:163> +0xda
main.runService.func2()
<http://github.com/evanw/esbuild/cmd/esbuild/service.go:92|github.com/evanw/esbuild/cmd/esbuild/service.go:92> +0x39
created by main.runService
<http://github.com/evanw/esbuild/cmd/esbuild/service.go:89|github.com/evanw/esbuild/cmd/esbuild/service.go:89> +0x313
Sam Hulick
10/21/2021, 4:37 PM@swc-node/jest
package)Ömer Toraman
10/21/2021, 10:22 PMSam Hulick
10/21/2021, 10:58 PM.build
folder can get quite huge over time 😳
111.4 GiB [###########] /.build
Adrián Mouly
10/22/2021, 2:40 AMMuhammad Ali
10/22/2021, 2:50 AMcount(*)
functionality. So the only other cost effective option is to trigger kinesis stream on each insert in db and use lambda to aggregate the count. Now here are my 2 questions
1. Is this the best approach?
2. Is there an example i can use which can guide me how to setup kinesis stream on dynamodb with a target lambda?Dan Van Brunt
10/22/2021, 7:57 PMSam Hulick
10/22/2021, 8:40 PMarda
10/22/2021, 8:56 PMsst remove
?Adrián Mouly
10/22/2021, 10:17 PMAdrián Mouly
10/24/2021, 4:26 AM[dotenv][DEBUG] "AWS_NODEJS_CONNECTION_REUSE_ENABLED" is already defined in `process.env` and will not be overwritten
Adrián Mouly
10/24/2021, 5:32 AMsst clean
?Dan Van Brunt
10/24/2021, 2:19 PMsst.Function
where you reference the assets using path
like you guys do with lambda.Function
?
Just trying to envision portability of a custom construct.Sean Matheson
10/24/2021, 3:01 PMDan Van Brunt
10/25/2021, 8:01 PMcopyFiles
from
hit save and it said no changes detected.
new sst.Api(scope, 'AppAPI', {
defaultFunctionProps: {
bundle: {
copyFiles: [{ from: '../../../contentful-app-frontend', to: '.' }],
},
},
routes: {
'ANY /': 'lib/constructs/ContentfulApp/lambda.handler',
'ANY /{proxy+}': 'lib/constructs/ContentfulApp/lambda.handler',
},
})
Muhammad Ali
10/26/2021, 3:35 AMErik Robertson
10/26/2021, 7:02 PMBuilding Lambda _function_ src/list.main
> node_modules/sequelize/lib/dialects/postgres/hstore.js:3:23: error: Could not resolve "pg-hstore" (_mark_ it _as_
external
to
_exclude_ it _from_
the
_bundle_, _or_
_surround_ it _with_
_try_/_catch_
to
handle
the
failure
at
_run_-_time_)
3 │ const hstore = require('pg-hstore')({ sanitize: _true_ });
And I've tried putting the module as external_modules as recommended (and also tried node_modules) but with no success in my stack API definition:
defaultFunctionProps: {
bundle: {
node_modules: ['pg-hstore'],
// external_modules: ['pg-hstore'],
// node_modules: ['pg', 'sqlite3', 'tedious', 'pg-hstore']
}
},
Any idea ?
Greg Martin
10/26/2021, 7:14 PMAdrián Mouly
10/27/2021, 3:35 AMDanny
10/27/2021, 11:41 AM