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

Some system variables either have no type (default: TypeString) or use TypeString when they could use a different builtin type (TypeInt, TypeEnum, TypeBool) that is more suited. Here is what I found from manual inspection:

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或者其他类型,那么这个配置就

It will be useful to install/show helm chart pre releases from a helm repo. Using helm from the commandline pre releases are also not shown or installed. Adding the --devel it will show or install pre releases. It would be nice to have a switch to show the pre releases or not like for example in rancher.
![rancher](https://user-images.githubusercontent.com/106823500/171875868-3c090565-2060-4fcc-a

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.

Checklist

• [✔] Double-checked my configuration.
• [✔] Tested using the latest version.
• [✔] Used the Emissary executor.

Summary

What happened/what you expected to happen?

The message that is output by the hook named on-fail should have the `{{ work

Is there an existing issue for this?

• I have searched the existing issues

What would you like to be added?

Current chunk manager didn't accept ctx for timeout and tracing control.
such as:
Read(ctx, Context, filePath string) ([]byte, error)

Why is this needed?

No response

Anything else?

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

Currently, the Quarkus caffeine cache offers the following properties (see https://quarkus.io/guides/cache#quarkus-cache-config-group-cache-config-caffeine-config_configuration):

• initial capacity
• maximum size
• expire after write
• expire after access
• metrics enabled

Caffeine also offers setting 'refresh after write' (see https://github.com/ben-manes/caffeine/wiki/Re

Description

Currently we are using Semantic Pull Requests to check in PR but the project is no longer maintained. we need some alternatives.

e.g.

• https://github.com/amannn/action-semantic-pull-request

If anyone is interested in this, please submit a PR to complete this replacement

What is the issue?

Browsing linkerd viz, you'll sometimes come across "Current Tap query" or similar, but when I copy the command and run it in the terminal it says,

Command "tap" is deprecated, use instead 'linkerd viz tap [flags] (RESOURCE)'

How can it be reproduced?

Troubleshooting the "getting started" emoji voto app, suggests on the Tap-site for the /api/vote-en

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

The MISCELLANEOUS top-level section in the docs navigation has grown organically over time. It feels like it's time to reorganize the content under MISCELLANEOUS that it's easier for people to find and more consistent.

Here's my proposal for where the conten

Description

source: https://docs.yugabyte.com/latest/architecture/transactions/isolation-levels/#root

We begin the section by listing out 4 transaction isolation levels in decreasing order of strictness. Where possible, subsequent sections should follow this order to make it easier for readers to follow. For example, rewrite the second paragraph to read:

YugabyteDB supports three transa

What problem are you facing?