I've noticed a new behavior (bug?) when running SS...
# sst
s
I've noticed a new behavior (bug?) when running SST locally that causes the live lambda dev environment to crash. It doesn't happen all the time, but when it does, it's always when I modify and save a file in my project (a python app). I just re-run
sst start
again, which seems to do the trick, but this behavior is new to me. I'm on SST 0.56.2
Copy code
Error: Unable to evaluate guard 'cond' in transition for event 'done.invoke.(machine).building:invocation[0]' in state node '(machine).building':
Cannot read property 'length' of undefined
    at StateNode.next (/Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/StateNode.js:587:17)
    at StateNode.transitionLeafNode (/Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/StateNode.js:454:26)
    at StateNode._transition (/Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/StateNode.js:547:19)
    at StateNode.transition (/Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/StateNode.js:818:32)
    at /Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/interpreter.js:706:28
    at Object.provide (/Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/serviceScope.js:12:16)
    at Interpreter.nextState (/Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/interpreter.js:705:34)
    at /Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/interpreter.js:108:31
    at Scheduler.process (/Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/scheduler.js:69:7)
    at Scheduler.schedule (/Users/sgeoghegan/dev/knock-attribution-service/node_modules/xstate/lib/scheduler.js:48:10)

error Command failed with exit code 1.
info Visit <https://yarnpkg.com/en/docs/cli/run> for documentation about this command.
t
someone else reported this recently will look
s
I'll report back if I'm able to reproduce. For now, it's just happening occasionally
@thdxr I was able to reproduce the issue reliably using this repo. It's the SST python REST API example modified to include numpy as a lambda layer (unrelated to this issue). After executing
sst start
, I was able to reproduce the error by modifying and saving the
notes.py
file. After doing this, it crashed immediately
t
I already fixed it haha
waiting for tests to pass
appreciate that tho
s
No problem! It's been happening a lot to me this morning, so I thought I'd see if I could reproduce elsewhere.
💥
t
releasing now
but it'll require an update to cdk 138 so that might be tricky