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-

lightning v5.3.0

After the content in parquet may be written by spark, the definition of bool is true or false. Regenerating the parquet file takes time, In tidb, bool behaves as tinyint, so proper type conversion will help improve the success rate of lightning import

parquet file：
![image](https://user-images.githubusercontent.com/21033020/147809823-214dcb34-0e10-4566-aa75-2109c0525144

Which Component
Sentinel

Describe what problem you have encountered
在hystrix和resilience4j中，我们可以配置default，对所有的feign client生效，例如熔断规则，隔离策略。在sentinel中我找不到类似的配置，似乎需要单个url去配置，这非常麻烦，请问怎么做。

In hystrix and resilience4j, we can configure "default", which will take effect for all feign clients, such as circuit breaker rules and isolation strategies. I can't find a similar configuration in sen

What would you like to be added:
I would to see instance type and instance region (if that labels are assigned to nodes) right from the list of Nodes

Why is this needed:
In case if you trying to manage a lot of nodes (30-50) sometimes it's complicated to understand what is that server for. This two columns will help me managed and understand without clicking details. Maybe much better

We at Jina are fans of the written word. And , if you are a beginner in neural search and OSS, what better than starting out with documentation and blogs ?
How to make a contribution?

Comment below this issue the topic you have in mind for writing a blog. The topic should revolve around - neural search/Jina/Jina-OSS etc. (basically about Jina)

What can it be about? It could be a tutorial or

current return queueOfferResult == QueueOfferResult.enqueued();

Both successful workflows and stopped workflows are generating similar kind of events with 'reason' as 'WorkflowSucceeded'. There is no way to differentiate successful vs stopped events to trigger different down streams based on the status.

What change needs making?
Would like to see reason as 'workflowStopped' for stopped workflows.

Use Cases

We are using [Argo events](https://argoproj

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe.

Currently, if a user insert failed, client has to retry the whole batch, which incur duplicated entities in the system.
If user define primary key then later on we will support primary key deduplication to solve the problem.
For auto increment p

Description

If we use io.quarkus.runtime.annotations.RegisterForReflection#classNames to register classes for reflection it does not register classes up in the hierarchy.

On the other hand, if we use -H:ReflectionConfigurationFiles, it does register the full class hierarchy.

Implementation ideas

I think we should look for the full hierarchy here: https://github.com/quarkusio/qu

Issue description

How to current limit both in minutes and day by using plugin limit-count?
current,the plugin limit-count only Set a traffic limiting mode, Second or minute,If I want to set seconds and minutes at the same time,plugin not support,Because what you set later overwrites what you set earlier,Is there a better solution to this problem?thank you

Environment

• apisix v

We're on 5.3.0 and would like to upgrade to v6, but that's a breaking change that requires manual intervention in our routes handling.

The React-router project has promised a compatibility layer to come up at some point that would avoid having to change things too much, but I feel that's a second-best solution and would prefer to have things written as per the best practice.

For anyone w

Description

We have created a udev rule similar to below on few nodes, where ndm i

Is your feature request related to a problem? Please describe.

Missing functionality to update min/max cpu/mem of an exiting ENV. Currently, to update, we are forced to delete and re-create the env. This also has a risk of dependent functions being erratic. It also de-couple resource utilization independent of function creation and be useful to update the resource in a quick to respond situ

The following code panics:

package main

import (
	"context"
	"log"

	"github.com/open-policy-agent/opa/sdk"
)

func main() {

	ctx := context.Background()
	opa, err := sdk.New(ctx, sdk.Options{}) // Config MUST be provided
	if err != nil {
		log.Fatal(err)
	}

	result, err := opa.Decision(ctx, sdk.DecisionOptions{})
	if err != nil {
		log.Fatal(err)
	}

	log.Printl

On recent versions, yb-admin ysql_catalog_version keeps returning zero even after catalog changes. This is because it uses CatalogManager::GetYsqlCatalogConfig which reads from the legacy protobuf catalog version, not the pg_yb_catalog_version system table. Fix yb-admin to get the version from the correct source.

How are you planning on using kubeedge?

I've been looking for something like this for a long time (Currently our team uses Rancher although their product wasn't really meant for edge computing.) I'd love to hear how others in the community would like to use this so I can compile a list of use cases that kubeedge can support out of the box.

Thanks!