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://

Which Component

Sentinel

Describe the solution you'd like

Upgrade Sentinel to 1.8.1.

Any hover effects doesn't properly applied to all header elements (top line with cluster name and cluster menu). It seems that something placed on top of them and covers most of their height.

https://user-images.githubusercontent.com/9607060/108056014-cd186a00-7061-11eb-8ac0-5d01e206e636.mp4

ActorAdapter will ignore null message with "Adapter function returned null which is not valid as an .."

However, this seems not be documented. For instance, scaladoc/javadoc of pipeToSelf could mention it as well as any other place where adapters are used.

Description

This follows a discussion on Zulip[1].

To generate the DDL for JPA and/or Panache entities, I can use the schema-generation.scripts properties in the persistence.xml file as follow:

<property name="javax.persistence.schema-generation.scripts.action" value="drop-and-create"/>
<property name="javax.persistence.schema-generation.scripts.create-target" value="create.

Local PV (device) provisioner leaves a stale BDC in the following case:

• On PVC request, creates a BDC
• If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
• Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.

This causes the stale BDC

Feature Request

What problem are you trying to solve?

The proxy-init container will fail to start if either of the PROXY_INIT_OUTPUT or PROXY_INIT_REDIRECT chains already exist in the iptables rules. When the init container fails to start, the pod goes into a CrashLoopBackOff state.

The scenario where this behavior was discovered is an edge case where a process external to Kubern

I find a solution in the forum
https://kubesphere.com.cn/forum/d/3384-kubespheredevopsdotnet-core
But it is too trouble to use , and waste much time to set up it .
So any plan for including it to the nodes of devops flow.

Extending the work in yugabyte/yugabyte-db#6772, it'll be helpful to also show in the http://yb-master:7000/tablet-server-clocks view, for each yb-tserver, the RTT time between the yb-tserver and yb-master leader.

This will give a quick indication of how geographically dispersed the nodes in the system are.

The OPA-Envoy plugin is integrated with Gloo Edge and a step-by-step tutorial is available here. We should add this tutorial to the Envoy section of the OPA docs. We could update the existing tutorial to send the request body to OPA and use that i

Improve Docs

https://github.com/apache/apisix/blob/master/FAQ.md#why-is-it-that-installing-apisix-dependencies-with-luarocks-causes-timeout-slow-or-unsuccessful-installation

luarocks install apisix --server https://luarocks.cn

Please describe which part of docs should be improved or typo fixed

A clear and concise description of what you want and what your use case is.

What would you like to be added/modified:

To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.

To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef

chaos-daemon doesn't have any authentication mechanism, which means any client in the cluster could modify the iptables and ipset config / cause stress / inject IO latency for nearly all the pods.

gRPC with server side SSL/TLS authentication is enough. However, it may break the chaosctl (which is definitely an evidence for the risk), or we need to distribute the certificate to it (or it can

Task

Convert CI to GitHub Actions

Context

Travis is removing its free tier for OSS projects, so this should be built with GitHub Actions instead, which is not going to add additional cost.

I would expect this to be one of the easier projects to convert given that Docker isn't used in the build.

See also:

https://github.com/mvdan/github-actions-golang
https://github.com/ac