lambda

Fission/Kubernetes version

Fission version above 1.14.1

Kubernetes platform (e.g. Google Kubernetes Engine)

Describe the bug
We have added support for Container functions in 1.14.1.
Currently, the grace period for container functions is hardcoded. We should make it configurable.
https://github.com/fission/fission/blob/76f51e977de9118494b74f929c383f1392f1d8b8/pkg/exec

this will very quickly get out of hand if we allow it, i realize we don't have principles written down anywhere but to date one of them has been that binaries 'just work' without having to do any configuration. currently a user must set FN_MAX_REQUEST_SIZE, FN_MAX_RESPONSE_SIZE -- neither of these should be required to run.

test case:

cd tests/fn-system-tests/
go test -v

this

Issue Summary

Building with serverless results in an error:

Build error occurred
TypeError: Class extends value undefined is not a

If we override PHP_INI_SCAN_DIR then the "special php.ini" files will not be used.
Ie: https://github.com/brefphp/bref/blob/0.5.9/runtime/layers/fpm/php.ini

Hi,

I wanted to enable binary support on API gateway, but could not find the way to do it via component's inputs.

Is this something that you would consider adding in the future?

If so, I can try to add this feature. It doesn't look too complicated.

Thanks!

Checklist

• Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a jets upgrade command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
• Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question

Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):