alertlogic/erllambda

test aws runtime response handler doesn't handle non-JSON responses

velimir opened this issue · 2 comments

{trace,<0.488.0>,call,
       {erllambda_poller,invoke_success,
                         [{state,<<"127.0.0.1:61505">>,
                                 erllambda_crash_handler,
                                 #Ref<0.1213196390.2356936705.178860>,
                                 undefined},
                          <<"ae3c0b08-8dc2-46b4-a859-7e682feac315">>,
                          <<"completed successfully">>]}}

should it really be a JSON as per docs it's just an object of content_type: */*
raw binary is fine...no?

missed this part, it's a mistake in test runtime, which always expects a valid json:

ResponseResult = jiffy:decode(Body, [return_maps]),