Skip to content

Lambda-Runtime-Function-Error-Type header missing when reporting errors. #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks
fabianfett opened this issue Jun 7, 2020 · 0 comments · Fixed by #128
Closed
2 tasks

Lambda-Runtime-Function-Error-Type header missing when reporting errors. #116

fabianfett opened this issue Jun 7, 2020 · 0 comments · Fixed by #128
Labels
good first issue Good for newcomers kind/bug Feature doesn't work as expected.

Comments

@fabianfett
Copy link
Member

fabianfett commented Jun 7, 2020

According to the documentation we must set a special header ("Lambda-Runtime-Function-Error-Type: Unhandled") when we report an error.

This must be done for both:

  • initialization error
  • invocation error
@fabianfett fabianfett added kind/bug Feature doesn't work as expected. good first issue Good for newcomers labels Jun 7, 2020
@fabianfett fabianfett changed the title Lambda-Runtime-Function-Error-Type header missing when reporting errors. Lambda-Runtime-Function-Error-Type header missing when reporting errors. Jun 7, 2020
tomerd pushed a commit that referenced this issue Jun 17, 2020
… (#128)

* allow the users of client to provide headers
* add initialization error header
* add error header to failed invocations
* fix external setting of ip and port via config
* add tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers kind/bug Feature doesn't work as expected.
Projects
None yet
1 participant