It looks like --increase-timeout is on by default....
# sst
m
It looks like --increase-timeout is on by default. I’m not sure if thats the intention given it’s a command option?
f
Hey @Mike McCall, I just tried it.. it seems turned off by default.
Which SST version r u using?
m
0.31.0
ok odd, all of lambda were set to 15 min timeouts!
f
lemme give 0.31.0 a try quickly
Just tried it and timeout seems fine. After you run
sst start
, can you check the CFN template in
.build/cdk.out
and search for
Timeout
?
m
I actually set the default in the app. I’ll have to remove that and give it a go.
f
Default set to 900s?
m
10 seconds
it was set to 900
But we didn’t set it to 900
f
Mike, lemme know if u need a hand tracking down where the timeout is set to 900s.
m
Right! actually let me deploy know and check
I’m not 900, I previous set app default to 10 I am seeing that everywhere, despite removing default.
f
You mean it looks okay now? Or are timeouts still getting set to 900?
m
Not setting a default at all. I don’t see 900s.
f
I see. That’s good. Before v0.28.0,
sst start
would automatically set the timeout to 900. And in v0.28.0, we added the
--increase-timeout
flag and only set the timeout to 900 if the flag is passed in.
Anyways let me know if u run into this again.
m
sweet, we just updated past 28. That’s probably why they were 900. Thanks!