Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

Expected Behavior

Request times out after certain amount of time

Actual Behavior

req {
    method
    PUT
    remoteHost
    127.0.0.1
    requestURI
    /actors/TimerActorType/zzz/ method / registerTimer
    requestURL
    http: //127.0.0.1:8080/actors/TimerActo

Describe the bug
If I pass 'Next 7 days' into the dateRange in query, the response is not a range over the next 7 days but only the day IN 7 days.

To Reproduce
Steps to reproduce the behavior:

1. Build a query like this:

const query: Query = {
    measures: [
      measure
    ],
    timeDimensions: [
      {
        dimension: 'Your.Dimension,
        dateRange: 'Next 7

🚀 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

Command: cortex debug exec API_NAME

Behavior: choose a running API pod (at random is ok if there are multiple), and run e.g. kubectl exec -it api-iris-classifier-6d866654f8-pwz62 --container api -- /bin/bash

This command should be executed in the manager container, similar to how the cortex cluster up command works. However unlike cortex cluster up, this command will require interact

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-

Issue description: Apisix stream_routes's parameter "remote_addr" only support single ip, needs to support multiple ip or match rules like "192.168.0.0/16", just like http routes parameter "remote_addr"

Environment

Request help without environment information will be ignored or closed.

• apisix version (cmd: apisix version): 2.6
• OS (cmd: uname -a): CentOS7
• OpenResty / Ng

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