Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

2.5.1.0

Current Behavior

When calling kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2:

A sender MUST NOT send a Content-

Feature Description

Now that we have a minimum of go1.16 set, we can use go's embed functionality to embed templates/web assets (css/js), and translations.

Screenshots

No response

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

What would you like to be added:
A button or link from the list of instances of

Describe the bug

Quick Start Page badger dis

Support importing Grafana templates to the workspace level. Currently, this function only can be accessed by the cluster lever.

Solution

See https://github.com/kubesphere/kubesphere/blob/511d0d02fffc766c0ee218dab15d399888681672/pkg/kapis/monitoring/v1alpha3/handler.go#L404 for detail. Maybe we need to add a namespace parameter as an optional to determine to convert it to Dashboard struct

Improved or typo fixed.

这里有个例子，在指定的路由中启用 dubbo-proxy 插件:
curl http://127.0.0.1:9080/apisix/admin/**upstream**/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"nodes": {
"127.0.0.1:20880": 1
},
"type": "roundrobin"
}'

Solution

curl http://127.0.0.1:9080/apisix/admin/upstreams/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.

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