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

[2022-02-14T04:12:14.746Z] ----------------------------------------------------------------------
[2022-02-14T04:12:14.746Z] FAIL: db_test.go:7069: testSerialDBSuite.TestModifyColumnTypeWhenInterception
[2022-02-14T04:12:14.746Z] 
[2022-02-14T04:12:14.746Z] db_test.go:7124:
[2022-02-14T04:12:14.746Z]     c.Assert(checkMiddleWarningCount, Equals, true)
[2022-02-14T04:12:

Hey, I found a little problem. if I configure a data-id without file extensions in extension-configs , but config content type is yaml. then there is a proble, configuration is invalid. because the configuration is parsed by properties. so I want to add fileExtension field in NacosConfigProperties.Config.

我发现一个小问题, 如果在extension-configs里的data-id没有带文件后缀,并且配置内容格式是yaml或者其他类型,那么这个配置就

What would you like to be added:

• a function (checkbox?) to use the helm switc

Problem: It is pretty challenging to find resource material and valuable articles, videos and such, and we spend a lot of time searching and finding the appropriate resource for us.

Proposed solution: Faceted search can come a long way when looking for a quick way to find a solution designed for our needs. Ratings on the resource can help us select the best solution based on our search

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.

Summary

Currently, the secrets are printed in the logs without any filtering. It would be nice if the secrets could be redacted in the logs while being printed

Use Cases

This would prevent unintentional leaks of a secret in the log by running something like env in the workflow

NOTE: This does not prevent intentionally leaks of the secrets. Someone can still run something like `en

Is there an existing issue for this?

• I have searched the existing issues

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

currently, milvus use protobuf heavily in the cgo interface for data exchange between go and c code.

However, if we take a deep look into it, many of the code path is copied and converted heavily, for instance in the load path:

1. read parquet

Description

It would be nice if Quarkus can support the Flyway cleanOnValidationError parameter. This would be really useful for dev and integration environments.

https://flywaydb.org/documentation/configuration/parameters/cleanOnValidationError

Implementation ideas

No response

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

I'm using grpc-transcode plugin to manage gRPC<=> HTTP, It would be great to convert grpc-status-details-bin in header to HTTP response body in case an error from the upstream.

Decoded grpc-status-details-bin :
![Screens

What problem are you trying to solve?

Under some configs, Grafana charts making use of the [i]rate function aren't displaying any data.

How should the problem be solved?

This happens when time duration parameters in promql queries are smaller than the scrape interval Prometheus is configured with. The solution is detailed in [this blog post](https://grafana.com/blog/2020/09/28/new-in-

Description

Help increase external contributors by quantity & by quality & reduce

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

Saw this rule in the clj-kondo linter, and I think it would be a good addition to our strict mode. Having duplicate elements in sets is probably always a mistake in a production policy, and while it's "harmless", the intent is likely to provide another element rather than the duplicate, leading to an unexpected

Description

Create a cluster with TEST_docdb_log_write_batches=true and observe the following -

./bin/yb-ctl create --rf=1 --data_dir ~/yugabyte-data --tserver_flags 'TEST_docdb_log_write_batches=true'
./bin/ysqlsh
yugabyte=# create table test (k int primary key, v int);
CREATE TABLE
yugabyte=# insert into test values (1, 1);
ERROR:  Network error: recvmsg error: Connection refus

What problem are you facing?