Allen Bai

From my understanding Helm is using the standard `os/exec` library (https://github.com/helm/helm/blob/main/pkg/postrender/exec.go#L46). And within the standard library > The Windows version specified by internally-linked Windows binaries is now Windows 7 rather...

I can reproduce this behavior in v3.7.0: ``` $ helm install issue-10392 . --dry-run Error: INSTALLATION FAILED: values don't meet the specifications of the schema(s) in the following chart(s): gateway:...

Don't think the provided test case will reproduce the original issue, since the issue does not happen all the time (70% of the time sha is identical). Also as pointed...

Thanks for the explanation! I reproduced your `go test` on main without ModTime, found the same result as printed above. Then I went ahead to reproduce the original issue. Unfortunately...

Tested with latest change (ModTime + subchart load order), worked as expected: same hash for each run. Then I was curious to see if only changing the load order will...

Link: https://github.com/zonggen/fcct-online Stack: Vue.js, Flask - [x] Front end that reads URL to autofill the text box - [x] Front end that contains a text box and button to submit...

Discussion thread on deployment location: https://github.com/coreos/fedora-coreos-tracker/issues/260

Hi @kirankumar26, do you always have the TLS handshake error or it's intermittent? Also could you try with `sudo` command? I referred to some possibly related issues: - https://github.com/helm/helm/issues/8172 -...

Did fresh builds on two different machines, and ran `cosa kola switch-kernel` inside the cosa container.. Will try again tomorrow morning to see if it works

So I've updated `src/config` and the error message went away. Though the rpm-ostree commands are now running without issue, `cosa kola switch-kernel` will _sometimes_ fail at the second stage (switching...