Serverless

Most of the tests that currently cover core functionalities depend heavily on (and sometimes test) internal implementation characteristics. While they should be testing whether the given implementation produces desired outcome (treating its implementation more as a black box).

_Current state of things is problematic for eventual internal improvements and refactors which occasionally we want t

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

2.5.1.0

Current Behavior

When calling kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2:

A sender MUST NOT send a Content-

Today, Dapr supports unix domain sockets on self-hosted mode only. We should add a dapr.io/unix-domain-socket-path or similar annotation on Kubernetes and mount a volume (if possible; if not, instruct users to do so in the deployment YAML) for the

🚀 Feature

(A clear and concise description of what the feature is.)

Have you spent some time to check if this issue has been raised before?

(Have you googled for a similar issue or checked our older issues for a similar bug)
Yes

Have you read the Code of Conduct?

Yes

Pitch

A common way to mana

Describe the bug
Using a time dimension on a runningTotal measure on Snowflake mixes quoted and unquoted columns in the query. This fails the query, because Snowflake has specific rules about quoted columns. Specifically:

• All unquoted column names are treated as upper case
• Quoted column names are case sensitive.

So "date_from" <> date_from

To Reproduce
Steps to reproduce

Improved or typo fixed.

We don't have a Chinese version of datadog plugin doc. The English one is here: https://github.com/apache/apisix/blob/master/docs/en/latest/plugins/datadog.md.

Solution

Add the Chinese version.

Is your feature request related to a problem? Please describe.

Missing functionality to update min/max cpu/mem of an exiting ENV. Currently, to update, we are forced to delete and re-create the env. This also has a risk of dependent functions being erratic. It also de-couple resource utilization independent of function creation and be useful to update the resource in a quick to respond situ

The typescript runtime was recently added to openwhisk but we do not yet have docs for the runtime and it is missing from runtimes.json.

We need a doc like https://github.com/apache/incubator-openwhisk/blob/master/docs/actions-nodejs.md for typescript functions.

Adding the runtime to the runtime manifest can be done per https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#the-