[WIP] Stab at "platform profiles"

Please provide a description of this PR:
Designed to be a best-effort Helm-level fix for https://github.com/istio/istio/issues/51121
Also (IMO) reduces some profile sprawl.
What this does is introduce a platform for Helm charts, which works pretty much like  compatibilityVersion and keys off the already-used global.platform value. If you --set global.platform=foo we look for a platform-foo.yaml values override.
This can be composed with profiles (and will always override the profile and compatVersion values):
e.g.

helm template manifests/charts/istio-cni --set profile=ambient --set global.platform=k3s
helm template manifests/charts/istio-cni --set profile=ambient --set global.platform=openshift (replacing the current ambient-openshift profile, effectively)

...others to come. This should help make https://istio.io/latest/docs/ambient/install/platform-prerequisites/ less intimidating.
I don't love that we're adding a third kind of magic templates value set, in addition to profiles and compatibilityVersions - but given we are already doing those, this is not a big stretch or that hard, and is probably easier to manage, since the combinatorics work out with normal Helm precedence.
Relevant changes are in

manifests/charts/helm-profiles/
manifests/charts/zzz_profile.yaml

the rest are genfile copies.

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test release-notes

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test release-notes

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test release-notes

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-cni_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

cc @howardjohn @dgn @jewertow for thoughts on this.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test release-notes

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-cni_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-cni

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test release-notes

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-cni_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-cni

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-basic-arm64_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test release-notes

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-cni_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-cni

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-basic-arm64_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-basic-arm64

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test release-notes

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-cni_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-cni

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-basic-arm64_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-basic-arm64

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test release-notes

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-cni_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-cni

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-basic-arm64_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-basic-arm64

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-cni_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-cni

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-basic-arm64_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-basic-arm64

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote-mc

release-notes_istio
7167203f8c326f7476b5a891d8637dc512c1e697
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test lint

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-cni_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-cni

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote-mc

release-notes_istio
7167203f8c326f7476b5a891d8637dc512c1e697
link
true
/test release-notes

integ-basic-arm64_istio
7167203f8c326f7476b5a891d8637dc512c1e697
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-cni_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-cni

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

integ-pilot-istiodremote-mc_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote-mc

release-notes_istio
7167203f8c326f7476b5a891d8637dc512c1e697
link
true
/test release-notes

integ-basic-arm64_istio
7167203f8c326f7476b5a891d8637dc512c1e697
link
true
/test integ-basic-arm64

lint_istio
7167203f8c326f7476b5a891d8637dc512c1e697
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

integ-basic-arm64_istio
7167203f8c326f7476b5a891d8637dc512c1e697
link
true
/test integ-basic-arm64

lint_istio
7167203f8c326f7476b5a891d8637dc512c1e697
link
true
/test lint

release-notes_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-helm

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

integ-basic-arm64_istio
7167203f8c326f7476b5a891d8637dc512c1e697
link
true
/test integ-basic-arm64

release-notes_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test release-notes

lint_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-istiodremote

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

release-notes_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test release-notes

lint_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test lint

integ-helm_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

release-notes_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test release-notes

lint_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test lint

integ-helm_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-helm

integ-pilot-istiodremote_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

+1 to the approach, makes more sense than the duplication we have right now (ambient vs openshift-ambient etc)

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-multicluster_istio
68487aa0acbe7a708ce7693e36d700cc65b814c6
link
true
/test integ-pilot-multicluster

release-notes_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test release-notes

lint_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test lint

integ-helm_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-helm

integ-pilot-istiodremote_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote

integ-cni_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-cni

integ-pilot_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test release-notes

lint_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test lint

integ-helm_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-helm

integ-pilot-istiodremote_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote

integ-cni_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-cni

integ-pilot_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test release-notes

lint_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test lint

integ-helm_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-helm

integ-pilot-istiodremote_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote

integ-cni_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-cni

integ-pilot_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-multicluster

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test lint

integ-helm_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-helm

integ-pilot-istiodremote_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote

integ-cni_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-cni

integ-pilot_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-multicluster

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

release-notes_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-multicluster

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

release-notes_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-multicluster

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

release-notes_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test release-notes

gencheck_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-multicluster

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

release-notes_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test release-notes

gencheck_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test gencheck

integ-ipv6_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-ipv6

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

integ-pilot_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Worth noting - our use of global.platform is a bit inconsistent, but:

It's defined as a global here: https://github.com/istio/istio/blob/master/operator/pkg/apis/values_types.proto#L606 and has been for some time
It makes sense that it should stay a global - it is a value used across several charts, that should not change across charts for a given install.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-multicluster

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

release-notes_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test release-notes

gencheck_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test gencheck

integ-ipv6_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-ipv6

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

integ-pilot_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-pilot-istiodremote

integ-cni_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-cni

integ-helm_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

gencheck_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test gencheck

integ-ipv6_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-ipv6

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

integ-pilot_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-pilot-istiodremote

integ-cni_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-cni

integ-helm_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-helm

release-notes_istio
c0ea88425aa4036a4646205ccb8b48a563710431
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

integ-ipv6_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-ipv6

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

integ-pilot_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-pilot-istiodremote

integ-cni_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-cni

release-notes_istio
c0ea88425aa4036a4646205ccb8b48a563710431
link
true
/test release-notes

integ-helm_istio
c0ea88425aa4036a4646205ccb8b48a563710431
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
2196f0df498f48fd980e2830546732381a746686
link
true
/test integ-pilot-istiodremote-mc

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

integ-ipv6_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-ipv6

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

integ-pilot_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-pilot

integ-pilot-istiodremote_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-pilot-istiodremote

integ-cni_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-cni

release-notes_istio
c0ea88425aa4036a4646205ccb8b48a563710431
link
true
/test release-notes

integ-helm_istio
c0ea88425aa4036a4646205ccb8b48a563710431
link
true
/test integ-helm

lint_istio
c0ea88425aa4036a4646205ccb8b48a563710431
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
efd07460379c87706e7ab3fdedbd1b8c2e4e9dcb
link
true
/test integ-basic-arm64

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

integ-helm_istio
c0ea88425aa4036a4646205ccb8b48a563710431
link
true
/test integ-helm

lint_istio
c0ea88425aa4036a4646205ccb8b48a563710431
link
true
/test lint

release-notes_istio
9b7a52edf700fb5521c7a01731cde96f99258850
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

lint_istio
c0ea88425aa4036a4646205ccb8b48a563710431
link
true
/test lint

release-notes_istio
9b7a52edf700fb5521c7a01731cde96f99258850
link
true
/test release-notes

integ-helm_istio
9b7a52edf700fb5521c7a01731cde96f99258850
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

release-notes_istio
9b7a52edf700fb5521c7a01731cde96f99258850
link
true
/test release-notes

integ-helm_istio
9b7a52edf700fb5521c7a01731cde96f99258850
link
true
/test integ-helm

lint_istio
9b7a52edf700fb5521c7a01731cde96f99258850
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

integ-helm_istio
9b7a52edf700fb5521c7a01731cde96f99258850
link
true
/test integ-helm

lint_istio
9b7a52edf700fb5521c7a01731cde96f99258850
link
true
/test lint

release-notes_istio
d8a6c21b5653b767d9f66c31f256f7e1edb77aac
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-distroless_istio
d514df4e9f0ef002d8ee339eb66be5b0933149ef
link
true
/test integ-distroless

release-notes_istio
d8a6c21b5653b767d9f66c31f256f7e1edb77aac
link
true
/test release-notes

integ-helm_istio
d8a6c21b5653b767d9f66c31f256f7e1edb77aac
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
d8a6c21b5653b767d9f66c31f256f7e1edb77aac
link
true
/test integ-helm

release-notes_istio
e24fe1774b3917cd73bd06ad2bae737ca9b980ab
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
e24fe1774b3917cd73bd06ad2bae737ca9b980ab
link
true
/test release-notes

integ-helm_istio
e24fe1774b3917cd73bd06ad2bae737ca9b980ab
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-helm_istio
e24fe1774b3917cd73bd06ad2bae737ca9b980ab
link
true
/test integ-helm

release-notes_istio
3192bdd0ef8f46e688dfcd1df9ef1fee765d1c79
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bleggett: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
3192bdd0ef8f46e688dfcd1df9ef1fee765d1c79
link
true
/test release-notes

integ-helm_istio
3192bdd0ef8f46e688dfcd1df9ef1fee765d1c79
link
true
/test integ-helm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

This should be RFR.

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
d1dd51d3c2265d31c1fb2ff0415af830e679cb63
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test integ-basic-arm64

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
44f4d56b2fce42e305b242615046930d9634e11f
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test integ-basic-arm64

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
44f4d56b2fce42e305b242615046930d9634e11f
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test integ-basic-arm64

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
44f4d56b2fce42e305b242615046930d9634e11f
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.


Add support for mzML

Dear @qinchunyuan can you added support for mzML files as input.

@ypriverol
Thanks for your comment, "support for mzML" is  done


feat(TSSdk): support OTEL

Follow-up on https://github.com/dagger/dagger/pull/6835
Support Open Telemetry Traces on the TypeScript SDK

Expose a new functions in the SDK named withTracer to create custom spans on the Dagger Cloud UI
Add open telemetry support in the TypeScript SDK, everything is exported to the local engine collector.
Update GraphQL connection to be in the OTLP context.
Update GrahpQL request header to include the traceparent identifier
Update runtime to include @dagger.io/dagger/telemetry dependency

Example
import { dag, Container, Directory, object, func } from<EMAIL_ADDRESS>import { withTracer } from<EMAIL_ADDRESS>
@object()
class Trace {
  /**
   * Returns a container that echoes whatever string argument is provided
   */
  @func()
  containerEcho(stringArg: string): Container {
    return dag.container().from("alpine:latest").withExec(["echo", stringArg])
  }

  @func()
  trace(name: string): Promise<string> {
    return withTracer(name, async () => {
     return this.containerEcho("test").stdout()
    })
  }
}

dagger call trace --name "example"
test

On dagger cloud, the execution will be nested inside a custom span name example:

⚠ The traces are not sent to dagger cloud, I need to investigate to understand why

Doesn't seem like you're injecting the context into the HTTP header for the API calls.

I'm currently stuck by https://github.com/open-telemetry/opentelemetry-js/commit/34387774caaa15307e8586206f1ca2e6df96605f that need to be released in order to complete the OTPL implementation.
I'm still trying to find a workaround, the issue is that data are sent with the sdk is shutdown, but the current shutdown method for the GRPC exporter is broken :D
So we do not send anything.
The nice workaround would be to send data in real time (I need to find the way though)

The PR has no integration tests but I manually tested.
@vito @helderco Do you have any idea how I can tests that?

It seems there's an issue with Bun regarding the hooks, I'm confused
/cc @benjaminstrasser

Discussed this 1:1 sync with @TomChv. In the interest of unblocking this due to CI failures:

Can this be tested on 0.10.3?
Does this pass on runs-on: dagger-v0.11.0?
What about runs-on: dagger-v0.10.3?

cc @matipan since I know he is looking into this too.

@vito @helderco Do you have any idea how I can tests that?

Unfortunately manual testing is the state of the art at the moment. Would love to think more about this though. Open to ideas!

It seems there's an issue with Bun regarding the hooks, I'm confused
/cc @benjaminstrasser

Ah! See this comment:

https://github.com/dagger/dagger/pull/7074#discussion_r1566217419

It seems there's an issue with Bun regarding the hooks, I'm confused
/cc @benjaminstrasser

I'll be happy to help, but would need some more context. I am currently unable to reproduce locally. The earliest I can look into this a bit more is Thursday.

@helderco @benjaminstrasser I did some update that may fix the Bun issue, I'm waiting for the CI

I have a weird error here

I can reproduce the error locally with dagger call test test --test-regex="TestDaggerRun"
    multi.go:85:       ✘ Container.from(address: "alpine:3.18.2"): Container! 1m0.0s
    multi.go:85:       ! failed to resolve source metadata for docker.io/library/alpine:3.18.2: failed to do request: Head "https://mirror.gcr.io/v2/library/alpine/manifests/3.18.2?ns=docker.io": dial tcp: lookup mirror.gcr.io: i/o timeout
    multi.go:85:         ✘ remotes.docker.resolver.HTTPRequest 30.0s
    multi.go:85:         ! dial tcp: lookup mirror.gcr.io: i/o timeout
    multi.go:85:           ✘ HTTP HEAD 30.0s
    multi.go:85:           ! dial tcp: lookup mirror.gcr.io: i/o timeout
    multi.go:85:         ✘ remotes.docker.resolver.HTTPRequest 30.0s
    multi.go:85:         ! dial tcp: lookup registry-1.docker.io: i/o timeout
    multi.go:85:           ✘ HTTP HEAD 30.0s
    multi.go:85:           ! dial tcp: lookup registry-1.docker.io: i/o timeout

but I do not understand it

The PR has no integration tests but I manually tested.
@vito @helderco Do you have any idea how I can tests that?

I suspect you can use the console exporter in tests and check the output.

I can reproduce the error locally with dagger call test test --test-regex="TestDaggerRun"

This should be fixed after a rebase thanks to #7138

@helderco I added all your comment, I think this PR is ready for a last review before a merge 🚀
As a follow up, I'll add a piece of documentation

@helderco I think I completed the changes that you asked, feel free to review anytime :D


Mmoitems support doesn't work after reload

Hello, I'm using bossshoppro and mmoitems. I have created my shop with instruction provided on MMoitems wiki (https://gitlab.com/phoenix-dvpmt/mmoitems/-/wikis/Supported Plugins#bossshoppro).  Buying MMoitems works ONLY after server restart, after using /bossshoppro reload command buying  mmoitems doesn't work anymore - I'm only losing money not getting any item.
Shop config:
shop:
  1:
    PriceType: money
    Price: 15
    RewardType: MMOITEM
    Reward:
    - SWORD.WOODEN_SWORD
    InventoryLocation: 22

Version: bossshoppro-2.1.0-20230422.101939-23
Server version: purpur 1.19.4
No erros in console.
Same issue on both spigot and paper

I had our developers look into this and they determined that the compatibility is not in our plugin. This compatibility would be in the mmoitems plugin. Make sure you talk to an actual mmoitems dev about this issue.


Per Container Metrics not availble

Hi team,
We weren't able to view the per container metrics through Vector. Do we need to install any modules inside the container to get those metrics. We could see only the Total Container Memory usage not per container measures.
Our current installation has pcp installed on the host system and configured pmwebd as a simple HTTP file server, in order to server Vector itself to a web browser. Could you please review and let us know.
Vector Version: v1.1.0-3-gc851eac
Thanks
Sattish.

@sattishv can you give us more details? You have no data in the per-container widgets?

Hi Martin,
Thanks for the response. Yes, when we open Per container graphs it displays "No Data Available"
Sattish.

Can you share your request/response from the _fetch request that is happening in the background?
Also, do you get a list of container Ids? Or is it just showing All?

I am not sure on how to get the req/res will search for the _fetch request and let u know, we dont get the container ids its shows only ALL

If you're on Chrome, just open the developer console and go to the Network tab.

Hi ,
I could see series of fetch requests. Have listed the request headers for one of the request.Let me know if you any other details
GET /pmapi/1921743143/_fetch?names=containers.cgroup,containers.name,kernel.all.cpu.sys,kernel.all.cpu.user,hinv.ncpu,kernel.percpu.cpu.sys,kernel.percpu.cpu.user,kernel.all.runnable,kernel.all.load,network.interface.in.bytes,network.interface.out.bytes,network.tcpconn.established,network.tcpconn.time_wait,network.tcpconn.close_wait,network.interface.in.packets,network.interface.out.packets,network.tcp.retranssegs,network.tcp.timeouts,network.tcp.listendrops,network.tcp.fastretrans,network.tcp.slowstartretrans,network.tcp.syncretrans,mem.util.cached,mem.util.used,mem.util.free,mem.util.bufmem,mem.vmstat.pgfault,mem.vmstat.pgmajfault,kernel.all.pswitch,disk.dev.read,disk.dev.write,disk.dev.read_bytes,disk.dev.write_bytes,disk.dev.avactive,disk.dev.read_rawactive,disk.dev.write_rawactive,cgroup.cpuacct.usage,cgroup.blkio.all.throttle.io_serviced.read,cgroup.blkio.all.throttle.io_serviced.write,cgroup.memory.usage,cgroup.cpusched.shares,cgroup.cpusched.periods HTTP/1.1
Host: <IP_ADDRESS>:44329
Connection: keep-alive
Accept: application/json, text/plain, /
Origin: http://kncntusrstage14007.qa.paypal.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Referer: http://kncntusrstage14007.qa.paypal.com/index.html
Accept-Encoding: gzip, deflate, sdch
Accept-Language: en-US,en;q=0.8

The response is what I mostly interested in.

Hi
Sorry for the discommode. here is the response
{"timestamp":{"s":1471562912,"us":736254 }, "values":[{"pmid":251658262,"name":"kernel.all.cpu.sys","instances":[
{"instance":-1, "value":39399360 }]},
{"pmid":251658260,"name":"kernel.all.cpu.user","instances":[
{"instance":-1, "value":141824400 }]},
{"pmid":251658272,"name":"hinv.ncpu","instances":[
{"instance":-1, "value":2 }]},
{"pmid":251658242,"name":"kernel.percpu.cpu.sys","instances":[
{"instance":0, "value":19222780 },{"instance":1, "value":20176580 }]},
{"pmid":251658240,"name":"kernel.percpu.cpu.user","instances":[
{"instance":0, "value":67092550 },{"instance":1, "value":74731850 }]},
{"pmid":251660290,"name":"kernel.all.runnable","instances":[
{"instance":-1, "value":3 }]},
{"pmid":251660288,"name":"kernel.all.load","instances":[
{"instance":1, "value":0.029999999 },{"instance":5, "value":0.15000001 },{"instance":15, "value":0.13 }]},
{"pmid":251661312,"name":"network.interface.in.bytes","instances":[
{"instance":0, "value":15597289897 },{"instance":1, "value":36222246 },{"instance":2, "value":0 },{"instance":3, "value":1281572765 },{"instance":4, "value":8712 },{"instance":8, "value":648 },{"instance":9, "value":648 }]},
{"pmid":251661320,"name":"network.interface.out.bytes","instances":[
{"instance":0, "value":126577123534 },{"instance":1, "value":88277811 },{"instance":2, "value":0 },{"instance":3, "value":1281572765 },{"instance":4, "value":418 },{"instance":8, "value":1296 },{"instance":9, "value":648 }]},
{"pmid":251677697,"name":"network.tcpconn.established","instances":[
{"instance":-1, "value":29 }]},
{"pmid":251677702,"name":"network.tcpconn.time_wait","instances":[
{"instance":-1, "value":6 }]},
{"pmid":251677704,"name":"network.tcpconn.close_wait","instances":[
{"instance":-1, "value":0 }]},
{"pmid":251661313,"name":"network.interface.in.packets","instances":[
{"instance":0, "value":60195928 },{"instance":1, "value":357347 },{"instance":2, "value":0 },{"instance":3, "value":4499088 },{"instance":4, "value":120 },{"instance":8, "value":8 },{"instance":9, "value":8 }]},
{"pmid":251661321,"name":"network.interface.out.packets","instances":[
{"instance":0, "value":43733344 },{"instance":1, "value":365570 },{"instance":2, "value":0 },{"instance":3, "value":4499088 },{"instance":4, "value":5 },{"instance":8, "value":16 },{"instance":9, "value":8 }]},
{"pmid":251672637,"name":"network.tcp.retranssegs","instances":[
{"instance":-1, "value":98747 }]},
{"pmid":251712576,"name":"network.tcp.timeouts","instances":[
{"instance":-1, "value":425 }]},
{"pmid":251712549,"name":"network.tcp.listendrops","instances":[
{"instance":-1, "value":0 }]},
{"pmid":251712573,"name":"network.tcp.fastretrans","instances":[
{"instance":-1, "value":2894 }]},
{"pmid":251712575,"name":"network.tcp.slowstartretrans","instances":[
{"instance":-1, "value":7 }]},
{"pmid":251659269,"name":"mem.util.cached","instances":[
{"instance":-1, "value":2539400 }]},
{"pmid":251659265,"name":"mem.util.used","instances":[
{"instance":-1, "value":6033700 }]},
{"pmid":251659266,"name":"mem.util.free","instances":[
{"instance":-1, "value":78016 }]},
{"pmid":251659268,"name":"mem.util.bufmem","instances":[
{"instance":-1, "value":328576 }]},
{"pmid":251686928,"name":"mem.vmstat.pgfault","instances":[
{"instance":-1, "value":276208928 }]},
{"pmid":251686929,"name":"mem.vmstat.pgmajfault","instances":[
{"instance":-1, "value":1318888 }]},
{"pmid":251658253,"name":"kernel.all.pswitch","instances":[
{"instance":-1, "value":4368607612 }]},
{"pmid":251658244,"name":"disk.dev.read","instances":[
{"instance":0, "value":3063571 },{"instance":1, "value":497 }]},
{"pmid":251658245,"name":"disk.dev.write","instances":[
{"instance":0, "value":3248261 },{"instance":1, "value":6 }]},
{"pmid":251658278,"name":"disk.dev.read_bytes","instances":[
{"instance":0, "value":157252197 },{"instance":1, "value":1594 }]},
{"pmid":251658279,"name":"disk.dev.write_bytes","instances":[
{"instance":0, "value":62260780 },{"instance":1, "value":3 }]},
{"pmid":251658286,"name":"disk.dev.avactive","instances":[
{"instance":0, "value":2464272 },{"instance":1, "value":112 }]},
{"pmid":251658312,"name":"disk.dev.read_rawactive","instances":[
{"instance":0, "value":3202892 },{"instance":1, "value":128 }]},
{"pmid":251658313,"name":"disk.dev.write_rawactive","instances":[
{"instance":0, "value":54306280 },{"instance":1, "value":8 }]},
{"pmid":12624898,"name":"cgroup.cpuacct.usage","instances":[
{"instance":0, "value":205983596699473 },{"instance":1, "value":26733384299102 },{"instance":2, "value":1342501118123 },{"instance":3, "value":660633885282 },{"instance":4, "value":141215345760 },{"instance":5, "value":5998524552659 },{"instance":6, "value":5954871455884 },{"instance":7, "value":18581909680859 },{"instance":8, "value":18581909680859 },{"instance":9, "value":473958848 },{"instance":11, "value":169476234138533 },{"instance":12, "value":61796315764 },{"instance":13, "value":278563648438 },{"instance":14, "value":5522839869875 },{"instance":15, "value":2138633348232 },{"instance":18, "value":76733959948 },{"instance":19, "value":71566233338 },{"instance":20, "value":25059257554 },{"instance":21, "value":12404619580 },{"instance":22, "value":473958848 }]},
{"pmid":12629072,"name":"cgroup.memory.usage","instances":[
{"instance":0, "value":4832018432 },{"instance":1, "value":0 },{"instance":2, "value":0 },{"instance":3, "value":977965056 },{"instance":4, "value":8065024 },{"instance":5, "value":0 },{"instance":6, "value":301592576 },{"instance":7, "value":0 },{"instance":8, "value":103653376 },{"instance":9, "value":0 },{"instance":11, "value":0 },{"instance":12, "value":195485696 },{"instance":13, "value":0 },{"instance":14, "value":2359296 },{"instance":15, "value":12574720 },{"instance":16, "value":83804160 },{"instance":17, "value":69337088 },{"instance":18, "value":37167104 },{"instance":19, "value":1299599360 },{"instance":20, "value":8192 }]}]}
Thanks
Sattish

It looks like the response is missing containers.cgroup and containers.name, so Vector is filtering out all containers because they are not on the container list. The list is empty because no Ids are being returned.
Something might have changed in the latest Docker version. I'll double-check and ping PCP if necessary.

According to @sattishv
# pminfo --fetch containers.name containers.state.running

containers.name
Error: Unknown or illegal instance identifier

Since Vector checks if a container is in that list before adding it to the graphs, (ContainerMetadataService.containerIdExist(instance.key)), that's likely the issue.
@natoscott Looks like a similar issue to the one we had migrating from 1.9 to 1.10. Should I open a issue for PCP?

Hi Martin,
Were you able to get any update from PCP team on this.
Sattish.

Just checked with docker v1.12 here, what version of PCP is being used on that host?

1.11.2-cs3 according to Sattish.

Martin

On Thu, Aug 25, 2016 at 9:23 AM, Lukas Berk<EMAIL_ADDRESS>wrote:

Just checked with docker v1.12 here, what version of PCP is being used on
that host?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Netflix/vector/issues/135#issuecomment-242450306, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACGut9BcUhr-703WEn6R8gXnyaXhGmGoks5qjcGKgaJpZM4Jn-ja
.

@spiermar I'm not familiar with PCP version 1.11.2-cs3 however the config.v2.json fix that you were alluding to earlier is in pcp-3.11.2 and later.

I mean Docker 1.11.

Martin

On Thu, Aug 25, 2016 at 10:43 AM, Lukas Berk<EMAIL_ADDRESS>wrote:

@spiermar https://github.com/spiermar I'm not familiar with PCP version
1.11.2-cs3 however the config.v2.json fix that you were alluding to earlier
is in pcp-3.11.2 and later.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Netflix/vector/issues/135#issuecomment-242477724, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACGut1v4F7cjO1-Tg4yT9tathMpOCAGpks5qjdQwgaJpZM4Jn-ja
.

@sattishv, @lberk tested the latest Docker version and it's working with the current release of PCP. Can you confirm you're running PCP 3.11.2 or newer?

Hi martin,
Sure will check and let you know soon
Thanks
Sattish.
On Tue, Aug 30, 2016 at 9:26 AM, Martin Spier<EMAIL_ADDRESS>wrote:

@sattishv https://github.com/sattishv, @lberk https://github.com/lberk
tested the latest Docker version and it's working with the current release
of PCP. Can you confirm you're running PCP 3.11.2 or newer?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Netflix/vector/issues/135#issuecomment-243497082, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHGqmTbNrbBOaXRMHII1H8QtVMZD_e1uks5qlFmagaJpZM4Jn-ja
.

--
with regards,
Sattish
9940080070

Assuming this was solved. Closing the issue.


Add REFRESH MATERIALIZED VIEW syntax

Before we add any language support, I'd like to understand how this is going to work. There's no notion of materialized views in the Presto engine, and if it's going to be a connector-specific concept, we may want to model this as callable functions instead of having dedicated syntax.
FWIW, this is not standard syntax, either.
In the long term, I'd like materialization of a view to be an optimization based on cpu/space tradeoffs and knowledge of dependencies and latency requirements (e.g., a query over a view needs to finish before a given time, so the engine chooses to materialize portions to satisfy that requirement).

We could do this for now as stored procedure calls.

We could do this for now as stored procedure calls.

:+1:

Closing. Opened https://github.com/prestodb/presto/pull/5237 instead.


[Schale] zh_cn_cn and zh_cn_tw data should be maintained manually

As is known, SchaleDB has a complete database for zh_cn support, which in fact falls in our so-called "zh_cn_jp" category that indicates it's a fan translation from the JP Server.
For Chinese (Simplified) however, there's more than one variant avalibale for BA players. They are:

zh_cn_cn The offcial CN server translation
zh_cn_jp The fan translation from JP server.
zh_cn_tw The official Chinese (Traditinal) translation but converted to Chinese (Simplified) version.

Given the situation that we have no exisiting databases for the other two varients, we think it is necessary to maintain the two manually.
We planned to:

Auto update the zh_cn_jp data.
Auto translate zh_tw data to zh_cn_tw data.
Manually maintain zh_cn_cn data.

This should give us a better localized expereince.

更新：SchaleDB已经将国服和先前的日服玩家翻译版数据隔离并单独成为语言选项。目前发现国服翻译会自动fallback到日服翻译，行为逻辑与项目相同，可直接转换。


Encoder.swift fatal error with image2image (possible .mlmodelc compatibility breaks)

When I try image2image with ready-made Core ML models, it throws the following error.
StableDiffusion/Encoder.swift:96: Fatal error: Unexpectedly found nil while unwrapping an Optional value

You can reproduce this issue with the following steps:

Download coreml-stable-diffusion-2-base.
Create a 512x512 input image.
swift run StableDiffusionSample --resource-path <resource dir> --image <input image> "test"

It doesn’t reproduce when I reconvert the model using the latest version of torch2coreml.
I also confirmed that it doesn’t reproduce when I revert the changes in https://github.com/apple/ml-stable-diffusion/commit/1147e87b790895feeddc1b146c8fddf6f8b9f8a5

Thanks for the report and good catch!  We will need to update the VAEEncoder.mlmodelc files on Hugging Face. cc: @pcuenca

Looking into it. Thanks, I didn't realize the encoder inputs had changed.

Submitted these PRs after converting the VAE encoder again:
https://huggingface.co/apple/coreml-stable-diffusion-v1-4/discussions/4/files
https://huggingface.co/apple/coreml-stable-diffusion-v1-5/discussions/5/files
https://huggingface.co/apple/coreml-stable-diffusion-2-base/discussions/6/files
https://huggingface.co/apple/coreml-stable-diffusion-2-1-base/discussions/2/files
Tested locally with this script:
declare -a repos=(
    coreml-stable-diffusion-v1-4
    coreml-stable-diffusion-v1-5
    coreml-stable-diffusion-2-base
    coreml-stable-diffusion-2-1-base
)

for repo in "${repos[@]}"
do
    for variant in "original" "split_einsum"
    do
        units="cpuAndNeuralEngine"
        if [ "$variant" == "original" ]
        then
            units="cpuAndGPU"
        fi
        echo swift run StableDiffusionSample --compute-units $units --resource-path models/apple/$repo/$variant/compiled --image image.jpg "test"
        swift run StableDiffusionSample --compute-units $units --resource-path models/apple/$repo/$variant/compiled --image image.jpg "test"
        echo
    done
done

I updated the .mlpackage directories too, but the Python inference script does not seem to have a way to test image-to-image yet.

@pcuenca Thank you very much!

@keijiro Could you please verify that the issue is not longer present for you as well?

I ran the following shell script with the updated models in those PRs, and verified that it works correctly.
swift run StableDiffusionSample --resource-path models/coreml-stable-diffusion-v1-4/original/compiled         --compute-units cpuAndGPU          --image source.png --strength 0.9 "painting of a cat"
swift run StableDiffusionSample --resource-path models/coreml-stable-diffusion-v1-4/split_einsum/compiled     --compute-units cpuAndNeuralEngine --image source.png --strength 0.9 "painting of a cat"
swift run StableDiffusionSample --resource-path models/coreml-stable-diffusion-v1-5/original/compiled         --compute-units cpuAndGPU          --image source.png --strength 0.9 "painting of a cat"
swift run StableDiffusionSample --resource-path models/coreml-stable-diffusion-v1-5/split_einsum/compiled     --compute-units cpuAndNeuralEngine --image source.png --strength 0.9 "painting of a cat"
swift run StableDiffusionSample --resource-path models/coreml-stable-diffusion-2-base/original/compiled       --compute-units cpuAndGPU          --image source.png --strength 0.9 "painting of a cat"
swift run StableDiffusionSample --resource-path models/coreml-stable-diffusion-2-base/split_einsum/compiled   --compute-units cpuAndNeuralEngine --image source.png --strength 0.9 "painting of a cat"
swift run StableDiffusionSample --resource-path models/coreml-stable-diffusion-2-1-base/original/compiled     --compute-units cpuAndGPU          --image source.png --strength 0.9 "painting of a cat"
swift run StableDiffusionSample --resource-path models/coreml-stable-diffusion-2-1-base/split_einsum/compiled --compute-units cpuAndNeuralEngine --image source.png --strength 0.9 "painting of a cat"

Thanks!

Thanks for the confirmation @keijiro! I just merged those PRs so I think this issue can be closed now :)

Thanks for the report and the fix both!


Azure pipeline first setup

First setup of Azure pipeline for running tests and building the binary.

I meant that you can do something like this as well I guess:
    - bash: "make go_build"
      displayName: Go build

But no big deal, we can keep the script as well.

Ahhhh ... You "we need" had the meaning of the opposite direction, I misunderstood. I agree, let's remove it for now, I was just following the scripts usage in drain cleaner for example. In this case it's pretty straightforward and simple.


"can't downgrade" is seen in the k8s version dropdown of a nodegroup in EKS cluster

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Deploy a hosted EKS cluster with k8s 1.15
After the cluster is deployed successfully, From the EKS console update the k8s version of the cluster to 1.16
The cluster upgrades to 1.16 in Rancher
Edit cluster
The nodegroups are in 1.15
The nodegroups are in 1.15 k8s version and show in the dropdown can't downgrade

Expected Result:
can't downgrade should NOT be shown for 1.15 k8s version as it is the one the nodegroup is currently on
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - commit id: 33f755f18
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Hosted EKS
Kubernetes version (use kubectl version):

1.15

The UX now does not allow the user to specify a specific version for upgrade. We are now more in line with how aws does it and the user is only presented with an option to upgrade when the node version is behind the cluster. And then you can only match the cluster version.

On master-head - commit id: c983bb ui tag: latest2

Deploy a hosted EKS cluster with k8s 1.15
After the cluster is deployed successfully, From the EKS console update the k8s version of the cluster to 1.16
The cluster upgrades to 1.16 in Rancher
Edit cluster --> User is not given multiple options to upgrade nodegroup's k8s version


SNI RESET

I have found some open source projects that can avoid SNI RESET, which are suitable for HTTPS websites.
GoodbyeDPI can avoid the SNI RESET of the HTTP protocol, but cannot do anything about the SNI RESET of the HTTPS protocol ( this is the case in China )
If Russia's network firewall starts the same SNI RESET, you can try them or integrate them into GoodbyeDPI.
https://github.com/URenko/Accesser
https://github.com/Macronut/SNI-Mask

In China, you can't just ignore TCP RST packets with blacklisted SNI, you need to do additional tricks to forge the packet as it's not a TLS ClientHello.

@ValdikSS so is that a China issue or what?


ceph-osd: fix typo in containerized OSD systemd unit

Signed-off-by: Andrew Schoen<EMAIL_ADDRESS>

jenkins test this please

jenkins test this please


Use CFPropertyList 2.0.1

CFPropertyList 2.0.1 changes the DTD on generated manifests to <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> and matches the DTD on manifests generated with Munki 2's manifestutil.

I'm assuming this has been tested fully on your end? I'm all for merging the code, but I no longer have any way to test functionality.

Yes. I have tested this extensively, running the enroll script on multiple machines in both development and production environments, including on machines with a client specific manifest that was previously generated with Munki Enroll.

Thanks for the confirmation and thank you for your work. I've merged it into the main branch.


Upgrade browserify to latest version

@puleos any change you could review this, and the other PRs? You can also give me merge rights, and I will leave the non-trivial stuff out for a proper review. Let me know what you prefer.

Thanks!


[Feature Request] can you prevent the close button from quitting the app?

to be more consistent with Spotify and other mac apps, can you prevent the close button from actually quitting the app?
so if I press Cmd-W (the standard close tab shortcut), it would close the current Saavn window but continue playing the song
if I press Cmd-Q, it actually quicks Saavn

also, thanks a bunch for making this!

I haven't updated the download link with the new build. For now, compiling it yourself should work. Let me know if you need me to update it, will do it later.

thanks for the quick turn around! will try it out

I think that Cmd-W should hide the app similar to Spotify. Currently its a noop.

Pressing the "X" button hides the app properly.
Pressing Cmd-H or Cmd-M also does not hide or minimize the application.

I also noticed while typing my password incorrectly, in an attempt to delete it and try again, Cmd-A didn't work to select all text in the input box. This is the window I'm referring to:

happy to look into this stuff if you point me in the right direction

I've not noticed this, nice catch! Seems like this is a gotcha with electron as described here.

This link seems more thorough.


Finalize CSS naming convention and architecture

@holly-johnson and I have discussed using BEMIT, based on BEM and ITCSS, but we've yet to fully commit to any one methodology.
Do we adopt the Hungarian notation-like used in the aforementioned BEMIT article?
Two dashes or one after the framework ('dcf' or whatever else we choose to call it) and institution (presumably 'unk', 'unl', 'unmc', 'unca') namespaces? I think @Shaderpixel (Richard Lock, here at UNL) is in favor of two dashes. I go back and forth.
In other words, which do you prefer for the 'display: grid' utility class:

dcf-d-grid
dcf--d-grid
dcf-u-d-grid ('u' for 'utility' class)
dcf--u-d-grid

If adopting the Hungarian notation, would it be helpful if the next fragment of the class name was restricted to not using another single letter (e.g. '…u-d-grid' vs '…u-disp-grid')?

@holly-johnson stopped by today and we discussed some architectural changes. We've moved theme files to a sibling directory of core. The theme directory structure now more closely matches the ITCSS-like structure of the core directory. #19

I'll go ahead and rephrase my question as a suggestion: if we do adopt the Hungarian notation to indicate class intent, the fragment that follows must not be another single letter to avoid confusion.
How would this change existing classes?
For display (none, block, inline, inline-block, flex, inline-flex, grid, inline-grid, subgrid, table), we could simply remove the d.  However, how do we distinguish between styling a table (.dcf--table) vs merely setting the display of an element as a table (display: table;)? Is that a distinction that needs to be made? I think most of the actual table styling occurs in the children elements (th, td, etc). In our meeting this morning, @ptryno also wondered if dcf--none was obvious enough to indicate display: none;. While there are other properties (borders, for example) that could use the value none, I don't know if any of them would warrant such a name. In other words, I think the weight of the name matches the gravity of the property. Or, do we use a fragment like disp- or even display-? I certainly prefer the simplicity of a name like dcf--block if we could find solutions for table and agreement around none.
For grid and flexbox, we could modify the g- and f-, respectively, to grid- and flex-. I also think we can remove flexbox and grid qualifiers for alignment and justification utilities. Because some of these properties are used for both, we can remove duplicate rules and save some file size. Any properties specific to either grid or flexbox simply won't work when applied to the wrong display.

I think we need a utility class for overflow: hidden;. I haven't been able to think of anything better than dcf--overflow-hidden or dcf--u-overflow-hidden. Something more succinct or is this ok?

Commenting on the prefix naming convention:
Submit VS
Submit
Trying to compare the two, I find that the former feels more difficult to scan given that the double dashes creates an extra cognitive effort to process the extended length of the class names and my eyes focuses more on the extra dashes than the actual class name as a whole. Also, when we do use the modifiers specified in BEM, dcf--c-btn--red or even dcf--c-card__child--promo-item feels cumbersome to look at, more so when we have a chain of classnames. So after giving some more thought, I kinda lean back towards single dashes as it feels more natural. Besides if we all follow the same prefix, I have a feeling our eyes will automatically pick out the common prefixes for the DCF framework and campus themes without relying on the double dashes. Also, the Hungarian notation namespaces that follow after the prefix helps with readability. (Note, @skoolbus39 and I looked at Salesforce's Lightning design system and they use single dash for their prefix.)
As for the Hungarian notation-like namespaces, I lean heavily towards using them. To me they help with identifying the purpose of each classes in the HTML without having the need to go into the style sheet to see what they do and whether with confidence they can be modified or overwritten. This article pretty much sums up all the benefits of using them.
@skoolbus39 per your question regarding the next fragment following the type namespace I will try to do more research and see if any recommendations/usage recommendations from other organizations out there and comment on that hopefully next week.

Examples of design systems using a namespace prefix with a single dash:
https://lightningdesignsystem.com/utilities/alignment/
https://design.cms.gov/utilities/

I could still be persuaded otherwise, but after more thought, like @Shaderpixel, I'm leaning toward: .dcf-u-[value]. Thoughts on single dash vs. double dashes vs. underscores for modifiers?
Where possible, for the sake of brevity, I prefer class names where the values themselves convey the intent of the property. Position properties (e.g. .dcf-u-absolute, .dcf-u-relative) work well because the values aren't used by other properties. Of course, this won't work for all classes.
Potential class names:

Visibility:

.dcf-u-invisible, .dcf-u-hidden, .dcf-u-visibility-hidden, .dcf-u-vis-hidden
.dcf-u-sr-only vs .dcf-u-visibility-screen-reader or .dcf-u-vis-screen-reader

Display: .dcf-u-[value] (would need to address the aforementioned issues for none and table), .dcf-u-disp-[value], .dcf-u-display-[value]
Flexbox:

I like these: .dcf-u-flex-col, .dcf-u-flex-col-rev, .dcf-u-flex-row, .dcf-u-flex-row-rev, .dcf-u-flex-wrap, .dcf-u-flex-wrap-rev, .dcf-u-flex-nowrap
…but am unsure about class names for flex order: .dcf-u-flex-o#, .dcf-u-flex-order#, .dcf-u-flex-no#, where # could be 1–9?

Box Alignment (for both flexbox and grid): .dcf-u-justify-content-[value] (seems long) or abbreviate .dcf-u-jc-[value]
Font Sizes: .dcf-u-lg#, .dcf-u-sm#. @Shaderpixel mentioned that 'lg' and 'sm' left him wondering where 'md' was. These classes should increase or decrease an element's font-size incrementally larger or smaller than the base font-size. Is there a better way to convey 'larger' and 'smaller'? 'plus' and 'minus'? 'incr' and 'decr'?
Line Height: .dcf-u-lh#, .dcf-u-line#, .dcf-u-line-height-# or instead of using numbers define with terms like 'compact', 'cozy', 'tight', 'loose', etc?
Horizontal Text Alignment: .dcf-u-text-[value] (my preference), .dcf-u-text-align-[value]
Vertical Text Alignment: .dcf-u-vertical-[value], .dcf-u-valign-[value], .dcf-u-text-[value]. I like the latter as it describes that text is being aligned, while the values themselves convey direction. However, I worry about potential for confusion using .dcf-u-text-top for vertical-align: top; and .dcf-u-text-text-top for vertical-align: text-top;). Is this an instance where double dashes or underscores for modifiers would add clarity?
Letter Spacing: dcf-u-ls#, dcf-u-letter#, dcf-u-spacing#, dcf-u-track#, dcf-u-tracking#

Are there other possibilities I'm not seeing?

Double dashes for modifiers are good with me, so is double underscores for block child elements (BEM). Its just that when seeing double dashes on both ends of a class name (when a modifier is present) throws me off when trying to scan. class="dcf--c-btn--red dcf--c-card--promo". Will weigh in on class names soon.

I like the idea of using either a double dash or an underscore for modifiers. I think your .dcf-u-text-text-top example is a good one. Trying to decide which I like better though.
class="dcf-u-text--text-top dcf-c-card--promo dcf-c-btn--red"
class="dcf-u-text_text-top dcf-c-card_promo dcf-c-btn_red"
For class names, I personally like clarity over brevity where it makes sense. Im thinking of all the other devs we have on campus that may be using this sometime down the road. A good example would be with font sizes. What do you think about .dcf-u-font-incr# .dcf-u-font-decr#? I just wonder if something like .dcf-u-incr# is enough?
I'll continue looking at it and try to add more input later.


Determinations on new CEs from collecting event take time to show up

Describe the bug
Determinations on new CEs from collecting event take time to show up
To Reproduce
Steps to reproduce the behavior:

When I use the "Add/Current" button to create new specimens from a collecting event
Then I add determinations
And I wait for the COs to be created
The COs are created and visible but the determinations do not show up immediately.

All of these COs should have determinations

"Coleoptera 4" with determination visible in annotator, but not CO table:

Expected behavior
Should see create determinations immediately for real-time validation.
Environment (please identify where you experience this bug:
*** One of ***

Sandbox - Sandworm
Chrome

We confirmed this is an issue with the dwc indexing (we're using dwc index as fields for the descriptor).

We confirmed this is an issue with the dwc indexing (we're using dwc index as fields for the descriptor).

@jlpereira do we need to catch this with spinners maybe?  Feel like this is the live-page update stuff we were thinking about doing down the road.


UAVCAN : Correct startup sequence and improve parameter description

This allows UAVCAN sensors to be used in static-allocation mode (no dynamic node ID allocation and no firmware update), which reduces memory usage significantly.

Tested with Zubax GNSS.


Collect warnings and print at the end of freezing process

Fix #277

First part should be done, maybe add some tests.
I have to think about: It should also have a way to filter out warnings or treat them as errors. This part is not implemented yet.

Please also test the Freezer.warnings list, and the behavior with more than one warning.

Please also test the Freezer.warnings list, and the behavior with more than one warning.

Completed :rocket:


add azure drivers

@cjellick @ibuildthecloud @will-chan

For the record, we are holding off on azure for now. do not merge.


Move public revenue and expenses in-house

Currently, the public revenue and expenses live on Notion. I'd love to move these three tables and rendering into the codebase.

Ideally, we don't have to calculate anything manually. So the few SUM columns should be done in Ruby (or the database). Quickly sketching this out, we could have a few YAML files that get read in and spit out into nice looking HTML styled with Tailwind UI. The Simple striped table looks perfect for this use case.

If you want to want to work on this but don't have access to Tailwind UI then feel free to open a PR with an un-styled table and I can finish it up.

This is a great first issue for someone to pick up because you don't need to know a lot about the existing codebase to get started.

@joemasilotti I would like to give it a try if possible 🙂

Sure thing! It's all yours :)

Closed via #270.


Using Cas instead of CAS #14341

Objective

Replacing CAS with Cas in CASPlugin
Closes #14341

Solution

Simple replace

this doesn't close #14341, there are other types using CAS instead of Cas: found DenoiseCAS, CASUniform, CASNode, CASPipeline, CASPipelineKey, ViewCASPipeline with a quick search.
Could you also change those?


No /*# sourceMappingURL=utility.min.css.map */ present

We forget utility.min.css.map and vite return error

Thanks for your feedback! We will fix that soon.

We have fixed the issue. Please install version 2.0.4. Thanks for your feedback again.