Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Is your feature request related to a problem? Please describe.
It would be great to be able to configure the route output, e.g. I want to hide the Cube.js server is running in production mode. Learn more about production mode. when the base route is hit

Describe the solution you'd like
I think it would be great if one could configure the output of https://github.com/cube-js/cube.js/

Description:

I'd like to be able to specify the IAM role Path on either a function or globals.

Observed result:

Able to specify Path on a Function or Globals

Expected result:

Path is set on the implicitly created IAM roles

When starting a basic Dapr app, there is a lot of noise about actors in the log that potentially could scare the user, whether user is using actors or not. Allow me to illustrate with some way to sarcastic narration ;)

There is the "hey, I'm not sure if you wanted to do anything with actors, but just in case, you got none configured... well, it could that you have more than one configured so we

Kubectl explains is useful for a Fission user to write function specs especially but it does not give any information as of now.

$ kubectl explain functions -ndefault
KIND:     Function
VERSION:  fission.io/v1

DESCRIPTION:
     <empty>

It should look something similar to:

$ kubectl explain pod.spec
KIND:     Pod
VERSION:  v1

RESOURCE: spec <Object>

DESCRIPTION

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

https://emotion.sh/

After this change in Material UI: mui-org/material-ui#6115

Appwrite playgrounds are a set of repositories with language/platform-specific Appwrite integration code samples. Each playground is composed of a readme file and a single code file with examples of different API calls to demonstrate how to initialize and use Appwrite SDK.

We have playgrounds for a few platforms, and we would love to get the community help with adding new ones and improve the

all of these files are ONLY for test cases.

The queue-proxy's main.go file contains a lot of stuff currently and is hard to test. We should decompose the queue-proxy where poss