Hey there, loving sst right now, especially the web interface for the console. But when an invoked function throws an error, the web interface crashes and forces me to restart the console.

Hey @Hans Song which tab in the console you mean? API tab?

it is the functions tab, i.e.

<https://console.serverless-stack.com/last-second/local/functions/>...

I'll check if i can reproduce it, meanwhile could you check the version of SST you're using and update to latest if not and try again?

here are the versions in my

package.json

"@serverless-stack/cli": "0.67.0",
"@serverless-stack/resources": "0.67.0",
"aws-cdk-lib": "2.7.0"

i can push up my code and link it here if that will help

Could you share a screenshot of the console crash? It'll help to debug.

sure 🙂

working on it

thanks @manitej 🙏

I’m not seeing any crashes in console, errors are shown in the console.

@manitej does the crash only happen when there’s no stack trace?

I think yeah

in the screenshot u shared above, stack trace seems to be there

i guess it has no contents in it though, that’s why

map

throwing the error

what’ is

props.invocation.response.error.stackTrace

for u?

i think i found the error

i think

props.invocation.response.error.stackTrace

is

undefined

for @Hans Song?

yep, in the screenshot i sent earlier, the stackTrace property is missing

I think the error is related to the Go syntax

@manitej you mean related to how i structure error responses in my lambdas?

the same issue happens when i avoid using something that would be mistaken for an escaped character

you are not getting the stacktrace it seems

yep…

@manitej can u see if this PR fixes this issue https://github.com/serverless-stack/serverless-stack/pull/1470

fixing it is easy, but i’m thinking why the

stacktrace

option is missing? backend related?

Merged. I think stack trace is optional, not all errors have it. But yeah let’s ping Dax and see if it’s a bug on the backend.

if it helps, it is not optional here https://github.com/serverless-stack/serverless-stack/blob/master/packages/core/src/runtime/server.ts#L45

@Frank figured it out,

go

doesn’t have a stacktrace option in the response https://docs.aws.amazon.com/lambda/latest/dg/golang-exceptions.html#go-exceptions-createfunction

@Hans Song are you using

go

runtime?

yep

I see. Do you know if you get stack trace if u deployed the code (with error) to AWS?

nice, its not crashing anymore 🙂 i’ll try doing a deploy now

Awesome!

just wanted to say, really loving the experience so far, especially how the bundling is cached, when i synth with the defaults in cdk, it redownloads all the dependencies for each lambda which can take a couple minutes 🙄

Yeah, Go runtime doesn't have a stackTrace

@Hans Song were you able to figure out the

fork/exec

error above?

Hi frank, yeah it was to do with a missing environment variable because i’m deploying from an m1 machine, i need to set

GOARCH

to

amd64

Ah I see. Can you show me how you are setting it? Might be worth adding it to the doc.

it looked something like this within the main function

app.setDefaultFunctionProps({
  runtime: "go1.x",
  environment: {
    CGO_ENABLED: "0",
    GOOS: "linux",
    GOARCH: "amd64",
  },
});

Got it. Thanks @Hans Song!