alertlogic/erllambda

need better exception handling

motobob opened this issue · 1 comments

one of issues reported is when erllambds itself swalloed an exception and went into perpetual mode of

{{case_clause,{ok,{{403,"Forbidden"},[{"content-length","127"},{"date","Fri, 16 Nov 2018 07:01:05 GMT"},{"content-type","application/json"}],<<"{\"errorMessage\":\"Transition from STATE_INVOKE_NEXT to STATE_INVOKE_NEXT is not allowed.\",\"errorType\":\"InvalidStateTransition\"}\n">>}}},[{erllambda_poller,invoke_next,1,[{file,"/home/jenkins/workspace/search-filter/_build/default/lib/erllambda/src/erllambda_poller.erl"},{line,160}]},

need better protection form such of errors on our side and make it fail the whole VM (erlang:halt() type) and report the issue to AWS Runtime so that the container is killed.

fixed in 1.0.2