L7 Ingress Policies not working for Azure CNI (Legacy) Chain mode

Is there an existing issue for this?

[X] I have searched the existing issues

Version
higher than v1.15.7 and lower than v1.16.0
What happened?
We have cilium 1.15.7 now deployed on Azure cluster 1.28.11 (Azure CNI - Legacy) in chain mode, running connectivity  test
Below tests are failing - that would indicate the L7 ingress policies are not supported in CNI chain mode, correct?
Test [echo-ingress-l7]
Test [echo-ingress-l7-named-port]
Test [echo-ingress-l7]
Test [echo-ingress-l7-named-port]to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))

$ kubectl get pods -n cilium-cnp --show-labels
NAME                        READY   STATUS    RESTARTS       AGE    LABELS
deathstar-b4b8ccfb5-dhfx2   1/1     Running   1 (129m ago)   138m   app.kubernetes.io/name=deathstar,class=deathstar,org=empire,pod-template-hash=b4b8ccfb5
frontend-7d5698c6bb-6bc9j   1/1     Running   0              31m    app.kubernetes.io/name=frontend,app=demo,pod-template-hash=7d5698c6bb,tier=frontend
frontend-7d5698c6bb-pxwpx   1/1     Running   0              31m    app.kubernetes.io/name=frontend,app=demo,pod-template-hash=7d5698c6bb,tier=frontend
tiefighter                  1/1     Running   1 (109m ago)   138m   app.kubernetes.io/name=tiefighter,class=tiefighter,org=empire
xwing                       1/1     Running   0              138m   app.kubernetes.io/name=xwing,class=xwing,org=alliance

$ cat l7-cnp.yaml
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
  name: allow-empire-in-namespace
  namespace: cilium-cnp
spec:
  endpointSelector:
    matchLabels:
      org: empire
      class: deathstar
  ingress:
  - fromEndpoints:
    - matchLabels:
        org: empire
        class: tiefighter
    toPorts:
    - ports:
      - port: "80"
        protocol: TCP
      rules:
        http:
        - method: "POST"
          path: "/v1/request-landing"
  - fromEndpoints:
    - matchLabels:
        org: empire
        class: maintenance-droid
    toPorts:
    - ports:
      - port: "80"
        protocol: TCP
      rules:
        http:
        - method: "PUT"
          path: "/v1/exhaust-port"

---
$ kubectl exec tiefighter -n cilium-cnp -- curl -s -XPOST deathstar.cilium-cnp.svc.cluster.local/v1/request-landing

$ hubble observe -f -n cilium-cnp
Jul 24 21:30:37.557: cilium-cnp/tiefighter:52684 (ID:34775) -> cilium-cnp/deathstar-b4b8ccfb5-dhfx2:80 (ID:5038) to-stack FORWARDED (TCP Flags: SYN)
Jul 24 21:30:37.558: cilium-cnp/tiefighter:52684 (ID:34775) -> cilium-cnp/deathstar-b4b8ccfb5-dhfx2:80 (ID:5038) to-proxy FORWARDED (TCP Flags: SYN)
Jul 24 21:30:37.559: <IP_ADDRESS> (remote-node) -> cilium-cnp/tiefighter (ID:34775) to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))
---

$ kubectl exec tiefighter -n cilium-cnp -- curl -s -v -XPUT deathstar.cilium-cnp.svc.cluster.local/v1/request-landing
*   Trying <IP_ADDRESS>:80...

$ hubble observe -f -n cilium-cnp
Jul 24 21:18:06.709: cilium-cnp/tiefighter:35606 (ID:34775) -> cilium-cnp/deathstar-b4b8ccfb5-4rrzk:80 (ID:5038) to-proxy FORWARDED (TCP Flags: SYN)
Jul 24 21:18:06.709: cilium-cnp/tiefighter:35606 (ID:34775) -> cilium-cnp/deathstar-b4b8ccfb5-4rrzk:80 (ID:5038) to-stack FORWARDED (TCP Flags: SYN)
Jul 24 21:18:06.714: <IP_ADDRESS> (remote-node) -> cilium-cnp/tiefighter (ID:34775) to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))
---

$ kubectl exec tiefighter -n cilium-cnp -- curl -s -v -XPUT deathstar.cilium-cnp.svc.cluster.local/v1/exhaust-port
*   Trying <IP_ADDRESS>:80...
Jul 24 21:18:48.885: cilium-cnp/tiefighter:36134 (ID:34775) -> cilium-cnp/deathstar-b4b8ccfb5-dhfx2:80 (ID:5038) to-proxy FORWARDED (TCP Flags: SYN)
Jul 24 21:18:48.886: <IP_ADDRESS> (remote-node) -> cilium-cnp/tiefighter (ID:34775) to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))
Jul 24 21:18:56.121: cilium-cnp/tiefighter:36134 (ID:34775) -> cilium-cnp/deathstar-b4b8ccfb5-dhfx2:80 (ID:5038) to-stack FORWARDED (TCP Flags: SYN)
Jul 24 21:18:56.122: cilium-cnp/tiefighter:36134 (ID:34775) -> cilium-cnp/deathstar-b4b8ccfb5-dhfx2:80 (ID:5038) to-proxy FORWARDED (TCP Flags: SYN)
Jul 24 21:18:56.123: <IP_ADDRESS> (remote-node) -> cilium-cnp/tiefighter (ID:34775) to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))

I see docs points to https://docs.cilium.io/en/stable/security/policy/language/#l7-policy and I can confirm same setup working in aws but not in Azure.
How can we reproduce the issue?
Install cilium 1.15.7 on AKS cluster with legacy CNI in chain mode, run connectivity test
Cilium Version
1.15.7
Kernel Version
5.15.0-1067-azure #76-Ubuntu SMP Wed Jun 12 18:19:38 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
1.28.11
Regression
No response
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Cilium Users Document

[X] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

We have had issues with chaining and L7 policy; it can be unreliable in AWS. I don't know enough about the Azure stack to know what the issue may be, but we can start to dive in.
Can you please capture a sysdump after issuing some affected traffic? The Hubble flows will be very useful in diagnosing this.

Hope below can help :)
$ kubectl get cnp -n cilium-l7-envoy
NAME    AGE
rule1   42h

$ kubectl get cnp rule1 -n cilium-l7-envoy -oyaml
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"cilium.io/v2","kind":"CiliumNetworkPolicy","metadata":{"annotations":{},"name":"rule1","namespace":"cilium-l7-envoy"},"spec":{"description":"L7 policy to restrict access to specific HTTP call","endpointSelector":{"matchLabels":{"class":"deathstar","org":"empire"}},"ingress":[{"fromEndpoints":[{"matchLabels":{"org":"empire"}}],"toPorts":[{"ports":[{"port":"80","protocol":"TCP"}],"rules":{"http":[{"method":"POST","path":"/v1/request-landing"}]}}]}]}}
  creationTimestamp: "2024-07-25T14:13:34Z"
  generation: 2
  name: rule1
  namespace: cilium-l7-envoy
  resourceVersion: "4225677"
  uid: ca1a3ba1-b91b-4e24-8ff5-bb72e6ad3d54
spec:
  description: L7 policy to restrict access to specific HTTP call
  endpointSelector:
    matchLabels:
      class: deathstar
      org: empire
  ingress:
  - fromEndpoints:
    - matchLabels:
        org: empire
    toPorts:
    - ports:
      - port: "80"
        protocol: TCP
      rules:
        http:
        - method: POST
          path: /v1/request-landing

$ kubectl get pods -n cilium-l7-envoy --show-labels
NAME                        READY   STATUS    RESTARTS      AGE   LABELS
deathstar-b4b8ccfb5-7hvkh   1/1     Running   1 (42h ago)   43h   app.kubernetes.io/name=deathstar,class=deathstar,org=empire,pod-template-hash=b4b8ccfb5
deathstar-b4b8ccfb5-v784c   1/1     Running   0             43h   app.kubernetes.io/name=deathstar,class=deathstar,org=empire,pod-template-hash=b4b8ccfb5
tiefighter                  1/1     Running   0             43h   app.kubernetes.io/name=tiefighter,class=tiefighter,org=empire
xwing                       1/1     Running   0             43h   app.kubernetes.io/name=xwing,class=xwing,org=alliance

$ kubectl get pods -n cilium-l7-envoy --show-labels -owide
NAME                        READY   STATUS    RESTARTS      AGE   IP              NODE                           NOMINATED NODE   READINESS GATES   LABELS
deathstar-b4b8ccfb5-7hvkh   1/1     Running   1 (42h ago)   43h   <IP_ADDRESS>   aks-wrk1-12565003-vmss000003   <none>           <none>            app.kubernetes.io/name=deathstar,class=deathstar,org=empire,pod-template-hash=b4b8ccfb5
deathstar-b4b8ccfb5-v784c   1/1     Running   0             43h   <IP_ADDRESS>   aks-wrk1-12565003-vmss000001   <none>           <none>            app.kubernetes.io/name=deathstar,class=deathstar,org=empire,pod-template-hash=b4b8ccfb5
tiefighter                  1/1     Running   0             43h   <IP_ADDRESS>   aks-wrk1-12565003-vmss000000   <none>           <none>            app.kubernetes.io/name=tiefighter,class=tiefighter,org=empire
xwing                       1/1     Running   0             43h   <IP_ADDRESS>    aks-wrk1-12565003-vmss000003   <none>           <none>            app.kubernetes.io/name=xwing,class=xwing,org=alliance

$ kubectl exec tiefighter -n cilium-l7-envoy -- curl -s -X POST deathstar.cilium-l7-envoy.svc.cluster.local/v1/request-landing
command terminated with exit code 28

$ hubble observe -f -n cilium-l7-envoy
Jul 27 09:10:17.645: cilium-l7-envoy/tiefighter:45929 (ID:42959) -> kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.647: cilium-l7-envoy/tiefighter:45929 (ID:42959) <- kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.647: cilium-l7-envoy/tiefighter:39056 (ID:42959) -> kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.649: cilium-l7-envoy/tiefighter:39056 (ID:42959) <- kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.649: cilium-l7-envoy/tiefighter:44254 (ID:42959) -> kube-system/coredns-68c5c6b8b5-27h5c:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.651: cilium-l7-envoy/tiefighter:44254 (ID:42959) <- kube-system/coredns-68c5c6b8b5-27h5c:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.651: cilium-l7-envoy/tiefighter:35847 (ID:42959) -> kube-system/coredns-68c5c6b8b5-27h5c:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.652: cilium-l7-envoy/tiefighter:45929 (ID:42959) -> kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.652: cilium-l7-envoy/tiefighter:45929 (ID:42959) <- kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.654: cilium-l7-envoy/tiefighter:39056 (ID:42959) -> kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.654: cilium-l7-envoy/tiefighter:39056 (ID:42959) <- kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.655: cilium-l7-envoy/tiefighter:35847 (ID:42959) <- kube-system/coredns-68c5c6b8b5-27h5c:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.656: cilium-l7-envoy/tiefighter:44254 (ID:42959) -> kube-system/coredns-68c5c6b8b5-27h5c:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.656: cilium-l7-envoy/tiefighter:44254 (ID:42959) <- kube-system/coredns-68c5c6b8b5-27h5c:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.656: cilium-l7-envoy/tiefighter:43500 (ID:42959) -> kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.657: cilium-l7-envoy/tiefighter:35847 (ID:42959) -> kube-system/coredns-68c5c6b8b5-27h5c:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.658: cilium-l7-envoy/tiefighter:43500 (ID:42959) <- kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.658: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-stack FORWARDED (TCP Flags: SYN)
Jul 27 09:10:17.660: <IP_ADDRESS> (remote-node) -> cilium-l7-envoy/tiefighter (ID:42959) to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))
Jul 27 09:10:17.660: cilium-l7-envoy/tiefighter:35847 (ID:42959) <- kube-system/coredns-68c5c6b8b5-27h5c:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.663: cilium-l7-envoy/tiefighter:43500 (ID:42959) -> kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-endpoint FORWARDED (UDP)
Jul 27 09:10:17.663: cilium-l7-envoy/tiefighter:43500 (ID:42959) <- kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 09:10:17.664: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) policy-verdict:L3-L4 INGRESS ALLOWED (TCP Flags: SYN)
Jul 27 09:10:17.665: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-proxy FORWARDED (TCP Flags: SYN)
Jul 27 09:10:24.884: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-stack FORWARDED (TCP Flags: SYN)
Jul 27 09:10:24.886: <IP_ADDRESS> (remote-node) -> cilium-l7-envoy/tiefighter (ID:42959) to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))
Jul 27 09:10:24.891: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-proxy FORWARDED (TCP Flags: SYN)
Jul 27 09:10:33.076: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-stack FORWARDED (TCP Flags: SYN)
Jul 27 09:10:33.080: <IP_ADDRESS> (remote-node) -> cilium-l7-envoy/tiefighter (ID:42959) to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))
Jul 27 09:10:33.083: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-proxy FORWARDED (TCP Flags: SYN)
Jul 27 09:10:49.208: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-stack FORWARDED (TCP Flags: SYN)
Jul 27 09:10:49.210: <IP_ADDRESS> (remote-node) -> cilium-l7-envoy/tiefighter (ID:42959) to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))
Jul 27 09:10:49.215: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-proxy FORWARDED (TCP Flags: SYN)
Jul 27 09:11:22.996: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-stack FORWARDED (TCP Flags: SYN)
Jul 27 09:11:22.998: <IP_ADDRESS> (remote-node) -> cilium-l7-envoy/tiefighter (ID:42959) to-endpoint FORWARDED (ICMPv4 TimeExceeded(TTLExceeded))
Jul 27 09:11:23.003: cilium-l7-envoy/tiefighter:33874 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-v784c:80 (ID:30147) to-proxy FORWARDED (TCP Flags: SYN)

$ kubectl get nodes -owide
NAME                           STATUS   ROLES   AGE     VERSION    INTERNAL-IP     EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
aks-wrk0-62684821-vmss000000   Ready    agent   2d20h   v1.28.11   <IP_ADDRESS>   <none>        Ubuntu 22.04.4 LTS   5.15.0-1067-azure   containerd://1.7.15-1
aks-wrk0-62684821-vmss000001   Ready    agent   2d20h   v1.28.11   <IP_ADDRESS>   <none>        Ubuntu 22.04.4 LTS   5.15.0-1067-azure   containerd://1.7.15-1
aks-wrk0-62684821-vmss000002   Ready    agent   2d20h   v1.28.11   <IP_ADDRESS>     <none>        Ubuntu 22.04.4 LTS   5.15.0-1067-azure   containerd://1.7.15-1
aks-wrk1-12565003-vmss000000   Ready    agent   2d20h   v1.28.11   <IP_ADDRESS>    <none>        Ubuntu 22.04.4 LTS   5.15.0-1067-azure   containerd://1.7.15-1
aks-wrk1-12565003-vmss000001   Ready    agent   2d20h   v1.28.11   <IP_ADDRESS>   <none>        Ubuntu 22.04.4 LTS   5.15.0-1067-azure   containerd://1.7.15-1
aks-wrk1-12565003-vmss000003   Ready    agent   2d20h   v1.28.11   <IP_ADDRESS>   <none>        Ubuntu 22.04.4 LTS   5.15.0-1067-azure   containerd://1.7.15-1

$ cilium status
    /¯¯\
 /¯¯\__/¯¯\    Cilium:             OK
 \__/¯¯\__/    Operator:           OK
 /¯¯\__/¯¯\    Envoy DaemonSet:    OK
 \__/¯¯\__/    Hubble Relay:       OK
    \__/       ClusterMesh:        disabled

Deployment             hubble-relay       Desired: 1, Ready: 1/1, Available: 1/1
DaemonSet              cilium             Desired: 6, Ready: 6/6, Available: 6/6
Deployment             cilium-operator    Desired: 2, Ready: 2/2, Available: 2/2
DaemonSet              cilium-envoy       Desired: 6, Ready: 6/6, Available: 6/6
Deployment             hubble-ui          Desired: 1, Ready: 1/1, Available: 1/1
Containers:            cilium-operator    Running: 2
                       cilium-envoy       Running: 6
                       cilium             Running: 6
                       hubble-ui          Running: 1
                       hubble-relay       Running: 1
Cluster Pods:          102/102 managed by Cilium
Helm chart version:
Image versions         cilium             quay.io/cilium/cilium:v1.15.7@sha256:2e432bf6879feb8b891c497d6fd784b13e53456017d2b8e4ea734145f0282ef0: 6
                       hubble-ui          quay.io/cilium/hubble-ui:v0.13.1@sha256:e2e9313eb7caf64b0061d9da0efbdad59c6c461f6ca1752768942bfeda0796c6: 1
                       hubble-ui          quay.io/cilium/hubble-ui-backend:v0.13.1@sha256:0e0eed917653441fded4e7cdb096b7be6a3bddded5a2dd10812a27b1fc6ed95b: 1
                       hubble-relay       quay.io/cilium/hubble-relay:v1.15.7@sha256:12870e87ec6c105ca86885c4ee7c184ece6b706cc0f22f63d2a62a9a818fd68f: 1
                       cilium-operator    quay.io/cilium/operator-generic:v1.15.7@sha256:6840a6dde703b3e73dd31e03390327a9184fcb888efbad9d9d098d65b9035b54: 2
                       cilium-envoy       quay.io/cilium/cilium-envoy:v1.29.7-39a2a56bbd5b3a591f69dbca51d3e30ef97e0e51@sha256:bd5ff8c66716080028f414ec1cb4f7dc66f40d2fb5a009fff187f4a9b90b566b: 6

Check cilium agent on node <IP_ADDRESS>
# cilium status --verbose
KVStore:                Ok   Disabled
Kubernetes:             Ok   1.28 (v1.28.11) [linux/amd64]
Kubernetes APIs:        ["EndpointSliceOrEndpoint", "cilium/v2::CiliumClusterwideEnvoyConfig", "cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumEndpoint", "cilium/v2::CiliumEnvoyConfig", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNod
e", "cilium/v2alpha1::CiliumCIDRGroup", "core/v1::Namespace", "core/v1::Pods", "core/v1::Secrets", "core/v1::Service", "networking.k8s.io/v1::NetworkPolicy"]
KubeProxyReplacement:   False   [eth0   <IP_ADDRESS> fe80::222:48ff:fe23:fe53 (Direct Routing)]
Host firewall:          Disabled
SRv6:                   Disabled
CNI Chaining:           generic-veth
CNI Config file:        successfully wrote CNI configuration file to /host/etc/cni/net.d/05-cilium.conflist
Cilium:                 Ok   1.15.7 (v1.15.7-de06bcfb)
NodeMonitor:            Listening for events on 4 CPUs with 64x4096 of shared memory
Cilium health daemon:   Ok
IPAM:                   IPv4: 2/254 allocated from <IP_ADDRESS>/24,
Allocated addresses:
  <IP_ADDRESS> (router)
  <IP_ADDRESS> (ingress)
IPv4 BIG TCP:           Disabled
IPv6 BIG TCP:           Disabled
BandwidthManager:       Disabled
Host Routing:           Legacy
Masquerading:           Disabled
Clock Source for BPF:   ktime
Controller Status:      122/122 healthy
  Name                                                                   Last success    Last error     Count   Message
  dns-garbage-collector-job                                              58s ago         never          0       no error
  endpoint-1095-regeneration-recovery                                    never           never          0       no error
  endpoint-1167-regeneration-recovery                                    never           never          0       no error
  endpoint-1453-regeneration-recovery                                    never           never          0       no error
  endpoint-1680-regeneration-recovery                                    never           never          0       no error
  endpoint-1741-regeneration-recovery                                    never           never          0       no error
  endpoint-1777-regeneration-recovery                                    never           never          0       no error
  endpoint-192-regeneration-recovery                                     never           never          0       no error
  endpoint-2011-regeneration-recovery                                    never           never          0       no error
  endpoint-2135-regeneration-recovery                                    never           never          0       no error
  endpoint-2511-regeneration-recovery                                    never           never          0       no error
  endpoint-2625-regeneration-recovery                                    never           never          0       no error
  endpoint-2679-regeneration-recovery                                    never           never          0       no error
  endpoint-274-regeneration-recovery                                     never           never          0       no error
  endpoint-604-regeneration-recovery                                     never           never          0       no error
  endpoint-820-regeneration-recovery                                     never           never          0       no error
  endpoint-86-regeneration-recovery                                      never           never          0       no error
  endpoint-890-regeneration-recovery                                     never           never          0       no error
  endpoint-921-regeneration-recovery                                     never           never          0       no error
  endpoint-977-regeneration-recovery                                     never           never          0       no error
  endpoint-980-regeneration-recovery                                     never           never          0       no error
  endpoint-gc                                                            4m0s ago        never          0       no error
  ep-bpf-prog-watchdog                                                   10s ago         never          0       no error
  fqdn-selector-checkpointing                                            60h11m39s ago   never          0       no error
  ipcache-inject-labels                                                  55s ago         61h44m1s ago   0       no error
  k8s-heartbeat                                                          5s ago          never          0       no error
  link-cache                                                             12s ago         never          0       no error
  neighbor-table-refresh                                                 24s ago         never          0       no error
  resolve-identity-1095                                                  1m3s ago        never          0       no error
  resolve-identity-2011                                                  1m35s ago       never          0       no error
  resolve-identity-2135                                                  1m3s ago        never          0       no error
  resolve-identity-86                                                    4m41s ago       never          0       no error
  resolve-identity-890                                                   3m59s ago       never          0       no error
  resolve-identity-921                                                   1m3s ago        never          0       no error
  resolve-labels-/                                                       61h43m59s ago   never          0       no error
  resolve-labels-cert-manager/cert-manager-cainjector-64588d6c98-nrpct   61h43m59s ago   never          0       no error
  resolve-labels-cilium-cnp/backend-7f97787866-4v2hb                     60h31m4s ago    never          0       no error
  resolve-labels-cilium-cnp/database-f5ff47946-mfmfs                     60h31m3s ago    never          0       no error
  resolve-labels-cilium-cnp/deathstar-b4b8ccfb5-dhfx2                    61h43m54s ago   never          0       no error
  resolve-labels-cilium-cnp/frontend-7d5698c6bb-pxwpx                    60h31m3s ago    never          0       no error
  resolve-labels-cilium-cnp/xwing                                        61h43m56s ago   never          0       no error
  resolve-labels-cilium-l7-envoy/deathstar-b4b8ccfb5-v784c               43h9m41s ago    never          0       no error
  resolve-labels-cilium-mauth/deathstar-b4b8ccfb5-5rf4q                  44h41m36s ago   never          0       no error
  resolve-labels-datadog-system/datadog-5f78z                            61h43m56s ago   never          0       no error
  resolve-labels-ingress-nginx/nginx-controller-frkt4                    61h43m59s ago   never          0       no error
  resolve-labels-k6-loadtesting/nginx-deployment-58c48cf57b-b2pwn        61h43m56s ago   never          0       no error
  resolve-labels-kube-system/coredns-68c5c6b8b5-27h5c                    61h43m56s ago   never          0       no error
  resolve-labels-kube-system/coredns-68c5c6b8b5-hj252                    61h43m56s ago   never          0       no error
  resolve-labels-kube-system/coredns-autoscaler-7d96ccd8d-r99gv          61h43m56s ago   never          0       no error
  resolve-labels-kube-system/metrics-server-656954cb78-jh4rk             61h43m59s ago   never          0       no error
  resolve-labels-kube-system/metrics-server-656954cb78-q4wzr             61h43m56s ago   never          0       no error
  resolve-labels-kube-system/microsoft-defender-collector-ds-rh2xh       61h43m56s ago   never          0       no error
  resolve-labels-kube-system/microsoft-defender-publisher-ds-cbvbb       61h43m59s ago   never          0       no error
  restoring-ep-identity (1167)                                           61h43m59s ago   never          0       no error
  restoring-ep-identity (1453)                                           61h43m59s ago   never          0       no error
  restoring-ep-identity (1680)                                           61h43m59s ago   never          0       no error
  restoring-ep-identity (1741)                                           61h43m59s ago   never          0       no error
  restoring-ep-identity (1777)                                           61h43m59s ago   never          0       no error
  restoring-ep-identity (192)                                            61h43m59s ago   never          0       no error
  restoring-ep-identity (2511)                                           61h43m59s ago   never          0       no error
  restoring-ep-identity (2625)                                           61h43m59s ago   never          0       no error
  restoring-ep-identity (2679)                                           61h43m59s ago   never          0       no error
  restoring-ep-identity (274)                                            61h43m59s ago   never          0       no error
  restoring-ep-identity (604)                                            61h43m59s ago   never          0       no error
  restoring-ep-identity (820)                                            61h43m59s ago   never          0       no error
  restoring-ep-identity (977)                                            61h43m59s ago   never          0       no error
  restoring-ep-identity (980)                                            61h43m59s ago   never          0       no error
  sync-host-ips                                                          55s ago         never          0       no error
  sync-lb-maps-with-k8s-services                                         61h43m59s ago   never          0       no error
  sync-policymap-1095                                                    1m3s ago        never          0       no error
  sync-policymap-1167                                                    13m56s ago      never          0       no error
  sync-policymap-1453                                                    13m56s ago      never          0       no error
  sync-policymap-1680                                                    13m53s ago      never          0       no error
  sync-policymap-1741                                                    13m56s ago      never          0       no error
  sync-policymap-1777                                                    13m55s ago      never          0       no error
  sync-policymap-192                                                     13m56s ago      never          0       no error
  sync-policymap-2011                                                    11m35s ago      never          0       no error
  sync-policymap-2135                                                    1m3s ago        never          0       no error
  sync-policymap-2511                                                    13m56s ago      never          0       no error
  sync-policymap-2625                                                    13m55s ago      never          0       no error
  sync-policymap-2679                                                    13m56s ago      never          0       no error
  sync-policymap-274                                                     13m56s ago      never          0       no error
  sync-policymap-604                                                     13m56s ago      never          0       no error
  sync-policymap-820                                                     13m54s ago      never          0       no error
  sync-policymap-86                                                      9m41s ago       never          0       no error
  sync-policymap-921                                                     1m3s ago        never          0       no error
  sync-policymap-977                                                     13m56s ago      never          0       no error
  sync-policymap-980                                                     13m55s ago      never          0       no error
  sync-to-k8s-ciliumendpoint (1095)                                      7s ago          never          0       no error
  sync-to-k8s-ciliumendpoint (1167)                                      12s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (1453)                                      12s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (1741)                                      11s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (1777)                                      11s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (192)                                       11s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (2011)                                      3s ago          never          0       no error
  sync-to-k8s-ciliumendpoint (2135)                                      6s ago          never          0       no error
  sync-to-k8s-ciliumendpoint (2511)                                      11s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (2625)                                      11s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (2679)                                      11s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (274)                                       11s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (604)                                       12s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (820)                                       11s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (86)                                        9s ago          never          0       no error
  sync-to-k8s-ciliumendpoint (921)                                       7s ago          never          0       no error
  sync-to-k8s-ciliumendpoint (977)                                       12s ago         never          0       no error
  sync-to-k8s-ciliumendpoint (980)                                       11s ago         never          0       no error
  sync-utime                                                             56s ago         never          0       no error
  template-dir-watcher                                                   never           never          0       no error
  waiting-initial-global-identities-ep (1167)                            61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (1453)                            61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (1741)                            61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (1777)                            61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (192)                             61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (2511)                            61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (2625)                            61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (2679)                            61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (274)                             61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (604)                             61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (820)                             61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (977)                             61h43m59s ago   never          0       no error
  waiting-initial-global-identities-ep (980)                             61h43m59s ago   never          0       no error
  write-cni-file                                                         61h44m1s ago    never          0       no error
Proxy Status:   OK, ip <IP_ADDRESS>, 3 redirects active on ports 10000-20000, Envoy: external
  Protocol              Redirect             Proxy Port
  cilium-dns-egress     1095:egress:UDP:53   46093
  cilium-http-ingress   820:ingress:TCP:80   13735
  cilium-http-ingress   86:ingress:TCP:80    13735
Global Identity Range:   min 256, max 65535
Hubble:                  Ok   Current/Max Flows: 4095/4095 (100.00%), Flows/s: 48.30   Metrics: Ok
KubeProxyReplacement Details:
  Status:                 False
  Socket LB:              Disabled
  Socket LB Tracing:      Disabled
  Socket LB Coverage:     Full
  Devices:                eth0   <IP_ADDRESS> fe80::222:48ff:fe23:fe53 (Direct Routing)
  Mode:                   SNAT
  Backend Selection:      Random
  Session Affinity:       Disabled
  Graceful Termination:   Enabled
  NAT46/64 Support:       Disabled
  XDP Acceleration:       Disabled
  Services:
  - ClusterIP:      Enabled
  - NodePort:       Enabled (Range: 30000-32767)
  - LoadBalancer:   Enabled
  - externalIPs:    Disabled
  - HostPort:       Disabled
BPF Maps:   dynamic sizing: on (ratio: 0.002500)
  Name                          Size
  Auth                          524288
  Non-TCP connection tracking   73541
  TCP connection tracking       147083
  Endpoint policy               65535
  IP cache                      512000
  IPv4 masquerading agent       16384
  IPv6 masquerading agent       16384
  IPv4 fragmentation            8192
  IPv4 service                  65536
  IPv6 service                  65536
  IPv4 service backend          65536
  IPv6 service backend          65536
  IPv4 service reverse NAT      65536
  IPv6 service reverse NAT      65536
  Metrics                       1024
  NAT                           147083
  Neighbor table                147083
  Global policy                 16384
  Session affinity              65536
[cilium-sysdump-20240727-023616.zip](https://github.com/user-attachments/files/16398943/cilium-sysdump-20240727-023616.zip)

  Sock reverse NAT              73541
  Tunnel                        65536
Encryption:       Wireguard   [NodeEncryption: Disabled, cilium_wg0 (Pubkey: 0ubW5TQ/ZN3LyCu/bPLe/7DOdMVCUudc71pdIS6XHW4=, Port: 51871, Peers: 5)]
Cluster health:               Probe disabled

cilium-sysdump-20240727-023616.zip

more info here egress policy is working as expected
apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: "rule1"
spec:
  description: "L7 policy to restrict access to specific HTTP call"
  endpointSelector:
    matchLabels:
      org: empire
  egress:
  # Allow DNS traffic
  - toPorts:
    - ports:
      - port: "53"
        protocol: UDP
      - port: "53"
        protocol: TCP
  - toEndpoints:
    - matchLabels:
        org: empire
    toPorts:
    - ports:
      - port: "80"
        protocol: TCP
      rules:
        http:
        - method: "POST"
          path: "/v1/request-landing"

$ kubectl apply -f l7-policy-egress.yaml -n cilium-l7-envoy

$ kubectl exec xwing -n cilium-l7-envoy -- curl -s -X POST deathstar.cilium-l7-envoy.svc.cluster.local/v1/request-landing
Ship landed

Jul 27 17:53:23.431: cilium-l7-envoy/tiefighter:51964 (ID:42959) -> kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) policy-verdict:L4-Only EGRESS ALLOWED (UDP)
Jul 27 17:53:23.431: cilium-l7-envoy/tiefighter:51964 (ID:42959) -> kube-system/coredns-68c5c6b8b5-hj252:53 (ID:50286) to-stack FORWARDED (UDP)
Jul 27 17:53:23.431: cilium-l7-envoy/tiefighter:38364 (ID:42959) <- cilium-l7-envoy/deathstar-b4b8ccfb5-7hvkh:80 (ID:30147) to-stack FORWARDED (TCP Flags: SYN, ACK)
Jul 27 17:53:23.431: cilium-l7-envoy/tiefighter:38364 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-7hvkh:80 (ID:30147) to-endpoint FORWARDED (TCP Flags: ACK)
Jul 27 17:53:23.431: cilium-l7-envoy/tiefighter:38364 (ID:42959) -> cilium-l7-envoy/deathstar-b4b8ccfb5-7hvkh:80 (ID:30147) to-endpoint FORWARDED (TCP Flags: ACK, PSH)


Organization Manager cannot add new operation system

In GitLab by @jasonpagetas on Jul 10, 2024, 06:08
When trying to create a new operating system a manager cannot add a operating system "403 Forbidden"
permissions include add operating system

In GitLab by @jasonpagetas on Jul 10, 2024, 06:20
user is not currently part of a team. This issue may be resolved when this is fixed

this is a feature not a bug. an organization manager must be assigned the permission like any other user.

added 2m of time spent

In GitLab by @jasonpagetas on Jul 10, 2024, 06:08
marked this issue as related to #74

In GitLab by @jasonpagetas on Jul 10, 2024, 06:20
marked this issue as related to #109


socket.error Connection refused

Hi Armon,
I have statsite 0.7.1 installed on heavy loaded instances (Storm supervisors). They processed up to 25K metrics per second. Statsite installed with a puppet module dchristensen-statsite v0.2.6.
Centos 7 - 3.10.0-229.4.2.el7.x86_64.
Python 2.7.5
/etc/statsite/config:
[statsite]
tcp_port = 8125
udp_port = 8125
bind_address = <IP_ADDRESS>
parse_stdin = 0
log_level = DEBUG
flush_interval = 10
timer_eps = 0.01
set_eps = 0.02
stream_cmd = python '/opt/statsite/current/sinks/graphite.py' 'graphite-relay.domain.com' 2003 'statsite.' 3
pid_file = /var/run/statsite.pid
binary_stream = 0
use_type_prefix = 1
extended_counters = 0

And sometime I've got this error:
Nov  4 12:05:15 storm statsite: Traceback (most recent call last):
Nov  4 12:05:15 storm statsite: File "/opt/statsite/current/sinks/graphite.py", line 94, in <module>
Nov  4 12:05:15 storm statsite: graphite = GraphiteStore(*sys.argv[1:])
Nov  4 12:05:15 storm statsite: File "/opt/statsite/current/sinks/graphite.py", line 34, in __init__
Nov  4 12:05:15 storm statsite: self.sock = self._create_socket()
Nov  4 12:05:15 storm statsite: File "/opt/statsite/current/sinks/graphite.py", line 73, in _create_socket
Nov  4 12:05:15 storm statsite: sock.connect((self.host, self.port))
Nov  4 12:05:15 storm statsite: File "/usr/lib64/python2.7/socket.py", line 224, in meth
Nov  4 12:05:15 storm statsite: return getattr(self._sock,name)(*args)
Nov  4 12:05:15 storm statsite: socket.error: [Errno 111] Connection refused

Any idea how to fix/workaround it?

@mrh666 It looks like the connection to graphite-relay.domain.com on port 2003 is being refused. This isn't a bug so much as the upstream sink is just down.

Got it. Thank you Armon!


How to reproduce data/true_hubble_m2.npz

It seems data/true_hubble_m2.npz comes from the SDSS catalog, but I don't see the code that produced it. Is there a way we can use the `SloanDigitalSkySurvey' class instead?
@ismael-mendoza @jeff-regier

@Runjing-Liu120 will you share the code for this with Derek?

It's not so clear from this thread what is left to do. Let's close this issue and open a fresh one if there's a task left to do.

Isn't this the task that is left to do? @jeff-regier

To fix this issue, I will add a script you can run in this repo, to generate this npy file.

Ah OK, I may have gotten carried away trying to close issues.


TLS failed to verify certificate

We are not to able to establish a secure connection to our hashicorp vault server.
The error message is:
unable to log in to auth method: unable to log in with Kubernetes auth: Put "https://xxx/v1/auth/xx-les-dev/login": tls: failed to verify certificate: x509: certificate signed by unknown authority
Can you please provide a guideline how to add a cacerts.pem to the values.yaml?

hi @jascsch ! you can use the CAProvider field to inject your custom CA certificates. https://external-secrets.io/latest/api/spec/#external-secrets.io/v1beta1.CAProvider


project card is getting overflown in y axis on mobile screen

fixed by changing the paragraph that overflowed. solution is not dynamic as expected.


Avoid TypeError when accessing matches

Accessing length on matches may cause a TypeError if matches isn't an array.
Maybe I'm using the directive wrong, but occasionally, I'll run into this issue and get TypeError: Cannot read property 'length' of undefined.

It looks like this fix already made it into master in some form - closing.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter enigma2 for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.enigma2
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E184] "common.subscribe" will be removed with js-controller >= 6. Please remove from io-package.json and adapt code if required.
[ ] :heavy_exclamation_mark: [E507] missing size attributes [xs,md,lg,xl] for staticText at admin/jsonConfig.json/items/_settings/_desc

WARNINGS:

[ ] :eyes: [W173] Potential sensitive data "Password" not listed at "protectedNative" in io-package.json
[ ] :eyes: [W174] Potential sensitive data "Password" not listed at "encryptedNative" in io-package.json
[ ] :eyes: [W505] setTimeout found in "main.js", but no clearTimeout detected

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
or
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
Note: This issue replaces issue #249
@mcm1957 for evidence
Last update at Wed, 13 Nov 2024 12:52:46 GMT based on commit d7954a8e0a603742b5645700cbcb7346fdaf55ac
ioBroker.repochecker 3.2.2

@ioBroker-Bot recreate


BMI parameter

Hi,
I miss the BMI parameter transfer to Garmin Connect.
Can you check if there is such a possibility?
Best Reagards,
Robert

Hi @RobertWojtowicz I already experienced this, but I cannot find the root cause yet.
It seems like the problem is in Garmin connect.
At the specific weight-ins the BMI is not shown, but when you use the weekly/monthly view, the average BMI shows up (maybe internally calculated).
It seems that this is also not possible in https://github.com/kochka/WeightLogger.
Regards

Hi @RobertWojtowicz I already experienced this, but I cannot find the root cause yet.
It seems like the problem is in Garmin connect.
At the specific weight-ins the BMI is not shown, but when you use the weekly/monthly view, the average BMI shows up (maybe internally calculated).
It seems that this is also not possible in https://github.com/kochka/WeightLogger.
Regards

Hi @davidkroell
Could you have a look at this? I guess you could add BMI:
https://github.com/jaroslawhartman/withings-garmin-v2/pull/19
In a newer version:
https://github.com/jaroslawhartman/withings-sync/blob/master/withings_sync/fit.py
Best Reagards,
Robert

Hi @RobertWojtowicz I'm currently looking into it. The base library I use will need an update.
I'm working on that right now.
Best regards

rrently looking into it. The base library I use will need an update

Thank you very much

Hi,
of course this could be also the case but I'm not sure if your code snippet is correct.
You maybe mix something up here.
I think the active_met is the burnt calories rather than the calories eaten.
Maybe it is also possible to implement this using a similar fix, but I'll have to investigate this further
BR,
David

Maybe it is also possible to implement this using a similar fix, but I'll have to investigate this further
BR, David

Thank you very much for your support, I am patiently waiting for the fixes  :)
I adapted Xiaomi scale sync with your amazing module, it works perfectly :)
Best Regards,
Robert

Part of the version v2.2.0
Regards,
David


fix(esl-toggleable): doesn't update after changing the activator

Fixed incorrect behavior of toggleable when the activator changes in the open state.
Closes #1677

Accepted for release 4.7.0


It does not go to https://localhost:3000. Instead it takes it to http://https//localhost:3000.

Environment (please complete the following information):

OS (e.g., Windows 10):
Extension version (e.g., 1.2.3):

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

Closing as incomplete.

Sorry, I closed this too quickly. Thanks for filing this issue. It seems like the code should do some detection to see if the URI scheme is already present.


Docs: Add example page for Customers Admin app

Link to further details.
We'll put the working app in https://github.com/mui/mui-private repo and a showcase version in: https://github.com/mui/mui-public

Rate limitation on the Xano API that is being used:

@prakhargupta1 It's possible to "fake" a backend in-memory. For example:
import { createQuery } from "@mui/toolpad/server";

const customers = [{ name: "John Doe" }];

export async function getCustomers() {
  return customers;
}

export const addCustomer = createQuery(
  async ({ parameters }) => {
    customers.push({ name: parameters.name });
  },
  {
    parameters: {
      name: {
        typeDef: { type: "string" },
      },
    },
  }
);

We may also be able to leverage @faker-js/faker to generate data for demonstration purposes.

Thanks, just did this and removed dependence on Xano APIs.


Fix mp4 output file naming for the bitrate only case

@mjh1 What if we have multiple mp4 outputs? Will they all have the same name? 🤔

@leszko Wouldn't they all have a different path? What kind of request are you thinking of?

@mjh1 What if we have multiple mp4 outputs? Will they all have the same name? 🤔

@leszko Wouldn't they all have a different path? What kind of request are you thinking of?

I think that we use the profile name for the path of mp4. Could you try making an API call to studio like this one:
curl --location 'http://<IP_ADDRESS>:8888/api/transcode' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer <API_KEY>' \
--data '{
    "input": {
        "url": "https://storage.googleapis.com/thom-vod-testing/mustwork/Pexels%20Videos%203444.mp4"
    },
    "storage": {
        "type": "s3",
        "endpoint": "https://gateway.storjshare.io",
        "credentials": {
            "accessKeyId": "<STORJ_S3_ACCESS_KEY>",
            "secretAccessKey": "<STORJ_S3_SECRET_KEY>"
        },
        "bucket": "<BUCKET>"
    },
    "outputs": {
        "mp4": {
            "path": "/mp4/"
        }
    }
}'

It results in having the following files in the bucket:
/mp4/360p0.mp4
/mp4/720p0.mp4
/mp4/1080p0.mp4

So, I think that after your change they might overwrite each other.

Ah I see, I think we're ok here as we're defining the profiles explicitly, so the name is only applicable to a single profile. the files created look like this:
profile:
                {
                    "name": "foo",
                    "bitrate": 400000
                }

File: /mp4/foo.mp4


duplicate token

I want to change something to an existing coin We've created called Cookie gem. I'm trying to change its decimals. I'm greeted with an error stating
duplicate token: token address DP9fXAemWm3SGMZ5hE1qNqRBHaaNhEZ9o3aqHUEMBroN is already used
any help is appreciated thank you !

that means you added another block rather than modifying the existing one

that means you added another block rather than modifying the existing one

how to i edit exisitng block ?

it's a text file, edit it in the appropriate place

it's a text file, edit it in the appropriate place

txt file? is it within solana -labs token list? Any info on how to edit it , and .txt files name ?

search for DP9fXAemWm3SGMZ5hE1qNqRBHaaNhEZ9o3aqHUEMBroN in the unedited version of solana.tokenlist.json.  you will find a json block that already exists. edit that.


Expose underlying connection in ServerRequest

The request object passed to the request handler should be able to access the underlying socket connection. At the moment, there is no way for the Connection object to be passed between a connection event handler and a request handler - an example of why this is an issue is data from a client certificate when using mutual authentication cannot be passed to the request handler (e.g. certificate Common Name).

Doesn't seem like it should be too difficult to expose the connection to a request handler. In StreamingServer, we should be able to do
$response = $callback($request, $conn);
Then surely just a matter of getting the MiddlewareRunner to make use of the connection being passed to it:
`
public function __invoke(ServerRequestInterface $request, ConnectionInterface $conn)
{
if (empty($this->middleware)) {
throw new \RuntimeException('No middleware to run');
}
    return $this->call($request, 0, $conn);
}

/** @internal */
public function call(ServerRequestInterface $request, $position, ConnectionInterface $conn=null)
{
    // final request handler will be invoked without a next handler
    if (!isset($this->middleware[$position + 1])) {
        $handler = $this->middleware[$position];
        return $handler($request, $conn);
    }

    $that = $this;
    $next = function (ServerRequestInterface $request) use ($that, $position, $conn) {
        return $that->call($request, $position + 1, $conn);
    };

    // invoke middleware request handler with next handler
    $handler = $this->middleware[$position];
    return $handler($request, $next, $conn);
}

`
Due to the nature of __invoke, the extra $conn parameter should just be ignored on existing middleware handlers.
Is this kind of approach workable? I'm new to ReactPHP, so just trying to figure this out as I go.

@dwgebler Thanks you for bringing this up, I can see how this would be useful! I see there was discussion about this on IRC and it seems to resolve mostly around TLS (formerly SSL) parameters?

In vanilla PHP & Apache, you would expect to be able to retrieve the peer certificate from $_SERVER; obviously with React, depending how you design your server you may not be capturing peer certificates but what if the request serverParams could include the peer certificate if captured? that would line up the behaviour with ordinary PHP

This sounds like a nice feature to me! I agree that we should provide support for accessing TLS parameters (if available) and agree that "server params" would probably be the best place for this. This mimics how nginx (http://nginx.org/en/docs/http/ngx_http_ssl_module.html#variables) and Apache (http://httpd.apache.org/docs/current/mod/mod_ssl.html#envvars) work.
That being said, it's my understanding that this should only be exposed as part of "server params" without exposing the underlying connection. The concept of "connection" is a lower-level detail that we should probably not leak to the HTTP layer.
The TLS parameters can be accessed through stream_get_meta_data() as of PHP 7+ (http://php.net/manual/en/migration70.deprecated.php#migration70.deprecated.capture-session-meta). In PHP 5.6+ this required an additional context option (http://php.net/manual/en/migration56.openssl.php#migration56.openssl.metadata) that appears to be undocumented otherwise (http://php.net/manual/en/context.ssl.php). For the reference: We've used similar logic in the past (https://github.com/reactphp/http/pull/167/files#diff-c611f5024b5b13f69f779505d1c6735eR408) which became obsolete with https://github.com/reactphp/http/pull/244. The gist of this is that we should probably provide a way to expose these options in the underlying socket component first (somewhat similar to https://github.com/reactphp/socket/issues/150 possibly).
Before looking into this further, I would love to hear some more thoughts from more people :+1:
I've you're feeling adventurous, here's a somewhat hacky gist to access these TLS parameters without having any dedicated APIs for this:
$server = new Server(function (ServerRequestInterface $request) {
    $connection = null;
    foreach (debug_backtrace() as $trace) {
        foreach ($trace['args'] as $arg) {
            if ($arg instanceof ConnectionInterface) {
                $connection = $arg;
                break 2;
            }
        }
    }

    ob_start();
    var_dump(
        $connection,
        isset($connection->stream) ? stream_get_meta_data($connection->stream) : null,
        isset($connection->stream) ? stream_context_get_options($connection->stream) : null
    );
    $response = ob_get_clean();

    return new Response(
        200,
        array(
            'Content-Type' => 'text/plain'
        ),
        $response
    );
});

Thanks @clue yes my interest in exposing the connection is to retrieve a client certificate at the HTTP layer, my particular use case being user level access control in a RESTful API. Obviously I've been looking for a quick solution (appreciate the hacky approach, which is great to carry on building a proof of concept of my API, but not a solution I can rely on in production) but yes from a design perspective, the HTTP layer should have the client certificate as part of the server environment rather than needing to know about a socket connection. Note we would need both meta data and context options to build the same server environment as Apache mod_ssl injects and would need to parse the peer certificate but AFAIK parsing is only possible with the openssl_ functions.


Back-end Implementation

As per offline discussion on Slack, @Mera-Gangapersaud would love to use MongoDB for the database with Node.js and Express for the web framework.

I have some experience using GraphQL to replace multiple endpoints with a single one, allowing the client (whoever is querying the API), the request exactly the data they want.
Let's consider it a bonus task!

Oh man, don't listen to me.  I kid only those I love <3

Note: Check whose watching the repo next time


Not exactly sure how to use this..

-- Closed, will make a PR for better instructions in Readme.

Same. Definitely need instructions on how to import from Spine. The sample project makes my godot crash.


Type problem in service.ts

Exception in Chrome:
Type 'Observable<{}>' is not assignable to type 'Observable<SlimLoadingBarEvent>'.

Fixed in v 1.2.1


Django 1.8+ support

{% resetcycle %} tag is introduced in Django 1.11 and is causing the templates to fail:
django.template.exceptions.TemplateSyntaxError: Invalid block tag on line 48: 'resetcycle', expected 'empty' or 'endfor'. Did you forget to register or load this tag?

I'm going a bit further with this and say we should add Django 1.8+ support. PR incoming, based on yours

So, turns out supporting Django 1.8 is rather hard or cumbersome here because of these issues:

Template inheritence works differently
the simple_tag for template tags can be used as an assignment tag only on Django 1.9

Since 1.9 and 1.10 aren't supported much longer I propose to just not support Django<1.11.

won't fix


Downloader just hangs

On MadOS (Sequoia 15). Tried both the binary and building from source. Both produce the same result -- the program hangs with no output except a backslash mark:
% ./kv_downloader --debug download "https://www.karaoke-version.com/custombackingtrack/deep-purple/perfect-strangers.html'

\

What other debug info can I provide to triage this?