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

I've following the various docs in an attempt to run Ory Hydra using the binary, and I've used the reference configuration from docs/docs/reference/configuration.md in order to speed up the setup of a basic playground.

On one hand, there seems to be a few outdated values in that reference configuration as per the following warning messages:

{
  "audience": "application",
  "file": "/g

Describe the bug
In the Apps section under Releases, you can sort on Revision. It seems to sort on the string values instead of the integers which looks silly (see screenshot below).

To Reproduce
Steps to reproduce the behavior:

1. Go to Apps -> Releases
2. Click on Revisions
3. See nonsensical number order

Expected behavior
Numbers sort in their counting order.

**Screen

Description

Enhance RawFile LocalPV repo CSI driver to change the default data-dir mount path using an ENV or chart template parameter to make it configurable.

The data directory used for creating the sparse file is hardcoded to "/var/csi/rawfile" in the task template.
https://github.com/openebs/rawfile-localpv/blob/master/templates/task.y

Bug Report

What is the issue?

'linkerd check' errors out with missing ClusterRole when prometheus is not deployed through configuration

How can it be reproduced?

Deploy linkerd with 'global.prometheus.enabled' set to false and run 'linkerd check'

Logs, error output, etc

(If the output is long, please create a gist and
paste the link here.)

The current message ("There is no data to display") is misleading. At the minimum, this message should be changed to something like "Fetching the data, please wait". Ideally the implementation should be changed to improving the data load behavior.

• we only test HS256 algorithm, not cover HS512 and RS256
• not test unsupported algorithm, for example HS384. we need throw the unsupported alg msg from https://github.com/SkyLothar/lua-resty-jwt/blob/master/lib/resty/jwt.lua#L505

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