cloud-native

expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

Enhancement

We have many place to use the exp/slices to sort our struct. It can improve performance by using pdqsort and clean branch check. But We have many placement using the old sort. Please remove it. Here is the example .

BTW, You haven't to change the bazel.build. it can be updated by robot.

• #36061
• #360

Which Component
spring-cloud-starter-stream-rocketmq

Describe the bug
When hot deployment in eclipse throw MQClientException: The producer group[mygroup] has been created before

To Reproduce
Steps to reproduce the behavior:

1. Spring boot application with devtools in Eclipse
2. Send message using org.springframework.cloud.stream.function.StreamBridge.send
3. Modify any cod

Pod tolerations number is sticked to the start of the line, causing text overflow.

What problem is the feature used to solve?

kratos does not provide client-side request retry logic

References

- [http retry](https://github.com/gojek/heimdall/tree/master/httpclient)
- [gprc retry](https://github.com/grpc-ecosystem/go-grpc-middleware/tree/master/retry)

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.

PodPriority should be deprecated from workflow spec since Kubernetes uses PodPriorityClass to indicate the importance and priority of a pod relative to others.

https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/

https://github.com/argoproj/argo-workflows/blob/178bbbc31c594f9ded4b8a66b0beecbb16cfa949/pkg/apis/workflow/v1alpha1/workflow_types.go#L351-L352

Is there an existing issue for this?

• I have searched the existing issues

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

When deploy milvus with external pulsar cluster provided by other team,
we meet the problem that milvus does not support pulsar auth,
but for security it's recommend to enable auth for pulsar cluster.
so will milvus support pulsar auth later?

Add a network option in creating workload

like rancher‘s Networking tab

** During workload creation, user can customize own hosts and DNS search doma

Description

At the moment, it seems that only configuring the db-kind of a datasource, and forgetting about the JDBC URL, will lead to the datasource not being created. It leads to confusing situations where the Hibernate ORM extension throws an error because it can't find the datasource.

See for example [here](https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/configure

Current State

The Kubernetes Service Discovery module supports a field default_weight as the weight for Apache APISIX upstream nodes, but it misses from both the config-default.yaml and the document https://apisix.apache.org/docs/apisix/next/discovery/kubernetes/.

Desired State

We need to add explanation for this field.

What problem are you trying to solve?

Having JSON output options for commands helps with programatic use of the CLI. The main driver behind this feature request though is for use in tests so that we can eliminate the manual parsing that we currently have to do in the integration tests as noted here.

How should the pro

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

While there's even a section named "Accessing Annotations", it does not mention, or link to, the Rego reference docs for instructions on how to do this from inside of a policy.

Suggestion: add new sub-heading under "Acessing Annotations" called "Rego", providing a very simple example, and link to the policy refere

Jira Link: DB-3034

Description

Rocksdb Rate limiter supports specifying the granularity at which the rate is enforced. This defaults to 100ms

extern RateLimiter* NewGenericRateLimiter(
    int64_t rate_bytes_per_sec,
    int64_t refill_period_us = 100 * 1000,
    int32_t fairness = 10);

However, Docdb doesn't seem to be spec

What problem are you facing?