Kubernetes

There is a strong and growing consensus in sig-node about the need of increasing the test coverage in the kubelet, improving the current testsuite about coverage and reliability. See for example the April 26 sig-node meeting notes and the [April 27 sig-node CI subgroup meeting notes](http

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

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

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

In what area(s)?

/area runtime

What version of Dapr?

dapr --version
CLI version: 1.7.0
Runtime version: 1.7.0

Expected Behavior

API methods to be logged without any errors

Actual Behavior

When I start my dapr actor host application like this:

dapr run --app-id myapp --app-port 5000 --dapr-http-port 3500 --log-level debug --enable-api-logging -- dotnet run

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

Platform

• version: verdaccio/verdaccio:nightly-master
• platform: docker

Describe the bug
Most of the settings changed in the config.yaml file are not applied.

To Reproduce

web:
  title: "Custom Title" => works
  darkMode: false => works
  showInfo: false => don't works
  showSettings: false => don't works
  showThemeSwitch: false => don't works

It should be more clear for users (and people trying to offer support by looking at logs!) which kube-context and cluster is being used.

$ skaffold dev
Listing files to watch...
 - skaffold-example
Generating tags...
 - skaffold-example -> skaffold-example:v1.34.0-60-gef8185519
Checking cache...
 - skaffold-example: Not found. Building
Starting build...
Building [skaffold-example]...