can there be a but with the way lumo calls the -main function? In my logs I see

00:55:00 in main
00:55:00 after main
00:55:00 START RequestId: acb1d829-79bc-430c-be3f-2970d6a5f542 Version: $LATEST
00:55:00 Exit
00:55:00 END RequestId: acb1d829-79bc-430c-be3f-2970d6a5f542
00:55:00 REPORT RequestId: acb1d829-79bc-430c-be3f-2970d6a5f542	Init Duration: 1550.70 ms	Duration: 55.39 ms	Billed Duration: 1700 ms Memory Size: 1024 MB	Max Memory Used: 186 MB
00:55:00 RequestId: acb1d829-79bc-430c-be3f-2970d6a5f542 Process exited before completing request
00:55:02 in main
^^ why is it here again?

there is also something else which is weird... maybe there is a reason why Grav here does this piece of dancing: https://github.com/grav/aws-lumo-cljs-runtime/blob/master/runtime.cljs#L53-L80

(see start) called in the .then

weird ok...that trick works in any case so I am not going to change it

oh nooo, I have segmentation fault with the AWS sdk...

and statically linked lumo

also it looks like older versions of node, even the LTS, cannot be compiled anymore

Is there a way to debug what is going on? Should I resort to gdb?

I feel like I am rabbit holing 😁

I can confirm it is the static build that crashes

oh I need to build in the Amazon Docker

that's why there is a docker container in @grav's repo

let me try that

Lumo can’t handle macros right?

@jayzawrotny it does yes, what is the error you get?

No errors yet, just didn’t think self-hosted clojurescript could do macros. I take it they still need to be defined in a cljc file?

@jayzawrotny yes they do need that 😄