What would you like to be added:

As the #1037

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

Important location: https://github.com/kubernetes/minikube/blob/master/cmd/minikube/cmd/version.go#L55

Discussion: https://kubernetes.slack.com/archives/C1F5CT6Q1/p1626820802044000?thread_ts=1626811554.016000&cid=C1F5CT6Q1

when killing the process running helm dep up it sometimes leave a temporary folder named tmpcharts and this makes the next helm dep up fail with the following error.

Error: Unable to move current charts to tmp dir: rename /mychart/charts /mychart/tmpcharts: file exists

This is easily reproducable by creating a folder named tmpcharts inside an helm chart root folder and try to l

Requirement - what kind of business use case are you trying to solve?

Hello team, in PR jaegertracing/jaeger#2798 the tls connection is enabled in collector, it would be good to support configuring cipher for it.

It would be similar to the fluentd tls settings in https://docs.fluentd.org/configuration/transport-section#tls-setting, you can config the ciphers fi

1. Describe IN DETAIL the feature/behavior/change you would like to see.

Implement WarmPool.RenderTerraform()

2. Feel free to provide a design supporting your feature request.

/kind feature
/area terraform
/lifecycle frozen

Feature Suggestion

Similarly to the Tauri CLI, add an info command to backstage-cli that lists at least

• ope

Overview of the Issue

vtexplain panics on SHOW TABLES and SHOW FULL TABLES

Reproduction Steps

Steps to reproduce this issue, example:

1. Deploy the following vschema.json:

{
    "ks1": {
        "sharded": true,
        "tables": {
            "user": {
                "column_vindexes": [
                    {
                        "column":

Is your proposal related to a problem?

Replication is currently slow.

Describe the solution you'd like

tools bucket replicate could upload a few objects at a time instead of one by one

Describe alternatives you've considered

Copying the objects with some other tool but tools bucket replicate is way too convenient because you can use two completely different object st

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered

In this document, following sentence has a typo,

# Register the intrumentation handlers (/metrics etc).

intrumentation -> instrumentation

# Register the instrumentation handlers (/metrics etc).

What would you like to be added/modified:

To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.

To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef

Feature Requests

Chaos Mesh need lots of tools for code generation, include:

• controller-gen
• protoc
• kukustomize
• failpoint-ctl

and some other tools as linter:

• revive
• gosec
• goimports

And we will use these binaries that already exist in PATH priority, and try to install with go get if it does not exist.

So here are two issues about that:

• if the user alread

i am cloning this git repository into the path /root/src/github.com/
my GOPATH=/root/src/
my GOROOT=/root/
my GOBIN="/root/src/github.com/virtual-kubelet/bin"
and i enter /root/src/github.com/virtual-kubelet directory and run the make build command, i get this error:

`which: no gobin in (/bin:/root/src/github.com//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/loc

I noticed that Contour is still using the VMware Code of Conduct, instead of the CNCF one. We have a Code of Conduct template that you can use.

cc: @jonasrosland