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-

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create database db;
use db;
rename table tb1 to tb2;

2. What did you expect to see? (Required)

MySQL 5.7
ERROR 1017 (HY000): Can't find file: './db_optimistic/tb1.frm' (errno: 2 - No suc

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:
In the manual scaling window for deployments,

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.

We need more metrics about DML latency, which including search,insert,delete.
For details, we should see latency histogram for each stage, for example e2e, proxy side, message queue, per segment and during reduce.
This will help users to invest

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

Improved or typo fixed.

https://github.com/apache/apisix/blob/0d4f65a9ae06430388af609ca0dcad386225d616/apisix/core/vault.lua

Solution

not doc for how to use vault with Apache APISIX

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

Fission/Kubernetes version

Fission version above 1.14.1

Kubernetes platform (e.g. Google Kubernetes Engine)

Describe the bug
We have added support for Container functions in 1.14.1.
Currently, the grace period for container functions is hardcoded. We should make it configurable.
https://github.com/fission/fission/blob/76f51e977de9118494b74f929c383f1392f1d8b8/pkg/exec

Currently, whenever there's a patch release, like 0.36.1, that becomes the only displayed docs version in the version picker:

That's fine. However, we also stop generating website content for the previous versions, so 0.36.0 disappears: https://www.openpolicyagent.org/docs/v0.36.

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!