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

Hey guys

I am learning and using seata recently, this is a great thing.

Component
spring-cloud-alibaba-seata:0.9.0.RELEASE

Question
I see that the seata source code contains the spring boot web dependency. **Is there a plan to support [sp

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.

Describe the bug

After Hydra startup log warns about configuration key deprecation. There is no records in documentation reference (https://www.ory.sh/hydra/docs/reference/configuration/) about oidc.subject_identifiers.supported_types.

Reproducing the bug

Steps to reproduce the behavior:

Start Hydra Hydra v1.9.0-alpha.2 with oidc.subject_identifiers.enabled set to public

_Se

For example in "confirm cluster delete" the "Remove" button is highlighted, but hitting enter doesn't submit it (however, esc does close it)

Description

Adding Indonesian translation of Readme.md and contributing.md

Con

Feature Request

What problem are you trying to solve?

When running linkerd check where the contents of IdentityContext.TrustAnchorsPem are a set of certificates (i.e. a bundle), the test for the validity of the identity will produce the following error:

linkerd-identity
----------------
× certificate config is valid
    IdentityContext.TrustAnchorsPem does not match ca.cr

Today the top-level YSQL statement metrics at the TServer level are categorized as:

For example:
http://yb-tserver:13000/metrics

See output below. It'll be good to break out from the OtherStmts category, separate metrics for Commit and Prepare operations.

  {
        "type": "server",
        "id": "yb.ysqlserver",
        "metrics": [
            {
                "name": "han

Feature Description

Kubersphere integrate the velero based on the k8s CRD extensions

How does it work
It's like monitoring component

I found that some admin API provided by apisix are not found in any documentation, such as
/apisix/admin/plugins/list, so do we need a doc to keep track of the admin API that is nowhere to put?

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

There is no e2e test and documents for external network delay and partition now 🤦 .

The e2e test could be found in /test/e2e/chaos/basic.go. Reading other tests in that file could help accomplish this issue.

Example for extern network delay:

apiVersion: chaos-mesh.org/v1alpha1
kind: NetworkChaos
metadata:
  name: network-netem-example
  namespace: chaos-testing
spec: