Container start fails with NetworkPolicy enabled after upgrade from 1.7.1 to 1.7.2

Bug description
Container start fails with NetworkPolicy egress restriction enabled after upgrade from 1.7.1 to 1.7.2
[x] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior

Pod starts and has status ready 2/2
Doc of which ingress/egress calls done by istiod/sidecar or minimal NetworkPolicy for istiod/sidecar would be nice

Steps to reproduce the bug

Use Calico plugin on aks with istio 1.7.1
Start pod with sidecar injected (here redis, but nginx didn't work as well)
label ns istio-system with networking/namespace: istio
label ns kube-system with networking/namespace: kube-system
Install NetworkPolicy to deny all egress

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: deny-all
spec:
  podSelector: {}
  policyTypes:
  - Egress

Install NetworkPolicy with restricted egress (here: redis pod, that should not be able to connect to anyone)

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-redis
spec:
  podSelector:
    matchLabels:
      app: redis
  policyTypes:
  - Ingress
  - Egress
  ingress:
  - {}
  egress:
  - to:
    # DNS lookup from sidecar
    - namespaceSelector:
        matchLabels:
          networking/namespace: kube-system
      podSelector:
        matchLabels:
          k8s-app: kube-dns
    # Istiod config from sidecar
    - namespaceSelector:
        matchLabels:
          networking/namespace: istio
      podSelector:
        matchLabels:
          app: istiod
    ports:
      # Istiod config from sidecar
    - port: 15012
      protocol: TCP
    - port: 15014
      protocol: TCP
      # DNS lookup from sidecar
    - port: 53
      protocol: UDP
    - port: 53
      protocol: TCP

Upgrade to istio 1.7.2
Restart pod
--> Pod will enter state "PostStartHookError: command 'pilot-agent wait' exited with 255: Error: timeout waiting for Envoy proxy to become ready. Last error: Get "http://localhost:15021/healthz/ready": dial tcp <IP_ADDRESS>:15021: connect: connection refused"/2
Change egress to

[...]
  egress:
  - {}

Restart pod
Pod will start and enter ready status 2/2

Version (include the output of istioctl version --remote and kubectl version --short and helm version if you used Helm)
istioctl version --remote
client version: 1.7.2
control plane version: 1.7.2
data plane version: 1.7.2 (9 proxies), 1.7.1 (2 proxies)

kubectl version --short
Client Version: v1.16.6-beta.0
Server Version: v1.16.10

How was Istio installed?
istioctl install -f values.yml

values.yml (IstioOperator)
  values:
    global:
      # Ensure that the Istio pods are only scheduled to run on Linux nodes
      defaultNodeSelector:
        beta.kubernetes.io/os: linux
      # Enable mutual TLS for the control plane
      controlPlaneSecurityEnabled: true
      # hold application until proxy starts
      proxy:
        holdApplicationUntilProxyStarts: true

Environment where bug was observed (cloud vendor, OS, etc)
Azure aks with linux VMs and network plugin calico
Additionally
Envoy logs when egress is restricted:
2020-09-25T10:30:05.560276Z	info	Received new config, creating new Envoy epoch 0
2020-09-25T10:30:05.560565Z	info	Epoch 0 starting
2020-09-25T10:30:06.575523Z	warn	HTTP request unsuccessful with status: 400 Bad Request
2020-09-25T10:30:06.581050Z	info	Envoy command: [-c etc/istio/proxy/envoy-rev0.json --restart-epoch 0 --drain-time-s 45 --parent-shutdown-time-s 60 --service-cluster logout-page.auth --service-node sidecar~<IP_ADDRESS>~logout-page-9478f747c-v4ldt.auth~auth.svc.cluster.local --local-address-ip-version v4 --log-format-prefix-with-location 0 --log-format %Y-%m-%dT%T.%fZ	%l	envoy %n	%v -l warning --component-log-level misc:error --concurrency 2]
2020-09-25T10:30:06.621002Z	warning	envoy runtime	Unable to use runtime singleton for feature envoy.reloadable_features.activate_fds_next_event_loop
2020-09-25T10:30:06.657738Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-09-25T10:30:06.657762Z	warning	envoy config	Unable to establish new stream
2020-09-25T10:30:07.511666Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-09-25T10:30:07.511716Z	warning	envoy config	Unable to establish new stream
2020-09-25T10:30:08.774146Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-09-25T10:30:08.774177Z	warning	envoy config	Unable to establish new stream
2020-09-25T10:30:14.229616Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-09-25T10:30:14.229647Z	warning	envoy config	Unable to establish new stream
2020-09-25T10:30:22.384860Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-09-25T10:30:22.384985Z	warning	envoy config	Unable to establish new stream
2020-09-25T10:30:41.355457Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-09-25T10:30:41.355489Z	warning	envoy config	Unable to establish new stream
2020-09-25T10:30:47.471721Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-09-25T10:30:47.471775Z	warning	envoy config	Unable to establish new stream
2020-09-25T10:30:49.741128Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-09-25T10:30:49.741165Z	warning	envoy config	Unable to establish new stream
2020-09-25T10:31:00.585519Z	warning	envoy config	StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-09-25T10:31:00.585554Z	warning	envoy config	Unable to establish new stream
2020-09-25T10:31:05.809632Z	info	Agent draining Proxy
2020-09-25T10:31:05.809640Z	info	Status server has successfully terminated
2020-09-25T10:31:05.809623Z	info	Watcher has successfully terminated
2020-09-25T10:31:05.809844Z	error	accept tcp [::]:15020: use of closed network connection
2020-09-25T10:31:05.810675Z	info	Graceful termination period is 5s, starting...
2020-09-25T10:31:10.810893Z	info	Graceful termination period complete, terminating remaining proxies.
2020-09-25T10:31:10.810930Z	warn	Aborting epoch 0...
2020-09-25T10:31:10.810943Z	warn	Aborted all epochs
2020-09-25T10:31:10.810946Z	info	Agent has successfully terminated
2020-09-25T10:31:10.811092Z	warning	envoy main	caught SIGTERM

is the pod restricted from calling localhost? That would cause the experimental holdApplicationUntilProxyStarts to fail.

No, I can call localhost from the main container.
When I apply the NetworkPolicy with egress restriction to the running pod with istio-sidecar and ssh into the pod kubectl exec -it <pod> -c <main> -- sh and do a curl -X POST http://localhost:15000/logging?level=info I get the expected response.
If I now restart the pod with the applied NetworkPolicy with egress restriction kubectl rollout restart deploy <pod> I get the PostStartHookError again. If I now change the NetworkPolicy to allow all egress, the pod will restart and enter READY 2/2 with STATUS Running.
Something else I have observed:
The PostStartHookError the pod will restart and go into state READY 1/2 with STATUS CrashLoopBackOff. My main application starts, the sidecar is marked as not-ready. When I ssh into the main container and do the curl command described above I will get the expected responde from the sidecar. Seams as if the sidecar is running but the status is not recognized from kubelet.

Update: I have disabled holdApplicationUntilProxyStarts for now. The pod starts and enters READY 1/2 with STATUS Running, when egress is restricted.
Investigating the logs and found:
error   citadelclient   Failed to create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"

I think this might be the root cause of the whole problem. Worked with istio 1.6.8, what changed with 1.7.x that breaks this?

error   citadelclient   Failed to create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"

This should be connecting to istiod over port 15012. Are you sure this is permitted in your policy?

Yes. It doesn't even work, if I allow any port.
I configured to allow egress:

Connection to istio namespace, app istiod
Connection to kube-sysem namespace, app kube-dns
Connection to <IP_ADDRESS>/32 (Azure VM Instance metadata endpoint)
Connection over any port

Still the sidecar isn't able to create certificate and enter ready state (btw state is READY 1/2 and STATUS Running, I would expect it to enter an error state after some time).
Here the logs with debug enabled:
2020-10-06T07:32:14.223632Z     info    JWT policy is third-party-jwt
2020-10-06T07:32:14.223679Z     info    PilotSAN []string{"istiod.istio-system.svc"}
2020-10-06T07:32:14.223693Z     info    MixerSAN []string{"spiffe://cluster.local/ns/istio-system/sa/istio-mixer-service-account"}
2020-10-06T07:32:14.223767Z     info    sa.serverOptions.CAEndpoint == istiod.istio-system.svc:15012
2020-10-06T07:32:14.223776Z     info    Using user-configured CA istiod.istio-system.svc:15012
2020-10-06T07:32:14.223780Z     info    istiod uses self-issued certificate
2020-10-06T07:32:14.223848Z     info    the CA cert of istiod is: -----BEGIN CERTIFICATE-----
[...]
-----END CERTIFICATE-----

2020-10-06T07:32:14.270563Z     info    sds     SDS gRPC server for workload UDS starts, listening on "./etc/istio/proxy/SDS"

2020-10-06T07:32:14.270690Z     info    sds     Start SDS grpc server
2020-10-06T07:32:14.270844Z     info    Starting proxy agent
2020-10-06T07:32:14.270856Z     info    Opening status port 15020

2020-10-06T07:32:14.270958Z     info    Received new config, creating new Envoy epoch 0
2020-10-06T07:32:14.270998Z     info    Epoch 0 starting
2020-10-06T07:32:15.289229Z     warn    HTTP request unsuccessful with status: 400 Bad Request
2020-10-06T07:32:15.294831Z     info    Envoy command: [-c etc/istio/proxy/envoy-rev0.json --restart-epoch 0 --drain-time-s 45 --parent-shutdown-time-s 60 --service-cluster <pod> --service-node sidecar~<IP_ADDRESS>~<pod>-5f85dc96f5-mk8z7.<ns>~<ns>.svc.cluster.local --local-address-ip-version v4 --log-format-prefix-with-location 0 --log-format %Y-%m-%dT%T.%fZ   %l      envoy %n        %v -l warning --component-log-level misc:error --concurrency 2]
2020-10-06T07:32:15.338764Z     warning envoy runtime   Unable to use runtime singleton for feature envoy.reloadable_features.activate_fds_next_event_loop
2020-10-06T07:32:15.378161Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-10-06T07:32:15.378192Z     warning envoy config    Unable to establish new stream
2020-10-06T07:32:15.513049Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-10-06T07:32:15.513087Z     warning envoy config    Unable to establish new stream
2020-10-06T07:32:17.549738Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-10-06T07:32:17.549776Z     warning envoy config    Unable to establish new stream
2020-10-06T07:32:22.178213Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-10-06T07:32:22.178250Z     warning envoy config    Unable to establish new stream
2020-10-06T07:32:45.811657Z     debug   envoy http      [C0][S2362696381035299037] encoding headers via codec (end_stream=false):
':status', '200'
'content-type', 'text/plain; charset=UTF-8'
'cache-control', 'no-cache, max-age=0'
'x-content-type-options', 'nosniff'
'date', 'Tue, 06 Oct 2020 07:32:45 GMT'
'server', 'envoy'

2020-10-06T07:32:45.812270Z     debug   envoy connection        [C0] remote close
2020-10-06T07:32:45.812298Z     debug   envoy connection        [C0] closing socket: 0
2020-10-06T07:32:45.812344Z     debug   envoy conn_handler      [C0] adding to cleanup list
2020-10-06T07:32:50.389710Z     debug   envoy main      flushing stats
2020-10-06T07:32:50.389760Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:32:51.827292Z     debug   envoy config    Establishing new gRPC bidi stream for rpc StreamAggregatedResources(stream .envoy.service.discovery.v3.DiscoveryRequest) returns (stream .envoy.service.discovery.v3.DiscoveryResponse);

2020-10-06T07:32:51.827349Z     debug   envoy router    [C0][S2419243086156396550] cluster 'xds-grpc' match for URL '/envoy.service.discovery.v3.AggregatedDiscoveryService/StreamAggregatedResources'
2020-10-06T07:32:51.827368Z     debug   envoy upstream  no healthy host for HTTP connection pool
2020-10-06T07:32:51.827407Z     debug   envoy http      async http request response headers (end_stream=true):
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '14'
'grpc-message', 'no healthy upstream'

2020-10-06T07:32:51.827420Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-10-06T07:32:51.827435Z     warning envoy config    Unable to establish new stream
2020-10-06T07:32:55.390347Z     debug   envoy main      flushing stats
2020-10-06T07:32:55.390380Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:33:00.392240Z     debug   envoy main      flushing stats
2020-10-06T07:33:00.392269Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:33:05.390402Z     debug   envoy main      flushing stats
2020-10-06T07:33:05.390429Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:33:09.871107Z     debug   envoy config    Establishing new gRPC bidi stream for rpc StreamAggregatedResources(stream .envoy.service.discovery.v3.DiscoveryRequest) returns (stream .envoy.service.discovery.v3.DiscoveryResponse);

2020-10-06T07:33:09.871170Z     debug   envoy router    [C0][S7209826945172009347] cluster 'xds-grpc' match for URL '/envoy.service.discovery.v3.AggregatedDiscoveryService/StreamAggregatedResources'
2020-10-06T07:33:09.871188Z     debug   envoy upstream  no healthy host for HTTP connection pool
2020-10-06T07:33:09.871229Z     debug   envoy http      async http request response headers (end_stream=true):
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '14'
'grpc-message', 'no healthy upstream'

2020-10-06T07:33:09.871251Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-10-06T07:33:09.871260Z     warning envoy config    Unable to establish new stream
2020-10-06T07:33:10.392675Z     debug   envoy main      flushing stats
2020-10-06T07:33:10.392706Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:33:15.390280Z     debug   envoy main      flushing stats
2020-10-06T07:33:15.390311Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:33:20.390824Z     debug   envoy main      flushing stats
2020-10-06T07:33:20.390851Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:33:25.392318Z     debug   envoy main      flushing stats
2020-10-06T07:33:25.392350Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:33:27.102107Z     debug   envoy config    Establishing new gRPC bidi stream for rpc StreamAggregatedResources(stream .envoy.service.discovery.v3.DiscoveryRequest) returns (stream .envoy.service.discovery.v3.DiscoveryResponse);

2020-10-06T07:33:27.102168Z     debug   envoy router    [C0][S17624152566446344490] cluster 'xds-grpc' match for URL '/envoy.service.discovery.v3.AggregatedDiscoveryService/StreamAggregatedResources'
2020-10-06T07:33:27.102184Z     debug   envoy upstream  no healthy host for HTTP connection pool
2020-10-06T07:33:27.102219Z     debug   envoy http      async http request response headers (end_stream=true):
':status', '200'
'content-type', 'application/grpc'
'grpc-status', '14'
'grpc-message', 'no healthy upstream'

2020-10-06T07:33:27.102236Z     warning envoy config    StreamAggregatedResources gRPC config stream closed: 14, no healthy upstream
2020-10-06T07:33:27.102256Z     warning envoy config    Unable to establish new stream
2020-10-06T07:33:30.381494Z     debug   envoy upstream  DNS request timed out 4 times
2020-10-06T07:33:30.381531Z     debug   envoy upstream  DNS refresh rate reset for istiod.istio-system.svc, (failure) refresh rate 5000 ms
2020-10-06T07:33:30.381538Z     debug   envoy upstream  initializing Primary cluster xds-grpc completed
2020-10-06T07:33:30.381544Z     debug   envoy init      init manager Cluster xds-grpc initializing
2020-10-06T07:33:30.381548Z     debug   envoy init      init manager Cluster xds-grpc initializing target SdsApi default
2020-10-06T07:33:30.381558Z     debug   envoy config    gRPC mux addWatch for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret
2020-10-06T07:33:30.381782Z     debug   envoy config    No stream available to sendDiscoveryRequest for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret
2020-10-06T07:33:30.381812Z     debug   envoy config    Establishing new gRPC bidi stream for rpc StreamSecrets(stream .envoy.service.discovery.v3.DiscoveryRequest) returns (stream .envoy.service.discovery.v3.DiscoveryResponse);

2020-10-06T07:33:30.381848Z     debug   envoy router    [C0][S18107257454375978299] cluster 'sds-grpc' match for URL '/envoy.service.secret.v3.SecretDiscoveryService/StreamSecrets'
2020-10-06T07:33:30.381902Z     debug   envoy router    [C0][S18107257454375978299] router decoding headers:
':method', 'POST'
':path', '/envoy.service.secret.v3.SecretDiscoveryService/StreamSecrets'
':authority', 'sds-grpc'
':scheme', 'http'
'te', 'trailers'
'content-type', 'application/grpc'
'x-envoy-internal', 'true'
'x-forwarded-for', '<IP_ADDRESS>'

2020-10-06T07:33:30.381923Z     debug   envoy pool      queueing request due to no available connections
2020-10-06T07:33:30.381928Z     debug   envoy pool      creating a new connection
2020-10-06T07:33:30.381981Z     debug   envoy client    [C1] connecting
2020-10-06T07:33:30.381994Z     debug   envoy connection        [C1] connecting to ./etc/istio/proxy/SDS
2020-10-06T07:33:30.382142Z     debug   envoy http2     [C1] updating connection-level initial window size to 268435456
2020-10-06T07:33:30.382637Z     debug   envoy upstream  DNS request timed out 4 times
2020-10-06T07:33:30.382656Z     debug   envoy upstream  DNS refresh rate reset for zipkin.istio-system, (failure) refresh rate 5000 ms
2020-10-06T07:33:30.382660Z     debug   envoy upstream  initializing Primary cluster zipkin completed
2020-10-06T07:33:30.382664Z     debug   envoy init      init manager Cluster zipkin contains no targets
2020-10-06T07:33:30.382667Z     debug   envoy init      init manager Cluster zipkin initialized, notifying ClusterImplBase
2020-10-06T07:33:30.382674Z     debug   envoy upstream  cm init: init complete: cluster=zipkin primary=1 secondary=0
2020-10-06T07:33:30.382677Z     debug   envoy upstream  maybe finish initialize state: 1
2020-10-06T07:33:30.382681Z     debug   envoy upstream  maybe finish initialize primary init clusters empty: false
2020-10-06T07:33:30.382711Z     debug   envoy connection        [C1] connected
2020-10-06T07:33:30.382717Z     debug   envoy client    [C1] connected
2020-10-06T07:33:30.382722Z     debug   envoy pool      [C1] attaching to next request
2020-10-06T07:33:30.382726Z     debug   envoy pool      [C1] creating stream
2020-10-06T07:33:30.382745Z     debug   envoy router    [C0][S18107257454375978299] pool ready
2020-10-06T07:33:30.384766Z     info    sds     resource:default new connection
2020-10-06T07:33:30.384884Z     info    sds     Skipping waiting for gateway secret
2020-10-06T07:33:30.391710Z     debug   envoy main      flushing stats
2020-10-06T07:33:30.391721Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:33:35.390475Z     debug   envoy main      flushing stats
2020-10-06T07:33:35.390504Z     debug   envoy main      Envoy is not fully initialized, skipping histogram merge and flushing stats
2020-10-06T07:33:39.519065Z     error   citadelclient   Failed to create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2020-10-06T07:33:39.569285Z     warn    cache   resource:default request:4ebd61ca-f39f-45e9-aaf3-496eba22ab11 CSR failed with error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout", retry in 50 millisec
2020-10-06T07:33:39.569424Z     error   citadelclient   Failed to create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"

Retries for citadelclient go on for > 20 minutes without success.
As I mentioned, this worked with 1.6.x.

Has anyone any idea how to fix this?

@Christoph-Raab it seems it trying to connect to istiod.istio-system.svc:15012 and getting i/o timeout so its killed very early in the connection. I don't think this is istios "fault", and likely an issue with your NetworkPolicy config

@howardjohn Thanks for your support. I switched from NetworkPolices to AuthorizationPolicy in the meantime.

Necro'ing a thread, but in case this helps anyone, this network policy (you'll need adjust label selectors to match the istio namespace and istiod pods) resolved this for me:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-to-istiod
spec:
  podSelector: {}
  policyTypes:
  - Egress
  egress:
  - to:
    - namespaceSelector:
        matchLabels:
          app.kubernetes.io/name: istio-controlplane.   # label name for istio-system namespace
    - podSelector:
        matchLabels:
          istio: pilot   # label match for istiod pods
  - ports:
    - port: 53
      protocol: TCP
    - port: 53
      protocol: UDP

Necro'ing a thread, but in case this helps anyone, this network policy (you'll need adjust label selectors to match the istio namespace and istiod pods) resolved this for me:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-to-istiod
spec:
  podSelector: {}
  policyTypes:
  - Egress
  egress:
  - to:
    - namespaceSelector:
        matchLabels:
          app.kubernetes.io/name: istio-controlplane   # label name for istio-system namespace
    - podSelector:
        matchLabels:
          istio: pilot   # label match for istiod pods
  - ports:
    - port: 53
      protocol: TCP
    - port: 53
      protocol: UDP

Tried this fix but it seems it does not solve our issue :/
We recently introduced network-policies to harden system but we allowed istio the following way:
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-to-and-from-istiod-namespace
  namespace: {{ .Release.Namespace }}
spec:
  podSelector: {}
  egress:
    - to:
        - namespaceSelector:
            matchLabels:
              name: istio-system
        - podSelector:
            matchLabels:
              istio: pilot
    - ports:
        - protocol: TCP
          port: 15012
        - protocol: TCP
          port: 443
        - protocol: TCP
          port: 53
        - protocol: UDP
          port: 53
  ingress:
    - from:
        - namespaceSelector:
            matchLabels:
              name: istio-system
        - podSelector:
            matchLabels:
              istio: pilot
  policyTypes:
    - Egress
    - Ingress

But this does not solve the connection issue

2022-01-31T16:16:50.783947Z    info    FLAG: --concurrency="2"
2022-01-31T16:16:50.783973Z    info    FLAG: --domain="clm-am-NAMESPACE.svc.cluster.local"
2022-01-31T16:16:50.783993Z    info    FLAG: --help="false"
2022-01-31T16:16:50.783999Z    info    FLAG: --log_as_json="false"
2022-01-31T16:16:50.784003Z    info    FLAG: --log_caller=""
2022-01-31T16:16:50.784008Z    info    FLAG: --log_output_level="default:info"
2022-01-31T16:16:50.784017Z    info    FLAG: --log_rotate=""
2022-01-31T16:16:50.784022Z    info    FLAG: --log_rotate_max_age="30"
2022-01-31T16:16:50.784028Z    info    FLAG: --log_rotate_max_backups="1000"
2022-01-31T16:16:50.784037Z    info    FLAG: --log_rotate_max_size="104857600"
2022-01-31T16:16:50.784043Z    info    FLAG: --log_stacktrace_level="default:none"
2022-01-31T16:16:50.784054Z    info    FLAG: --log_target="[stdout]"
2022-01-31T16:16:50.784067Z    info    FLAG: --meshConfig="./etc/istio/config/mesh"
2022-01-31T16:16:50.784072Z    info    FLAG: --outlierLogPath=""
2022-01-31T16:16:50.784078Z    info    FLAG: --proxyComponentLogLevel="misc:error"
2022-01-31T16:16:50.784092Z    info    FLAG: --proxyLogLevel="warning"
2022-01-31T16:16:50.784097Z    info    FLAG: --serviceCluster="istio-proxy"
2022-01-31T16:16:50.784103Z    info    FLAG: --stsPort="0"
2022-01-31T16:16:50.784116Z    info    FLAG: --templateFile=""
...
2022-01-31T16:16:50.784284Z    info    Proxy role    ips=[<IP_ADDRESS>] type=sidecar id=APP-deployment-7d8779bd5-npb4q.clm-am-bom-resolution domain=clm-am-NAMESPACE.svc.cluster.local
2022-01-31T16:16:50.784363Z    info    Apply proxy config from env {"tracing":{"zipkin":{"address":"zipkin.kyma-system:9411"}}}
2022-01-31T16:16:50.875039Z    info    Effective config: binaryPath: /usr/local/bin/envoy
concurrency: 2
configPath: ./etc/istio/proxy
controlPlaneAuthPolicy: MUTUAL_TLS
discoveryAddress: istiod.istio-system.svc:15012
drainDuration: 45s
parentShutdownDuration: 60s
proxyAdminPort: 15000
serviceCluster: istio-proxy
statNameLength: 189
statusPort: 15020
terminationDrainDuration: 5s
tracing:
  zipkin:
    address: zipkin.kyma-system:9411
2022-01-31T16:16:50.875072Z    info    JWT policy is third-party-jwt
2022-01-31T16:16:52.875645Z    info    CA Endpoint istiod.istio-system.svc:15012, provider Citadel
2022-01-31T16:16:52.875664Z    info    Opening status port 15020
2022-01-31T16:16:52.875733Z    info    Using CA istiod.istio-system.svc:15012 cert with certs: var/run/secrets/istio/root-cert.pem
2022-01-31T16:16:52.875856Z    info    citadelclient    Citadel client using custom root cert: istiod.istio-system.svc:15012
2022-01-31T16:16:52.887896Z    info    ads    All caches have been synced up in 2.107010001s, marking server ready
2022-01-31T16:16:52.888092Z    info    sds    SDS server for workload certificates started, listening on "etc/istio/proxy/SDS"
2022-01-31T16:16:52.888111Z    info    xdsproxy    Initializing with upstream address "istiod.istio-system.svc:15012" and cluster "Kubernetes"
2022-01-31T16:16:52.888174Z    info    sds    Starting SDS grpc server
2022-01-31T16:16:52.888427Z    info    Pilot SAN: [istiod.istio-system.svc]
2022-01-31T16:16:52.888432Z    info    starting Http service at <IP_ADDRESS>:15004
2022-01-31T16:16:52.975052Z    info    Starting proxy agent
2022-01-31T16:16:52.975092Z    info    Epoch 0 starting
2022-01-31T16:16:52.975115Z    info    Envoy command: [-c etc/istio/proxy/envoy-rev0.json --restart-epoch 0 --drain-time-s 45 --drain-strategy immediate --parent-shutdown-time-s 60 --local-address-ip-version v4 --bootstrap-version 3 --file-flush-interval-msec 1000 --disable-hot-restart --log-format %Y-%m-%dT%T.%fZ    %l    envoy %n    %v -l warning --component-log-level misc:error --concurrency 2]
2022-01-31T16:17:12.878012Z    warn    ca    ca request failed, starting attempt 1 in 102.093205ms
2022-01-31T16:17:12.980664Z    warn    ca    ca request failed, starting attempt 2 in 217.620363ms
2022-01-31T16:17:13.199094Z    warn    ca    ca request failed, starting attempt 3 in 413.164804ms
2022-01-31T16:17:13.584645Z    warning    envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2022-01-31T16:17:13.612945Z    warn    ca    ca request failed, starting attempt 4 in 790.034269ms
2022-01-31T16:17:33.879113Z    warn    sds    failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2022-01-31T16:17:33.915466Z    warning    envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: i/o timeout"
2022-01-31T16:17:35.074784Z    warn    ca    ca request failed, starting attempt 1 in 103.736461ms
2022-01-31T16:17:35.179057Z    warn    ca    ca request failed, starting attempt 2 in 182.62548ms
2022-01-31T16:17:42.887119Z    warn    ca    ca request failed, starting attempt 3 in 372.52154ms
2022-01-31T16:17:42.887363Z    warning    envoy config    StreamAggregatedResources gRPC config stream closed: 14, connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:60987-><IP_ADDRESS>:53: i/o timeout"
2022-01-31T16:17:43.259838Z    warn    ca    ca request failed, starting attempt 4 in 735.515123ms
2022-01-31T16:17:43.996334Z    warn    sds    failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup istiod.istio-system.svc on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:60987-><IP_ADDRESS>:53: i/o timeout"
2022-01-31T16:17:51.219862Z    info    Agent draining Proxy
2022-01-31T16:17:51.219843Z    info    Status server has successfully terminated
2022-01-31T16:17:51.219950Z    error    accept tcp [::]:15020: use of closed network connection
2022-01-31T16:17:51.220887Z    info    Graceful termination period is 5s, starting...
2022-01-31T16:17:56.221160Z    info    Graceful termination period complete, terminating remaining proxies.
2022-01-31T16:17:56.221190Z    warn    Aborted all epochs
2022-01-31T16:17:56.221198Z    warn    Aborting epoch 0
2022-01-31T16:17:56.221300Z    info    Epoch 0 aborted normally
2022-01-31T16:17:56.221307Z    info    Agent has successfully terminated
stream closed

Any ideas what goes wrong here? IMHO lookup istiod.istio-system.svc on <IP_ADDRESS>:53 should be reachable with the network-policy maybe I overlook something?

This should be connecting to istiod over port 15012. Are you sure this is permitted in your policy?

Can confirm this worked for us when it was trying to request a certificate on pod startup.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: app-egress-netpol
  namespace: app
spec:
  podSelector:
    matchLabels:
      app.kubernetes.io/name: app
  policyTypes:
    - Egress
  egress:
    - to:
      - namespaceSelector:
          matchLabels:
            kubernetes.io/metadata.name: istio-system   # label name for istio-system namespace
      - podSelector:
          matchLabels:
            istio: pilot   # label match for istiod pods
    - ports:
      - port: 15012
        protocol: TCP
      - port: 15012
        protocol: UDP


Add copyright tag to bazel configuration files

Apologies - I was unreasonably quick to merge the PR, which broke Bazel build: https://github.com/openxla/stablehlo/actions/runs/4111453637/jobs/7095229136. This will be fixed momentarily.

Fixed forward in https://github.com/openxla/stablehlo/pull/1075.


About unifying APIs for all protocols

Currently, Meshblu supports various protocols including HTTP, Websocket, MQTT, CoAP...  To work with individual protocols, we must use different APIs.
So is it reasonable to unify them into one? For example, here is what I think about the unified APIs:
var meshblu = require('meshblu');

var endpoint = meshblu.createConnection({
  "uuid": "xxxxxxxxxxxx-My-UUID-xxxxxxxxxxxxxx",
  "token": "xxxxxxx-My-Token-xxxxxxxxx",
  "protocol": "mqtt", // protocol to work with
  "mqtt": { // configuration for the protocol
      "qos": 0, // MQTT Quality of Service (0=no confirmation, 1=confirmation, 2=N/A)
      "host": "localhost", // optional - defaults to meshblu.octoblu.com
      "port": 1883  // optional - defaults to 1883
  }
});

// register for event handlers
endpoint.on('<a message>', function(data){
});

// to send data or messages
endpoint.send('data', data, function(err, result){
});
endpoint.send('message', message, function(err, result){
});
endpoint.send('subscription', uuid, function(err, result){
});

In Meshblu 2.0 we have a standard set of jobs across all protocols. To preserve backwards compatibility we support the legacy meshblu API, however we will start exposing the "Job Manager" style APIs to all protocols. We should continue to try and support the native paradigms of each protocol, however the client libraries should have some consistency between them.  If you look at the XMPP and AMQP protocol adapters, you can see some examples.
https://github.com/octoblu/meshblu-core-protocol-adapter-xmpp
https://github.com/octoblu/meshblu/wiki/Job

@iamruinous Thank you!


🦭 Add types declaration to viem package

#30  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MiksuJak and the rest of your teammates on  Graphite


[Bug]: Ob425 Chinese stored procedure displays garbled characters

ODC version
odc433
OB version

What happened?

What did you expect to happen?
Display Chinese normally
How can we reproduce it (as minimally and precisely as possible)?
View after creating a Chinese stored procedure
Anything else we need to know?
No response

It's not an odc bug, it's an ob bug


Region Options

Added the ability to pass a WoW player region into the query. This allows players to query a player from the EU region if the US one is specified in the Config Vars. If one is not provided it falls back to the default. I have updated the unit tests to handle this use case. So far this has been tested on the eu, us and kr realms without issue. I also added the region next to the realm part of Discord message, for example Burning Legion (US).
I've also added some error handling incase a configuration variable is missing, it will now exit the application and log the reason to the terminal window.
Also moved all configuration options into a settings.py file and removed a few unneeded declarations.
This PR resolves #24

Successfully tested with eu, us, and kr. Still need to test the others.

Also tested the tw realm, everything seems to work both url and regular query.


Site request: http://www.unicaen.fr/recherche/mrsh/forge/4055

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2<IP_ADDRESS>. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2<IP_ADDRESS>

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[x] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['http://www.unicaen.fr/recherche/mrsh/forge/4055', '-v']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 3.5.1+ - Linux-4.4.0-28-generic-x86_64-with-Ubuntu-16.04-xenial
[debug] exe versions: ffmpeg 2.8.6-1ubuntu2, ffprobe 2.8.6-1ubuntu2, rtmpdump 2.4
[debug] Proxy map: {}
[generic] 4055: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 4055: Downloading webpage
[generic] 4055: Extracting information
ERROR: Unsupported URL: http://www.unicaen.fr/recherche/mrsh/forge/4055
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/youtube_dl/YoutubeDL.py", line 676, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/lib/python3.5/dist-packages/youtube_dl/extractor/common.py", line 343, in extract
    return self._real_extract(url)
  File "/usr/local/lib/python3.5/dist-packages/youtube_dl/extractor/generic.py", line 2222, in _real_extract
    raise UnsupportedError(url)
youtube_dl.utils.UnsupportedError: Unsupported URL: http://www.unicaen.fr/recherche/mrsh/forge/4055

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: http://www.unicaen.fr/recherche/mrsh/forge/4055

canal-u.tv embed. Related to #9491.


getSetting fails on arrays

It returns an object like {0: 'firstValue'}, try with apolloServer.corsWhitelist for example, instead of an array. Accessing through Meteor.settings does work though.
Maybe it happens only for values that are nested within an object.

Hi there! Do you mind if I take a look at this issue?

No problem! Vulcan Meteor development is not active, we are currently focused on the Next.js version

_hey folk can i try to solve this issue ?_


[CP]  reland weaken affinity of raster/ui to non-e core instead of only fast core

Issue Link
flutter/flutter#153690
Target
stable
Cherry pick PR Link
https://github.com/flutter/engine/pull/54842
Changelog Description

Adjust engine threading affinities on Android to better match actual core count.

Impacted Users
Android Skia
Impact Description

Worse performance in scenarios with multiple flutter applications

Workaround
No work around
Risk
low
Test Coverage
yes
Validation Steps
Attached unit tests.

@zanderso

CP lgtm


Set up branch protection

https://securityscorecards.dev/viewer/?uri=github.com/refaktor/rye
doesn't find any branch protection rules:

Linking to https://github.com/ossf/scorecard/blob/7ce8609469289d5f3b1bf5ee3122f42b4e3054fb/docs/checks.md#branch-protection
A quick recipe to fix this:

Visit https://github.com/refaktor/rye/settings/rules
Add new branch ruleset
Give it a name, eg. "default branch protection"
Set enforcement to active

apply it to default branch

Tick checkboxes at

[x] Restrict deletions (so that the master branch cannot be deleted)
[x] Block force puhes (to avoid rewriting history)

Consider other options (eg requiring pull requests, approval...)

More info about the repository rulesets: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets

Thank you for issue and instructions. I've set it up, I hope it's OK now.

Thanks! We'll see if it is ok after https://securityscorecards.dev/viewer/?uri=github.com/refaktor/rye is updated next (on a commit to master or on a weekly schedule).

It is better now, but still not ideal:


Change Java version

Change maven build from Java 8 to Java 11

Would you mind a followup to document the Java 11 requirement in the README? Maybe under a Requirements section.


MAKE A CRUD API IN NODE.JS

I would like create a crud api code, so that it learn more about api, routes, node.js framework
@neerajrathore please review this and add the label as hactoberfest

Can I work on this issue under Hacktoberfest 24

@Arpit529Srivastava You can proceed with your contribution.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Include the issue number in your PR description for better tracking.

I'm excited to see your contribution as part of Hacktoberfest 2024! 🎉
Don't forget to follow me on GitHub for more updates.
Happy open-source contributing! 🚀

@vverma022 issue assign to first come basis. You can contribute other topics as well.

@neerajrathore please merge the PR and add the label hactoberfest-accepted

@Arpit529Srivastava your pr #45 does not qualify hacktoberfest.
you can add topics of javascript.


Duplicate Asset

It'd be nice to duplicate an asset without importing a CSV.
Votes: 1
Author: viendih
Voters: viendih

Scheduled - duplicate of asset will create exact copy w/o history or assignment. Should immediately open for editing.  Only history line should note it was created as a copy of existing entry.  Only for equipment
Author: postit

Scheduled - duplicate of asset will create exact copy w/o history or assignment. Should immediately open for editing.  Only history line should note it was created as a copy of existing entry.  Only for equipment
Author: postit


chore(main): release project-cli-tools 0.4.0

:robot: I have created a release beep boop
0.4.0 (2024-04-04)
Features

project-cli-tools: add nodemon, turbo and wait-on (45122b5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fuf-stack/ts-project-setup/releases/tag/project-cli-tools-v0.4.0 :sunflower:


Using valid sql "source" command gives ER_PARSE_ERROR

Reproduction
Dockerfile:
FROM mariadb:10.5.6
COPY /database/sql/* /sql/
# ^ Contains one sql file "creation.sql"

creation.sql
CREATE DATABASE my_db;

There will eventually be more SQL here to build and populate a test database.
Node js:
import mysql from 'mysql';

const connection = mysql.createConnection({
   // connection info here -- connects to docker container
});

function queryPromise(sql) {
   console.log('SQL> ', sql);
   return new Promise((resolve, reject) => {
      connection.query(sql, (error, results, fields) => {
         if (error) console.error(error);
         console.log('\tSQL result:', results);
         resolve({ error, results });
      });
   });
}

connection.connect();
// Using chained promises to stop queries from running at the same time and the connection getting cut off
queryPromise('SELECT 1 + 1 AS solution') // Works OK
   .then(() => queryPromise('show databases')) // Works OK
   .then(() => queryPromise('source sql/creation.sql')) // Throws an error
   .then(() => connection.end());

Trying to run queryPromise('source sql/creation.sql') via a mysql query it throws an error.
Error: ER_PARSE_ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'source sql/creation.sql' at line 1
at Query.Sequence._packetToError (C:\code\tox-db-prototype\node_modules\mysql\lib\protocol\sequences\Sequence.js:47:14)

If I instead go into the container, run mysql, and run source sql/creation.sql from the mysql command line, then it runs fine. If I use queryPromise('CREATE DATABASE my_db') as the query, it also runs okay. The issue seems to be that running "source" as a query with this module is giving an error.

Duplicate of #2336


Warning when packaging match's metavalue should be a valid match pattern string

metablock.json
{
  "match": [
    "https://app.slack.com/client/*",
    "http://<IP_ADDRESS>:*/*",
    "https://userjs.rxliuli.com/*"
  ]
}

The match pattern is defined in Chrome extension dev & MDN.
There is no description to host:port in Chrome, but MDN explicitly says it is an invalid match pattern:

Note: The path pattern string should not include a port number. Adding a port, as in: "http://localhost:1234/" causes the match pattern to be ignored. However, "http://localhost:1234" will match with "http://localhost/"

To reduce the warning, I suggest you using include instead of match to http://<IP_ADDRESS>:*/* pattern.

If you have more questions, we can reopen it.


AndroidX

AndroidX conversion (to use AndroidX namespace). Seems working okay, I've tested it with included app.

Gradle was also updated. :)


[mistralai]: Don´t support stop sequence

System Info
Python: 3.11
Langchain: 0.0.352
mistralai: 0.0.8
Who can help?
@efriis
Information

[ ] The official example notebooks/scripts
[X] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[X] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
If the ChatMistralAI model is used for an agent or similar, an error appears because the official Mistral API does not currently support the stop parameter (as other APIs such as OpenAI do).
Expected behavior
Although this is something that should be fixed by Mistral in its official API, one of the following options should be done:

Warn the user that this model cannot be used with a stop sequence before breaking execution due to the error.
Implement an own solution for the stop sequence in the same package and do not send that parameter to the official client call.

Hi @DavidLMS and @efriis,
I fixed that in my pull request: https://github.com/langchain-ai/langchain/pull/15375. What do you think of my suggested solution?
Thanks and cheers, Niels


Windows default cursor if overriden

My default cursor is changed to the color picker cursor even after killing the app from background.

It is quite annoying as restarting pc or uninstalling this app also doesnt help.

Just found that text select cursor got corrupted and overriden by color picker cursor. Resetting from windows cursor menu fixed the issue.


[v2.7] KDM Update for K8s February patch release

KDM Updates
TO BE RELEASED: OOB post v2.7.11

New Kubernetes Version
Min Rancher Version
Min RKE Version

1.27.11-rancher1-1
2.7.11-patch0
1.4.15-rc0

1.26.14-rancher1-1
2.7.5-patch0
1.4.6-rc0

Rancher System Images & Add-ons
Note: Please update system images and add-ons in the template as needed.
TBD
Developer Changelog

Add templates for new K8s versions. If a template that hasn't been released yet already exists, update it in place.
Update the default K8s version, and add or update the version information (MinRancherVersion and MinRKEVersion) in k8s_version_info.go for new K8s versions if needed (Use table from above).
Confirm versions for system images, add-on templates are correct using versioning reference table from below (expand details to view the table). Update the table if new versions are introduced.
Confirm add-on template version constraints in template.go are correct using versioning reference table from below (expand details to view the table). Update the table if needed.

Versioning Reference

Expand for system images & add-on templates versioning table

Note: Truncated repository names with a * indicates there are multiple images with that prefix. All repository names that match a truncated prefix should be checked for the same version stated in the table.
For example: rancher/weave-* matches weaveworks/weave-kube and weaveworks/weave-npc, and they should both have the same version.
v1.27.11-rancher1-1

Repository
Tag

rancher/mirrored-coreos-etcd
v3.5.10

rancher/hyperkube
v1.27.11-rancher1

rancher/rke-tools
v0.1.96

rancher/mirrored-k8s-dns-*
1.22.28

rancher/mirrored-cluster-proportional-autoscaler
1.8.6

rancher/flannel-cni
v0.3.0-rancher8

rancher/mirrored-flannel-flannel
v0.21.4

rancher/mirrored-calico-*
v3.26.3

weaveworks/weave-*
2.8.1

noiro/* (All ACI images)
<IP_ADDRESS>.81c2369

rancher/mirrored-pause
3.7

rancher/nginx-ingress-controller
nginx-1.9.4-rancher1

rancher/mirrored-nginx-ingress-controller-defaultbackend
1.5-rancher1

rancher/mirrored-jettech-kube-webhook-certgen
v20231011-8b53cabe0

rancher/mirrored-metrics-server
v0.6.3

rancher/mirrored-coredns-coredns
1.9.4

rancher/mirrored-cluster-proportional-autoscaler
1.8.6

rancher/mirrored-k8s-dns-node-cache
1.22.28

Add-on Name
Add-on Template Version Constraint

Calico
calicov3261Rancher2

Canal
canalv3261Rancher2

Flannel
flannelv0214

CoreDNS
coreDnsv183Rancher2

KubeDNS
kubeDnsv116

MetricsServer
metricsServerv061

Weave
weavev122

Aci
aciv6032

NginxIngress
nginxIngressv194Rancher1

Nodelocal
nodelocalv121

v1.26.14-rancher1-1

Repository
Tag

rancher/mirrored-coreos-etcd
v3.5.10

rancher/hyperkube
v1.26.14-rancher1

rancher/rke-tools
v0.1.96

rancher/mirrored-k8s-dns-*
1.22.28

rancher/mirrored-cluster-proportional-autoscaler
1.8.6

rancher/flannel-cni
v0.3.0-rancher8

rancher/mirrored-flannel-flannel
v0.21.4

rancher/mirrored-calico-*
v3.26.3

weaveworks/weave-*
2.8.1

noiro/* (All ACI images)
<IP_ADDRESS>.81c2369

rancher/mirrored-pause
3.7

rancher/nginx-ingress-controller
nginx-1.9.4-rancher1

rancher/mirrored-nginx-ingress-controller-defaultbackend
1.5-rancher1

rancher/mirrored-jettech-kube-webhook-certgen
v20231011-8b53cabe0

rancher/mirrored-metrics-server
v0.6.3

rancher/mirrored-coredns-coredns
1.9.4

rancher/mirrored-cluster-proportional-autoscaler
1.8.6

rancher/mirrored-k8s-dns-node-cache
1.22.28

Add-on Name
Add-on Template Version Constraint

Calico
calicov3261Rancher2

Canal
canalv3261Rancher2

Flannel
flannelv0214

CoreDNS
coreDnsv183Rancher2

KubeDNS
kubeDnsv116

MetricsServer
metricsServerv061

Weave
weavev122

Aci
aciv6032

NginxIngress
nginxIngressv194Rancher1

Nodelocal
nodelocalv121

Fresh install checks - PASS

On rancher version v2.7.11-rc3, KDM pointing to dev-v2.7-2024-02-patches branch, cluster creation succeeds for v1.26.14-rancher1-1, v1.27.11-rancher1-1 on all network providers - canal/flannel/weave/calico
Network checks look good
Canal network checks look good

Upgrade checks - PASS

On rancher v2.7.10-rc3, KDM pointing to release-v2.7, cluster creation succeeds for k8s v1.26.13-rancher1-1, v1.27.10-rancher1-1 version with all network providers.
Pre-upgrade checks look good.
KDM points to dev-v2.7-2024-02-patches branch.
Upgraded cluster to k8s versions - v1.26.14-rancher1-1, v1.27.11-rancher1-1.
Post upgrade checks look good.

RKE default k8s version - PASS
dev-v2.7-2024-02-patches should have the default as v1.26.13-rancher1-1
"RKEDefaultK8sVersions": {
  "0.3": "v1.16.3-rancher1-1",
  "default": "v1.27.11-rancher1-1"
 }

RKE checks using v1.4.16-rc1 passed successfully.

Minimum rancher version checks - PASS

On rancher v2.7.5 with KDM pointing to dev-v2.7-2024-02-patches branch, cluster creation succeeds for v1.26.14-rancher1-1 versions with all network providers.
Network checks look good.
Canal network checks look good.


standard_init_linux.go:178: exec user process caused "exec format error"

Gitea version (or commit ref):
Docker image with latest tag from docker hub, built 9 hours ago (at the time of this writing)
Git version:
2.8.3 bundled within the image
Operating system:
Container: Alpine 3.4.6
Host: CoreOS Stable channel
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:
docker logs service_container_name outputs:
standard_init_linux.go:178: exec user process caused "exec format error"

Description
Just updated a gitea instance i have to the latest image available, and the service was unable to start
docker stack services gitea:
ID            NAME                    MODE             REPLICAS      IMAGE
njn2n9alnrg0  gitea_backend           replicated       0/1           gitea/gitea:latest
mhw4lxjig93e  gitea_db                replicated       1/1           postgres:9.6-alpine

When i see the logs docker logs service_container_name it outputs:
standard_init_linux.go:178: exec user process caused "exec format error"
So i had to roll back the to the 1.1.0 tag.

Unable to replicate, please re-open if needed


comment delete?

This may be something really simple I'm overlooking but how would I go about deleting a comment? I don't see any method that provide this function.
Thank you

you must create model traditionaly

You can delete your comments with the traditional way.


chore(blog): Add status post for week 41-20

Description

Add status post for week 41-20

@fmvilas made some final fixes, with 8:10 too


chore: create SVI example to live on the DSSG webpage

How would you all feel if I created an SVI example and put it on my github so that you could have it as an example on the DSSG website, at least until the Water Reuse one is complete? Alternatively, anyone else could do the same thing and link to theirs on the DSSG website. @npovejsil

I would appreciate it! At least to see if it maps for you using the SVI dataset.


Platform selector in gallery.

I feel like @dragostis filed a bug about this, but I don't find one.


Update Set-OwaMailboxPolicy.md

Added ProjectMocaEnabled parameter

Docs Build status updates of commit 911b4ab:
:clock10: Full build: the average full build time is 17 min(s) 40 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 911b4ab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-OwaMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Support selection of cited Zotero group library items

Per https://twitter.com/danstillman/status/1141812891542347781, there appears to be a separate syntax for selecting group library items:
zotero://select/library/items?itemKey=[key1],[key2],[keyn]
zotero://select/groups/:groupID/items?itemKey=[key1],[key2],[keyn]
Within Word .docx documents, the item URIs look like (courtesy to @bwiernik for the group library examples):
"uris":["http://zotero.org/users/1386342/items/TANS5GUE"]
"uris":["http://zotero.org/groups/227594/items/2TK9HDKD"]
"uris":["http://zotero.org/groups/2268106/items/A86NXHJE"]
In view of the selection link syntax, we'll have to provide individual selection links for items cited from a user's personal library, and for items cited from one or more group libraries. Maybe use a button dropdown (https://getbootstrap.com/docs/3.4/components/#btn-dropdowns-single) so the Reference Extractor user can select which library/group to select items for.

@bwiernik, can you confirm by the way that it's not possible in Zotero to have items from multiple libraries selected at the same time? (if it is possible, we could ask Zotero for a syntax that would allow items to be selected across libraries with a single link, but if it isn't, there is no point)

Could you make a URI with the syntax that might make it work? There isn’t a way to display multiple libraries in the interface at one time, so it’s not possible to manually select items from multiple libraries.

Could you make a URI with the syntax that might make it work?

No, Zotero would likely need to modify its UI code, and would have to adopt a different selection link scheme, e.g. something like zotero://select/items?itemKey=[key1],[groupID1|key2],[groupID2|key3]. I'll just look into generating separate selection links for each library for now, which should work out of the box.

@bwiernik, let me know how it works for you.


Update to Spring Boot 2.4.0 / Spring Framework 5.3.1 / Spring Security 5.4.1 / Reactor 3.4.0 / Micrometer 1.6.1

Update to Spring Boot 2.4.0
Update to Spring Framework 5.3.1
Update to Spring Security 5.4.1
Update to Project Reactor 3.4.0
Update to Micrometer 1.6.1

@deki @coheigea @amarkevich the update looks good now, one thing I intended to incorporate is switch to Maven Surefire 3.0.0-M5 (so we could run JUnit 4 & JUnit 5 test cases side by side) but I run into an issue with tooling tests org.apache.cxf.tools.common.ProcessorTestBase::getClassPath() which seems to be relying on some Surefire intrinsic details, probably better to tackle as separate effort. If no objections, I would like to merge it into master.


Tweetdeck will no longer opening ( Version 3.0.8 )

This is all I see when I try to open tweetdeck, it worked perfectly fine last night and now I open to only this. Reinstalled the entire thing on chrome but it's not coming back.

me too

"Found. Redirecting to https://twitter.com/i/premium_sign_up" is now displayed when attempting to log in.

This is sad, hoping for it to be fixed. :(

Can't confirm similar issue. Was working as of 2 hours ago

Can't confirm similar issue. Was working as of 2 hours ago

Consider checking again, same issue on my end and seems to have stopped not much more than half an hour ago.

Same issue here since like 30m

confirming issue. on latest build of oldtweetdeck the redirect goes through and takes me to the subscription popup. seems like they're actively trying to shut it down now.

Twitter killed all old versions of the API, meaning OldTweetDeck is dead at the moment, and will no longer allow multi account posting anymore once it's fixed.

Oof. Feed Frozen, then same issue.

Yes it would

I have just donated 50,- EUR via Paypal to keep you motivated ;-) Thanks so much for OldTweetdeck!

 Great! Thanks!!!!

Same here no longer working

Not working yet for me :(

Just stopped working for me too. Gah. I have been so grateful for this. Hope you can get it working again - thank you for your work on this!

It's back again, but I can only read all columns, but not tweet or reply ...

Updated to the new version and i think retweets are broken? I can't retweet anything anymore.

Stopped working for me today as well. Shame..

I installed the 3.1.0 version. Now I can see all the tweets running. However, I can do nothing (I can't tweet, retweet, etc).

Yeah. Same as Parrelo. I'm okay with this for now. Perhaps they added Premium checks to actions.

working for me. just reloaded, v3.7. thank you gods of tw.
On Wed, Sep 13, 2023 at 2:07 PM B. Keyport @.***> wrote:

Yeah. Same as Parrelo. I'm okay with this for now. Perhaps they added
Premium checks to actions.
—
Reply to this email directly, view it on GitHub
https://github.com/dimdenGD/OldTweetDeck/issues/94#issuecomment-1718317990,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCFHZA4CCIEQ5SKISOKGQMLX2IN7PANCNFSM6AAAAAA4WYNR2A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

i also cleared the cache and cleaned chrome of all cookies and stuff.
On Wed, Sep 13, 2023 at 2:08 PM MediaWest Productions @.***>
wrote:

working for me. just reloaded, v3.7. thank you gods of tw.
On Wed, Sep 13, 2023 at 2:07 PM B. Keyport @.***>
wrote:

Yeah. Same as Parrelo. I'm okay with this for now. Perhaps they added
Premium checks to actions.
—
Reply to this email directly, view it on GitHub
https://github.com/dimdenGD/OldTweetDeck/issues/94#issuecomment-1718317990,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCFHZA4CCIEQ5SKISOKGQMLX2IN7PANCNFSM6AAAAAA4WYNR2A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

i see i cant tweet from tw. just use the desktop version.
On Wed, Sep 13, 2023 at 2:09 PM MediaWest Productions @.***>
wrote:

i also cleared the cache and cleaned chrome of all cookies and stuff.
On Wed, Sep 13, 2023 at 2:08 PM MediaWest Productions @.***>
wrote:

working for me. just reloaded, v3.7. thank you gods of tw.
On Wed, Sep 13, 2023 at 2:07 PM B. Keyport @.***>
wrote:

Yeah. Same as Parrelo. I'm okay with this for now. Perhaps they added
Premium checks to actions.
—
Reply to this email directly, view it on GitHub
https://github.com/dimdenGD/OldTweetDeck/issues/94#issuecomment-1718317990,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCFHZA4CCIEQ5SKISOKGQMLX2IN7PANCNFSM6AAAAAA4WYNR2A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

on top of everything mentioned I can't view replies to tweets.

I can't view replies to tweets either

Now, this is what happens

Update to 3.1.1

Great. It working now. You're the best. Thanks!!!!!

Confirmed. Thanks, even works well with BTD.

Not working again. Sorry to send this messages but is just to inform you (I am recognized by your hard work, of course)

I'm sad it's not working, hope it gets fixed.

It works fine for me - I suspect it's because I'm lazy and went from 3.0.2 straight to 3.1.1
Would try reinstalling.

Works perfectly fine for me, and I updated every step of the way. Could be A/B testing on Twitter's side that's breaking it for some people but not others, but I'd try deleting any trace of prior versions, deleting Twitter cookies and starting fresh with the latest version.

It works fine for me too. The only thing I noticed is the fact that in the feed the tts stop running for almost a minute and after that is updated and restart this cycle (stop, jump, stop, jump). But I really don't know if this "bug" is caused by my machine....


Can advance past the end of video

If I am trying to advance more frames than there is in the video, I get this error freezing the app. It makes it impossible to save data after the issue

This was believed to be fixed but has occured again


Add support for custom success and error messages

Hello! My team faced with an Issue recently. We wanted a detailed information on success and error log messages so it would be easier for us to filter it in datadog service.
Currently the messages are "request completed" and "request errored" and there is no way to configure them so I decided to write them as a callbacks which accepts response and error objects.
If you ok with those changes, I'll add tests and update README in this PR.

Sure. I'll add tests and update README

Would you mind to add a unit test?
I added tests and updated the README

The API section of the readme has not been updated to reflect the new options.
I updated the README


EventBus: support KinesisStream target

Fixes #991.

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


Black Stone Revival

https://github.com/thisisyou33-publishing-networks/Black-Stone-Revival/blob/e6b82eb1154fbf8129ef9f2960b8fcb08e08b11f/SECURITY.md

[Black Stone Revival ]

https://www.facebook.com/100030807408746/posts/pfbid0pMx8VYbDctc6dEKfQrDvUGVNNUwYff9biusM9gkaCqZVbSWZdR7wmh2hrYfaCFZsl/?app=fbl


split spec files, for custom usage

fixed #3631
spec/dsl - renamed to spec/methods
move part of spec.cr to spec/dsl
require "spec/dsl"

begin
  1.should eq 2
rescue ex : Spec::AssertionFailed
  p ex.message
end

"expected: 2\n     got: 1"

Thanks! I think this split is harmless, so let's go with it :-)


Figure out how to handle types and specs

This isn't a priority but I would like to support both eventually.

I've been thinking about adding type comments in the same way flow allows now. That way the flow type checker could be used if desired.

Now realizing that for this project at least, thing probably don't matter as much. They are currently being explicitly ignored during the compilation process now.


DB: Ensure dbhandler Query and Exec are able to return error

ATM on error when calling Query or Exec app crash with log.Fatalxxx
While it's nice to crash early ... not sure it's quite that nice ;)
Add error to possible output of Query & Exec, with a nice(and appropriate) message.

#110 refactor to return error on query and go up.

Add function in tools to return error in API Avec indication DEbug user admin etc..


OPA Middleware Rego example has incorrect casing for "Authorization"

URL of the docs page
https://docs.dapr.io/reference/components-reference/supported-middleware/middleware-opa/
How is it currently worded?

Sample rego has incorrect casing on the Authorization matching string
        jwt = { "payload": payload } {
            auth_header := input.request.headers["authorization"]
            [_, jwt] := split(auth_header, " ")
            [_, payload, _] := io.jwt.decode(jwt)
        }

How should it be worded?

It should be as actually provided in the rego playground sample: https://play.openpolicyagent.org/p/oRIDSo6OwE
        jwt = { "payload": payload } {
            auth_header := input.request.headers["Authorization"]
            [_, jwt] := split(auth_header, " ")
            [_, payload, _] := io.jwt.decode(jwt)
        }

Screenshots

Additional context

/assign


Adds the netbeans.diff.default.compact system property for a more com…

…pact diff view that only shows the graphical diff and not the big tabbed pane with the graphical and text diff
This basically gets rid of these tab buttons (as well as the huge border on the macOS LnF) which saves about 45 pixels on my machine, ie. 2 lines of visible code:

+1 thanks for doing this

I do use the textual diff (at times its easier to spot differences there, than in graphics view). I'm not a big fan of adding random system properties, that at the end most people don't know about and won't use.
Would it be better to make this a config item? That way a normal user would have a change to find it.

Note the system property is documented in apichanges.xml
This seems like a good first step for people that need to see more lines of code in the diff window. If you need this, and search for it, you might find the magical incantation.
Long-term, this could morph into either some checkbox in Options or, even better, into a combobox in the diff window toolbar (or Options) allowing the user to toggle between the graphical / textual diff. This way the tab pane buttons take no extra height.
I would not add directly something in Options because my hope is to get to that combobox. But it requires quite some changes.

With the long-term vision in, I'm good with this. My doubt just came from personal experience: Who reads documentation?! (just kidding).


The heroku app is down

I have closed the heroku instance. You can run the api locally by following the instructions in readme.


Create GitHub Pages

Create a site for the repository showing examples of requests and possible tutorial.

Completed by PR #17


Coolify preset

A Nitro Coolify preset to standardise and improve security when deploying to Coolify.
Attached issue 2762.
❓ Type of change
Docs and Preset for Coolify.

[ x ] ✨ New feature (a non-breaking change that adds functionality)
[ x ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)

📚 Description
As discussed earlier over multiple channels with pi0 this is the right step moving forward.
Requesting feedback, the preset now correctly adds the start script to the output package.json.
📝 Checklist

[X] I have linked an issue or discussion.
[X] I have updated the documentation accordingly.

Currently I wouldn't call this a Coolify preset but rather a Nixpacks preset, since it has more to do with that compared to Coolify.
In particular, because if someone during a Coolify deployment picks a different Build Pack than this preset will be just useless or might become counterproductive in future versions.

To add onto this, since there will be a dedicated Nixpacks preset, we could create a dedicated [`nixpacks.toml' or `nixpacks.json` configuration file](https://nixpacks.com/docs/configuration/file) solely for proper Nitro/Nuxt deployments. Coping into the final image only the required folders and files (eg: `.output`).
While this is still not as optimized Dockerfile+Alpine images, it is still an improvement. With a downside that I still have no idea how to handle additional folders like content from @nuxt/content.

Thanks for your pull-request dear @justserdar and feedback @sandros94.
Few notes:

Please read nitro core principles in detail i have tried to explain.
#2762 is requires nitro + "coolify" recommended deployment method regardless of details. nixpacks/decker could be another preset we extend from but it is a detail.
We still have to find a way to deploy build output directory. Not project root.

As we take this step by step, I feel the PR is currently at the point of:
Preset:

[x] Append 'start' script.
[ ] Solution for handling the build output directory.
[ ] Making Coolify a provider by adding the neccesary deploy code.

Docs:

[x] Steps to get started in Coolify using Nixpacks (server)
[ ] Steps to get started in Coolify using Nixpacks (static)
[ ] Steps to get started in Coolify using Docker (server/static)


Update grpc-api, grpc-okhttp to 1.40.0

Updates

io.grpc:grpc-api
io.grpc:grpc-okhttp

from 1.39.0 to 1.40.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.grpc" } ]

labels: library-update, semver-minor

@mergifyio update


[Bug]: Floodlight T8423 cams disabled after HB restart

What happened?
Every time I restart homebridge, my flood light cameras T8423 are disabled.
When I open them in accessories page, it says:
HomeKit Camera Active	0
Manually Disabled	1
Manufacturer	Eufy
Model	FLOODLIGHT_CAMERA_8423
I have a 3rd indoor cam (pan&tilt 2k) and it works just fine.
Device Type
Floodlight (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.6.x (Supported)
NodeJS Version
v18 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
[9/21/2023, 8:24:43 AM] [homebridge-eufy-security] Loaded homebridge-eufy-security v2.2.19 child bridge successfully
[9/21/2023, 8:24:43 AM] Loaded 7 cached accessories from cachedAccessories.0E739E97776E.
[09/21/2023, 08:24:44]  [EufySecurity]  WARN    warning: planned changes, see https://github.com/homebridge-eufy-security/plugin/issues/1
[09/21/2023, 08:24:44]  [EufySecurity]  INFO    Country set: CZ
[09/21/2023, 08:24:44]  [EufySecurity]  INFO    Finished initializing![09/21/2023, 08:24:52]  [EufySecurity]  INFO    Updating existing accessory: T8030P23230302C1
[09/21/2023, 08:24:52]  [EufySecurity]  INFO    Updating existing accessory: Living Room
[09/21/2023, 08:24:52]  [EufySecurity]  INFO    Updating existing accessory: Floodlight T8423
[09/21/2023, 08:24:52]  [EufySecurity]  INFO    Updating existing accessory: Floodlight T8423
[09/21/2023, 08:24:54]  [EufySecurity]  INFO    CAM Indoor is set to balanced snapshot handling.
[09/21/2023, 08:24:54]  [EufySecurity]  INFO    CAM Frontyard is set to balanced snapshot handling.
[09/21/2023, 08:24:54]  [EufySecurity]  INFO    CAM Backyard is set to balanced snapshot handling.

config
{
            "username": "xxx",
            "password": "xxx",
            "country": "CZ",
            "deviceName": "",
            "platform": "EufySecurity",
            "cameras": [
                {
                    "serialNumber": "T8410P422242881C",
                    "enableCamera": "true",
                    "videoConfig": {
                        "audio": false,
                        "audioSampleRate": 0
                    },
                    "snapshotHandlingMethod": 2,
                    "refreshSnapshotIntervalMinutes": 0,
                    "useCachedLocalLivestream": false,
                    "rtsp": false,
                    "delayCameraSnapshot": false
                },
                {
                    "serialNumber": "T8423N10221004CC",
                    "enableCamera": "true",
                    "videoConfig": {
                        "audio": false,
                        "audioSampleRate": 0
                    },
                    "snapshotHandlingMethod": 2,
                    "delayCameraSnapshot": false
                },
                {
                    "serialNumber": "T8423N10221005CE",
                    "enableCamera": "true",
                    "videoConfig": {
                        "audio": false,
                        "audioSampleRate": 0
                    },
                    "snapshotHandlingMethod": 2
                }
            ],
            "_bridge": {
                "username": "0E:73:9E:97:77:6E",
                "port": 43050
            },
            "ignoreStations": [],
            "ignoreDevices": [],
            "cleanCache": true,
            "stations": [
                {
                    "serialNumber": "T8410P422242881C",
                    "manualTriggerModes": [
                        1,
                        2,
                        0,
                        3
                    ]
                },
                {
                    "serialNumber": "T8423N10221004CC",
                    "manualTriggerModes": [
                        0,
                        1,
                        2,
                        3
                    ]
                },
                {
                    "serialNumber": "T8423N10221005CE",
                    "manualTriggerModes": [
                        0,
                        1,
                        2,
                        3
                    ]
                }
            ],
            "pollingIntervalMinutes": 5,
            "enableDetailedLogging": false
        },

Hello @czbird77, if you just upgraded you will need to add manually cam.

Hi, I've managed to work around this issue, for some reason, the corresponding power switch accessories were disabled in HB. However, even after enabled, I still can't see stream preview in the Home app. Any clues? Thanks!

This is being closed as much of the work has already been completed in the new version. If you require assistance, please open a new case.


The "WmName" tag for the group settings

Please add "WmName" tag for the group settings. The "WmName" tag is WM_NAME property of a window.
 */

  /** List of match patterns for a group. */
  typedef struct PatternListType {
***************
*** 124,129 ****
--- 125,140 ----
     }
  }

+ void AddGroupWmName(GroupType *gp, const char *pattern)
+ {
+    Assert(gp);
+    if(JLIKELY(pattern)) {
+       AddPattern(&gp->patterns, pattern, MATCH_WMNAME);
+    } else {
+       Warning(_("invalid group name"));
+    }
+ }
+
  /** Add a pattern to a pattern list. */
  void AddPattern(PatternListType **lp, const char *pattern, MatchType match)
  {
***************
*** 181,195 ****
--- 192,210 ----
     GroupType *gp;
     char hasClass;
     char hasName;
+    char hasWmName;
     char matchesClass;
     char matchesName;
+    char matchesWmName;

     Assert(np);
     for(gp = groups; gp; gp = gp->next) {
        hasClass = 0;
        hasName = 0;
+       hasWmName = 0;
        matchesClass = 0;
        matchesName = 0;
+       matchesWmName = 0;
        for(lp = gp->patterns; lp; lp = lp->next) {
           if(lp->match == MATCH_CLASS) {
              if(Match(lp->pattern, np->className)) {
***************
*** 201,211 ****
                 matchesName = 1;
              }
              hasName = 1;
           } else {
              Debug("invalid match in ApplyGroups: %d", lp->match);
           }
        }
!       if(hasName == matchesName && hasClass == matchesClass) {
           ApplyGroup(gp, np);
        }
     }
--- 216,231 ----
                 matchesName = 1;
              }
              hasName = 1;
+          } else if(lp->match == MATCH_WMNAME) {
+             if(Match(lp->pattern, np->name)) {
+                matchesWmName = 1;
+             }
+             hasWmName = 1;
           } else {
              Debug("invalid match in ApplyGroups: %d", lp->match);
           }
        }
!       if(hasName == matchesName && hasClass == matchesClass && hasWmName == matchesWmName) {
           ApplyGroup(gp, np);
        }
     }
diff -cr old/src/group.h jwm-2.3.1/src/group.h
*** old/src/group.h 2015-07-30 10:38:01.000000000 +0300
--- jwm-2.3.1/src/group.h   2015-07-30 10:42:38.025426239 +0300
***************
*** 73,78 ****
--- 73,85 ----
   */
  void AddGroupName(struct GroupType *gp, const char *pattern);

+ /** Add a window name to a group.
+  * @param gp The group.
+  * @param pattern A pattern to match with the window name.
+  */
+ void AddGroupWmName(struct GroupType *gp, const char *pattern);
+
+
  /** Add a group option that doesn't take a value.
   * @param gp The group.
   * @param option The option.
diff -cr old/src/lex.c jwm-2.3.1/src/lex.c
*** old/src/lex.c   2015-06-29 01:21:20.000000000 +0300
--- jwm-2.3.1/src/lex.c 2015-07-30 10:41:52.032092604 +0300
***************
*** 86,92 ****
     { "TrayButtonStyle",    TOK_TRAYBUTTONSTYLE  },
     { "TrayStyle",          TOK_TRAYSTYLE        },
     { "Width",              TOK_WIDTH            },
!    { "WindowStyle",        TOK_WINDOWSTYLE      }
  };
  static const unsigned int TOKEN_MAP_COUNT
     = sizeof(TOKEN_MAP) / sizeof(TOKEN_MAP[0]);
--- 86,93 ----
     { "TrayButtonStyle",    TOK_TRAYBUTTONSTYLE  },
     { "TrayStyle",          TOK_TRAYSTYLE        },
     { "Width",              TOK_WIDTH            },
!    { "WindowStyle",        TOK_WINDOWSTYLE      },
!    { "WmName",             TOK_WMNAME           }
  };
  static const unsigned int TOKEN_MAP_COUNT
     = sizeof(TOKEN_MAP) / sizeof(TOKEN_MAP[0]);
diff -cr old/src/lex.h jwm-2.3.1/src/lex.h
*** old/src/lex.h   2015-06-29 01:21:20.000000000 +0300
--- jwm-2.3.1/src/lex.h 2015-07-30 10:38:56.375424787 +0300
***************
*** 82,88 ****
     TOK_TRAYBUTTONSTYLE,
     TOK_TRAYSTYLE,
     TOK_WIDTH,
!    TOK_WINDOWSTYLE

  } TokenType;

--- 82,89 ----
     TOK_TRAYBUTTONSTYLE,
     TOK_TRAYSTYLE,
     TOK_WIDTH,
!    TOK_WINDOWSTYLE,
!    TOK_WMNAME

  } TokenType;

diff -cr old/src/parse.c jwm-2.3.1/src/parse.c
*** old/src/parse.c 2015-07-30 10:38:01.000000000 +0300
--- jwm-2.3.1/src/parse.c   2015-07-30 10:41:39.822092523 +0300
***************
*** 1714,1719 ****
--- 1714,1722 ----
        case TOK_NAME:
           AddGroupName(group, np->value);
           break;
+       case TOK_WMNAME:
+          AddGroupWmName(group, np->value);
+          break;
        case TOK_OPTION:
           ParseGroupOption(np, group, np->value);
           break;

My biggest concern for this is that the window title can change while a window is mapped and may not even be set when a window is mapped.  This could cause confusing behaviour.  According to the ICCCM, WM_CLASS should not be changed while a window is mapped (http://tronche.com/gui/x/icccm/sec-4.html#s-<IP_ADDRESS>), which makes it much nicer for loading group options, since that can be checked only when a window is mapped.
I can see why someone might want this setting from an ease of configuration standpoint, but unfortunately, I really don't think it's safe to rely on the window title.

The property is need for change the one window of the program.
Example:
   <Group>
      <WmName>^pgAdmin III$</WmName>
      <Option>notitle</Option>
      <Option>maximized</Option>
      <Option>noborder</Option>
   </Group>

For safety, can be used with the WM_CLASS:
   <Group>
      <WmName>^pgAdmin III$</WmName>
      <Class>Pgadmin3</Class>
      <Option>notitle</Option>
      <Option>maximized</Option>
      <Option>noborder</Option>
   </Group>

WM_CLASS has both a name and class field (Name matches the name field).  The instance name field is intended for this type of thing.  If the instance name can't be used for this, I tend to think that's a problem with the client program.
The problem with using the title is that it can change and may be unset when the window is mapped, in which case JWM will not know to do the right thing (JWM only applies group settings on map).  Combining with class would prevent a group from applying to an unintended window, but it won't ensure that this applies to desired windows.
If JWM were to do this, there would need to be a caveat mentioned in the documentation that it doesn't always work, which would lead to an issue to fix it so it always works (re-apply groups when the title changes).  Of course, that would be a rather involved change.

IMHO this is a problem user. It is up to you.

I could see this making sense is if the name property accepted a regex or globbing

JWM does support regular expressions for group options.  However, I really don't think it would be worth the effort to make JWM apply the groups when a title changed, which would be required for this to be implemented properly.

Pull request: #265

I can understand wanting this, but unless windows that set the title after mapping (or change titles) can be handled, I don't think this should be supported.  To only support windows that set the title before mapping seems likely to cause confusion.  Further, the WM_CLASS property is set to enable this type of functionality (without needing to resort to regexes on arbitrary window titles).


refactor: Make launch state and components generic

This is a refactoring step to prepare the launch state machine and components for being able to handle tasks as a source.
I separated the state machine into a base config that is composed into more specific machines for workflow and task launching.
The form components and state hook were also made generic and now accept the xstate state/service generated by interpreting either a workflow or task machine. The base LaunchForm component will now conditionally render the correct form component based on the props passed to it.

Codecov Report

Merging #100 into single-task-execution will increase coverage by 0.17%.
The diff coverage is 87.50%.

@@                    Coverage Diff                    @@
##           single-task-execution     #100      +/-   ##
=========================================================
+ Coverage                  67.71%   67.89%   +0.17%
=========================================================
  Files                        374      377       +3
  Lines                       6078     6108      +30
  Branches                     947      946       -1
=========================================================
+ Hits                        4116     4147      +31
+ Misses                      1962     1961       -1

Impacted Files
Coverage Δ

src/components/Launch/LaunchForm/BlobInput.tsx
75.00% <ø> (ø)

...c/components/Launch/LaunchForm/CollectionInput.tsx
19.35% <ø> (ø)

src/components/Launch/LaunchForm/DatetimeInput.tsx
66.66% <ø> (ø)

...omponents/Launch/LaunchForm/SearchableSelector.tsx
92.63% <ø> (ø)

src/components/Launch/LaunchForm/SimpleInput.tsx
96.55% <ø> (ø)

.../components/Launch/LaunchForm/UnsupportedInput.tsx
100.00% <ø> (ø)

...unch/LaunchForm/UnsupportedRequiredInputsError.tsx
94.11% <ø> (ø)

src/components/Launch/LaunchForm/constants.ts
100.00% <ø> (ø)

src/components/Launch/LaunchForm/getInputs.ts
96.15% <ø> (ø)

.../components/Launch/LaunchForm/inputHelpers/blob.ts
93.18% <ø> (ø)

... and 38 more

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 c5462f6...8aa7a77. Read the comment docs.


[WIP] My experiences with acid-store

First of all, thanks a lot for making this crate! I am very interested in trying it out, and am currently experimenting with it. This issue is a platform for communicating my findings and experiences in the hopes to provide you with yet another usecase which might one day be supported.
Motivation
I am building a mining platform for crates.io which consists of 3 stages:

fetch changes

The first fetch will always be all crate versions thus far, which is ~215000. Then it fetches changes again in intervals, and won't see more than say 100 new crate versions per day
Receiving the first batch of 215000 is incredibly fast, as it basically serializes all of the them from memory into the database.
it also stores crate objects which are merely the available versions per crate. There are ~36000 of them.

processing

This stage runs in intervals and will iterate all crate versions to see if there are unfinished tasks. Tasks are currently downloading the crate and extracting it to gather meta-data. Tasks are stored as small objects that serve as markers. For two tasks currently available, it would store numCrates times two small task types.
Each task produces a task result to store the outcome of the computation.
more tasks are planned

reporting
runs in intervals, and traverses all crate versions and generates one or more HTML files for displaying intelligence obtained from the data we gathered thus far.
to avoid generating a page needlessly, it marks the presence of a page in the database （even though right now it marks them with symlinks)

For the current implementation, we are talking about 6 * 215000 + 36000 objects, that are read often, and usually written in small batches, excluding the first run when we see all ~215k crate versions at once.
Eventually I would like to run 'criner' on a Raspberry Pi with 512MB of memory for all tasks that don't require running cargo/rustc. Thus I would prefer a DB which trades of speed for lower and predictable memory consumption. Sled clearly is optimized for speed, which is great, but it's something I can't even pay for on my current hardware as it simply consumes too much memory when during migrations and when there are too many objects.
The current database
The database of choice is Sled, but I ran into the following issues that make me seek out an alternative.

high memory usage when using many tiny objects
performance issues when using criner

Despite sled generally being lightning fast, it costs a lot of memory to support it. Now I run into problems where the memory consumption is disproportional and so high that I feel uncomfortable proceeding with it. Database sizes tend to be large, even though that isn't my primary concern. It's the concern of not being able to interact with the data anymore that one spent days producing. For instance, migrating from one version to another once took 50GB in memory (and it's a wonder my MBPro did not die trying, but completed the herculean task).
Observations
Migration

When transferring all data in Sled to an ObjectRepository with SQLite backend, while doing a commit only at the end of all object write, the processing got slower and slower the more objects were uncommitted. I will try committing every 1000 objects to see if the performance slowdown is caused by the commit mechanism, or the underlying database. Edit: Committing every 1000 or 100 objects avoids the slowdown.

When looking at IO statistics at the end of writing ~210k objects into SQLite, it tooks about 6GB of writes to produce a 115MB file.

SQLite files are small! This seems great, especially after seeing sled easily take 10GB

When using an ObjectRepository with a DirectoryBackend, the removal of obsolete objects was prohibitively slow. The runtime was dominated by IO calls.

It's surprisingly hard to 'open or create' a database.

I would love to disable encryption and compression with cargo features, they pull in around 100 additional crates to compile.

I hope you find this information useful.
acid-store has incredibly interesting properties, and I feel that with encryption, compression and deduplication along with an sqlite container, it could be an amazing storage format for sensitive data, and more.
Of course, all that comes at a cost so for my particular usecase, it's too slow and would block criner on IO all the time. Recent tests show that even naive usage of sqlite is orders of magnitudes faster.

Thank you so much for this feedback @Byron! Sorry it took me so long to reply—things have been kinda hectic lately and I apparently had email notification disabled (whoops). I really appreciate the thorough testing.
Performance is something I plan to work on. I'll try and do the following:

Look into why performance degrades with many uncommitted objects
Try to reduce the number of writes where possible
Improve performance cleaning up obsolete objects (I have some ideas here)
Add an option to open or create a data store (or at least check whether a data store exists)
Gate encryption/compression behind cargo features (you're right; that's a lot of dependencies)

Thanks again!


Refactor plugin configurations

The configurations of metric plugins and check plugins are contained in Config.Plugin. It makes it easy to decode from the configuration file. But basically we should differentiate the struct of metric plugin and check plugin in my opinion. A check plugin config has NotificationInterval field but a metric plugin config does not.
This pull request introduces MetricPlugin and CheckPlugin and now a Config has MetricPlugins and CheckPlugins. The method *Config.buildPlugins builds these plugin configurations and clears the Plugin field to stop others use this field later. I think we should remove this field if possible and move the building phase on toml unmarshalization but I'm not sure how to do.

I think we should remove this field if possible and move the building phase on toml unmarshalization but I'm not sure how to do.

Maybe we can do it by implementing UnmarshalTOML for config.Plugin?
https://godoc.org/github.com/BurntSushi/toml#Unmarshaler
https://godoc.org/github.com/BurntSushi/toml#ex-package--UnmarshalTOML

Maybe we can do it by implementing UnmarshalTOML for config.Plugin?

Yes, probably we have to implement unmarshalizer by hand using reflect. I think it does too much...

func createTagMap(rv reflect.Type) map[string]int {
	num := rv.NumField()
	ret := make(map[string]int)
	for i := 0; i < num; i += 1 {
		field := rv.Field(i)
		name := field.Tag.Get("toml")
		if name == "" {
			name = strings.ToLower(field.Name)
		}
		ret[name] = i
	}
	return ret
}

// UnmarshalTOML defines how to decode toml data to Config
func (conf *Config) UnmarshalTOML(data interface{}) error {
	dataMap, ok := data.(map[string]interface{})
	if !ok != nil {
		return errors.New("type mismatch for Config: expected a map but found %T", data)
	}
	rv := reflect.ValueOf(v)
	if rv.IsNil() {
		return errors.New("Decode of nil %s", reflect.TypeOf(v))
	}
	tm := createTagMap(rv.Type())
	for key, datum := range dataMap {
		if key == "plugin" {
			continue
		}
		if i, ok := tm[key]; ok {
			switch rv.Field(i).Kind() {
			case reflect.String:
				// Apibase, Apikey, etc
				rv.Field(i).Set(reflect.ValueOf...
			case reflect.Struct:
				// ConnectionConfig, HostStatus, FileSystems
				Unmarshalize again and again...
		}
	}
}

LGTM!

Thank you!


private password protected registry

Is it possible to create a container from a image that sits in a private password protected registry?

Shipyard v3 has been released and is a major refactor. Could you please check to see if this is still an issue? If so, please re-open. Thanks!


Combine V1 and V2 Functionalities

Thanks for stopping by to let us know something could be better!
Is your feature request related to a problem? Please describe.
The V1 version of the Resource Manager Java SDK has functionality related to Projects, and the V2 version of the Resource Manager Java SDK has functionality related to Folders. It's extremely frustrating that I cannot use both V1 and V2 libraries at the same time.
Describe the solution you'd like
I would like to see the two libraries combined into a single package. ServiceUsage library for example, utilizes a .v1 in the package name.
Combining in the way mentioned below, would enable this change to happen in a non-breaking enhancement.
V2 would have a .v1 namespace containing the V1 functionality.
V1 would have a .v2 namespace containing the V2 functionality.
Describe alternatives you've considered
None - I posted on stack overflow.
https://stackoverflow.com/questions/65115397/gcp-java-sdk-cloud-resource-manager-conflicting-dependencies-for-project-and-f?noredirect=1#comment115130966_65115397
Additional context
Any other context or screenshots about the feature request.

We just released a v3 client in 0.119.0 which should contain the functionality from v1 and v2. It's a gRPC-based, fully-generated client so the usage will be different (follows the same patterns as other fully-generated google-cloud-* libraries).


investigate the use of google benchmark for Shogun

https://github.com/google/benchmark
we do have a benchmark folder, but this could maybe be done more systematically?

I wrote hayai benchmarks to compare native and eigen3 dots. Sharing it if it is helpful for someone :)
https://gist.github.com/sanuj/1099abec85e90b11eb0d

I like that framework. Is it well maintained? Thats a big plus for the google one ..... in addition to the readme being shorter ;)

@karlnapf hayai is header only which is an advantage - we could just take the code once. As it is dead simple we can maintain that by ourselves

I would like to avoid any overhead and stick to standard things to do that. But if it is that easy, why not

We now have benchmarks going.


Maintain single branch

As stated by @lasley in https://github.com/Tecnativa/docker-odoo-base/issues/1#issuecomment-270717480, we should have only one branch with conditional install scripts depending on the Odoo version being installed.

Huzzaah!
PS. I'm just using a lot of your code in my Docker at the moment, but will begin converting soon. Found a bug or two that I'll submit upstream too as I finish testing 😄

Closed in 90b21f4fec66405a2c6f2d4fdaf5c8fc8dada88f (it did not close #1, but prepared it to be in the master branch). BTW I'm using now docker hub as a testing CI.

Is Dockerhub able to add statuses into PRs?

i'm afraid not, that's the use case that would justify another CI indeed.

Yeah tags were the only idea I could come up with too. Oh well, I'll keep working on the docker-quality-tools then, but make it more compatible with the existing hub tests instead of the duct-tape stuff going on now.


[Feature] Add Flac support to GTA III & VC

Flac support would be cool for VC and would help save a few GB on my PC

Due to III and VC having mss this is technically out of scope (to be fair, this addition was out of scope for San Andreas too, but what's done is done) and would be better suited for a separate plugin much like VBdec, but I will keep it open here for tracking purposes.


Define the order of links in sidebar

What kind of changes does this PR include?

Changes to Starlight code

Description

What does this PR change?
This allows the user to define the order that document links are displayed in, in the sidebar, when autogenerate is used. If no order is defined then the default alphabetical order is used.
Did you change something visual? No

That's ok @delucis, I don't mind you commandeering as my time is a bit limited at the moent.
You may want to add a recomendation to the docs around ordering the pages in counts of 5 or 10 so that if a page needs to be added between existing pages then it reduces the need to change the numbering of every other page.


Error occurred when executing FaceParse(FaceParsing):  module 'matplotlib.cm' has no attribute 'get_cmap'

Hi
Can anyone help with this error?:
Error occurred when executing FaceParse(FaceParsing):
module 'matplotlib.cm' has no attribute 'get_cmap'
So far I have:
I've installed all of the requirements.txt file
Uninstalled and re-installed the nodes
Restarted the server
Tried various versions of metalotlib
Full error message:
Error occurred when executing FaceParse(FaceParsing):
module 'matplotlib.cm' has no attribute 'get_cmap'
File "C:\Users\ai\ComfyUI\execution.py", line 151, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "C:\Users\ai\ComfyUI\execution.py", line 81, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "C:\Users\ai\ComfyUI\execution.py", line 74, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
File "C:\Users\ai\ComfyUI\custom_nodes\comfyui_face_parsing\face_parsing_nodes.py", line 582, in main
colormap = cm.get_cmap('viridis', 19)
Thank you

sorry for the delay. it seems that the new matplotlib 3.9 has removed the function. i have updated the code, and it should be fixed now.


Select query from Different Databases (on same server)

Hi, there.
I was trying to do:
var cps = require('cps');
var db = require('node-mysql');

var box = new db.DB({{
 host: 'localhost',
 user: 'username',
 password: 'pass'
});

var basicTest = function(cb) {
    box.connect(function(conn, cb) {
        cps.seq([
            function(_, cb) {
                conn.query('select * from DATABASE.TABLE limit 12', cb);
            },
            function(res, cb) {
                console.log('Result:', res);
                cb();
            }
        ], cb);
    }, cb);
};

basicTest(function(){
    console.log("Done");
});

Cannot get results without connecting to specific DATABASE

I believe you can just connect to any database and write your query with the DATABASE.TABLE format.


Evergreen: Updated static checks

Ensures that Kotlin and Scala checks are also run.
JAVA-5095

Only needs a single LGTM - so first reviewer wins.


[Docs] fix props anchor links

All anchor links are broken because of https://github.com/facebook/react-native/blob/master/website/core/Site.js#L37 base tag it means that relative urls won't work.
closes #5450
proof

@facebook-github-bot shipit

@vjeux I'm so sorry. I wanted to update PR to fix others anchor links. Can I update this one or create separate PR?

@facebook-github-bot shipit

@vjeux again I'm sorry. At last update I fixed anchors on support page and clean code a little bit. Could you please ship again?

Erg sorry, I was too fast :p I can't shipit again but can you open up a pull request with the changes and i'll make sure to merge them in