Enable CiliumNetworkPolicy between loki components

Due to a change in onprem MCs, we need to enable cilium network policy between all loki components, otherwise they cannot communicate with each other

I will enable the cilium netpol from upstream. What are the affected MCs ?

@QuantumEnigmaa can you link the upstream issue here ?

Sure ! There it is : https://github.com/grafana/loki/pull/11838

Getting released into https://github.com/giantswarm/loki-app/pull/284

This is not solved:
For backend pods we have this:
evel=info ts=2024-02-14T14:20:13.880016205Z caller=reporter.go:305 msg="failed to send usage report" retries=0 err="Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
level=info ts=2024-02-14T14:20:19.915226327Z caller=reporter.go:305 msg="failed to send usage report" retries=1 err="Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
level=info ts=2024-02-14T14:20:27.010931417Z caller=reporter.go:305 msg="failed to send usage report" retries=2 err="Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
level=info ts=2024-02-14T14:20:38.67392354Z caller=reporter.go:305 msg="failed to send usage report" retries=3 err="Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
level=info ts=2024-02-14T14:20:54.911201185Z caller=reporter.go:305 msg="failed to send usage report" retries=4 err="Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
level=info ts=2024-02-14T14:20:54.911313916Z caller=reporter.go:281 msg="failed to report usage" err="5 errors: Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers); Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers); Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers); Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers); Post \"https://stats.grafana.org/loki-usage-report\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
level=warn ts=2024-02-14T14:21:13.248449982Z caller=tcp_transport.go:437 component="memberlist TCPTransport" msg="WriteTo failed" addr=<IP_ADDRESS>:7946 err="dial tcp <IP_ADDRESS>:7946: i/o timeout"
level=info ts=2024-02-14T14:21:13.87920526Z caller=reporter.go:305 msg="failed to send usage report" retries=0 err="Post \"https://stats.grafana.org/loki-usage-report\": proxyconnect tcp: dial tcp <IP_ADDRESS>:3128: i/o timeout (Client.Timeout exceeded while awaiting headers)"
level=warn ts=2024-02-14T14:21:15.744060127Z caller=tcp_transport.go:437 component="memberlist TCPTransport" msg="WriteTo failed" addr=<IP_ADDRESS>:7946 err="dial tcp <IP_ADDRESS>:7946: i/o timeout"
level=warn ts=2024-02-14T14:21:17.849164994Z caller=tcp_transport.go:437 component="memberlist TCPTransport" msg="WriteTo failed" addr=<IP_ADDRESS>:7946 err="dial tcp <IP_ADDRESS>:7946: i/o timeout"

Not sure what happens with the gateways:
> k logs -n loki loki-gateway-85d6b554b6-4qjtx -c nginx
/docker-entrypoint.sh: No files found in /docker-entrypoint.d/, skipping configuration
> k logs -n loki loki-gateway-85d6b554b6-pp4jr
Defaulted container "nginx" out of: nginx, dnsmasq
/docker-entrypoint.sh: No files found in /docker-entrypoint.d/, skipping configuration

Loki read pods:
evel=info ts=2024-02-14T14:22:50.419026941Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"
level=info ts=2024-02-14T14:22:55.164117669Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"
level=warn ts=2024-02-14T14:22:59.413270393Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:41989-><IP_ADDRESS>:1053: i/o timeout"
level=info ts=2024-02-14T14:23:00.419440574Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"
level=warn ts=2024-02-14T14:23:04.373897014Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:54379-><IP_ADDRESS>:1053: i/o timeout"
level=info ts=2024-02-14T14:23:10.419347589Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"
level=warn ts=2024-02-14T14:23:12.415151604Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:54659-><IP_ADDRESS>:1053: i/o timeout"
level=info ts=2024-02-14T14:23:20.419586009Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"
level=warn ts=2024-02-14T14:23:24.37578316Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:39492-><IP_ADDRESS>:1053: i/o timeout"
level=warn ts=2024-02-14T14:23:25.417421171Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:35322-><IP_ADDRESS>:1053: i/o timeout"
level=info ts=2024-02-14T14:23:30.419334606Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"
level=warn ts=2024-02-14T14:23:38.419479008Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:57308-><IP_ADDRESS>:1053: i/o timeout"
level=info ts=2024-02-14T14:23:40.419139546Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"
level=warn ts=2024-02-14T14:23:44.3777889Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:42681-><IP_ADDRESS>:1053: i/o timeout"
level=info ts=2024-02-14T14:23:50.419512862Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"
level=warn ts=2024-02-14T14:23:51.421193603Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:57727-><IP_ADDRESS>:1053: i/o timeout"
level=info ts=2024-02-14T14:24:00.419691585Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"
level=warn ts=2024-02-14T14:24:04.379832734Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:60039-><IP_ADDRESS>:1053: i/o timeout"
level=warn ts=2024-02-14T14:24:04.423074389Z caller=dns_resolver.go:225 msg="failed DNS A record lookup" err="lookup query-scheduler-discovery.loki.svc.cluster.local. on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:33488-><IP_ADDRESS>:1053: i/o timeout"
level=info ts=2024-02-14T14:24:05.163507541Z caller=frontend.go:316 msg="not ready: number of schedulers this worker is connected to is 0"

ts=2024-02-14T14:17:25.908295609Z caller=memberlist_logger.go:74 level=warn msg="Failed to resolve loki-memberlist: lookup loki-memberlist on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:55240-><IP_ADDRESS>:1053: i/o timeout"
level=warn ts=2024-02-14T14:17:25.908359195Z caller=memberlist_client.go:595 msg="joining memberlist cluster: failed to reach any nodes" retries=5 err="1 error occurred:\n\t* Failed to resolve loki-memberlist: lookup loki-memberlist on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:55240-><IP_ADDRESS>:1053: i/o timeout\n\n"

I think a few of those issues are related to coredns not being accessible

Sadly I cannot open hubble on gerbil

Here is the list of blocked connections:
b 15 10:53:22.837: kube-system/prometheus-prometheus-agent-0:49430 (ID:2328) <> loki/loki-backend-1:3100 (ID:1697) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:25.796: kube-system/prometheus-prometheus-agent-0:34740 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:26.325: kube-system/prometheus-prometheus-agent-0:41304 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:26.805: kube-system/prometheus-prometheus-agent-0:34740 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:28.821: kube-system/prometheus-prometheus-agent-0:34740 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:30.598: kube-system/prometheus-prometheus-agent-0:51038 (ID:2328) <> loki/loki-backend-1:3100 (ID:1697) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:30.932: kube-system/prometheus-prometheus-agent-0:35740 (ID:2328) <> loki/loki-backend-1:3100 (ID:1697) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:31.605: kube-system/prometheus-prometheus-agent-0:51038 (ID:2328) <> loki/loki-backend-1:3100 (ID:1697) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:33.077: kube-system/prometheus-prometheus-agent-0:34740 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:33.621: kube-system/prometheus-prometheus-agent-0:51038 (ID:2328) <> loki/loki-backend-1:3100 (ID:1697) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:35.637: kube-system/prometheus-prometheus-agent-0:41304 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: ACK, FIN, PSH)
Feb 15 10:53:36.117: kube-system/prometheus-prometheus-agent-0:42396 (ID:2328) <> loki/loki-read-57fb9575dd-22nxt:3100 (ID:10532) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:36.898: kube-system/ingress-nginx-controller-75b9d479b4-x24br:34170 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:36.945: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:45644 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:37.153: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:45644 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:37.361: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:45644 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:37.482: kube-system/ingress-nginx-controller-75b9d479b4-x24br:60926 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:37.685: kube-system/prometheus-prometheus-agent-0:57718 (ID:2328) <> loki/loki-backend-0:3100 (ID:10253) Policy denied DROPPED (TCP Flags: ACK, FIN, PSH)
Feb 15 10:53:37.685: kube-system/prometheus-prometheus-agent-0:51038 (ID:2328) <> loki/loki-backend-1:3100 (ID:1697) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:37.738: kube-system/ingress-nginx-controller-75b9d479b4-x24br:44798 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: ACK, FIN)
Feb 15 10:53:37.781: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:45644 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:37.794: kube-system/ingress-nginx-controller-75b9d479b4-x24br:60928 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:37.899: kube-system/ingress-nginx-controller-75b9d479b4-x24br:34170 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:38.587: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:47984 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:38.613: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:45644 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:38.826: kube-system/ingress-nginx-controller-75b9d479b4-x24br:60928 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:39.274: kube-system/ingress-nginx-controller-75b9d479b4-x24br:44798 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:39.498: kube-system/ingress-nginx-controller-75b9d479b4-x24br:60926 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:39.594: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:47984 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:39.733: kube-system/prometheus-prometheus-agent-0:54214 (ID:2328) <> loki/loki-read-57fb9575dd-n6946:3100 (ID:10532) Policy denied DROPPED (TCP Flags: ACK, FIN, PSH)
Feb 15 10:53:39.733: kube-system/prometheus-prometheus-agent-0:35740 (ID:2328) <> loki/loki-backend-1:3100 (ID:1697) Policy denied DROPPED (TCP Flags: ACK, FIN, PSH)
Feb 15 10:53:39.914: kube-system/ingress-nginx-controller-75b9d479b4-x24br:34170 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:40.245: kube-system/prometheus-prometheus-agent-0:42396 (ID:2328) <> loki/loki-read-57fb9575dd-22nxt:3100 (ID:10532) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:40.277: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:45644 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:40.795: kube-system/prometheus-prometheus-agent-0:53078 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:40.842: kube-system/ingress-nginx-controller-75b9d479b4-x24br:60928 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:40.915: kube-system/prometheus-prometheus-agent-0:57314 (ID:2328) <> loki/loki-write-0:3100 (ID:1360) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:41.428: kube-system/prometheus-prometheus-agent-0:41304 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:41.475: kube-system/ingress-nginx-controller-75b9d479b4-x24br:41364 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:41.578: kube-system/prometheus-prometheus-agent-0:42348 (ID:2328) <> loki/loki-write-0:3100 (ID:1360) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:41.618: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:47984 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:41.813: kube-system/prometheus-prometheus-agent-0:53078 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:41.897: kube-system/ingress-nginx-controller-75b9d479b4-x24br:45944 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:41.941: kube-system/prometheus-prometheus-agent-0:57314 (ID:2328) <> loki/loki-write-0:3100 (ID:1360) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:41.987: kube-system/prometheus-prometheus-agent-0:44280 (ID:2328) <> loki/loki-backend-0:3100 (ID:10253) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:42.506: kube-system/ingress-nginx-controller-75b9d479b4-x24br:41364 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:42.602: kube-system/prometheus-prometheus-agent-0:57718 (ID:2328) <> loki/loki-backend-0:3100 (ID:10253) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:42.793: kube-system/ingress-nginx-controller-75b9d479b4-x24br:41378 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:42.922: kube-system/ingress-nginx-controller-75b9d479b4-x24br:45944 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:42.997: kube-system/prometheus-prometheus-agent-0:44280 (ID:2328) <> loki/loki-backend-0:3100 (ID:10253) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:43.573: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:45644 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: ACK)
Feb 15 10:53:43.588: kube-system/ingress-nginx-controller-75b9d479b4-8rwjd:55430 (ID:23796) <> loki/loki-gateway-85d6b554b6-4qjtx:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:43.818: kube-system/ingress-nginx-controller-75b9d479b4-x24br:41378 (ID:23796) <> loki/loki-gateway-85d6b554b6-pp4jr:8080 (ID:34283) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:43.829: kube-system/prometheus-prometheus-agent-0:53078 (ID:2328) <> loki/loki-write-1:3100 (ID:23001) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:43.833: kube-system/prometheus-prometheus-agent-0:44732 (ID:2328) <> loki/loki-read-57fb9575dd-22nxt:3100 (ID:10532) Policy denied DROPPED (TCP Flags: ACK, FIN, PSH)
Feb 15 10:53:43.943: kube-system/prometheus-prometheus-agent-0:56708 (ID:2328) <> loki/loki-read-57fb9575dd-n6946:3100 (ID:10532) Policy denied DROPPED (TCP Flags: SYN)
Feb 15 10:53:43.957: kube-system/prometheus-prometheus-agent-0:57314 (ID:2328) <> loki/loki-write-0:3100 (ID:1360) Policy denied DROPPED (TCP Flags: SYN)

I've done some manual changes to the CNPs (which I'll push upstream) and it looks better for the write pods ;
level=info ts=2024-02-15T13:17:44.87193431Z caller=checkpoint.go:611 msg="starting checkpoint"
level=info ts=2024-02-15T13:17:44.872294014Z caller=checkpoint.go:336 msg="attempting checkpoint for" dir=/var/loki/wal/checkpoint.004935
level=info ts=2024-02-15T13:17:44.875514858Z caller=checkpoint.go:498 msg="atomic checkpoint finished" old=/var/loki/wal/checkpoint.004935.tmp new=/var/loki/wal/checkpoint.004935
level=info ts=2024-02-15T13:18:04.863673219Z caller=table_manager.go:136 index-store=boltdb-shipper-2023-01-24 msg="uploading tables"
level=info ts=2024-02-15T13:18:04.86489981Z caller=table_manager.go:171 index-store=boltdb-shipper-2023-01-24 msg="handing over indexes to shipper"
level=info ts=2024-02-15T13:18:04.864944863Z caller=table_manager.go:136 index-store=tsdb-2024-01-02 msg="uploading tables"
level=info ts=2024-02-15T13:19:04.863795698Z caller=table_manager.go:136 index-store=boltdb-shipper-2023-01-24 msg="uploading tables"
level=info ts=2024-02-15T13:19:04.864802049Z caller=table_manager.go:171 index-store=boltdb-shipper-2023-01-24 msg="handing over indexes to shipper"
level=info ts=2024-02-15T13:19:04.864838685Z caller=table_manager.go:136 index-store=tsdb-2024-01-02 msg="uploading tables"

However backend pods are not logging anything useful. Gateway pods are still having troubles :
2024/02/15 13:19:52 [error] 9#9: *8564 loki-multi-tenant-proxy.loki.svc.cluster.local could not be resolved (3: Host not found), client: <IP_ADDRESS>, server: , request: "POST /loki/api/v1/push HTTP/1.1", host: "loki.gerbil.test.gigantic.io"
<IP_ADDRESS> - gerbil [15/Feb/2024:13:19:52 +0000]  502 "POST /loki/api/v1/push HTTP/1.1" 157 "-" "GrafanaAgent/v0.37.2" "<IP_ADDRESS>"
2024/02/15 13:19:58 [error] 9#9: *8562 loki-multi-tenant-proxy.loki.svc.cluster.local could not be resolved (3: Host not found), client: <IP_ADDRESS>, server: , request: "POST /loki/api/v1/push HTTP/1.1", host: "loki.gerbil.test.gigantic.io"
<IP_ADDRESS> - gerbil [15/Feb/2024:13:19:58 +0000]  502 "POST /loki/api/v1/push HTTP/1.1" 157 "-" "GrafanaAgent/v0.37.2" "<IP_ADDRESS>"
2024/02/15 13:20:09 [error] 9#9: *8564 loki-multi-tenant-proxy.loki.svc.cluster.local could not be resolved (3: Host not found), client: <IP_ADDRESS>, server: , request: "POST /loki/api/v1/push HTTP/1.1", host: "loki.gerbil.test.gigantic.io"
<IP_ADDRESS> - gerbil [15/Feb/2024:13:20:09 +0000]  502 "POST /loki/api/v1/push HTTP/1.1" 157 "-" "GrafanaAgent/v0.37.2" "<IP_ADDRESS>"
2024/02/15 13:20:40 [error] 12#12: *8570 loki-multi-tenant-proxy.loki.svc.cluster.local could not be resolved (3: Host not found), client: <IP_ADDRESS>, server: , request: "POST /loki/api/v1/push HTTP/1.1", host: "loki.gerbil.test.gigantic.io"
<IP_ADDRESS> - gerbil [15/Feb/2024:13:20:40 +0000]  502 "POST /loki/api/v1/push HTTP/1.1" 157 "-" "promtail/2.8.4" "<IP_ADDRESS>"

Upstream issue to fix the CNPs : https://github.com/grafana/loki/pull/11963
Adding a plain netpol to allow loki pods access to coredns helped having the gateway pods work :
<IP_ADDRESS> - gerbil [15/Feb/2024:14:47:59 +0000]  499 "POST /loki/api/v1/push HTTP/1.1" 0 "-" "promtail/2.8.4" "<IP_ADDRESS>"
<IP_ADDRESS> - gerbil [15/Feb/2024:14:48:47 +0000]  499 "POST /loki/api/v1/push HTTP/1.1" 0 "-" "promtail/2.8.4" "<IP_ADDRESS>"
<IP_ADDRESS> - gerbil [15/Feb/2024:14:48:59 +0000]  499 "POST /loki/api/v1/push HTTP/1.1" 0 "-" "GrafanaAgent/v0.37.2" "<IP_ADDRESS>"
<IP_ADDRESS> - gerbil [15/Feb/2024:14:49:07 +0000]  499 "POST /loki/api/v1/push HTTP/1.1" 0 "-" "GrafanaAgent/v0.37.2" "<IP_ADDRESS>"
<IP_ADDRESS> - gerbil [15/Feb/2024:14:49:09 +0000]  499 "POST /loki/api/v1/push HTTP/1.1" 0 "-" "promtail/2.8.4" "<IP_ADDRESS>"
<IP_ADDRESS> - gerbil [15/Feb/2024:14:49:39 +0000]  499 "POST /loki/api/v1/push HTTP/1.1" 0 "-" "GrafanaAgent/v0.37.2" "<IP_ADDRESS>"
<IP_ADDRESS> - gerbil [15/Feb/2024:14:49:41 +0000]  499 "POST /loki/api/v1/push HTTP/1.1" 0 "-" "promtail/2.8.4" "<IP_ADDRESS>"

Is there a way to fix all CNPs at once and have it in our app in the meantime?

Or maybe we can disable cnps for loki until this is merged?

Lucky this time : already merged upstream :sunglasses:

After adding additional CNPs for both write and backend pods to allow them egress access to the "world" entity, it finally works

Now loki have upstream CNPs + custom ones (coredsn, egress to world for write, egress to world + kube-apiserver for backend) enabled by default for all capi installations.
This should solve all CNPs related issues for loki components

Can we create a new one to push them upstream?

https://github.com/giantswarm/giantswarm/issues/29990


SideNav: Add APIs for aria-label and aria-labelledby

Could probably implement HasAriaLabel interface as used in other components.
Implementation-wise this is extremely simple as they just need to be on the root element that has role="navigation"

Created a web component issue based on this issue.


[HUDI-928]: Consider changes needed in pom.xml to exit incubation

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
Remove incubating(*) from project POMs
Brief change log
Verify this pull request
This pull request is a trivial rework / code cleanup without any test coverage.
Committer checklist

[X] Has a corresponding JIRA in PR title & commit

[X] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Covered by PR #1658, closing this


Allow adding hyperlinks to monitors on status page

Is your feature request related to a problem? Please describe.
It would be nice to be able to configure it so each monitor could link to the service it's monitoring.
Describe the solution you'd like
Each monitor should have an option to make it link to the page it's monitoring. There should also be a text box to set a custom URL, in case it's different from the endpoint being monitored.
Describe alternatives you've considered
None
Additional context
Upptime does this by clicking on the service (which views history), and then clicking on the service name again. There are probably other status page programs that do this too, but I couldn't find any easily.

Currently, you can enable the link for HTTP/HTTPS/Keyword monitors, it has a button as below.

But custom link for each monitor is not supported.

@BBaoVanC I think your issue is resolved. Please remember to close the issue if it is (only you or louis can do so)

@BBaoVanC I think your issue is resolved. Please remember to close the issue if it is (only you or louis can do so)

How can it be done?

All monitors which have enough context to show an url have this option.
Monitors like the docker monitor don't, as it is not clear what url to display.
See https://github.com/louislam/uptime-kuma/issues/3784 for a duplicate of this issue.

All monitors which have enough context to show an url have this option Monitors like the docker monitor don't, as it is not clear what url to display. See #3784 for a duplicate of this issue.
What monitor do you have? What url should be displayed?

I am using an HTTP(s) monitor. It should link to the URL of the service being monitored.

I cannot reproduce this behaviour. Could you please share screenshots?

I cannot reproduce this behaviour. Could you please share screenshots?

After checking "Show Clickable Link" and then "Close", nothing happens, and if I click the settings cog again, then it's no longer checked.

After pressing close and then settings again:

You need to click on the save-button to persist changes.
(can confirm the bug that on reopening the changes are reset to the previous saved status)

You need to click on the save-button to persist changes. (can confirm the bug that on reopening modal resets to the previous saved status)

Alright, I guess it is solved. I will open a different issue for the modal reset bug (and some sort of indicator in the edit ui to show that clickable link is enabled)


feat: integrate subgraph api into the front-end as a library

We just need a typescript file that can be fetched from the subgraph.
Then, it should be reproduced in the rest of the contract when needed.
We recommend trying to first detect if the connected wallet has tags, and then display accordingly.

This issue is duplicated from #154 contract-frontend.
What is the procedure for this situation, can I just delete it? @0xneves


Add support for relative paths

This allows us to write imports in avdl files like:
import idl "../keybase1" as keybase1;

Since relative imports in go are considered somewhat unidiomatic, this line will be compiled to:
import (
    keybase1 "github.com/<path/to/my/output/dir>/keybase1"
)

Relative imports will allow us to support languages like Python and TypeScript, where the concept of a GOPATH doesn't exist.

@maxtaco


fix: simulator test fix

Please read contributing guidelines and remove this line.

#6295  👈
master

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

Join @benesjan and the rest of your teammates on  Graphite

Duplicate of https://github.com/AztecProtocol/aztec-packages/pull/6293


Feature Request: Close all chats

I can't be the only one that uses this often enough to run into this fairly regularly:

It would be great to have a button near the top that simply closes all these instead of clicking "X" on each

I will be adding two new popup actions ("Close" and "Close Other Tabs") in the upcoming days.

Available in version 2.0.6.


log: Fix the build when log is disabled

Signed-off-by: Flavio Ceolin<EMAIL_ADDRESS>

:+1:

merged, thanks guys


Update amazon-kinesis-producer to 0.14.13

Updates com.amazonaws:amazon-kinesis-producer from 0.14.3 to 0.14.13.
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!

Files still referring to the old version number
The following files still refer to the old version number (0.14.3).
You might want to review and update them manually.
project/LibraryDependencies.scala

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "amazon-kinesis-producer" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "amazon-kinesis-producer" }
}]

Note that the Scala Steward config file `.scala-steward.conf` wasn't parsed correctly
String: 1: Key 'updates.pin' may not be followed by token: '[' (if you intended '[' to be part of a key or string value, try enclosing the key or value in double quotes)

labels: library-update, early-semver-minor, semver-spec-patch, old-version-remains, commit-count:1

@mergifyio refresh


Poor WMS performance on bigger screens

Hi, first of all thanks for your work in such an awesome opensource library like OpenLayers.
I would like to report poor map performance in bigger resolutions loading multiple WMS layers.
The example shown in the video loads 14 sample WMS layers from GeoServer and the map performance decreases significantly when you drag and zoom on a bigger screen. The video attached shows that, first on a smaller screen with a 1366x768 resolution and second (from 18 seconds) with a bigger screen with a 1920x1080 resolution.
CodePen: https://codepen.io/joaoces/pen/rJjMNj
Video: https://www.dropbox.com/s/2h9u6xpxuw7be9y/ol4_bad_performanc_multiple_layers.mp4?dl=0
Computer specs:

Windows 10 64 bits
Chrome Version 63.0.3239.132 (Official compilation) (64 bits)
Intel Core i5-4200U @ 2.3GHz
16 GB of RAM
ADATA SP900 250 GB SDD

Thanks
João César

You're putting unnecessary load on both your server, network connection and your browser's renderer. There are two ways to optimize:

Configure the source with ratio: 1 to only request and process the extent that is currently shown on the map.
Combine WMS layers from the same WMS into a single ol.layer.Image instance.

So if you now have something like
new ol.Map({
  layers: [new ol.layer.Image({
    source: new ol.source.ImageWMS({
      url: url,
      params: [
        LAYERS: 'layer1'
      ]
   })
  }), new ol.layer.Image({
    source: new ol.source.ImageWMS({
      url: url,
      params: [
        LAYERS: 'layer2'
      ]
   })
  })]
})

you should have the following instead:
new ol.Map({
  layers: [new ol.layer.Image({
    source: new ol.source.ImageWMS({
      ratio: 1,
      url: url,
      params: [
        LAYERS: 'layer1, layer2'
      ]
   })
  })]
});

Also note that you should not pass an SRS (or CRS) param to the WMS Source. That is set automatically. If you have a WMS that does not support your view projection, you have to set projection on the WMS source instead, which will trigger raster reprojection, which adds another potential performance problem. So it is always better to use the view projection if provided by the WMS.

Hi @ahocevar ,
Me and @joaoces19,
At start, we think that the browsers at this time already can handle a lot of layers on a full screen resolution like 1920x1080. But ok, there's always some limitations. :)
We have a lot of layers, and a big layerswitcher, so we've developed and extension for the layerswitcher to combine all the layers dynamically into some groups that we define. We've already tested by changing the default ratio (1.5) to 1, and it helps a bit, but once more depending of the resolution.
For now, we got a good behavior.
Thank you,
Tiago Vieira


chore: add unit tests for generate_library.sh

In this PR:

extract utility functions used in testing to test_utilities.sh.
add unit tests against generate_library.sh.

A follow up of #1948.

I see a bunch of goldens being added. Is that intentional?

Yes.

When we were talking about unit tests, I mostly had in mind testing individual functions in utilities.sh but I don't really see those tests in this PR.

Unit tests against utilities.sh is in #1948.

The change in the generator is not propagated to googleapis-gen. I'll rerun integration tests later.
+ diff -r googleapis-gen/google/bigtable/v2/google-cloud-bigtable-v2-java google-cloud-bigtable-v2-java -x '*gradle*'
diff -r -x '*gradle*' googleapis-gen/google/bigtable/v2/google-cloud-bigtable-v2-java/proto-google-cloud-bigtable-v2-java/src/main/java/com/google/bigtable/v2/InstanceName.java google-cloud-bigtable-v2-java/proto-google-cloud-bigtable-v2-java/src/main/java/com/google/bigtable/v2/InstanceName.java
140c140
<     if (o != null || getClass() == o.getClass()) {
---
>     if (o != null && getClass() == o.getClass()) {
diff -r -x '*gradle*' googleapis-gen/google/bigtable/v2/google-cloud-bigtable-v2-java/proto-google-cloud-bigtable-v2-java/src/main/java/com/google/bigtable/v2/TableName.java google-cloud-bigtable-v2-java/proto-google-cloud-bigtable-v2-java/src/main/java/com/google/bigtable/v2/TableName.java
157c157
<     if (o != null || getClass() == o.getClass()) {
---
>     if (o != null && getClass() == o.getClass()) {

generate_library_unit_tests.sh runs the entire generate_library.sh even for testing a small thing like skipping the protobuf_version argument. Maybe, it will be easier to create true unit tests by breaking down the code in generate_library.sh into smaller functions.
Also, can we do the "golden" tests in a separate PR? I think we should make a distinction between golden tests and unit tests.

Unit tests against utilities.sh are added through #1948.
This PR is intended to add golden unit tests against generate_library.sh. It also has some test cases with invalid versions (to verify the script can exit early).
I can create a new script to run golden unit tests as @blakeli0 suggested.

@blakeli0 @meltsufin Since we have concerns that vast lines of golden file is polluting the repo, I plan to use commit hash in googleapis-gen to remove golden files. WDYT?

@blakeli0 @meltsufin Since we have concerns that vast lines of golden file is polluting the repo, I plan to use commit hash in googleapis-gen to remove golden files. WDYT?

I see a few options:

As @meltsufin suggested in another comment, try to split the script more so that we don't have to run the whole script to test a few edge cases.
If it's too hard or impossible, try to use a set of mock configs(proto, yaml, json). For example, just one RPC with one request message and one response message, that should reduce the generated golden files to minimum(maybe only 5 files?).
If neither of the above options works, then we can use the commit hash in googleapis-gen, but keep in mind that we have to keep the versions up to date since googleapis-gen is always on main, and we will have to change it to  google-cloud-java later very soon as we are adding owlbot to the script.

If neither of the above options works, then we can use the commit hash in googleapis-gen, but keep in mind that we have to keep the versions up to date since googleapis-gen is always on main, and we will have to change it to google-cloud-java later very soon as we are adding owlbot to the script.

I can pin the commit hash in googleapis (protos) and googleapis-gen (generated files) so that we don't need to update versions.

As @meltsufin suggested in another https://github.com/googleapis/sdk-platform-java/pull/1964#pullrequestreview-1618187174, try to split the script more so that we don't have to run the whole script to test a few edge cases.

Currently the script can't do this.
However, I can add a dry_run option to verify the dependencies versions and return without actually generating the library.

As @meltsufin suggested in another #1964 (review), try to split the script more so that we don't have to run the whole script to test a few edge cases.

Currently the script can't do this.

Can you modify it though so it's more a sequence of function calls? Think of each major block of code in the script as a function.

However, I can add a dry_run option to verify the dependencies versions and return without actually generating the library.

This wouldn't solve the problem of breaking the script up into testable units.

If we decide to implement this, I suggest to implement it in another PR and remove all golden tests in this PR and only keep the unit tests (cases with invalid versions).

Sounds good. Let's tackle golden tests in a separate PR.

@blakeli0 @meltsufin I remove all golden tests in this PR and will create another one for them.


Creating a temp file

- What I did
- How I did it
- How to verify it
- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

Update info


Oracle Supported

Can we use Anemometer for Oracle ?

Can we have MariaDB support as it has a slow_log table under mysql DB and performence_schema as well, i tried with the sample_config but it does not have a checksum column so do know how to configure it further any guidance or documentation will be good


Support route

support --route in flutter run --resident (fix https://github.com/flutter/flutter/issues/4466)


Improve responsiveness of the floating text format toolbar buttons

Introduced a movement threshold so button clicks with slight motion to them aren't filtered out. The current behavior will ignore all clicks to the toolbar with even the slightest of mouse movement, causing the toolbar to feel unresponsive.
This was broken with the fix introduced in #3959. My fix should help to improve the feel of the buttons while still mitigating the toolbar flashes on drag to highlight.
Current Behavior:
https://user-images.githubusercontent.com/29527680/231000297-d6c2cb05-dc8a-4479-b8c7-32e4c3066d45.mov

Fixed Behavior:
https://user-images.githubusercontent.com/29527680/231000315-ad7d6c40-2c45-4f8b-88e1-614efdafadc9.mov

Thank you, mind expanding on the reasoning behind a px threshold vs checking whether mouse down + up happen within the same element?

Thank you, mind expanding on the reasoning behind a px threshold vs checking whether mouse down + up happen within the same element?

Nothing in particular, I'm sure both ways would work just fine.

checking whether mouse down + up happen within the same element?

Could you hypothetically have different mousedown and mouseup targets though? Like an icon nested in a button? Haven't tested, just wondered if that would work as reliably. @zurfyx

checking whether mouse down + up happen within the same element?

Could you hypothetically have different mousedown and mouseup targets though? Like an icon nested in a button? Haven't tested, just wondered if that would work as reliably. @zurfyx

My hunch is that the target should be the most realiable approach, but we would check for the a common parent in this case.
That said, I think that what @ChronicLynx is proposing is valid and it fixes an existing problem so I'll proceed to merge this. Thank you!


Release

Revised release system.  Ported some work from master to avoid extra work.  (docs, mock, setupext)

[x] Start from the release branch
git checkout release
[x] Make a new branch for the release cycle
git checkout -b releases/{version}
[x] Merge the current master with the release
git pull origin master
[x] Edit doc/CHANGELOG.rst
[x] Start a release
bumpversion release
[x] Send the release to be evaluated
git push
[x] Verify CI on azure
[x] Manually trigger a jpype.release on azure
If successful, download the artifacts for publication.
[ ] Advance the release pointer
git checkout release
git pull releases/<version>
[ ] Publish the release

Add draft release on github
Attach the artifacts to the release.

 Why would we omit that minor version?
I thought I borked the source dist of 0.7.3/4

v0.7.5 is waiting on the branch for your approval.  This PR is the post release which the final state after release.  The master will be 0.7.6pre1  so that we no longer get confusion between the master and the release branches.

So lets run down the remaining tasks on the v0.7.5 release

[ ] Checkout releases/0.7.5 and add the missing version_info using split.  Commit.
[ ] Manually trigger the release pipeline to create a fresh set of binaries.
[ ] Download all of the different artifacts from https://dev.azure.com/jpype-project/jpype/_build/results?buildId=378&view=results  (or rather the next run)
[ ] Go to releases page and draft the release notes from the CHANGELOG
[ ] On the release page select ask it create a tag on releases/0.7.5  (not master or we will have to repeat the process or move the tag (which is bad because some processes trigger on it)
[ } Copy all the wheels onto the release (including the sdist which I forgot until 2 days later last time)
[ ] Merge v0.7.5 into this PR so that we have the correct head for future work.
[ ] Merge this PR

Okay I think that covers it.   Assuming that you have approved everything, I can finish the cycle late tonight.  (9PM PST 5/12)  I believe that there was only the one requested change.  But poke me between now and then if I missed something.

I cannot login to Azure via Github... sorry. I really wanted to perform all the steps necessary. In the meantime I will fix the source release for 0.7.4

Okay you should be on the access list.  If not just poke me on my email.

I don't believe it is an permission problem, since I cannot login via github at all

@marscher are you going to kick of PyPi distributions soon?

Sorry for the delay. The packages are online on PyPI now.


empty RichText fields renders as

Issue Summary
An empty RichText fields on my models are rendering as

 the first time they are saved. If I edit the page again and save it, it renders fine (as empty element).
Steps to Reproduce

wagtail start myproject
Edit models.py as follows

from django.db import models

from wagtail.core.models import Page
from wagtail.core.fields import RichTextField

from wagtail.admin.edit_handlers import FieldPanel

class HomePage(Page):
    pass

class ContentPage(Page):
  body = RichTextField(blank=True)

  content_panels = Page.content_panels + [
    FieldPanel('body'),
  ]

Add a new page and add title only and render the field as:

$ cat home/templates/home/content_page.html
{{ self.body }}

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes

Technical details

Python version: Python 3.6.5
Django version: 1.11.5
Wagtail version: 2.2.1
Browser version: whatsmybrowser.org/b/33MFAZT (Chrome 68 OS X)

You need to add richtext filter to your {{ self.body }} tag. Like this {{ self.body|richtext }}. I believe it's located in wagtailcore_tags, but I'd need to check.

@twoblokeswithapostie that will just render it as HTML, but still will be empty. So I have currently:
{% if self.body %}
...

which evaluates to true

Hi @dpetrov - thanks for the report! I think this is covered by #4549.

It does indeed, I've missed it somehow. Thanks for pointing it out.


Get wp_title() in header.php

Describe the bug
I'm trying to retrieve the title string with function wp_title() in the header.php before wp_head() is called with an empty result. It works in other themes but it seems to be supressed in this theme. How I can get it back to work?
Reference:
https://developer.wordpress.org/reference/functions/wp_title/
Steps to reproduce
$page_title = wp_title('–', false, 'right');
echo $page_title; // just empty but why?
wp_head();

Screenshots and Additional Info
No response
Website link
No response

Why not simply use <?php the_title(); ?>?

Becauase It returns only the title of a post or page and if you have a page as "Front page", then you will get only the title of the page and not the title of the whole site.
I need this for the og:title meta-tag. How did you got it solved on bootscore.me?
<meta property="og:title" content="bootScore » A powerful free Bootstrap 5 WordPress Starter Theme">

Backend Settings > General - Site Title and tagline

There is all fine on my settings. I just disabled all plugins and tried it with the main- and with child-theme but I'm getting the same empty result. Yoast is to much to fill some simple meta-values in the header.php.

Can't explain why your code does not work. On bootscore.me it's done with Yoast. But you can load site name and description as well.

<?php bloginfo('name'); ?>
<?php bloginfo('description'); ?>
<?php the_title(); ?>

And put something like this to your head:
<title><?php bloginfo('name'); ?> » <?php the_title(); ?></title>


Implementing SDE nodes

We need to implement a node type for stochastic differential equations.

It seems we can get pretty far into stochastic modeling without implementing a specific node type. I attached an image showing a network diffusion with additive, pulsating noise at the edges. The generating script can be found in the examples section.

Issue for tracking documentation of the feature: https://github.com/FHell/NetworkDynamics.jl/issues/26


Fix resources section link

Updated the resources section link in the README file to point to the correct page on tensorflow.org

Can one of the admins verify this patch?

PR merged. Thanks, @bhaprayan !

Sure! @caisq


Fix the final consumer write size from unchunked to chunked tunnel

(cherry picked from commit 8977a45054302b37bcc0d0a1cca3ad2dae98df6a)

This is a cherry-pick of #7577 to 8.1.x.  I'm suggesting we cherry-pick this for 8.1.x because it cherry-picks cleanly and users reported the issue there: #7880 .

[approve ci autest]


Osmosis (cosmos-sdk v0.46.10) GetNodeInfo transport error

I think this is likely related to  Proto-build fails for SDK 0.46 #318 due to the recent proto changes.
docker run fullstorydev/grpcurl osmosis-grpc.lavenderfive.com:443 cosmos.base.tendermint.v1beta1.Service/GetNodeInfo

works, but using cosmos-rust I get
status: Unknow, message: "transport error"

code:
cosmos_sdk_proto::cosmos::base::tendermint::v1beta1::service_client::ServiceClient::new(c).get_node_info(GetNodeInfoRequest{}).await

full code can be found here
I will wait until #318 is fixed, if the issue persists there is something else going on.

It seems to be a different issue: GoAway(b"", FRAME_SIZE_ERROR, Library)
Not sure what it means.
[2023-04-02T08:21:40Z ERROR cosmos_rust_package::api::core::cosmos::channels] GetNodeInfoRequest failed for http://osmosis-grpc.lavenderfive.com:443: Status { code: Unknown, message: "transport error", source: Some(tonic::transport::Error(Transport, hyper::Error(Http2, Error { kind: GoAway(b"", FRAME_SIZE_ERROR, Library) }))) }
[2023-04-02T08:21:40Z ERROR cosmos_rust_package::api::core::cosmos::channels] GetNodeInfoRequest failed for http://grpc-osmosis-ia.cosmosia.notional.ventures:443: Status { code: Unknown, message: "transport error", source: Some(tonic::transport::Error(Transport, hyper::Error(Http2, Error { kind: GoAway(b"", FRAME_SIZE_ERROR, Library) }))) }
[2023-04-02T08:21:40Z ERROR cosmos_rust_package::api::core::cosmos::channels] GetNodeInfoRequest failed for http://osmosis.grpc.stakin-nodes.com:443: Status { code: Unknown, message: "transport error", source: Some(tonic::transport::Error(Transport, hyper::Error(Io, Custom { kind: BrokenPipe, error: "stream closed because of a broken pipe" }))) }
[2023-04-02T08:21:42Z ERROR cosmos_rust_package::api::core::cosmos::channels] Unable to establish a connection to http://osmosis.grpc.interchain.ivaldilabs.xyz:433: transport error

    Caused by:
        0: error trying to connect: tcp connect error: No route to host (os error 113)
        1: tcp connect error: No route to host (os error 113)
        2: No route to host (os error 113)

related issue https://github.com/cosmos/cosmos-rust/issues/313

These kind of errors often indicate you're connecting to the wrong port

Hmm the endpoints are taken from the chain registry.
I tested the same endpoints using grpcurl and that worked fine, difficult to debug this error further..

Closing this issue, the solution was to use the https:// schema and add the tonic feature flag "tls-roots":
tonic = { version = "^0.8", features = ["transport","tls","tls-roots","tls-webpki-roots"] }


chore: Platform release 2.68.0

:robot: I have created a release beep boop
2.68.0
2.68.0 (2023-08-16)
Features

admin action to delete all segments for project (#2646) (4df1b80)

Bug Fixes

password-reset: rate limit password reset emails (#2619) (db98743)
user-create: duplicate email error message (#2642) (7b65a8d)

2.67.0
2.67.0 (2023-08-16)
Features

admin action to delete all segments for project (#2646) (4df1b80)

Bug Fixes

password-reset: rate limit password reset emails (#2619) (db98743)
user-create: duplicate email error message (#2642) (7b65a8d)

This PR was generated with Release Please. See documentation.

Codecov Report
Patch coverage: 98.23% and project coverage change: +0.01% :tada:

Comparison is base (de0e554) 95.43% compared to head (bc327ab) 95.45%.
 Consider uploading reports for the commit 2e1c919 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2648      +/-   ##
==========================================
+ Coverage   95.43%   95.45%   +0.01%
==========================================
  Files         975      978       +3
  Lines       27252    27364     +112
==========================================
+ Hits        26009    26119     +110
- Misses       1243     1245       +2

Files Changed
Coverage Δ

...pi/tests/unit/projects/test_unit_projects_admin.py
94.11% <94.11%> (ø)

api/app/settings/common.py
87.71% <100.00%> (+0.08%)
:arrow_up:

api/custom_auth/migrations/0001_initial.py
100.00% <100.00%> (ø)

api/custom_auth/models.py
100.00% <100.00%> (ø)

api/custom_auth/views.py
100.00% <100.00%> (ø)

api/projects/admin.py
100.00% <100.00%> (ø)

api/tests/unit/users/test_unit_users_views.py
100.00% <100.00%> (ø)

api/users/models.py
95.02% <100.00%> (+0.17%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:robot: Release is at https://github.com/Flagsmith/flagsmith/releases/tag/v2.68.0 :sunflower:


Assessor's Reflection accidentally takes an argument

Using Hexcasting 0.10.3, if you cast Assessor's Reflection with an empty stack, it mishaps, saying "Assessor's Reflection expected 1 or arguments, but the stack was empty". If your stack is not empty, it eats whatever iota is on the top of the stack and returns the value the Reflection should normally return.

Duplicate of #375


Postgis extension to Postgres doesn't work.

Despite issue #3389 being closed, postgis doesn't seem to work for me. With this stanza in /etc/nixos/configuration.nix:
  services.postgresql = {
    enable = true;
    package = pkgs.postgresql94;
    dataDir = "/data/postgresql";
    extraPlugins = [ pkgs.postgis.v_1_5_8 ];
  };

...I get postgres 9.4, as expected, but no postgis extension.
In a perfect world, I'd be able to install PostGIS 2.1.5 (PostGIS 2 is nearing its third birthday now), and I'd be able to install it with Nix on OSX too (ie., not just as part of a Nixos service).
Can anyone help? @ocharles maybe?
I've tried fixing it myself, but this is beyond my nix-fu. I'm happy to do whatever legwork my skill level can include. :-)
For the diagnostic record, SELECT * FROM pg_available_extensions doesn't list PostGIS as available, and CREATE EXTENSION postgis fails with:
ERROR:  could not open extension control file "/nix/store/ycr025z3w42yawyjs4zr3w6gb0ng6gvc-postgresql-and-plugins-9.4beta3/share/extension/postgis.control": No such file or directory

Try https://github.com/NixOS/nixpkgs/pull/5926

Doh! I searched the issues but not the pull requests. Thanks @iElectric, that worked a treat. :-)


Styles

On loading the page and after changing themes the favicon gets weard behavior on rerendering, need to rework
Maybe increase the font-size of dirs names in tree

[x] Favicon has been updated to custom (both light and dark theme looks alright)
[x] Font size of nav div has been increased
[x] The NEWS tab is added and colored
[ ] The social footer draft is added,in progress


Overriding and Overloadng

Hi all. Below is our Prof's answer to my question. For your reference.
——————————————————————————————
I understand that for the code circled in red, at compile-time, the computer does not know it is of Circle type, so only object.equals() is possible; at run-time circle.equals() replaces object.equals() due to overriding. This is called dynamic binding.
But why cannot this code circled in green be interpreted as dynamic binding so that this code can work? I understand that though c refers to a FilledCircle but itself is still just of Circle type. Is it because there is not such an overriden fillColor() method in Class Circle, just like .equals() is overriden in Class Object?
Also, can I interpret today's concepts like this: run-time type is associated with overriding and dynamic binding, while compile-time type associated with overloading and static binding?
If you do not mind, can I post my questions along with your answers to our GitHub forum?
Kind Regards,
Huang Hongyi
——————————————————————————————————————————
Hi Hongyi,
There's a major different between the two scenarios.  For equals, both Object and Circle class have the equals method with the same signature that takes in an Object.  That is why the compile allows equals(Object) to be called because this method is specified in the Object class.
For the fillColor example, Circle does not have fillColor.  So there is no way that the compiler to call fillColor from a Circle compile-time type.
As for github, yes you may post my answers and hopefully it encourages more discussion.
henry

Also, can I interpret today's concepts like this: run-time type is associated with overriding and dynamic binding, while compile-time type associated with overloading and static binding?

Yes, this should be correct. For those who missed the QnA session, you might experiment with this Java code on your own.
class A {
    void foo(Object obj) { System.out.println("one"); }
    void foo(Circle c) { System.out.println("two"); }
}
class B extends A {
    void foo(Object obj) { System.out.println("three"); }
    void foo(Circle c) { System.out.println("four"); }
}


Add and relink resulting images for the docs of Det3DLocalVisualizer

Motivation
Fix this issue #2960 to improve the docs for Det3DLocalVisualizer.
Modification
Add two missing images referenced by the docs.
By this PR, we can see the completed explanations!

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Toshiyuki Kato seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@ZwwWayne Could you review my PR?

@JingweiZhang12 Could you review my PR?


SSL/TLS secure channel failure

Module Version
ModuleVersion = '1.0.0'
Affected Resource(s)

ArcGIS_DataStore
Configuration Files
ArcGIS_DataStore arcgisDatastore {
    Ensure = 'Present'
    ServerHostName = $env:COMPUTERNAME.Substring(0,$env:COMPUTERNAME.Length -5) + "ags01"
    ContentDirectory = $dataStoreContentLocation
    DataStoreTypes = 'relational'
    RunAsAccount = $serviceAccountCredential
    SiteAdministrator = $psaCredential
    DependsOn = @('[xFirewall]arcgisDatastoreFirewallRules')
}

Expected Behavior
Datastore should be configured with the ArcGIS Server site.
Actual Behavior
The standard output shows
... failed to execute Set-TargetResource functionality with error message: Register Data Store Failed after multiple attempts.

Checking the dsc logs, found the following error
[WARNING]:- The request was aborted: Could not create SSL/TLS secure channel.

Important Factoids

Using Esri 10.6.1 image in Azure Marketplace
Digging into the ArcGIS_DataStore module, found that the issue is located in the Register-DataStore function, specifically when setting the certificate callback to $true. To get around the issue, I added the following line immediately below the callback.

[System.Net.ServicePointManager]::SecurityProtocol = "tls11, tls12"

I am sure there is a more appropriate solution but this is what I came up with. Issue does not seem to occur when using the Esri 10.6 image in the Azure Marketplace which likely means this is related to changes in ArcGIS 10.6.1.

is this on a single machine deployment or a multi machine deployment?

Multi-machine deployment. Server, Portal and DataStore are all on different machines.

is data store in HA config?

No, single only.

Reviewing the .psm1 directly in Gitub, it looks like I was missing
[Net.SecurityProtocolType]::Tls12 -bor [Net.SecurityProtocolType]::Tls11 -bor [Net.SecurityProtocolType]::Tls
in my file for some reason which explains why it works after I added [System.Net.ServicePointManager]::SecurityProtocol = "tls11, tls12"
I am running my tests again after making a new copy of the updated module and believe it will work. Will update shortly.


UX Issue: On Windows Installer, server takes a long time to start

OS: Windows 8.1
After installing, it took a long time to get the server up and running, and there was a bit of concern as to what its status was.

This is happening for people on the Mac installer as well (takes several minutes to "start" the server, with no indication that anything is in progress, so it just seems like it's hung.

(At least one intern gave up and uninstalled the app, thinking it didn't work for them)

This should be improved a lot by https://github.com/learningequality/installers/issues/80 (but it may still be useful to have some "Loading, please wait..." message somewhere, to keep the user from worrying.


Jump to line on IF checks does not match

Courtesy of @darrenwhite99
Function 117 specifically, the other IF checks probably have the same issue

Fixed


fix(GUI): use mountpoint and displayname as fallback labels

We use the mountpoint label fields if description is unavailable, and
ultimately fall back to displayName if there is no mountpoint
label available.
Change-Type: patch
Changelog-Entry: Use mountpoint label and displayName as fallback labels
when description is unavailable.

While this should not be needed anymore after https://github.com/resin-io/etcher/pull/2207 – it might make sense to default to "Untitled" at the appropriate place (which is perhaps drivelist)? Wdyt @Shou?

@jhermsmeier we should probably leave drivelist as-is, I think, in case someone might want to rely on there not being a label for the device, should that ever happen. We can add a null-check at the GUI layer and return 'Untitled' there.

Good point, let's do that then

@jhermsmeier done


[GCP] 0.7 docs for workload identity management

In 0.7 we will be switching to workload identity with GCP.
We will need docs on how this works.

@lluunn Are you happy to create the doc for workload identity management (I see you commented on https://github.com/kubeflow/kubeflow/issues/3638#issuecomment-525520248)? If you like, you can either point me at a draft in a Google Doc, or send a PR.

v0.7 demo script: http://bit.ly/demo-v0-7

/assign


ValueError: invalid literal for int() with base 10: "b''" in single_key/binary_polinomial_factoring.py

python3 RsaCtfTool.py -e 101 -n 52035749 --uncipher 31018357
private argument is not set, the private key will not be displayed, even if recovered.
[] Testing key /tmp/tmpfgax3htr.
[] Performing binary_polinomial_factoring attack on /tmp/tmpfgax3htr.
Traceback (most recent call last):
File "RsaCtfTool.py", line 265, in
attackobj.attack_single_key(publickey, attacks_list)
File "/home/lai/leo/crypto/RsaCtfTool/lib/rsa_attack.py", line 193, in attack_single_key
self, self.publickey, self.cipher
File "/home/lai/leo/crypto/RsaCtfTool/attacks/single_key/binary_polinomial_factoring.py", line 30, in attack
p = int(sageresult[0])
ValueError: invalid literal for int() with base 10: "b''"
There can be an error for type conversion when sage got no result.

Fixed in latest commit !


Dependency Conflict: Laravel 11.9.2, Twill 3.3, Symfony Http-Foundation v7.1.0, and Doctrine DBAL 3.8.4, please update to dbal 4

Problem 1
- Root composer.json requires area17/twill 3.3 -> satisfiable by area17/twill[3.3.0].
- carbonphp/carbon-doctrine-types 3.2.0 conflicts with doctrine/dbal 3.8.4.
- area17/twill 3.3.0 requires doctrine/dbal ^3.0 -> satisfiable by doctrine/dbal[3.0.0, ..., 3.8.4].
- nesbot/carbon 3.5.0 requires carbonphp/carbon-doctrine-types * -> satisfiable by carbonphp/carbon-doctrine-types[3.2.0].
- symfony/http-foundation v7.1.0 conflicts with doctrine/dbal 3.5.4.
- symfony/http-foundation v7.1.0 conflicts with doctrine/dbal 3.4.6.
- symfony/http-foundation v7.1.0 conflicts with doctrine/dbal 3.3.8.
- symfony/http-foundation v7.1.0 conflicts with doctrine/dbal 3.3.5.
- symfony/http-foundation v7.1.0 conflicts with doctrine/dbal 3.2.2.
- symfony/http-foundation v7.1.0 conflicts with doctrine/dbal 3.1.5.
- symfony/http-foundation v7.1.0 conflicts with doctrine/dbal 3.1.0.
- symfony/http-foundation v7.1.0 conflicts with doctrine/dbal 3.0.0.
- laravel/framework v11.9.2 requires nesbot/carbon ^2.72.2|^3.0 -> satisfiable by nesbot/carbon[3.5.0].
- laravel/framework v11.9.2 requires symfony/http-foundation ^7.0 -> satisfiable by symfony/http-foundation[v7.1.0].
- laravel/framework is locked to version v11.9.2 and an update of this package was not requested.
Versions
Twill version: 3.3
Laravel version: 11.9.2
PHP version:8.3

Laravel 11 removed the need for dbal, it also originally is a requirement of laravel and not twill so it should be removed from the list of dependencies


kubernetes: git clone broken

Component
server, agent, web-ui
Describe the bug
Step git clone does not work.
It was working with next-94f2331a4c (July 6th 2023).
It is broken with next-1d6b073ca5 (July 8th 2023 few hours ago).

On the right pane, I can read Chargement… that means Loading...
I can switch from one version (it works) to the other version (it does not work) and rollback to the previous version (it works) again and again. I made no change anywhere except the image tag of Woodpecker agent and server.
I compared the logs ( kubectl logs woodpecker-0; kubectl logs woodpecker-agent-xxxxxx). There is no interesting difference.
System Info
Working with next-94f2331a4c (July 6th 2023).
Broken with next-1d6b073ca5 (July 8th 2023 few hours ago).

Kubernetes backend

Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

there are two related pulls since then:  #1914 &  #1909
cc @zc-devs

thanks for the detailed report @ymettier :+1:

Custom next-556607b525.
  containers:
    - name: wp-01h4w19zvmmgb91jgdwcwde9qt-0-step-3
      image: woodpeckerci/plugin-docker-buildx
      workingDir: /woodpecker/src/forge/user/woodpecker
      env:
        - name: CI_PREV_COMMIT_SHA
        - name: CI_REPO_PRIVATE
          value: 'true'
          ...
        - name: DRONE_REPO_BRANCH
          value: master
        - name: CI_SYSTEM_PLATFORM
        - name: CI_SYSTEM_ARCH
          value: linux/amd64
          ...

witch should not have any erffect:
https://github.com/woodpecker-ci/woodpecker/blob/ea895baf836fc7d9c46e02fd883f432f2d0261e9/pipeline/frontend/metadata/environment.go#L109
https://github.com/woodpecker-ci/woodpecker/blob/ea895baf836fc7d9c46e02fd883f432f2d0261e9/pipeline/frontend/metadata/environment.go#L116

hmm we might need the actual logs ?

woodpecker-server.log
woodpecker-agent.log
Unfortunately, Agent is terse even though in TRACE level.

0001-Log-platform.patch
woodpecker-agent.log
Agent crashes right after running pipeline.

Metadata.System.Platform is always empty https://github.com/woodpecker-ci/woodpecker/blob/de13aeea339bd72d8417b2aea5b51dd1dc540632/pipeline/frontend/metadata.go#L97
Therefore on Server both env vars (CI_SYSTEM_ARCH, CI_SYSTEM_PLATFORM) are empty.
Agent receives empty vars via RPC. But then right before https://github.com/woodpecker-ci/woodpecker/blob/de13aeea339bd72d8417b2aea5b51dd1dc540632/pipeline/pipeline.go#L152 both vars are empty. But right before https://github.com/woodpecker-ci/woodpecker/blob/de13aeea339bd72d8417b2aea5b51dd1dc540632/pipeline/pipeline.go#L180 CI_SYSTEM_ARCH is set.
Between this two lines of code there were two lines in log that mentioned tracer. So, here we are https://github.com/woodpecker-ci/woodpecker/blob/de13aeea339bd72d8417b2aea5b51dd1dc540632/agent/tracer.go#L79


Privacy concerns about Gist

I didn't create any accounts (I see people in issues that did this), I just created resume.json file in my Gist and it works. Whenever I load https://registry.jsonresume.org/mygistfile?theme=cora it shows me my CV. Do I need any account at all?
I have privacy concerns about this approach, now registry accepts only public gists as a source for resume and this is not good. Everybody can search gist and find my resume together with contact details.
I tried to create secret gist but registry does not see it. Can we somehow solve this problem?

dude are you kidding me ? you literally open your CV for public (companies to hire you) your data is already out there all can see it so there is no privacy

Open CV is not the same as open CV contact details, I definitely do not want that every *ucking recruiter call me by phone and know my email, I want to be picky and choose to whom give the details and to whom not. And in current implementation every layman can search the directory and find my gist.
If you don;t understand such simple thing then you are a rookie on a labor market.

for me its already exposed data so i do not care, lol


Fixing the multiple clicks on home button part of issue #1262

Description
Every time on back-button is pressed  control returns to home fragment.
Related issues and discussion
#1262

@Karljoones  I checked the youtube ,whattsapp and other apps . They do not directly  return to home on back pressed  .

Merging.

Thanks @danzzen


[STORM-3359]Allow deprecated config on ConstraintSolverStrategy for backwards com…

…patibility

TOPOLOGY_CONSTRAINTS isn't in Config in master. Doesn't look like it's in 1.2.3 either. When did it exist?

@srdo  My bad, I had this internal version.


Function returning a switch expression returns an Object class instead of a class type

When you create a function that returns a switch expression that returns an instance of a class that inherits from some abstract class BaseClass<Object> AND specifies the type after the inherited class(class F extends BaseClass<Object>), then the return type of the function turns into an Object. The runtimeType of these objects is still BaseClass. It can be fixed by turning switch expression into a switch statement.
It can be reproduced with the following code:
abstract class BaseClass<Object> { BaseClass(); }

class F extends BaseClass<Object> { F(); }

class S extends BaseClass { S(); }

enum V { f, s }

// Works perfectly fine
BaseClass switchStatement(V v) {
  switch (v) {
    case V.f: return F();
    case V.s: return S();
  }
}

// Causes an error:
// Error: A value of type 'Object' can't be returned
// from a function with return type 'BaseClass<Object>'.
BaseClass switchExpression(V v) => switch (v) {
      V.f => F(),
      V.s => S(),
    };

void main() {}

The workaround is using dynamic as a return type or add as BaseClass after the class constructor call. The first solution communicates a wrong idea. The second solution confuses Dart Analysis server because it is an unnecessary cast.
What am I missing?
This tracker is for issues related to:

dev_compiler
Dart SDK version: 3.0.6 (stable)

That's just how the you bound of BaseClass<Object>  and BaseClass<dynamic> is computed.
Your two branches have different types.
To figure out which type to give to the switch, which can evaluate to either branch, the compiler tries to find a type that both branches satisfy, an upper bound on the types of all the branches.
The easy that works it's that it looks at the interfaces that both types have, but since they implement different versions of BaseClass, that's not seen as a solution, so the closest shared interface is Object.
It's a known issue that guessing at the upper bound is not particularly smart.
There are hard cases where a smart algorithm can get lost, but the current algorithm may be erring on the side of dumbness a little too much.

Hi, thank you for your reply. When I encountered the problem, BaseClass was defined as class BaseClass<T extends Object>. I tried to make the simplest example with which this problem can be reproduced. If I change the code to the following:
abstract class BaseClass<T extends Object> { BaseClass(); }

class F extends BaseClass<Object> { F(); }

class S extends BaseClass { S(); }

This works, but only if the F class type parameter is Object. Anything extending Object in a type parameter will cause the switch expression to guess the return type as Object once again.
Either way, I now understand why it is happening and will close this issue. Thanks for the clarification.

Cf. https://github.com/dart-lang/language/issues?q=is%3Aopen+is%3Aissue+label%3Aleast-upper-bound for further discussions about this topic.


Make it work without jQuery

Looks good to me. As of this moment this is the only addon preventing me to migrate off jQuery completely.

I still have a few addons to fix to go.

@cibernox - Sorry, I made a rebase conflict for you by landing the<EMAIL_ADDRESS>support PR.  I think you will also have to update this in a few places now (since we have multiple copies of this file and use the correct one depending ember-cli version and such).

@rwjblue Rebased and green.

ember-cli-head 0.2.2 published 🎉


Cleaner create-map versioning + EE credential bug

This PR:

Adds a cleaner version update if the map has already been made
Adds the ability to pass credentials to EarthEngineExporter to fix ee authentication issue
Sets the Gcloud project environment variable in the create-map notebook

LGTM!


Add jones-complexity

I find this tool very useful when working with students, as they seem to put a lot of logic into the same line: https://pypi.python.org/pypi/jones-complexity/0.1.2

Niiice, thanks!


Optimistic: support start task with inconsistent upstream table schema

What problem does this PR solve?
close #3786
close #3629
close #3708
What is changed and how it works?

worker flush table info when entering sync stage
master get table info when receiving ddl info
remove info/operation/locks/drop columns when stop a optimistic task

For DM-master:

fetch table info for every table when creating a lock rather than use joined as init table
when master restart, no need to rebuild locks base on init schema, just handle info by order
when the task stops, remove all metadata for optimism, when restarting the task, we can fetch table info from downstream instead.

For DM-worker:

get and flush table info when entering sync stage

Check List
Tests

Unit test
Integration test

Release note
support start task with inconsistent upstream table schemas in optimistic shard mode.

/hold
/run-all-tests

/run-dm-integration-test
/verify

/run-all-tests

/run-unit-test

/run-all-tests

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/unhold

Codecov Report

Merging #3903 (3e9f372) into master (3873d39) will decrease coverage by 1.8468%.
The diff coverage is 66.8493%.

Flag
Coverage Δ

cdc
58.6985% <66.8493%> (+0.4619%)
:arrow_up:

dm
52.2869% <ø> (-3.7477%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #3903        +/-   ##
================================================
- Coverage   57.0741%   55.2273%   -1.8469%
================================================
  Files           478        485         +7
  Lines         56551      60050      +3499
================================================
+ Hits          32276      33164       +888
- Misses        20978      23535      +2557
- Partials       3297       3351        +54

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/hold
waiting @lichunzhu review

Should we delete obsolete init-schema for dm-clusters upgraded from lower versions?

I leave a TODO in
https://github.com/pingcap/tiflow/blob/c9a821c2c23f45e5182d3e230e8fbc22ba345fde/dm/dm/common/common.go#L81  I think we should prune them after upgrading to a major version(e.g. 6.0)

Should we flush table info for newly added tables

Yes. We still have some problem with newly create/drop table(e.g. #3823), I will create a new pr to solve them.

/run-all-tests

/run-all-tests

/run-all-tests

/unhold

/merge


Resolve #19327

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
#19327

Thanks


Multiple threading version to calculate feature matrix

Hello,
calculating feature matrix takes reasonable amount of time on single thread, while most of the other threads are doing nothing.
Is it possible to calculate feature matrix in parallel mode with multi threading support?

Hi @dfayzur, we are currently working on a multicore version in PR #84. It should be merged in in the next few weeks, hopefully sooner. In the meantime, users have had success using Dask bags to parallelize calculate_feature_matrix. See our conversation with @jeff-hernandez on the Featuretools Gitter.

Thanks @bschreck. I will look to the Gitter.

Closing via #173


个人小建议

1.在app设置内添加深色/浅色切换按钮
2.在阅读界面添加自动翻页或者自动滚动，且可以在设置中调节翻页时间
3.在阅读界面添加横/竖屏切换按钮

可以有

From: GeekBug @.>
Sent: Thursday, July 6, 2023 9:17:20 PM
To: wgh136/PicaComic @.>
Cc: Subscribed @.***>
Subject: [wgh136/PicaComic] 个人小建议 (Issue #80)
1.在app设置内添加深色/浅色切换按钮
2.在阅读界面添加自动翻页或者自动滚动，且可以在设置中调节翻页时间
3.在阅读界面添加横/竖屏切换按钮
―
Reply to this email directly, view it on GitHubhttps://github.com/wgh136/PicaComic/issues/80, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQEI6J6QGNQ6CE4IC5FBB5LXO23GBANCNFSM6AAAAAA2ANTJSY.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

完成


config: Swap ConfigMap usage with Configuration CRD in the pkg/configurator module

This is the final task from the config series. This issue is for the removal of the Configmap and using instead the Config CRD in the pkg/configurator module:
Where the osm-system/osm-config ConfigMap is used: https://github.com/openservicemesh/osm/blob/main/pkg/configurator/client.go#L94-L101

This issue is blocked / depends on:

[ ] config: Create new Configuration CRD informers #3038

All related issues:

[ ] config: Design a new OSM Config CRD (YAML only) #3033
[ ] config: Add validation to the new OSM Config CRD (in YAML) #3034
[ ] config: Create code gen helper for generation of Go Client code for new OSM Config CRD #3035
[ ] config: Generate Go Client code for new OSM Config CRD #3037
[ ] config: Create new Configuration CRD informers #3038
[ ] config: Swap ConfigMap usage with Configuration CRD in the pkg/configurator module #3039
[ ] config: Update documentation to reflect the usage of a Configuration CRD (not a ConfigMap); Cleanup #3040
[ ] config: Update ValidatingWebhookConfig and handler (for osm-config ConfigMap changes) #3041

all the code changes for this have been checked in, cleanup will be handled with issue #3040


extended themeing engine to allow for patching

added new functionality to allow for theme developers to override via JSON patching angular and other top level (themes folder) .json files

Documentation
In order to activate the theme overrides, you much create a .patches folder at the root of your theme folder. There is a small formatting convention to that the new functionality expects in order to read this correctly, and it is as follows;
2020-02-12-113055.angular.json
--- timestamp ---|--filename--

The timestamp portion helps for the sorting since patching can be sequence sensitive and the last part is filename to override. There is not directory crawling ability (that is safely tested) so you can only give this feature file names that are directly below the themes.
P.S: You may theoretically be able patch lower files by adding escaped directory separators but this was not in scope for the this release so mileage may vary.
The patching leverages the fast-json-path module so please refer to that npm package for how to format and create patches [https://www.npmjs.com/package/fast-json-patch].
Signed-off-by: mario.bonito<EMAIL_ADDRESS>

This can be closed off as themes are being extracted away from the core codebase as separate client applications.

This can be closed off as themes are being extracted away from the core codebase as separate client applications.


gdm-settings: init at 4.4

Description of changes
gdm-settings is a settings app for GNOME's Login Manager, GDM
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

cc @doronbehar @philippcou from https://github.com/gdm-settings/gdm-settings/issues/234

Result of nixpkgs-review pr 335233 run on x86_64-linux 1

1 package built:

gdm-settings


Update mendix-cloud.md

Add release notes for update in alerting template for Mendix Cloud

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

@udh-mendix I've edited the text a little, let me know if you have any comments.
Also, I'm getting a warning from github because it seems your account hasn't accepted the contributor license agreement https://cla-assistant.io/mendix/docs?pullRequest=5054
Can you sign it at the above link? I'll merge the PR after that.

@katarzyna-koltun-mx I have signed it but it's not reflecting on github

@udh-mendix Got it, thank you for clarifying. I'm merging the request now.


How do you even start this?

followed the instructions and this happens.
I also did npm install vue-analytics
ERROR  Nuxt error
Error: Cannot resolve "@nuxtjs/google-analytics" from "/home/jerico/public_html/jerico.xyz/client/nuxtjs/google-analytics"

nuxt.js:220 Nuxt.resolvePath
[jerico.xyz]/[nuxt]/lib/core/nuxt.js:220:11

module.js:114 ModuleContainer.addModule
[jerico.xyz]/[nuxt]/lib/core/module.js:114:35

utils.js:96 promise.then
[jerico.xyz]/[nuxt]/lib/common/utils.js:96:43

next_tick.js:188 process._tickCallback
internal/process/next_tick.js:188:7

module.js:686 Function.Module.runMain
module.js:686:11

bootstrap_node.js:187 startup
bootstrap_node.js:187:16

bootstrap_node.js:608

Hey. It seems @nuxtjs/google-analytics package is not probably installed. We use it in some production apps ;)

How to install?
Npm install @nuxtjs/google-analytics?

@jericopulvera this is taken from the setup in the Readme file

Add  @nuxtjs/google-analytics dependency using yarn or npm to your project

So yes, you need to run yarn add @nuxtjs/google-analytics, which is the nuxt wrapper of vue-analytics, and follow the nuxt plugins installation process.
After that, for every options or API reference you can refer to vue-analytics


DSDL Actuator

The current actuator is for position control only. It might be useful to support other types (speed / torque controlled) actuators in the future. So I suggest renaming the actuator definition to indicate that they control position.

I guess we should extend the existing command message rather than defining a new one. The first solution that comes to mind is to add a field for command type:

unitless -1..+1
linear/angular position [meter or radian]
linear/angular force [Newton or Newton metre]
linear/angular speed [m/s or rad/s]

I'm not sure though if it would be useful to distinguish linear and angular commands.
Also, it seems like the Status message should have a speed field as well, and the power field should probably be dropped in order to keep the Status message just one CAN frame long.

This sounds good. I think it isn't necessary to explicitly distinguish the linear and angular type in the message since for a specific actuator it is evident whether it is linear or angular.
I agree about the speed field for the status. The power could then still be computed if the speed and torque/force is given.

@Stapelzeiger I just updated the definition. Please re-open if there's something missing.


⚠ Mobitopup has degraded performance

In 74ebfba, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 4211 ms

Resolved: Mobitopup performance has improved in 1964c1a.


#[insertable_into] fails with lifetimes other than 'a or 'insert

The following code fails to compile unless the 'b lifetime is changed to 'a or 'insert:
#![feature(custom_attribute, plugin)]
#![plugin(diesel_codegen)]

#[macro_use]
extern crate diesel;

table! {
    foo {
        id -> Integer,
        s -> VarChar,
    }
}

#[insertable_into(foo)]
pub struct Bar<'b> {
    pub s: &'b str,
}

I believe that this code only works with 'a because as far as I know lifetimes are exempt from macro hygiene.

Fixed in 4771cb6b624ae4fbff42ed6115034b831591125c


Export CARTO MGL styles

Enable the following usage:
const map = new mapboxgl.Map({
    style: carto.basemaps.voyager
})

This would allow in the future to embed our basemap styles in the CARTO VL library avoiding extra requests and reducing loading time.

Yes, I think there are 3 ways of implementing it:

Storing just the URL
Storing the JSON
Storing the JSONs. Each JSON actually points to other JSONs. We could also remove this level of indirection.

I'd prefer the third option, but I don't know how difficult is to remove that level of indirection, and if the bundle size is increased by much.
Maybe @rochoa has more input.

This is ready in the PR.
@davidmanzanares and @rochoa It would be great if you could check it, cause there are a lot of examples updated there (just replacing old url with new constant)

This has been merged 🚀


Do we need api.py?

click calls conda index class directly, but api.py does some more parsing

Keep open


Diamond Tests fail on nonReentrant

Pull Request #6

StackExchange Issue --> https://ethereum.stackexchange.com/questions/149801/evmerror-notactivated-when-modifying-variables-in-fallback

My intuition tells me that we cannot change the local state of a contract in a function that performs delegatecall since the context is changed upon execution.


Allow services to be copied to other locations.

Closes #313.

Coverage increased (+0.0%) to 99.5% when pulling 66e8974277d9f29a3d4c7d93f7d786ecf6292a39 on 313-copy-service into 4a232759fcbdb93ec60755e95af2146898813932 on master.


Request: Please clean up your stale branches

This repo currently has 20 active branches and 57 stale branches.
Please delete your stale branches if no longer needed:

User
Stale Branches

@ranjeshj
22

@stmoy
7

@anawishnoff
6

@RBrid
4

@MarissaMatt
3

@YuliKl
2

@jevansaks
2

@micahl
2

@DmitriyKomin
2

@gabbybilka
2

@kaiguo
1

@LucasHaines
1

@teaP
1

@StephenLPeters
1

@RealTommyKlein
1

We're down to 5 Active and 7 stale.  Closing