Kubernetes

Presumably this would occur when changing the default from one class to another. E.g.

• Class X exists and is marked default
• Class Y is created
• Class Y is marked as default
• Uh oh!! 2 defaults
• Class X is marked as not default

At the case in point, when there are 2 defaults, we currently do not assign default values to new PVCs.

We should change this semantic - while there a

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?

In a Jepsen test run of five etcd 3.5.3 nodes, with process pauses (sending processes SIGSTOP and SIGCONT), compaction (performed via the admin API), and defragmentation (via etcdctl), one etcd process crashed with the following error message:

{"level":"panic","ts":"2022-06-13T14:11:27.870Z","caller":"etcdserver/apply.go:638","msg":"unexpected error during txn","error

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

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.

So pretty weird issue:
I am creating 2 prefixes, one empty, one not empty like this...

consul kv put testprefix/
consul kv put testprefix2/testkey

then when I curl those prefixes recursively like:

curl localhost:8500/v1/kv/testprefix?keys
# this is the reply -> ["testprefix/","testprefix2/testkey"]

notice how only testprefix/ is specifically listed?

now

It's not possible to enable addons with --no-kubernetes passed because the addons in their current state are deployed to Kubernetes. So if a user tries to enable an addon with --no-kubernetes output a message notifying them that it's not possible without Kubernetes and exit execution.

Related kubernetes/minikube#13461

Backgroud

背景

There are three ways of getting arguments in the client module now, from the properties、from the Jvm arguments and from the system environment. so it needs an unified way that get arguments.

现在总共有3种获取参数的方式在客户端模块中, 有从 properties中获取的、从Jvm参数获取的和从System环境变了中获取的. 所以需要一种统一获取参数的方式.

The reasons are as follows:

• switch arguments getting order
• better mock test

原因如

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.

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

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

The feature ask - expose Dapr runtime version in the Metadata API: https://docs.dapr.io/reference/api/metadata_api/

There are certain scenarios where apps would like to check that they are running within a tested Dapr version.

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

Backdrop:

Around 466 million people worldwide currently have a hearing loss and 34 million of those individuals are children. Hearing loss is increasing every year, and it is estimated that by 2050, over 900 million people will have a hearing loss. Sign language is a natural way of communication for challenged people with speaking and hearing disabilities. There have been

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: