injection-template sidecar add volumes

After adding volumes and volumeMounts to istio-1.13.3/manifests/charts/istio-control/istio-discovery/files/injection-template.yaml , sidecar failed to be injected.

istiod log:
2022-10-25T12:32:23.349307Z	debug	AdmissionRequest for path=/inject
2022-10-25T12:32:23.351335Z	info	Sidecar injection request for default/productpage-v1-778c664bbd-***** (actual name not yet known)
2022-10-25T12:32:23.351398Z	debug	Object: {"kind":"Pod","apiVersion":"v1","metadata":{"generateName":"productpage-v1-778c664bbd-","creationTimestamp":null,"labels":{"app":"productpage","pod-template-hash":"778c664bbd","sidecar.istio.io/inject":"true","version":"v1"},"ownerReferences":[{"apiVersion":"apps/v1","kind":"ReplicaSet","name":"productpage-v1-778c664bbd","uid":"8ab3e080-2e0e-4763-aaf0-a2a9995fd4d2","controller":true,"blockOwnerDeletion":true}],"managedFields":[{"manager":"kube-controller-manager","operation":"Update","apiVersion":"v1","time":"2022-10-25T12:32:23Z","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:app":{},"f:pod-template-hash":{},"f:sidecar.istio.io/inject":{},"f:version":{}},"f:ownerReferences":{".":{},"k:{"uid":"8ab3e080-2e0e-4763-aaf0-a2a9995fd4d2"}":{}}},"f:spec":{"f:containers":{"k:{"name":"productpage"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:ports":{".":{},"k:{"containerPort":9080,"protocol":"TCP"}":{".":{},"f:containerPort":{},"f:protocol":{}}},"f:resources":{},"f:securityContext":{".":{},"f:runAsUser":{}},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{},"f:volumeMounts":{".":{},"k:{"mountPath":"/tmp"}":{".":{},"f:mountPath":{},"f:name":{}}}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:serviceAccount":{},"f:serviceAccountName":{},"f:terminationGracePeriodSeconds":{},"f:volumes":{".":{},"k:{"name":"tmp"}":{".":{},"f:emptyDir":{},"f:name":{}}}}}}]},"spec":{"volumes":[{"name":"tmp","emptyDir":{}},{"name":"kube-api-access-kc8kt","projected":{"sources":[{"serviceAccountToken":{"expirationSeconds":3607,"path":"token"}},{"configMap":{"name":"kube-root-ca.crt","items":[{"key":"ca.crt","path":"ca.crt"}]}},{"downwardAPI":{"items":[{"path":"namespace","fieldRef":{"apiVersion":"v1","fieldPath":"metadata.namespace"}}]}}],"defaultMode":420}}],"containers":[{"name":"productpage","image":"docker.io/istio/examples-bookinfo-productpage-v1:1.16.2","ports":[{"containerPort":9080,"protocol":"TCP"}],"resources":{},"volumeMounts":[{"name":"tmp","mountPath":"/tmp"},{"name":"kube-api-access-kc8kt","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"IfNotPresent","securityContext":{"runAsUser":1000}}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"bookinfo-productpage","serviceAccount":"bookinfo-productpage","securityContext":{},"schedulerName":"default-scheduler","tolerations":[{"key":"node.kubernetes.io/not-ready","operator":"Exists","effect":"NoExecute","tolerationSeconds":300},{"key":"node.kubernetes.io/unreachable","operator":"Exists","effect":"NoExecute","tolerationSeconds":300}],"priority":0,"enableServiceLinks":true,"preemptionPolicy":"PreemptLowerPriority"},"status":{}}
2022-10-25T12:32:23.351416Z	debug	OldObject:
2022-10-25T12:32:23.351481Z	debug	Sidecar injection policy for default/productpage-v1-778c664bbd-***** (actual name not yet known): namespacePolicy:enabled useDefault:false inject:true required:true prometheus.istio.io/merge-metrics:(unset) proxy.istio.io/config:(unset) sidecar.istio.io/interceptionMode:(unset) sidecar.istio.io/enableCoreDump:(unset) readiness.status.sidecar.istio.io/initialDelaySeconds:(unset) readiness.status.sidecar.istio.io/periodSeconds:(unset) traffic.sidecar.istio.io/includeOutboundIPRanges:(unset) traffic.sidecar.istio.io/excludeInboundPorts:(unset) status.sidecar.istio.io/port:(unset) readiness.status.sidecar.istio.io/failureThreshold:(unset) traffic.sidecar.istio.io/excludeOutboundIPRanges:(unset) traffic.sidecar.istio.io/includeInboundPorts:(unset) traffic.sidecar.istio.io/excludeOutboundPorts:(unset)
2022-10-25T12:32:23.353152Z	debug	Failed to decode proto: "unknown field "enabled" in v1alpha1.GlobalConfig". Trying decode with AllowUnknownFields=true
2022-10-25T12:32:23.363419Z	debug	Failed to decode proto: "unknown field "namespace" in v1alpha1.GlobalConfig". Trying decode with AllowUnknownFields=true
2022-10-25T12:32:23.364122Z	debug	Failed to decode proto: "unknown field "namespace" in v1alpha1.GlobalConfig". Trying decode with AllowUnknownFields=true
2022-10-25T12:32:23.368936Z	debug	AdmissionResponse: patch=[{"op":"add","path":"/metadata/labels/security.istio.io~1tlsMode","value":"istio"},{"op":"add","path":"/metadata/labels/service.istio.io~1canonical-name","value":"productpage"},{"op":"add","path":"/metadata/labels/service.istio.io~1canonical-revision","value":"v1"},{"op":"add","path":"/metadata/annotations","value":{"kubectl.kubernetes.io/default-container":"productpage","kubectl.kubernetes.io/default-logs-container":"productpage","prometheus.io/path":"/stats/prometheus","prometheus.io/port":"15020","prometheus.io/scrape":"true","sidecar.istio.io/status":"{"initContainers":["istio-init"],"containers":["istio-proxy"],"volumes":["istio-envoy","nginx_conf","istio-data","istio-podinfo","istio-token","istiod-ca-cert"],"imagePullSecrets":null,"revision":"default"}"}},{"op":"add","path":"/spec/volumes/2","value":{"name":"istio-data","emptyDir":{}}},{"op":"add","path":"/spec/volumes/3","value":{"name":"istio-podinfo","downwardAPI":{"items":[{"path":"labels","fieldRef":{"fieldPath":"metadata.labels"}},{"path":"annotations","fieldRef":{"fieldPath":"metadata.annotations"}}]}}},{"op":"add","path":"/spec/volumes/4","value":{"name":"istio-token","projected":{"sources":[{"serviceAccountToken":{"audience":"istio-ca","expirationSeconds":43200,"path":"istio-token"}}]}}},{"op":"add","path":"/spec/volumes/5","value":{"name":"istiod-ca-cert","configMap":{"name":"istio-ca-root-cert"}}},{"op":"add","path":"/spec/volumes/6","value":{"name":"tmp","emptyDir":{}}},{"op":"add","path":"/spec/volumes/7","value":{"name":"kube-api-access-kc8kt","projected":{"sources":[{"serviceAccountToken":{"expirationSeconds":3607,"path":"token"}},{"configMap":{"name":"kube-root-ca.crt","items":[{"key":"ca.crt","path":"ca.crt"}]}},{"downwardAPI":{"items":[{"path":"namespace","fieldRef":{"apiVersion":"v1","fieldPath":"metadata.namespace"}}]}}],"defaultMode":420}}},{"op":"replace","path":"/spec/volumes/0/name","value":"istio-envoy"},{"op":"add","path":"/spec/volumes/0/emptyDir/medium","value":"Memory"},{"op":"replace","path":"/spec/volumes/1/name","value":"nginx_conf"},{"op":"add","path":"/spec/volumes/1/hostPath","value":{"path":"/etc/nginx/","type":"Directory"}},{"op":"remove","path":"/spec/volumes/1/projected"},{"op":"add","path":"/spec/initContainers","value":[{"name":"istio-init","image":"docker.io/istio/proxyv2:1.13.3","args":["istio-iptables","-p","15001","-z","15006","-u","1337","-m","REDIRECT","-i","","-x","","-b","","-d","15090,15021,15020"],"resources":{"limits":{"cpu":"2","memory":"1Gi"},"requests":{"cpu":"100m","memory":"128Mi"}},"securityContext":{"capabilities":{"add":["NET_ADMIN","NET_RAW"],"drop":["ALL"]},"privileged":false,"runAsUser":0,"runAsGroup":0,"runAsNonRoot":false,"readOnlyRootFilesystem":false,"allowPrivilegeEscalation":false}}]},{"op":"add","path":"/spec/containers/1","value":{"name":"istio-proxy","image":"docker.io/lqsun666/api-gateway_ubuntu:v1.7","ports":[{"name":"http-envoy-prom","containerPort":15090,"protocol":"TCP"}],"env":[{"name":"JWT_POLICY","value":"third-party-jwt"},{"name":"PILOT_CERT_PROVIDER","value":"istiod"},{"name":"CA_ADDR","value":"istiod.istio-system.svc:15012"},{"name":"POD_NAME","valueFrom":{"fieldRef":{"fieldPath":"metadata.name"}}},{"name":"POD_NAMESPACE","valueFrom":{"fieldRef":{"fieldPath":"metadata.namespace"}}},{"name":"INSTANCE_IP","valueFrom":{"fieldRef":{"fieldPath":"status.podIP"}}},{"name":"SERVICE_ACCOUNT","valueFrom":{"fieldRef":{"fieldPath":"spec.serviceAccountName"}}},{"name":"HOST_IP","valueFrom":{"fieldRef":{"fieldPath":"status.hostIP"}}},{"name":"PROXY_CONFIG","value":"{}\n"},{"name":"ISTIO_META_POD_PORTS","value":"[\n    {"containerPort":9080,"protocol":"TCP"}\n]"},{"name":"ISTIO_META_APP_CONTAINERS","value":"productpage"},{"name":"ISTIO_META_CLUSTER_ID","value":"Kubernetes"},{"name":"ISTIO_META_INTERCEPTION_MODE","value":"REDIRECT"},{"name":"ISTIO_META_WORKLOAD_NAME","value":"productpage-v1"},{"name":"ISTIO_META_OWNER","value":"kubernetes://apis/apps/v1/namespaces/default/deployments/productpage-v1"},{"name":"ISTIO_META_MESH_ID","value":"cluster.local"},{"name":"TRUST_DOMAIN","value":"cluster.local"}],"resources":{"limits":{"cpu":"2","memory":"1Gi"},"requests":{"cpu":"100m","memory":"128Mi"}},"volumeMounts":[{"name":"istiod-ca-cert","mountPath":"/var/run/secrets/istio"},{"name":"istio-data","mountPath":"/var/lib/istio/data"},{"name":"nginx_conf","mountPath":"/etc/nginx"},{"name":"istio-envoy","mountPath":"/etc/istio/proxy"},{"name":"istio-token","mountPath":"/var/run/secrets/tokens"},{"name":"istio-podinfo","mountPath":"/etc/istio/pod"}],"securityContext":{"capabilities":{"drop":["ALL"]},"privileged":false,"runAsUser":1337,"runAsGroup":1337,"runAsNonRoot":true,"allowPrivilegeEscalation":false}}}]
2022-10-25T12:32:23.384888Z	debug	AdmissionRequest for path=/inject
2022-10-25T12:32:23.385590Z	info	Sidecar injection request for default/productpage-v1-778c664bbd-***** (actual name not yet known)
2022-10-25T12:32:23.385621Z	debug	Object: {"kind":"Pod","apiVersion":"v1","metadata":{"generateName":"productpage-v1-778c664bbd-","creationTimestamp":null,"labels":{"app":"productpage","pod-template-hash":"778c664bbd","sidecar.istio.io/inject":"true","version":"v1"},"ownerReferences":[{"apiVersion":"apps/v1","kind":"ReplicaSet","name":"productpage-v1-778c664bbd","uid":"8ab3e080-2e0e-4763-aaf0-a2a9995fd4d2","controller":true,"blockOwnerDeletion":true}],"managedFields":[{"manager":"kube-controller-manager","operation":"Update","apiVersion":"v1","time":"2022-10-25T12:32:23Z","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:generateName":{},"f:labels":{".":{},"f:app":{},"f:pod-template-hash":{},"f:sidecar.istio.io/inject":{},"f:version":{}},"f:ownerReferences":{".":{},"k:{"uid":"8ab3e080-2e0e-4763-aaf0-a2a9995fd4d2"}":{}}},"f:spec":{"f:containers":{"k:{"name":"productpage"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:ports":{".":{},"k:{"containerPort":9080,"protocol":"TCP"}":{".":{},"f:containerPort":{},"f:protocol":{}}},"f:resources":{},"f:securityContext":{".":{},"f:runAsUser":{}},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{},"f:volumeMounts":{".":{},"k:{"mountPath":"/tmp"}":{".":{},"f:mountPath":{},"f:name":{}}}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:serviceAccount":{},"f:serviceAccountName":{},"f:terminationGracePeriodSeconds":{},"f:volumes":{".":{},"k:{"name":"tmp"}":{".":{},"f:emptyDir":{},"f:name":{}}}}}}]},"spec":{"volumes":[{"name":"tmp","emptyDir":{}},{"name":"kube-api-access-qc7wl","projected":{"sources":[{"serviceAccountToken":{"expirationSeconds":3607,"path":"token"}},{"configMap":{"name":"kube-root-ca.crt","items":[{"key":"ca.crt","path":"ca.crt"}]}},{"downwardAPI":{"items":[{"path":"namespace","fieldRef":{"apiVersion":"v1","fieldPath":"metadata.namespace"}}]}}],"defaultMode":420}}],"containers":[{"name":"productpage","image":"docker.io/istio/examples-bookinfo-productpage-v1:1.16.2","ports":[{"containerPort":9080,"protocol":"TCP"}],"resources":{},"volumeMounts":[{"name":"tmp","mountPath":"/tmp"},{"name":"kube-api-access-qc7wl","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"IfNotPresent","securityContext":{"runAsUser":1000}}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","serviceAccountName":"bookinfo-productpage","serviceAccount":"bookinfo-productpage","securityContext":{},"schedulerName":"default-scheduler","tolerations":[{"key":"node.kubernetes.io/not-ready","operator":"Exists","effect":"NoExecute","tolerationSeconds":300},{"key":"node.kubernetes.io/unreachable","operator":"Exists","effect":"NoExecute","tolerationSeconds":300}],"priority":0,"enableServiceLinks":true,"preemptionPolicy":"PreemptLowerPriority"},"status":{}}
2022-10-25T12:32:23.385627Z	debug	OldObject:
2022-10-25T12:32:23.385705Z	debug	Sidecar injection policy for default/productpage-v1-778c664bbd-***** (actual name not yet known): namespacePolicy:enabled useDefault:false inject:true required:true status.sidecar.istio.io/port:(unset) readiness.status.sidecar.istio.io/failureThreshold:(unset) traffic.sidecar.istio.io/excludeOutboundIPRanges:(unset) traffic.sidecar.istio.io/includeInboundPorts:(unset) traffic.sidecar.istio.io/excludeOutboundPorts:(unset) traffic.sidecar.istio.io/excludeInboundPorts:(unset) prometheus.istio.io/merge-metrics:(unset) proxy.istio.io/config:(unset) sidecar.istio.io/interceptionMode:(unset) sidecar.istio.io/enableCoreDump:(unset) readiness.status.sidecar.istio.io/initialDelaySeconds:(unset) readiness.status.sidecar.istio.io/periodSeconds:(unset) traffic.sidecar.istio.io/includeOutboundIPRanges:(unset)
2022-10-25T12:32:23.387389Z	debug	Failed to decode proto: "unknown field "namespace" in v1alpha1.GlobalConfig". Trying decode with AllowUnknownFields=true
2022-10-25T12:32:23.423232Z	debug	Failed to decode proto: "unknown field "enabled" in v1alpha1.GlobalConfig". Trying decode with AllowUnknownFields=true
2022-10-25T12:32:23.424057Z	debug	Failed to decode proto: "unknown field "namespace" in v1alpha1.GlobalConfig". Trying decode with AllowUnknownFields=true
2022-10-25T12:32:23.428573Z	debug	AdmissionResponse: patch=[{"op":"add","path":"/metadata/labels/security.istio.io~1tlsMode","value":"istio"},{"op":"add","path":"/metadata/labels/service.istio.io~1canonical-name","value":"productpage"},{"op":"add","path":"/metadata/labels/service.istio.io~1canonical-revision","value":"v1"},{"op":"add","path":"/metadata/annotations","value":{"kubectl.kubernetes.io/default-container":"productpage","kubectl.kubernetes.io/default-logs-container":"productpage","prometheus.io/path":"/stats/prometheus","prometheus.io/port":"15020","prometheus.io/scrape":"true","sidecar.istio.io/status":"{"initContainers":["istio-init"],"containers":["istio-proxy"],"volumes":["istio-envoy","nginx_conf","istio-data","istio-podinfo","istio-token","istiod-ca-cert"],"imagePullSecrets":null,"revision":"default"}"}},{"op":"add","path":"/spec/volumes/2","value":{"name":"istio-data","emptyDir":{}}},{"op":"add","path":"/spec/volumes/3","value":{"name":"istio-podinfo","downwardAPI":{"items":[{"path":"labels","fieldRef":{"fieldPath":"metadata.labels"}},{"path":"annotations","fieldRef":{"fieldPath":"metadata.annotations"}}]}}},{"op":"add","path":"/spec/volumes/4","value":{"name":"istio-token","projected":{"sources":[{"serviceAccountToken":{"audience":"istio-ca","expirationSeconds":43200,"path":"istio-token"}}]}}},{"op":"add","path":"/spec/volumes/5","value":{"name":"istiod-ca-cert","configMap":{"name":"istio-ca-root-cert"}}},{"op":"add","path":"/spec/volumes/6","value":{"name":"tmp","emptyDir":{}}},{"op":"add","path":"/spec/volumes/7","value":{"name":"kube-api-access-qc7wl","projected":{"sources":[{"serviceAccountToken":{"expirationSeconds":3607,"path":"token"}},{"configMap":{"name":"kube-root-ca.crt","items":[{"key":"ca.crt","path":"ca.crt"}]}},{"downwardAPI":{"items":[{"path":"namespace","fieldRef":{"apiVersion":"v1","fieldPath":"metadata.namespace"}}]}}],"defaultMode":420}}},{"op":"replace","path":"/spec/volumes/0/name","value":"istio-envoy"},{"op":"add","path":"/spec/volumes/0/emptyDir/medium","value":"Memory"},{"op":"replace","path":"/spec/volumes/1/name","value":"nginx_conf"},{"op":"add","path":"/spec/volumes/1/hostPath","value":{"path":"/etc/nginx/","type":"Directory"}},{"op":"remove","path":"/spec/volumes/1/projected"},{"op":"add","path":"/spec/initContainers","value":[{"name":"istio-init","image":"docker.io/istio/proxyv2:1.13.3","args":["istio-iptables","-p","15001","-z","15006","-u","1337","-m","REDIRECT","-i","","-x","","-b","","-d","15090,15021,15020"],"resources":{"limits":{"cpu":"2","memory":"1Gi"},"requests":{"cpu":"100m","memory":"128Mi"}},"securityContext":{"capabilities":{"add":["NET_ADMIN","NET_RAW"],"drop":["ALL"]},"privileged":false,"runAsUser":0,"runAsGroup":0,"runAsNonRoot":false,"readOnlyRootFilesystem":false,"allowPrivilegeEscalation":false}}]},{"op":"add","path":"/spec/containers/1","value":{"name":"istio-proxy","image":"docker.io/lqsun666/api-gateway_ubuntu:v1.7","ports":[{"name":"http-envoy-prom","containerPort":15090,"protocol":"TCP"}],"env":[{"name":"JWT_POLICY","value":"third-party-jwt"},{"name":"PILOT_CERT_PROVIDER","value":"istiod"},{"name":"CA_ADDR","value":"istiod.istio-system.svc:15012"},{"name":"POD_NAME","valueFrom":{"fieldRef":{"fieldPath":"metadata.name"}}},{"name":"POD_NAMESPACE","valueFrom":{"fieldRef":{"fieldPath":"metadata.namespace"}}},{"name":"INSTANCE_IP","valueFrom":{"fieldRef":{"fieldPath":"status.podIP"}}},{"name":"SERVICE_ACCOUNT","valueFrom":{"fieldRef":{"fieldPath":"spec.serviceAccountName"}}},{"name":"HOST_IP","valueFrom":{"fieldRef":{"fieldPath":"status.hostIP"}}},{"name":"PROXY_CONFIG","value":"{}\n"},{"name":"ISTIO_META_POD_PORTS","value":"[\n    {"containerPort":9080,"protocol":"TCP"}\n]"},{"name":"ISTIO_META_APP_CONTAINERS","value":"productpage"},{"name":"ISTIO_META_CLUSTER_ID","value":"Kubernetes"},{"name":"ISTIO_META_INTERCEPTION_MODE","value":"REDIRECT"},{"name":"ISTIO_META_WORKLOAD_NAME","value":"productpage-v1"},{"name":"ISTIO_META_OWNER","value":"kubernetes://apis/apps/v1/namespaces/default/deployments/productpage-v1"},{"name":"ISTIO_META_MESH_ID","value":"cluster.local"},{"name":"TRUST_DOMAIN","value":"cluster.local"}],"resources":{"limits":{"cpu":"2","memory":"1Gi"},"requests":{"cpu":"100m","memory":"128Mi"}},"volumeMounts":[{"name":"istiod-ca-cert","mountPath":"/var/run/secrets/istio"},{"name":"istio-data","mountPath":"/var/lib/istio/data"},{"name":"nginx_conf","mountPath":"/etc/nginx"},{"name":"istio-envoy","mountPath":"/etc/istio/proxy"},{"name":"istio-token","mountPath":"/var/run/secrets/tokens"},{"name":"istio-podinfo","mountPath":"/etc/istio/pod"}],"securityContext":{"capabilities":{"drop":["ALL"]},"privileged":false,"runAsUser":1337,"runAsGroup":1337,"runAsNonRoot":true,"allowPrivilegeEscalation":false}}}]

What is the error? Pod doesn't start? It doesn't have volume?

What is the error? Pod doesn't start? It doesn't have volume?

sidecar is not injected.

The entire pod is not injected? The istiod logs AdmissionResponse: patch=... so that seems unexpected.

yes.

The entire pod is not injected? The istiod logs AdmissionResponse: patch=... so that seems unexpected.

yes, the entire pod is not injected.The volume name "nginx_conf " was changed to "nginx-conf" and succeeded

maybe underscore is not valid k8s spec
On Tue, Oct 25, 2022 at 12:08 PM liuqi-sun @.***> wrote:

The entire pod is not injected? The istiod logs AdmissionResponse:
patch=... so that seems unexpected.
yes.
The entire pod is not injected? The istiod logs AdmissionResponse:
patch=... so that seems unexpected.
yes, the entire pod is not injected.The volume name "nginx_conf " was
changed to "nginx-conf" and succeeded
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/41627#issuecomment-1290809265, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXPC6OYJXMYLSTG3MBTWFAAXJANCNFSM6AAAAAARN56ROA
.
You are receiving this because you commented.Message ID:
@.***>

maybe underscore is not valid k8s spec
…
On Tue, Oct 25, 2022 at 12:08 PM liuqi-sun @.> wrote: The entire pod is not injected? The istiod logs AdmissionResponse: patch=... so that seems unexpected. yes. The entire pod is not injected? The istiod logs AdmissionResponse: patch=... so that seems unexpected. yes, the entire pod is not injected.The volume name "nginx_conf " was changed to "nginx-conf" and succeeded — Reply to this email directly, view it on GitHub <#41627 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEYGXPC6OYJXMYLSTG3MBTWFAAXJANCNFSM6AAAAAARN56ROA . You are receiving this because you commented.Message ID: @.>

Thank you so much


Select: placeholderMarginHorizontal console warning

🐛 Bug Report
Variable placeholderMarginHorizontal is no longer used (but left in mapping), which causes console warning.
As you can see here, it was used in the previous version (one commit before 5.0.0):
https://github.com/akveo/react-native-ui-kitten/blob/ff7b5a5bd5943605d2b1d13faec0161dad7a45fa/src/components/ui/select/select.component.tsx#L362
But in the current one, it's not used:
https://github.com/akveo/react-native-ui-kitten/blob/master/src/components/ui/select/select.component.tsx#L337
As one can see, in the newest eva-design/eva this variable is still present:
https://github.com/eva-design/eva/blob/master/packages/eva/mapping.json#L3691
To Reproduce
Steps to reproduce the behavior:
NA - simply try to use Select component on a normal github project, and the warning (error) should be in console.
Expected behavior
There is no warning in the console.
UI Kitten and Eva version

Package
Version

@eva-design/eva
2.0.0

@ui-kitten/components
5.0.0

Environment information

  System:
    OS: macOS Mojave 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 13.12.0 - ~/.nvm/versions/node/v13.12.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v13.12.0/bin/npm
  IDEs:
    Xcode: /undefined - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz => 0.61.4

EDIT: Ah, of course I've forgot to put in the warning:

This happens to me as well

I too have this problem.

still having this issue, any workaround to this yet?


[Snyk] Security upgrade juicy-chat-bot from 0.6.6 to 0.8.0

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

package.json

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Regular Expression Denial of Service (ReDoS) SNYK-JS-ASYNC-7414156
  631

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

Checkmarx One – Scan Summary & Details – 323f29b3-a256-4328-81c8-959c8ea1ff07
Policy Management Violations

Policy Name
Rule(s)
Break Build

No highs or mediums
No Highs or Mediums
false

New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2022-23539
Npm-jsonwebtoken-0.1.0
Vulnerable Package

CVE-2022-23539
Npm-jsonwebtoken-0.4.0
Vulnerable Package

CVE-2022-23540
Npm-jsonwebtoken-0.1.0
Vulnerable Package

CVE-2022-23540
Npm-jsonwebtoken-0.4.0
Vulnerable Package

CVE-2022-25858
Npm-terser-5.5.1
Vulnerable Package

CVE-2022-25881
Npm-http-cache-semantics-3.8.1
Vulnerable Package

CVE-2022-25883
Npm-semver-7.3.4
Vulnerable Package

CVE-2022-25887
Npm-sanitize-html-1.4.2
Vulnerable Package

CVE-2022-3517
Npm-minimatch-3.0.4
Vulnerable Package

CVE-2022-37599
Npm-loader-utils-2.0.0
Vulnerable Package

CVE-2022-37601
Npm-loader-utils-2.0.0
Vulnerable Package

CVE-2022-37603
Npm-loader-utils-2.0.0
Vulnerable Package

CVE-2023-26136
Npm-tough-cookie-2.5.0
Vulnerable Package

CVE-2023-32314
Npm-vm2-3.9.17
Vulnerable Package

CVE-2023-32695
Npm-socket.io-parser-4.0.5
Vulnerable Package

CVE-2023-37466
Npm-vm2-3.9.17
Vulnerable Package

CVE-2023-37903
Npm-vm2-3.9.17
Vulnerable Package

CVE-2023-42282
Npm-ip-1.1.9
Vulnerable Package

CVE-2023-46233
Npm-crypto-js-3.3.0
Vulnerable Package

CVE-2024-29180
Npm-webpack-dev-middleware-3.7.2
Vulnerable Package

CVE-2024-37890
Npm-ws-7.4.6
Vulnerable Package

CVE-2024-38355
Npm-socket.io-3.1.2
Vulnerable Package

CVE-2024-4068
Npm-braces-2.3.2
Vulnerable Package

Cxc7705965-e0f0
<EMAIL_ADDRESS>Vulnerable Package

CVE-2022-23541
Npm-jsonwebtoken-0.1.0
Vulnerable Package

CVE-2022-23541
Npm-jsonwebtoken-0.4.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-11.1.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-6.2.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-4.4.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-3.9.0
Vulnerable Package

CVE-2022-36313
Npm-file-type-5.2.0
Vulnerable Package

CVE-2022-41940
Npm-engine.io-4.1.2
Vulnerable Package

CVE-2023-0842
Npm-xml2js-0.4.23
Vulnerable Package

CVE-2023-28155
Npm-request-2.88.2
Vulnerable Package

CVE-2023-32313
Npm-vm2-3.9.17
Vulnerable Package

CVE-2023-44270
Npm-postcss-8.2.15
Vulnerable Package

CVE-2023-44270
Npm-postcss-7.0.39
Vulnerable Package

CVE-2024-21501
Npm-sanitize-html-1.4.2
Vulnerable Package

CVE-2024-28863
Npm-tar-4.4.19
Vulnerable Package

CVE-2024-4067
Npm-micromatch-3.1.10
Vulnerable Package

CVE-2024-4067
Npm-micromatch-4.0.7
Vulnerable Package

Angular_Usage_of_Unsafe_DOM_Sanitizer
/frontend/src/app/score-board/score-board.component.ts: 175
Attack Vector

Unpinned Actions Full Length Commit SHA
/release.yml: 50
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: 62
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: 64
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: 72
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/lint-fixer.yml: 24
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 145
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 205
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 266
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/zap_scan.yml: 17
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: 66
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 123
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 203
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 249
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/update-news-www.yml: 20
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: 97
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/update-challenges-www.yml: 24
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/codeql-analysis.yml: 20
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 221
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/codeql-analysis.yml: 22
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/rebase.yml: 17
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/release.yml: 78
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/codeql-analysis.yml: 18
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 83
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 77
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Unpinned Actions Full Length Commit SHA
/ci.yml: 207
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...

Using Platform Flag with FROM Command
/Dockerfile: 1
Don't use '--platform' flag with FROM

Fixed Issues

Severity
Issue
Source File / Package

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

Angular_Client_Stored_DOM_XSS
/frontend/src/app/last-login-ip/last-login-ip.component.ts: 31

CVE-2021-23440
Npm-set-value-2.0.1

CVE-2021-23449
Npm-vm2-3.9.3

CVE-2021-23555
Npm-vm2-3.9.3

CVE-2021-35065
Npm-glob-parent-3.1.0

CVE-2021-35065
Npm-glob-parent-5.1.2

CVE-2021-44906
Npm-minimist-0.2.1

CVE-2022-21213
Npm-mout-1.2.3

Code_Injection
/routes/showProductReviews.ts: 25

Code_Injection
/routes/trackOrder.ts: 12

Code_Injection
/routes/trackOrder.ts: 12

Passwords And Secrets - Generic Password
/users.yml: 115

Passwords And Secrets - Generic Password
/users.yml: 107

Passwords And Secrets - Generic Password
/users.yml: 166

Passwords And Secrets - Generic Password
/users.yml: 242

Passwords And Secrets - Generic Password
/users.yml: 31

Passwords And Secrets - Generic Password
/users.yml: 236

Passwords And Secrets - Generic Password
/users.yml: 88

Passwords And Secrets - Generic Password
/users.yml: 3

Passwords And Secrets - Generic Password
/users.yml: 203

Passwords And Secrets - Generic Password
/users.yml: 149

Passwords And Secrets - Generic Password
/users.yml: 248

Passwords And Secrets - Generic Password
/users.yml: 63

Passwords And Secrets - Generic Password
/users.yml: 176

Passwords And Secrets - Generic Password
/users.yml: 212

Passwords And Secrets - Generic Password
/users.yml: 140

Passwords And Secrets - Generic Password
/users.yml: 123

Passwords And Secrets - Generic Password
/users.yml: 158

Passwords And Secrets - Generic Secret
/users.yml: 150

Passwords And Secrets - Google OAuth
/default.yml: 57

Reflected_XSS
/routes/recycles.ts: 12

Second_Order_SQL_Injection
/data/datacreator.ts: 215

Second_Order_SQL_Injection
/data/datacreator.ts: 122

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 45

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 44

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/product-details/product-details.component.html: 38

Angular_Improper_Type_Pipe_Usage
/frontend/src/app/search-result/search-result.component.html: 20

Angular_Improper_Type_Pipe_Usage

More results are available on AST platform


Command line parameter for bcrypt_pbkdf password cracking defenses, e.g. iteration counts

As noted e.g. at Recommended # of iterations when using PKBDF2-SHA256?, it is important to take steps to protect the password for the secret key from brute force attacks. It appears that the signify code uses bcrypt_pbkdf to do this, but the parameters like iteration count used aren't noted in the documentation. It should be possible to increase the count over time.
Can the number of iterations/rounds be modified via the command-line tool? If not can that feature be added?

From the point of view of this Signify project, the one and only goal is to take the code from OpenBSD (where it originated and is maintained) and apply the minimum set of modifications needed to make it run on GNU/Linux—also, I do not have more spare time than for doing that, sorry!
New features should be added by submitting patches to the OpenBSD project, and once they have been included there I will be more than happy to update the source code here for the portable version.
Let's keep this issue open nevertheless, in case someone else is looking for ideas that could be contributed back to the OpenBSD project.


SyntaxError: Unexpected token function (init.js)

I tried following the instructions for testing, and it failed on npm run setup. It's possible I did something dumb. I don't know anything about Node.js. Below is the log output.

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'setup' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'presetup', 'setup', 'postsetup' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for presetup, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/rocapp/Git/bbot-rocketchat-boilerplate/node_modules/.bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/rocapp/Git/bbot-rocketchat-boilerplate
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node init.js' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec setup script
14 verbose stack Error<EMAIL_ADDRESS>setup: node init.js
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:891:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/rocapp/Git/bbot-rocketchat-boilerplate
17 error Linux 4.15.0-42-generic
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "setup"
19 error node v6.11.2
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>setup: node init.js
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>setup script 'node init.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the brocket-demo package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     node init.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs brocket-demo
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls brocket-demo
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

@rocapp I don't know what to make of that. It might be your node version 🤷♂
Node 6 is approaching end of life, I would recommend updating to Node 8.
The setup script is not crucial. It mostly just sets the environment variables in a .env file by copying from the provided .env.example. So you can try doing that manually, then proceed to the next steps, but you may continue to have issues with Node 6, I haven't tested for it.


Generate kubeconfig secret with additional CAs

Adds field to ClusterDeployment status to hold the raw kubeconfig
Points the original status.AdminKubeconfigSecret to a new generated secret that contains additional CAs
Includes fix to hive operator to force a reload of the hive controllers pod when the AdditionalCertificateAuthorities value changes.

Reworked to use a single secret with a key for the original kubeconfig (raw-kubeconfig) and the regular kubeconfig with additional CAs added.

/lgtm


change link to MS FAQ to point to 'faq'

I'm not familiar to Jeckyll, so I'm not completely sure that changing the link like this will have the appropriate effect, however the link should point to /faq instead of questions.md (https://tudelft-in4303.github.io/assignments/ms1/faq) instead of (https://tudelft-in4303.github.io/assignments/ms1/questions.md)

Yes, this fixed it. Thanks.

Cool!


Supplier integration

This PR adds:

GenericWebTransaction model
transitions WebhookMessage to GenericWebTransaction
Adds WebConnection (including admin, API)
Adds WebConnectionTransaction  inheriting from GenericWebTransaction)
Adds ConnectionSetting (including API, admin)
Adds PluginSearch view (in the API) to search through connections and adds it to search
Adds SupplierMixin
Adds get_api_url method to PluginConfig model
Adds plugin_connections tag

Open:

[x] tests for webconnections
[ ] tests for search API
[x] API to add part from search result
[x] tests for part add API
[x] UI for adding part from search result

Before merge:

[ ] Move OAuth checks to mixin
[ ] Move requests middleware to mixin
[ ] Move WebConnectionData to plugin namespace
[ ] Move SearchRunResult to plugin namespace

Fixes parts of #3261

Ok only tests left before this can be tried out

Ok, this is ready for testing.
Install
1.1 Use this branch
1.2 activate plugins
1.3 install and activate https://github.com/matmair/inventree-digikey/tree/v1 (use v1 branch!)
1.4 make sure all integrations are active
One-time setup
2.1 You need to register a production app at DigiKey.
2.2 Activate all product information endpoints on the app
2.3 Go to the settings page for the plugin
2.4 Add a new connection under 'web connections'
2.5 Add your production key and secret to the connection
2.6 Click on the setup URL link on the plugin page
2.7 Log in on the Digikey auth page
Test instructions
3.1 Open the start page of your instance
3.2 Click on 'Supplier API' navigation tab
3.3 Click on 'Import supplier part'
3.4 Fill out the popup. Select the connection you added in 2.4, add a digikey reference (eg. 1528-2280-ND) and select the category the part should be created in
3.5 The new part should open
Caveats
4.1 THIS IS NOT PRODUCTION READY
4.2 The current setup flow is not how it is intended to be in the final stage
4.3 The digikey sample plugin is very naive and has limited options
4.4 Currently only search and import APIs are integrated (the sample plugin only contains import API for now)
4.5 The plugin does not do oauth refreshes for now - so you will need to press the setup button from time to time - THIS IS NOT PRODUCTION READY

@matmair this is a lot to comprehend!

A tip on how the test is working on sqlite but not postgres would be highly appreciated though.

Still in the WIP pipeline

@matmair I'm still very keen to see this implemented - do you have motivation on this still too? Does this in your mind require the react integration, or can we look at getting it merged in now?

I will move this to a plugin; it requires either the react integration or shipping the UI - which I will do with the plugin. Development velocity is also much easier to handle in a plugin.

How is that going to work then? Would this plugin basically enable the use of other supplier plugins? Or would it just be one big plugin supporting multiple suppliers?
Tbh I haven't really had time to look at this in depth yet, but I feel like it'd integrate well with what I've been working on in #5509 and the backend part should probably be in core ... buuut I really have no clue about the frontend requirements here. Could this maybe be divided into multiple smaller features/PRs?
Also, regarding actual supplier support: I've seen that you already have a WIP digikey plugin. I've been working on my own part importer script (basically a simplified/improved version of Ki-nTree, with proper support for nested categories). It's working quite well for my purposes, but I still feel like it shouldn't really be a script, but a plugin aswell, thus useable directly from the inventree interface. So I'd be interested in contributing that into core/your plugin aswell.

There will be a plugin that provides a basic UI and all that is required to handle the typical flows like search, data gathering, and creation of new parts/stock. I will not continue development with core as a target.
This plugin can be used as a target for vendor-specific APIs.

Is there a better / recent setup guide than this https://github.com/inventree/InvenTree/pull/3791#issuecomment-1439224710?
In my current setup there is only one setting available and it's called "Supplier - The Supplier which acts as 'DigiKey'".

This or is closed, development of this was shifted and none of the linked components are finished. I refactored basically the whole thing, some of the decisions made here were not scalable enough.

In my current setup there is only one setting available and it's called "Supplier - The Supplier which acts as 'DigiKey'".

That's from the supplier barcode plugins (introduced in #5509).

Ah I see, I thought it was the same thing.
So there won't be a native DigiKey plugin?
Thanks for the info.


Added a test for simultaneous async await

Running this test with code from before the RPC pooling fails with:

Now with pooling the test goes green.
Good to see that the pooling is working, nice work!

Awesome!
On that note, you might've noticed, that the unittest-results are also generated when tests fail.
I think ill make a branch with all failing tests (that are currently disabled) enabled, so that we can see what currently doesn't work, and more easily track progress.
This branch would then be updated from master.
Any suggestions as for the branch name?

Sounds good, something simple like all-tests maybe.


Getting crash on game launch

---- Minecraft Crash Report ----
// Surprise! Haha. Well, this is awkward.
Time: 04/06/2022, 13:28
Description: Mod loading error has occurred
java.lang.Exception: Mod Loading has failed
at net.minecraftforge.logging.CrashReportExtender.dumpModLoadingCrashReport(CrashReportExtender.java:55) ~[forge-1.18.2-40.1.31-universal.jar%2357!/:?] {re:classloading}
at net.minecraftforge.client.loading.ClientModLoader.completeModLoading(ClientModLoader.java:169) ~[forge-1.18.2-40.1.31-universal.jar%2357!/:?] {re:classloading,pl:runtimedistcleaner:A}
at net.minecraft.client.Minecraft.lambda$new$1(Minecraft.java:555) ~[client-1.18.2-20220404.173914-srg.jar%2353!/:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at net.minecraft.Util.m_137521_(Util.java:397) ~[client-1.18.2-20220404.173914-srg.jar%2353!/:?] {re:classloading}
at net.minecraft.client.Minecraft.lambda$new$2(Minecraft.java:549) ~[client-1.18.2-20220404.173914-srg.jar%2353!/:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at net.minecraft.client.gui.screens.LoadingOverlay.m_6305_(LoadingOverlay.java:135) ~[client-1.18.2-20220404.173914-srg.jar%2353!/:?] {re:classloading,pl:runtimedistcleaner:A}
at net.minecraft.client.renderer.GameRenderer.m_109093_(GameRenderer.java:879) ~[client-1.18.2-20220404.173914-srg.jar%2353!/:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at net.minecraft.client.Minecraft.m_91383_(Minecraft.java:1044) ~[client-1.18.2-20220404.173914-srg.jar%2353!/:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at net.minecraft.client.Minecraft.m_91374_(Minecraft.java:663) ~[client-1.18.2-20220404.173914-srg.jar%2353!/:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at net.minecraft.client.main.Main.main(Main.java:205) ~[client-1.18.2-20220404.173914-srg.jar%2353!/:?] {re:classloading,pl:runtimedistcleaner:A}
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] {}
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?] {}
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] {}
at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] {}
at net.minecraftforge.fml.loading.targets.CommonClientLaunchHandler.lambda$launchService$0(CommonClientLaunchHandler.java:31) ~[fmlloader-1.18.2-40.1.31.jar%2316!/:?] {}
at cpw.mods.modlauncher.LaunchServiceHandlerDecorator.launch(LaunchServiceHandlerDecorator.java:37) [modlauncher-9.1.3.jar%235!/:?] {}
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:53) [modlauncher-9.1.3.jar%235!/:?] {}
at cpw.mods.modlauncher.LaunchServiceHandler.launch(LaunchServiceHandler.java:71) [modlauncher-9.1.3.jar%235!/:?] {}
at cpw.mods.modlauncher.Launcher.run(Launcher.java:106) [modlauncher-9.1.3.jar%235!/:?] {}
at cpw.mods.modlauncher.Launcher.main(Launcher.java:77) [modlauncher-9.1.3.jar%235!/:?] {}
at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) [modlauncher-9.1.3.jar%235!/:?] {}
at cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) [modlauncher-9.1.3.jar%235!/:?] {}
at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:149) [bootstraplauncher-1.0.0.jar:?] {}
A detailed walkthrough of the error, its code path and all known details is as follows:
-- Head --
Thread: Render thread
Stacktrace:
at java.util.Optional.orElseThrow(Optional.java:403) ~[?:?] {}
-- MOD easierchests --
Details:
Mod File: easierchests-1.0.2.jar
Failure message: EasierChests (easierchests) encountered an error during the sided_setup event phase
java.lang.RuntimeException: null
Mod Version: 1.0.2
Mod Issue URL: https://github.com/CorgiTaco/EasierChests-Forge/issues
Exception message: java.lang.RuntimeException
Stacktrace:
at java.util.Optional.orElseThrow(Optional.java:403) ~[?:?] {}
at de.guntram.mcmod.easierchests.ConfigurationHandler.readConfig(ConfigurationHandler.java:89) ~[easierchests-1.0.2.jar%2352!/:1.0.2] {re:mixin,re:classloading}
at de.guntram.mcmod.easierchests.ConfigurationHandler.getInstance(ConfigurationHandler.java:67) ~[easierchests-1.0.2.jar%2352!/:1.0.2] {re:mixin,re:classloading}
at de.guntram.mcmod.easierchests.ConfigurationHandler.getInstance(ConfigurationHandler.java:62) ~[easierchests-1.0.2.jar%2352!/:1.0.2] {re:mixin,re:classloading}
at de.guntram.mcmod.easierchests.EasierChests.clientInit(EasierChests.java:63) ~[easierchests-1.0.2.jar%2352!/:1.0.2] {re:mixin,re:classloading}
at net.minecraftforge.eventbus.EventBus.doCastFilter(EventBus.java:247) ~[eventbus-5.0.3.jar%232!/:?] {}
at net.minecraftforge.eventbus.EventBus.lambda$addListener$11(EventBus.java:239) ~[eventbus-5.0.3.jar%232!/:?] {}
at net.minecraftforge.eventbus.EventBus.post(EventBus.java:302) ~[eventbus-5.0.3.jar%232!/:?] {}
at net.minecraftforge.eventbus.EventBus.post(EventBus.java:283) ~[eventbus-5.0.3.jar%232!/:?] {}
at net.minecraftforge.fml.javafmlmod.FMLModContainer.acceptEvent(FMLModContainer.java:106) ~[javafmllanguage-1.18.2-40.1.31.jar%2355!/:?] {}
at net.minecraftforge.fml.ModContainer.lambda$buildTransitionHandler$4(ModContainer.java:107) ~[fmlcore-1.18.2-40.1.31.jar%2354!/:?] {}
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?] {}
at java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1796) ~[?:?] {}
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) ~[?:?] {}
at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) ~[?:?] {}
at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) ~[?:?] {}
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) ~[?:?] {}
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) ~[?:?] {}
-- System Details --
Details:
Minecraft Version: 1.18.2
Minecraft Version ID: 1.18.2
Operating System: Windows 10 (amd64) version 10.0
Java Version: 17.0.1, Microsoft
Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Microsoft
Memory: 483979176 bytes (461 MiB) /<PHONE_NUMBER> bytes (1472 MiB) up to<PHONE_NUMBER> bytes (2048 MiB)
CPUs: 12
Processor Vendor: GenuineIntel
Processor Name: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
Identifier: Intel64 Family 6 Model 158 Stepping 10
Microarchitecture: Coffee Lake
Frequency (GHz): 3.70
Number of physical packages: 1
Number of physical CPUs: 6
Number of logical CPUs: 12
Graphics card #0 name: NVIDIA GeForce GTX 1080 Ti
Graphics card #0 vendor: NVIDIA (0x10de)
Graphics card #0 VRAM (MB): 4095.00
Graphics card #0 deviceId: 0x1b06
Graphics card #0 versionInfo: DriverVersion=<IP_ADDRESS>5
Memory slot #0 capacity (MB): 8192.00
Memory slot #0 clockSpeed (GHz): 2.93
Memory slot #0 type: DDR4
Memory slot #1 capacity (MB): 8192.00
Memory slot #1 clockSpeed (GHz): 2.93
Memory slot #1 type: DDR4
Memory slot #2 capacity (MB): 8192.00
Memory slot #2 clockSpeed (GHz): 2.93
Memory slot #2 type: DDR4
Memory slot #3 capacity (MB): 8192.00
Memory slot #3 clockSpeed (GHz): 2.93
Memory slot #3 type: DDR4
Virtual memory max (MB): 51124.39
Virtual memory used (MB): 16038.21
Swap memory total (MB): 18432.00
Swap memory used (MB): 73.11
JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
ModLauncher: 9.1.3+9.1.3+main.9b69c82a
ModLauncher launch target: forgeclient
ModLauncher naming: srg
ModLauncher services:
mixin PLUGINSERVICE
eventbus PLUGINSERVICE
slf4jfixer PLUGINSERVICE
object_holder_definalize PLUGINSERVICE
runtime_enum_extender PLUGINSERVICE
capability_token_subclass PLUGINSERVICE
accesstransformer PLUGINSERVICE
runtimedistcleaner PLUGINSERVICE
mixin TRANSFORMATIONSERVICE
fml TRANSFORMATIONSERVICE
FML Language Providers:
<EMAIL_ADDRESS>javafml@null
Mod List:
client-1.18.2-20220404.173914-srg.jar             |Minecraft                     |minecraft                     |1.18.2              |ENQUEUE_IM|Manifest: a1:d4:5e:04:4f:d3:d6:e0:7b:37:97:cf:77:b0:de:ad:4a:47:ce:8c:96:49:5f:0a:cf:8c:ae:b2:6d:4b:8a:3f
easierchests-1.0.2.jar                            |EasierChests                  |easierchests                  |1.0.2               |ERROR     |Manifest: NOSIGNATURE
forge-1.18.2-40.1.31-universal.jar                |Forge                         |forge                         |40.1.31             |ENQUEUE_IM|Manifest: 84:ce:76:e8:45:35:e4:0e:63:86:df:47:59:80:0f:67:6c:c1:5f:6e:5f:4d:b3:54:47:1a:9f:7f:ed:5e:f2:90
Crash Report UUID: ebbaca9d-1ec8-406e-a325-c455898e7591
FML: 40.1
Forge: net.minecraftforge:40.1.31

got some more info on what you did to make it crash ?
looking into it at the moment and it seems the config file can't be read for some reason. more info would be welcome

got some more info on what you did to make it crash ? looking into it at the moment and it seems the config file can't be read for some reason. more info would be welcome

Hi there, thank you for looking into it for me!
I installed Forge fresh as I was using Fabric before this port because I love this mod. (tried latest version and previous versions of Forge). I dropped the .zip into my mods folder, selected the Forge profile on the Launcher. The Mojang loading screen when the game loads up hung on about ~90% then the next screen was the error. I'll see if I have any other logs I can provide, hopefully get to the bottom of it! :)

i managed to recreate the issue.
I deleted some entries from the config file and it gave me the same error.
try and delete your config file and let the mod generate a new one.
I higly recomand overwolf's curseforge app to take care of profiles and mod installation. they keep every profile apart so that no old files get mixed up with new ones, or incompatible ones, which I feel is the case here.
Once you deleted the config file and it worked, please come close the issue.
if it didnt , keep me posted

You absolute legend, that worked! Thank you SO much!
I did try Overwolf profile but it changed all my in-game settings and my world wasn't there etc so I just decided to do things manually. I'll definitely give it another go though.
Closing issue now and thanks again! Take care :)

glad that worked out!
regarding overwolf: yes, their profiles all make a new directory with a clean install. i think its handy. they probably have some setting somewhere to enable acommon save, but i never looked for it.
have fun with the mod !!


Create radboudumc.txt

This domain is part of the Radboud University (already present with ru.txt), specifically for students and teachers at the associated medical center. We provide a medical image analysis and machine learning course, now three years running:
2016:
https://sis.ru.nl/osiris-student/OnderwijsCatalogusSelect.do?selectie=cursus&collegejaar=2016&cursus=NWI-IMC037&taal=en
2017:
http://www.ru.nl/prospectus/socsci/courses-osiris/ai/nwi-imc037-intelligent-systems-medical-imaging/
2018:
https://sis.ru.nl/osiris-student/OnderwijsCatalogusSelect.do?selectie=cursus&cursus=NWI-IMC037&collegejaar=2018
Both teachers mentioned on the page have radboudumc.nl e-mail addresses:
<EMAIL_ADDRESS><EMAIL_ADDRESS>

@GeertLitjens Pull request merged. Thank you!


[2.5] Add OpenSearch Dashboards context to component and common folder …

Signed-off-by: Junqiu Lei<EMAIL_ADDRESS>Description
Add OpenSearch Dashboards context to component and common folder changes
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

wait for github actions to complete

Codecov Report

Merging #208 (b9d4b6d) into 2.5 (e9117ee) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              2.5     #208   +/-   ##
=======================================
  Coverage   87.42%   87.42%
=======================================
  Files           6        6
  Lines         175      175
  Branches       24       24
=======================================
  Hits          153      153
  Misses         16       16
  Partials        6        6

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Will also raise PR to merge to main and 2.x

It's a known issue that cypress test might failed on windows OS because of timeout find element.


Prepare 2.2.2 release

Codecov Report

:exclamation: No coverage uploaded for pull request base (2.2@e9212f7). Click here to learn what that means.
The diff coverage is 100%.

@@          Coverage Diff           @@
##             2.2    #6503   +/-   ##
======================================
  Coverage       ?   83.24%
  Complexity     ?    12823
======================================
  Files          ?     1483
  Lines          ?    48582
  Branches       ?     5916
======================================
  Hits           ?    40443
  Misses         ?     5387
  Partials       ?     2752

Impacted Files
Coverage Δ
Complexity Δ

core/src/main/java/io/crate/Version.java
71.42% <100%> (ø)
12 <0> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e9212f7...d1f0322. Read the comment docs.


Add missing ci test variables

With the recent switchover for ci tests to use matrix configurations, a couple test variables were not ported over correctly.

/azp run java - cosmos

/azp run java - core - ci


Auto-approving

Hi,
Would you be up for adding/supporting a feature of auto-approving new changes?
Imagine a scenario:

You have plenty of tests and you make a change which includes approving many changes
Some changes may even mean that "some approvals (files) should be removed and others created".

Which may mean:

You make your change and would want to just approve all changes.
You might even want to be able to:

rm -rf approvals/
Rerun your approvals.bash tests
Have all changes be auto-approved.

Hah, nice to see I was on a track that made sense. And thanks for really quick feedback and help. ❤

Merged. Thanks for the suggestion :)

Lovely. Will you make a release also? 🙏🏻

Of course. I am just working on another small update:

Adding it annotation, so we have the full "rspec compatible" context -> describe -> it chain
Reducing the color cacophony and changing all annotations to something unified.

Will be released today.

v0.5.1 is released.
If you have additional suggestions or issues, feel free to open another issue.


Updates to README, Travis, test coverage

Thanks @opiethehokie . I think that definitely clarifies usage in the readme and improving the test coverage is always welcome :tada:


add imports to code sample in REDME.md

Hi @manfredsteyer,
Great package!
I added updated import statements to code samples. That should help developers like myself to migrate from angular2-oauth2. Later, you can remove then, but now it cold be helpful.

It is not necessary to change it into "angular-oauth2-oidc/dist". The main file exported all the modules that we need ;). So you only need to import "angular-oauth2-oidc" instead of "angular-oauth2-oidc"

Thanks for this. There was also another PR that did the same.


Feature request - Generate Kubernetes Manifests

It would be extremely useful for ddev to produce Kubernetes manifests in addition to docker-compose yaml files when running ddev config. This would make it so much easier to deploy configurations into the local docker k8s or on minikube, as well as helping to deploy tested systems onto cloud-based k8s systems.

Well, I don't think it IS outside ddev's goals. K8s is where cloud computing container orchestration is going. The ideal dev environment mirrors, as much as possible, the environment that the software will eventually run in when deployed for production, so local dev environments are, or at least seem to be, heading toward Docker-embedded k8s or minikube, not raw docker containers orchestrated by docker-compose.

I vote for this because it can vital if you are forced to deploy on a company infrastructure and using hosters is no option.

This is not currently a part of our roadplan, so I'm going to close it for now. We always appreciate generous thinking and suggestions!


Coordinates for different gesture in real-time hand detection

Hello Mediapipe team,
I am working on hand gesture recognition using mediapipe in a real-time video in python although I was able to extract all the co-ordinates of each frame but I am unable to identify the range required for each (x,y&z) coordinates for different gestures like numbers(1,2,3..) or when palm is closed how the co-ordinates are changing.
Any help in how to understand and read co-ordinates for different gestures is valuable.
Thanks :)

Hi @shreyanshsatvik, Hand detection is clearly described here. Please go through it and reach us if you have any relevant request. Thanks!


Missing install guide for single machine or virtual machine instance

The best way to run Flynn on a development environment is described here: https://flynn.io/docs/installation/vagrant
However there's a "missing manual" on how to bootstrap Flynn on a single machine or virtual machine, for example running on Hyper-V or VMWare or bare-metal Linux server (non-clustered configuration) is missing.
The "Bootstrap Flynn" section in this manual https://flynn.io/docs/installation/manual does not seem to apply to Single machine instance (bare-metal or virtual machine)

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


add pytest.ini file or tool:pytest section in setup.cfg

(to be explicit about the test configuration)

Why do you think we need pytest.ini when we are not requiring anything special from pytest? We don't even have any command line options when calling pytest.
setup.cfg configures the behavior of the various setup commands when installing the project. You don't need pytest to install the Kernel Tuner, why do you think we should change this?

I prefer to be explicit about the test setup, even when the tool is using the default directory to look for tests, and the globbing pattern it's using is the default pattern.
I guess there are two schools of thought about this, some people think that as long as you're doing 'the normal thing' there's no need to be explicit about it. I disagree with this, because my normal thing may not be your normal thing. So, I'm firmly in one school, but if you are in the other, feel free to close the issue.


Docs for fs2 KCL should clarify call to consumer.commitRecords

First of all, thank you for a great library! I was able to use it to migrate an old KCL app still using v1 of the AWS KCL.
One hurdle I ran into, however, was that the docs for using the KCLConsumerFS2 show a call to consumer.commitRecords, so I added one in my code as well, thinking it was necessary. Only after testing and debugging did I find that the default config results in auto-committing. Ultimately this resulted in runtime errors when my manual commit occurred, because I was trying to commit a record that had already been committed by the auto-commit:
java.lang.IllegalArgumentException: Could not checkpoint at extended sequence number {SequenceNumber: XXXXX,SubsequenceNumber: 0} as it did not fall into acceptable range between the last checkpoint {SequenceNumber: YYYYY,SubsequenceNumber: 0} and the greatest extended sequence number passed to this record processor {SequenceNumber: YYYYY,SubsequenceNumber: 0}
	software.amazon.kinesis.checkpoint.ShardRecordProcessorCheckpointer.checkpoint(ShardRecordProcessorCheckpointer.java:124)
	kinesis4cats.kcl.CommittableRecord.$anonfun$checkpoint$1(CommittableRecord.scala:87)
	map @ kinesis4cats.compat.retry.package$.$anonfun$retryingOnSomeErrorsImpl$3(package.scala:103)
	map @ kinesis4cats.compat.retry.package$.$anonfun$retryingOnSomeErrorsImpl$3(package.scala:98)
	flatMap @ kinesis4cats.compat.retry.package$.$anonfun$retryingOnSomeErrorsImpl$2(package.scala:97)
	map2 @ fs2.Stream$.$anonfun$fromQueueUnterminated$1(Stream.scala:3540)
	map @ kinesis4cats.compat.retry.package$.applyPolicy(package.scala:116)
	flatMap @ kinesis4cats.compat.retry.package$.$anonfun$retryingOnSomeErrorsImpl$1(package.scala:96)

Do you think it would make sense to update the docs to clarify that calling consumer.commitRecords is not necessary unless you've explicitly changed the default RecordProcessor.Config behavior?

Sorry for the late response here. The default configuration for the FS2 consumer should have false for this, see the override here. How are you constructing your FS2 consumer? Can you give me a quick reproducible example?

No worries, thanks for getting back to me! I searched the repo and that defaultProcessConfig you linked to doesn't appear to be used anywhere.
I tested in a repl and can confirm that autoCommit is set to true when using KCLConsumerFS2.Builder.default. I had to do a bunch of reflection and asInstanceOfs to work around private class fields, so excuse that 😅
import cats.effect.IO
import cats.effect.unsafe.implicits.global
import kinesis4cats.kcl.RecordProcessor
import kinesis4cats.kcl.fs2.KCLConsumerFS2
import software.amazon.kinesis.common.{InitialPositionInStream, InitialPositionInStreamExtended}
import software.amazon.kinesis.processor.SingleStreamTracker

val consumer = KCLConsumerFS2.Builder.default[IO](
  streamTracker = new SingleStreamTracker(
    "test",
    InitialPositionInStreamExtended.newInitialPosition(InitialPositionInStream.TRIM_HORIZON),
  ),
  appName = "test",
).build

val fs2ConfField = classOf[KCLConsumerFS2[IO]].getDeclaredField("config")
fs2ConfField.setAccessible(true)

val processorFactory = consumer.use(c =>
  IO.pure(fs2ConfField.get(c).asInstanceOf[KCLConsumerFS2.Config[IO]].underlying.processorConfig.shardRecordProcessorFactory)
).unsafeRunSync().asInstanceOf[RecordProcessor.Factory[IO]]

val factoryConfField = classOf[RecordProcessor.Factory[IO]].getDeclaredField("config")
factoryConfField.setAccessible(true)

val conf = factoryConfField.get(processorFactory).asInstanceOf[RecordProcessor.Config]

conf.autoCommit // true

It looks like it might have gotten lost in 8ea14b623d37c4194294933a3bd12657d3e6ab28

Yep, that's exactly what happened. Good catch! I introduced #265 to resolve.

Resolved in #265


Inlaid Drawer component design

Provide designs for Inlaid Drawer using existing layout (parent-child, border layouts) and UI components, and Salt --spacing tokens for margins.
Document as examples.
Designs provide the basis for Pepper inlaid drawer patterns.

Waiting for a11y direction

Zazu Goal: M(5)

waiting for a11y feedback from Jared

Outstanding Decision

Should Inlaid drawer be a component ? (create issue for decision, pattern or component)

Kick off notes:
Two separate concerns:
Implement Inlaid Drawer somewhere in code as component.
Nav to do docs + specs + figma for component – Design work to be done by EOS (Zazu).
i.      To confirm what will be in component vs example (Josh)
ii.      Asmita to identify definitive ‘drawer’ requirements that Pepper need from Salt.
Build > Pepper dev to build (Thushara/Vineet) in Americano.
i.      T/V to confirm with Adrian whether unopinionated Inlaid Drawer is sufficient from Pepper, specifically:

Do Pepper actually need inlaid behaviour?
Pepper happy to build header/footer/main regions into Salt Drawer as Pepper component/pattern?

Asmita to follow up with Anh/Adrian/JJ Pepper implementation of Drawer (Salt to update as necessary).
Modal behaviour on Overlay Drawer (ability to interact with app underneath) is a separate issues.
Ben/Josh to align on follow-up with Jared.

Nav working on site docs, likely some overlap into Americano for reviews + final decisions on how we want to handle sizing (i.e. follow drawer, or provide S/M/L set sizes).
Characteristics complete, enough available for Pepper devs to make a start on build

Goal: ready for Dev by EOS

Figma assets merged (Salt 1 Light/Dark, Salt Next + figma guide)

Carryover to address ADA spec w/ Jake

Outstanding ADA questions addressed with Jake in figma spec. Closing ticket.


[Task]: Upgrade mongodb-java-driver up to 4.7

What needs to happen?
MongoDB 4.4 is reaching its EOL in February 2024 and the current driver officially - we've got it working with 4.4 just fine - only supports till 4.2.
Since I suppose that it's still nice-to-have compatibility with MongoDB 2.6 onwards, 4.7 is the one providing all the possible compatibility including legacy versions, all but 7.0 and 6.1.
https://github.com/apache/beam/blob/master/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L843
Issue Priority
Priority: 3 (nice-to-have improvement)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[X] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

.take-issue


fix: docker install

docker install

This looks good. Techincally the cpem add on module will STILL be broken after this PR, but this gets it closer to working by fixing the kubernetes and docker installs (the old k8s key was causing problems).


Variant "箆"

The character "箆" should be a variant of "篦".

I have just remembered there is another data source here. Besides, the format of this data is explained in another file in the same repository.

In Guangyun, 姊 is written as 𡛷.

In Guangyun, 姊 is written as 𡛷.

In Guangyun, 匆 is written as 怱.

In Guangyun, 樣 is written as 㨾.
(not to be confused by 样）


[feat] Link to exported member

You know how you can link to specific lines?
<EMAIL_ADDRESS>How about also the ability to link to exported members?
<EMAIL_ADDRESS>

Overcomplicated to implement for little benefit; should rather link to a docview symbol and one can view the source from the view source button


Fix github icon styles and add gitlab icon

Before:

After:

I wasn't able to run locally due to the following errors with both node 14 and node 16, which means I couldn't verify the gitlab icon... but the url for it looks snazzy 😬
❯ npx @11ty/eleventy --serve
[11ty] Problem writing Eleventy templates: (more in DEBUG output)
[11ty] Cannot read property '0' of undefined (via TypeError)
[11ty]
[11ty] Original error stack trace: TypeError: Cannot read property '0' of undefined
[11ty]     at /Users/charlie/Developer/11ty/11ty-website/node_modules/@11ty/eleventy/src/Plugins/Pagination.js:316:61
[11ty]     at Array.map (<anonymous>)
[11ty]     at Pagination.getPageTemplates (/Users/charlie/Developer/11ty/11ty-website/node_modules/@11ty/eleventy/src/Plugins/Pagination.js:316:41)
[11ty]     at Template.getTemplates (/Users/charlie/Developer/11ty/11ty-website/node_modules/@11ty/eleventy/src/Template.js:668:45)

Thank you!


resize logo and convert to jpg to support dark theme

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


BG canvas not updated on resize

It looks like the second canvas doesn't get updated while resizing the browser.

Not a real issue, I was using an outdated version of d3-fg


Add chan_dongle, googletts, speech-recog, and more

I had to use root user for Asterisk because otherwise it won't have permission to talk to USB. In fact, I wanted to do this earlier, because every single addon in HA also run as root so I see no concern in doing so. It even makes it more consistent.
I also dropped some lines that I was unsure about.
Fixes #125

@nanosonde if you can have a look at this one as well I would appreciate. :)

For me, this ready already. I'm using this since days now.

@felipecrs
I have already added some question.

@felipecrs
IMHO the way how you passthrough the serial devices is wrong.
You are supposed to use uart: true for this.
See the wellknown zigbee2mqtt addon: https://github.com/zigbee2mqtt/hassio-zigbee2mqtt/blob/master/zigbee2mqtt/config.json#L6

@nanosonde uart: true worked! Do you have any other concern about this PR?

Looks good to me!

Me too, can't wait to see your video! 🙂

We should disable chan_dongle by default in modules.conf.
It spams the log if there is no such HW.
Trying to connect on /dev/ttyUSB2...
[Mar 17 18:59:44] WARNING[615]: chan_dongle.c:229 opentty: unable to open /dev/ttyUSB2: No such file or directory
[Mar 17 18:59:59]     -- [dongle0] Trying to connect on /dev/ttyUSB2...
[Mar 17 18:59:59] WARNING[615]: chan_dongle.c:229 opentty: unable to open /dev/ttyUSB2: No such file or directory
[Mar 17 19:00:14]     -- [dongle0] Trying to connect on /dev/ttyUSB2...
[Mar 17 19:00:14] WARNING[615]: chan_dongle.c:229 opentty: unable to open /dev/ttyUSB2: No such file or directory
[Mar 17 19:00:29]     -- [dongle0] Trying to connect on /dev/ttyUSB2...
[Mar 17 19:00:29] WARNING[615]: chan_dongle.c:229 opentty: unable to open /dev/ttyUSB2: No such file or directory

Right. I agree.

I think we should expose it as an addon config, like: enable_chan_dongle, false by default.
WDYT?

Here is the video BTW: https://www.youtube.com/watch?v=15i9AqgfHNE
I know, the producing quality was ridiculous. But I just wanted to show it for you, quickly.

Very cool @felipecrs! This is very powerful. Guessing it's also possible to call outwards right?
I don't think we should use a option for it. Then you would have to make it a template file and it won't be possible to configure it yourself unless we do some hacky way like replace line or something.
Think it's best to edit the default modules.conf and add a section by usage in readme.


Revisit OptionsMonitor/ReloadableOptions/ChangeTracking

is there a deadline for this feature?
is there a way for now to reload options on configuration change?

Assigning to 1.1.0 after talking to @glennc about @DamianEdwards feedback on this.

@HaoK  I see that this is still needing design, but if this is something that can be worked on by the community I'd like to take a stab at this (or part of it).

[IUpdateableOptions].Value (name tweaking TBD)
Scoped cache of IOptionsMonitor.CurrentValue

We also decided that serviceCollection.Configure() extension method

How about IOptionsState instead of IUpdateableOptions giving us:
IOptions [Singleton permanent value]
IOptionsMonitor [Singleton permanent until notifications to trigger rebuild]
IOptionsState [ Captures the options state from the monitor for the scope of the request]
cc @davidfowl @DamianEdwards @Eilon

I prefer IOptionsSnapshot instead of IUpdatableOptions or IOptionsState.
cc @davidfowl @DamianEdwards @Eilon

Snapshot works for me as well

Not feeling it. Need to stew on it some more...

Boo.

I think it us a pretty good name but besides,  IOptionsSnapshot is the first name we have discussed that accurately reflects what it is and doesn't convey wrong expectations, e.g. you would not expect to be able to load or update the options value using an instance of this service.
Any problem if we go with it for an initial PR? We can keep looking and rename if we find something better.

Ok I admit it's actually growing on me (but that might just be the 🍺 talking). But yes a PR would be good anyway. Have plenty of time to rename if needed.

This is a ping to make everyone think about the name again. All the ideas I have had are technically incorrect for one reason or other. So I am hoping someone throws out something amazing... :)

Looking at what it does, I almost feels like an OptionsCache in that it holds a value that can be invalidated  base on a watcher or trigger. There isn't a timeout, but that would be easy to implement.
The problem is that the name OptionsCache is already used, but I think it is the thing with the wrong name.  It is really an OptionsBuilder/factory or DeferredOptionsBuilder.
Just my 2 cents.

I still positively like IOptionsSnapshot<TOptions>. I think @haok came up with it first. It is definitely just a snapshot of the options.

@DamianEdwards how's the stew taste now?

Go with Snapshot. It is the least bad of all the bad options. @DamianEdwards agrees.

acecacff57f9399e5871216a3f5a073548700dc3

I'm not sure if this is by design, but it's really confusing and just took me about an hour to debug. There are two different AddOptions extension methods in two different class libraries. In order to get this to work I had to reference Microsoft.Extensions.Options.ConfigurationExtensions in my project.json. Shouldn't there just be a single extension method for consistency?
Microsoft.Extensions.Options does not hook up the IOptionsMonitor
https://github.com/aspnet/Options/blob/rel/1.1.0-preview1/src/Microsoft.Extensions.Options/OptionsServiceCollectionExtensions.cs#L40
Microsoft.Extensions.Options.ConfigurationExtensions does:
https://github.com/aspnet/Options/blob/rel/1.1.0-preview1/src/Microsoft.Extensions.Options.ConfigurationExtensions/OptionsConfigurationServiceCollectionExtensions.cs#L22
Once I figured out the wrong method was being called, everything worked well.

Yes this is how things are supposed to work, unless you bind options to an configuration instance, there's no way for the monitoring to be set up.

Just to add to what @HaoK already said, keep in mind that configuration is right now the only sources of changes that Options knows about. If that changes in the future we may add sugar methods to register other IChangeTokenSource implementations.
Re the separate package for Microsoft.Extensions.OptionsConfigurationExtensions, that was done to reduce the coupling (see #97) between components that only need to depend on Options and packages in Configuration. We try to make it less confusing by adding the package in our default application templates whenever both Options and Configuration are included, but there might be cases in which we don't (and that may be a template bug).


Sysbox build attributes missing from "--version" output

I following the guide from here https://github.com/nestybox/sysbox/blob/master/docs/developers-guide/build.md, download the source code from the release page but it's failed when try to run make sysbox like this:
OS version: Ubuntu 18.04.5 LTS
Kernel version: 5.4.0-48-generic #52~18.04.1-Ubuntu SMP
** Building sysbox **

docker run --privileged --rm --hostname sysbox-build --name sysbox-build -v /root/sysbox-0.2.1:/root/nestybox/sysbox -v /root/go/pkg/mod:/go/pkg/mod -v /lib/modules/5.4.0-48-generic:/lib/modules/5.4.0-48-generic:ro -v /usr/src/:/usr/src/:ro -v /usr/src/:/usr/src/:ro sysbox-test /bin/bash -c "buildContainerInit sysbox-local"
cd sysbox-runc && make clean
make[1]: Entering directory '/root/nestybox/sysbox/sysbox-runc'
make[1]: Leaving directory '/root/nestybox/sysbox/sysbox-runc'
make[1]: *** No rule to make target 'clean'.  Stop.
Makefile:325: recipe for target 'clean' failed
make: *** [clean] Error 2
Makefile:110: recipe for target 'sysbox' failed
make: *** [sysbox] Error 2

@myugan, are you sure that you git-clone Sysbox making use of the "--recursive" flag as indicated in our doc? (we have a various repos within Sysbox project).
git clone --recursive git@github.com:nestybox/sysbox.git

Let me know if any problem.

Okay, I guess the source code will contain all of the code instead of --recursive flag using git command, and now it's working but when I try sysbox-runc -v there is and output only at oci-specs like this:
sysbox-runc
        version:
        commit:
        built at:
        built by:
        oci-specs:      1.0.2

is that ok?

Thanks @myugan, you have encountered a bug in our build-infrastructure logic, which is preventing these attributes (version/commit/build-at, etc) from being properly passed to the sysbox builder container. This was probably introduced a few weeks ago when we made some Makefile changes.
However, please keep in mind that none of this will impact Sysbox functionality, as we are dealing with a cosmetic issue here.
Btw, I'll go ahead and adjust this issue's title to reflect the problem that you just found. Please change it if you find a better title.

Hi @myugan,

However, please keep in mind that none of this will impact Sysbox functionality, as we are dealing with a cosmetic issue here.

Do you agree with @rodnymolina comment here? Or is this more than a cosmetic issue for you?

I'm agreed @ctalledo

Thanks @myugan ; let's leave the issue open and we will get to it soon (we definitely want to fix it). In the meantime let us know of any other issue you hit, we appreciate you trying Sysbox.

This was fixed back in 01/2021 and will be present in the upcoming 0.3.0 release.
root@sysbox-test:~/nestybox/sysbox# sysbox-runc --version
sysbox-runc
        version:        0.3.0-dev
        commit:         "0e845604d5f62365825df03b305f18eb706ccbb5"
        built at:
        built by:
        oci-specs:      1.0.2-dev
root@sysbox-test:~/nestybox/sysbox# sysbox-fs --version
sysbox-fs
        version:        0.3.0-dev
        commit:         "4fe6862a6d2114827f4977959b683101bf90a252"
        built at:
        built by:
root@sysbox-test:~/nestybox/sysbox# sysbox-mgr --version
sysbox-mgr
        version:        0.3.0-dev
        commit:         "95010ecb3e813d75ec8b523bd8f6d8890dfa26e6"
        built at:
        built by:

Closing.


In your Readme.md

RKObjectManager *manager = [RKObjectManager managerWithBaseURL:[NSURL URLWithString:@"http://restkit.org"];
should be
RKObjectManager *manager = [RKObjectManager managerWithBaseURL:[NSURL URLWithString:@"http://restkit.org"]];

Would love a PR fixing this!

https://github.com/RestKit/RestKit/pull/2168
Cheers!

Also, let me know if you are interested in another project collaborator - I've really enjoyed using restkit and wanna help out some more.

@voznesenskym I'm always happy to welcome new contributors to the project!

Great. Any outstanding big issues that need taking care of? Or small
bugs...? Or should I just look at issues?
On Thursday, February 19, 2015, Samuel E. Giddins<EMAIL_ADDRESS>wrote:

@voznesenskym https://github.com/voznesenskym I'm always happy to
welcome new contributors to the project!
—
Reply to this email directly or view it on GitHub
https://github.com/RestKit/RestKit/issues/2167#issuecomment-75019338.

All the issues are here on GitHub.


Please create additional "good first issues" to reach the suggested minimum of 15 by 9/15.

Is your feature request related to a problem? Please describe
Open Source Contributor Initiative (OSCI) launches on September 20th. Java client repo lacks the minimum of 15 "good first issues" that can be picked up by participants of OSCI.
Describe the solution you'd like
Please create additional "good first issues" to reach the suggested minimum of 15 by 9/15.
Describe alternatives you've considered
No response
Additional context
No response

Hi @rednaksi91 ,
This repository mainly concentrates on Jenkins CI/CD librarie so not many issues to create. If you feel these are not enough, please feel free to remove the repository from the program.
Thanks!
cc: @bbarani

Closing this issue.


403 error when accessing transmission GUI

Seeing the following message when accessing transmission via web:
403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.
If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

Transmission can take the settings from several places:

/etc/transmission-daemon/settings.json
~/.config/transmission-daemon/settings.json

The rpc-whitelist entry needs to contain the IP of the accessing machine. E.g:
"rpc-whitelist": "<IP_ADDRESS>,192.168.*.*"


Bump ansi-style dependency to ^2.2.0

The dependency to ansi-styles is ^2.1.0
After the unpublish of<EMAIL_ADDRESS>as result of this issue: https://github.com/chalk/ansi-styles/issues/15 chalk fails to build.
Please upgrade package.json to take the steps described in the post mortem: https://github.com/chalk/ansi-styles/issues/15#issuecomment-202589714

+1

Hi - I can do this, but it shouldn't be failing.
What errors are you facing?

@Qix- Thanks for looking into it. It was actually our shrinkwrap that was broken. No need to upgrade.
Closing this

Aha yeah, I think that's what's going to cause issues.
chalk/ansi-styles#17 addresses shrinkwrap. I've also released a new patch version with the updated dependency (landed in a838948dcbf2674dd28adfbb78e791900ae741e9).


Windows 11 testing

Hi,
I'm researching UAC bypasses to come up with the respective detection tradecraft and UACME caught my attention. The akagi release binary was produced as indicated in one of the previous issues:

initial build to generate the DLLs + Akagi binary
naka to generate AES keys
naka --stable to produce the secrets
rebuilt Akagi to embed the DLLs inside PE resource directory

The build output shows the resource compilation stage as below:
  Resource.rc.
  Writing ICON:1,       lang:0x409,     size 7336
  Writing ICON:2,       lang:0x409,     size 3240
  Writing GROUP_ICON:104,       lang:0x409,     size 34.
  Writing VERSION:1,    lang:0x409,     size 792.
  Writing RCDATA:100,   lang:0x409,     size 12336.
  Writing RCDATA:200,   lang:0x409,     size 10960.
  Writing RCDATA:103,   lang:0x409,     size 5520.
  Writing RCDATA:104,   lang:0x409,     size 8432.
  Writing RCDATA:300,   lang:0x409,     size 144

However, running the akagi binary doesn't seem to trigger any method, and I tried a dozen of them. The platform is Windows 11 build 22631. Windows Defender services disabled.
Do you have any clues? Is UACME still relevant in Windows 11?

If something doesn't work as you expected then open solution in MSVS, compile debug version and trace program code execution. Finally, show me your results.

Oddly, the binary generated in Debug mode does work as expected. I'm fine with this, so closing the issue. Thanks for the help!

That's weird, because executing a couple of methods resulted in spawning an elevated cmd. I'll try attaching the debugger and get back to you

Methods that doesn't require anything specific, e.g. registry manipulations, will work fine in all build configurations.

I'm exercising the elevated COM interface technique. Does it pertain to the category of simple methods you're calling out above?

Yes

The debugger is revealing the following exception raised in Akagi\stub.c line 75:
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2875

    Key  : Analysis.Elapsed.mSec
    Value: 24601

    Key  : Analysis.IO.Other.Mb
    Value: 8

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 30

    Key  : Analysis.Init.CPU.mSec
    Value: 93

    Key  : Analysis.Init.Elapsed.mSec
    Value: 36769

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 100

    Key  : Failure.Bucket
    Value: INTEGER_DIVIDE_BY_ZERO_c0000094_Akagi.exe!StubInit

    Key  : Failure.Hash
    Value: {2895f328-1204-a57e-8395-38364b51a212}

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 2740

    Key  : Timeline.Process.Start.DeltaSec
    Value: 36

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

    Key  : WER.Process.Version
    Value: <IP_ADDRESS>3

NTGLOBALFLAG:  70

APPLICATION_VERIFIER_FLAGS:  0

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff780323fbb (Akagi!StubInit+0x00000000000000bb)
   ExceptionCode: c0000094 (Integer divide-by-zero)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  00001d00

PROCESS_NAME:  Akagi.exe

ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

EXCEPTION_CODE_STR:  c0000094

STACK_TEXT:
000000e2`0f12f480 00007ff7`8030f597     : 00007ff7`8030674e 00000000`00000000 00000000`00000000 00000000`00000000 : Akagi!StubInit+0xbb
000000e2`0f12f650 00007ffa`c4b4257d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Akagi!main+0x27
000000e2`0f12f750 00007ffa`c5f8aa48     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x1d
000000e2`0f12f780 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28

FAULTING_SOURCE_LINE:  C:\<redacted>\UACME\Source\Akagi\stub.c

FAULTING_SOURCE_FILE:  C:\<redacted>\UACME\Source\Akagi\stub.c

FAULTING_SOURCE_LINE_NUMBER:  75

FAULTING_SOURCE_CODE:
    71:
    72:         __try {
    73:             v = (int)USER_SHARED_DATA->NtProductType;
    74:             d = (int)USER_SHARED_DATA->AlternativeArchitecture;
>   75:             v = (int)(v / d);
    76:         }
    77:         __except (ucmSehHandler(GetExceptionCode(), GetExceptionInformation())) {
    78:             v = 1;
    79:         }
    80:

SYMBOL_NAME:  Akagi!StubInit+bb

MODULE_NAME: Akagi

IMAGE_NAME:  Akagi.exe

STACK_COMMAND:  dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s ; .cxr ; kb

FAILURE_BUCKET_ID:  INTEGER_DIVIDE_BY_ZERO_c0000094_Akagi.exe!StubInit

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  <IP_ADDRESS>3

FAILURE_ID_HASH:  {2895f328-1204-a57e-8395-38364b51a212}

Followup:     MachineOwner
---------

I don't know if I need to comment this, if you don't understand the source.

Well, you asked me to trace the program's execution and let you know the results. I thought that may be insightful to you. However, if you think there is nothing actionable on your end, that's fine too.
Cheers


Roll engine 3b944102a56e..bcde838d778e (6 commits)

https://github.com/flutter/engine/compare/3b944102a56e...bcde838d778e
git log 3b944102a56e8f4182e6601113fc36538edf3de9..bcde838d778eecd39282cfb84ebba1d484bb7515 --no-merges --oneline
bcde838d7 Roll Wuffs and buildroot (flutter/engine#9791)
3b75979d3 fix ColorFilter.matrix constness (flutter/engine#9789)
3c9a22c77 Fall back to a fully qualified path to libapp.so if the library can not be loaded by name (flutter/engine#9762)
298a610c7 Roll fuchsia/sdk/core/mac-amd64 from XOXaWqvr4OuJ6O3uPefSwSFjZMaEmDHy5JQm3Q8Oc0wC to CDbRdGJ3bu-aWMCZqN5VzfQqIBwDGL2wfFodWABKdCIC (flutter/engine#9790)
833f6b4fc Roll src/third_party/skia f9fcf7ffa89a..7825d4983f90 (6 commits) (flutter/engine#9788)
1250c3773 Add comments to differentiate two cache paths (flutter/engine#9721)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (garyq@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


implement a flag --process-classless-ingress-v1beta1

Once #731 is implemented, a user should be able to change the behavior of the controller to be same as that in 0.9.0, which is, it will satisfy ingress resources which do not contain a kubernetes.io/ingress.class annotation.
The scope here:

come up with a better name for the flag, if you can't, use the one in the issue title
implement the flag (and corresponding behavior in the controller)
the default value for the flag should be false

For background, please see the doc in #690.

Modified community flag toggling the old behavior off to default to this in fb3ab86. The renamed flags flips the default behavior to not ingest classless ingresses, i.e. false.

Handled in #767.