Kubernetes

Nowadays, when the kube-scheduler is initialized, the provided component config (via --config flag) is logged. E.g.

I0404 08:35:16.471898       1 configfile.go:96] Using component config
-------------------------Configuration File Contents Start Here---------------------- 
apiVersion: kubescheduler.config.k8s.io/v1beta3
clientConnection:
  acceptContentTypes: ""
  burst: 100
  conten

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

What happened?

If you don't pass a --name argument to your etcd processes, they will all have the name default and the cluster will operate normally. However, when you add a member, the generated ETCD_INITIAL_CLUSTER variable will have multiple entries with the name "default". When this environment variable is used, etcd will parse these into a mapping under a single key ("defau

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

overview

Today, the RequestRecorder records service RPC calls. If those take less than < 0ms, the recorder marks them as 0ms.

proposal

Make the RequestRecorder report the elapsed time for service calls that take less than < 0ms as decimal values, instead of 0.

notes

testing

If you take this on, I'd kindly advise to start in a TDD fashion. Write a test

Currently:

==> Audit <==
|---------|---------------------|----------|--------------|---------|-------------------------------|-------------------------------|
| Command |        Args         | Profile  |     User     | Version |          Start Time           |           End Time            |
|---------|---------------------|----------|--------------|---------|-----------------------------

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

这样很方便查看

Output of helm version:
version.BuildInfo{Version:"v3.8.1", GitCommit:"5cb9af4b1b271d11d7a97a71df3ac337dd94ad37", GitTreeState:"clean", GoVersion:"go1.17.8"}

If HELM_DATA_HOME contains spaces, like `/Users/My Name/Library/hel

In the application details view, we list the ports an application deployment is listening on, but there is no "quick launch" or even a "copy" button..

We should add a "copy" button next to the port to copy to clipboard.

In what area(s)?

/area runtime

What version of Dapr?

All versions -- tested since 1.4.2.

Expected Behavior

The Dapr sidecar / daprd should not start when dapr-app-port and dapr-http-port are identical and return a meaningful error.

Actual Behavior

Dapr sidecar starts, but upon service invocation returns an error unrelated to the problem.

`{"errorCode":"ERR

What would you like to be added:

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

Is your feature request related to a problem? Please describe.
Logs are shown in UTC. IT is frustrating when trying to troubleshoot an issue and need to keep converting timestamps to determine which logs are relevant.

**Describe the sol

Our parser outputs all aggregations functions using the general sqlparser.FuncExpr. This is a little clunky and requires us to do additional checks before we are sure that the aggregation we have is valid and what it is aggregating.

I suggest we instead introduce one struct type per aggregation, and have them all implement some interface. This would help clean up the code.

Example:

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

Ìt seems a library is not compatible, worth look into it.

packages/plugins/memory test: FAIL test/memory.spec.ts (9.385 s)
packages/plugins/memory test:   ● writing files › should abort while write a tarball
packages/plugins/memory test:     TypeError: Cannot set property closed of [object Object] which has only a getter
packages/plugins/memory test:       at class_2.Object.<anonymous>.Fs