query: v0.32.1+ remote-write prometheus + layered queriers: "vector cannot contain metrics with the same labelset"

After upgrading to v0.32.0 and later v0.32.1+, our setup no longer functions, returning a random labelset error. We're using a layered thanos-query setup, with the top layer being the target for thanos-frontend.
Thanos, Prometheus and Golang version used: Since v0.31, currently main-2023-08-28-32412dc

Object Storage Provider:
gcs
What happened:
When executing an instant query on our setup, after upgrade from 0.30.2 to 0.32.1+ (main), we're seeing this error:
{"status":"error","errorType":"execution","error":"vector cannot contain metrics with the same labelset"}
What you expected to happen:
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[5m]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693271364.906,"580"]}]}}
A value higher than >500
How to reproduce it (as minimally and precisely as possible):
kubectl port-forward directly to a thanos-ring pod and execute and instant query using the HTTP API. This eliminates any issues with thanos-frontend by exclusion.
❯ kubectl port-forward -n org-monitoring deployment/thanos-ring 10902
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[5m]))'
{"status":"error","errorType":"execution","error":"vector cannot contain metrics with the same labelset"}

Our Setup:
Queries are made against thanos-frontend, which passes them directly to thanos-ring.
The ring component has the job of Query Fanout against all thanos-query targets in our fleet. It is configured like so:
query
--endpoint=dns+thanos-query.org-monitoring.svc.clusterset.local:10901
--query.replica-label=replica
--query.replica-label=prometheus_replica
--query.replica-label=rule_replica

thanos-query.org-monitoring.svc.clusterset.local:10901  is a GKE MultiClusterServices Target. It produces a list of thanos-query endpoints discovered across the fleet. This list is the number of running thanos-query replicas across the fleet.
Each discovered thanos-query is responsible for the endpoints in it's own region, it is configured like so:
query
--endpoint=dns+prometheus.org-monitoring.svc:10901
--endpoint=dnssrv+_grpc._tcp.thanos-receive
--endpoint=dnssrv+_grpc._tcp.thanos-store-shard-0
--endpoint=dnssrv+_grpc._tcp.thanos-store-shard-1
--endpoint=dnssrv+_grpc._tcp.thanos-store-shard-2
--query.auto-downsampling
--query.replica-label=replica
--query.replica-label=prometheus_replica
--query.replica-label=rule_replica
--query.timeout=5m
--store.response-timeout=5s
--store.sd-dns-interval=5s
--store.unhealthy-timeout=1m

This is a layered querier setup as described in: https://thanos.io/tip/components/query.md/#global-view
Full logs to relevant components:
thanos-ring log

{"caller":"main.go:67","level":"debug","msg":"maxprocs: Updating GOMAXPROCS=[8]: determined from CPU quota","ts":"2023-08-29T02:20:10.989916878Z"}
{"caller":"options.go:26","level":"info","msg":"disabled TLS, key and cert must be set to enable","protocol":"gRPC","ts":"2023-08-29T02:20:10.995682676Z"}
{"caller":"query.go:842","level":"info","msg":"starting query node","ts":"2023-08-29T02:20:10.997116884Z"}
{"cachedEndpoints":0,"caller":"endpointset.go:354","component":"endpointset","level":"debug","msg":"starting to update API endpoints","ts":"2023-08-29T02:20:10.998004757Z"}
{"activeEndpoints":0,"caller":"endpointset.go:433","component":"endpointset","level":"debug","msg":"updated endpoints","ts":"2023-08-29T02:20:10.998508706Z"}
{"caller":"intrumentation.go:56","level":"info","msg":"changing probe status","status":"ready","ts":"2023-08-29T02:20:10.998376499Z"}
{"address":"<IP_ADDRESS>:10901","caller":"grpc.go:131","component":"query","level":"info","msg":"listening for serving gRPC","service":"gRPC/server","ts":"2023-08-29T02:20:10.999831529Z"}
{"caller":"intrumentation.go:75","level":"info","msg":"changing probe status","status":"healthy","ts":"2023-08-29T02:20:11.000108915Z"}
{"address":"<IP_ADDRESS>:10902","caller":"http.go:73","component":"query","level":"info","msg":"listening for requests and metrics","service":"http/server","ts":"2023-08-29T02:20:11.000234749Z"}
{"address":":10902","caller":"tls_config.go:274","component":"query","level":"info","msg":"Listening on","service":"http/server","ts":"2023-08-29T02:20:11.001127239Z"}
{"address":":10902","caller":"tls_config.go:277","component":"query","http2":false,"level":"info","msg":"TLS is disabled.","service":"http/server","ts":"2023-08-29T02:20:11.001827998Z"}
{"cachedEndpoints":0,"caller":"endpointset.go:354","component":"endpointset","level":"debug","msg":"starting to update API endpoints","ts":"2023-08-29T02:20:16.001726936Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:392","component":"endpointset","err":"dialing connection: context deadline exceeded","level":"warn","msg":"new endpoint creation failed","ts":"2023-08-29T02:20:21.003893904Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-northamerica-northeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"northamerica-northeast1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-northamerica-northeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"northamerica-northeast1\", tier=\"engineering\"},{receive_cluster=\"northamerica-northeast1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004178958Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-us-east1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-east1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-east1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-east1\", tier=\"engineering\"},{receive_cluster=\"us-east1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004265675Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west4\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"europe-west4\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west4\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"europe-west4\", tier=\"engineering\"},{receive_cluster=\"europe-west4\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004337318Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-us-central1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-central1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-central1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-central1\", tier=\"engineering\"},{receive_cluster=\"us-central1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004393088Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-us-east1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-east1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-east1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-east1\", tier=\"engineering\"},{receive_cluster=\"us-east1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004428556Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west4\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"europe-west4\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west4\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"europe-west4\", tier=\"engineering\"},{receive_cluster=\"europe-west4\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004476601Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-us-central1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-central1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-central1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-central1\", tier=\"engineering\"},{receive_cluster=\"us-central1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004523324Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-us-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-west1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-west1\", tier=\"engineering\"},{receive_cluster=\"us-west1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004587081Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"europe-west1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"europe-west1\", tier=\"engineering\"},{receive_cluster=\"europe-west1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004686835Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-australia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"australia-southeast1\", tier=\"engineering\"},{receive_cluster=\"australia-southeast1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004730393Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-us-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-west1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-west1\", tier=\"engineering\"},{receive_cluster=\"us-west1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004783825Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-australia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"australia-southeast1\", tier=\"engineering\"},{receive_cluster=\"australia-southeast1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004852742Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-asia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"asia-southeast1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-asia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"asia-southeast1\", tier=\"engineering\"},{receive_cluster=\"asia-southeast1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004886759Z"}
{"address":"<IP_ADDRESS>:10901","caller":"endpointset.go:425","component":"endpointset","extLset":"{can_alert=\"false\", cluster=\"pre-prod-monitor-asia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"asia-southeast1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-asia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"asia-southeast1\", tier=\"engineering\"},{receive_cluster=\"asia-southeast1\", tenant_id=\"default-tenant\"}","level":"info","msg":"adding new query with [storeEndpoints rulesAPI exemplarsAPI targetsAPI MetricMetadataAPI QueryAPI]","ts":"2023-08-29T02:20:21.004938184Z"}
...

{"caller":"proxy.go:318","level":"debug","msg":"Tenant info in Series()","tenant":"default-tenant","ts":"2023-08-29T02:21:07.636981742Z"}
{"caller":"proxy.go:364","component":"proxy","level":"debug","msg":"Series: started fanout streams","request":"min_time:1693275367636 max_time:1693275667636 matchers:<name:\"__name__\" value:\"prometheus_build_info\" > aggregates:COUNT aggregates:SUM without_replica_labels:\"replica\" without_replica_labels:\"prometheus_replica\" without_replica_labels:\"rule_replica\" ","status":"store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-northamerica-northeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"northamerica-northeast1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-northamerica-northeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"northamerica-northeast1\", tier=\"engineering\"},{receive_cluster=\"northamerica-northeast1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"europe-west1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"europe-west1\", tier=\"engineering\"},{receive_cluster=\"europe-west1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-australia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"australia-southeast1\", tier=\"engineering\"},{receive_cluster=\"australia-southeast1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west4\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"europe-west4\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west4\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"europe-west4\", tier=\"engineering\"},{receive_cluster=\"europe-west4\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-australia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"australia-southeast1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-australia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"australia-southeast1\", tier=\"engineering\"},{receive_cluster=\"australia-southeast1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-us-central1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-central1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-central1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-central1\", tier=\"engineering\"},{receive_cluster=\"us-central1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-asia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"asia-southeast1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-asia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"asia-southeast1\", tier=\"engineering\"},{receive_cluster=\"asia-southeast1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-us-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-west1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-west1\", tier=\"engineering\"},{receive_cluster=\"us-west1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-us-central1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-central1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-central1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-central1\", tier=\"engineering\"},{receive_cluster=\"us-central1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-asia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"asia-southeast1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-asia-southeast1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"asia-southeast1\", tier=\"engineering\"},{receive_cluster=\"asia-southeast1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-us-east1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-east1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-east1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-east1\", tier=\"engineering\"},{receive_cluster=\"us-east1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-us-east1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-east1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-east1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-east1\", tier=\"engineering\"},{receive_cluster=\"us-east1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west4\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"europe-west4\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-europe-west4\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"europe-west4\", tier=\"engineering\"},{receive_cluster=\"europe-west4\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried;store Addr: <IP_ADDRESS>:10901 LabelSets: {can_alert=\"false\", cluster=\"pre-prod-monitor-us-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-0\", region=\"us-west1\", tier=\"engineering\"},{can_alert=\"false\", cluster=\"pre-prod-monitor-us-west1\", envreg=\"pre-prod-monitor\", gcp_project_id=\"sanitized\", prometheus_replica=\"prometheus-1\", region=\"us-west1\", tier=\"engineering\"},{receive_cluster=\"us-west1\", tenant_id=\"default-tenant\"} MinTime: -62167219200000 MaxTime:<PHONE_NUMBER>854775807 queried","ts":"2023-08-29T02:21:07.638288025Z"}
{"caller":"proxy.go:318","level":"debug","msg":"Tenant info in Series()","tenant":"default-tenant","ts":"2023-08-29T02:21:08.936129958Z"}
{"caller":"proxy.go:318","level":"debug","msg":"Tenant info in Series()","tenant":"default-tenant","ts":"2023-08-29T02:21:08.936305335Z"}

Anything else we need to know:
Most of our remote senders have an external label set like:
replica: prometheus-n
Some newer senders have an external label with a more specific prometheus_replica label.
We've tried a mix of playing with external labels and thanos query settings to no avail. Reverting just the ring component to v0.30.2 resolves the issue.
Also, sometimes the query works if the duration is kept really short:
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[1s]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693275793.558,"14"]}]}}
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[1s]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693275795.497,"16"]}]}}
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[1s]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693275798.886,"9"]}]}}
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[1s]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693275800.061,"11"]}]}}
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[1s]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693275801.252,"12"]}]}}
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[5s]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693275804.402,"195"]}]}}
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[5s]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693275806.031,"193"]}]}}
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[5s]))'
{"status":"error","errorType":"execution","error":"vector cannot contain metrics with the same labelset"}
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[5s]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693276058.426,"121"]}]}}
❯ curl http://localhost:10902/api/v1/query --data-urlencode 'query=count(last_over_time(prometheus_build_info[5s]))'
{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1693276059.51,"139"]}]}}

Are stores and receivers version 0.32.1 too?

Are stores and receivers version 0.32.1 too?

Yes, they match the version of the leaf thanos-query

Maybe you could write out the labels of each series when you query prometheus_build_info?

I don't understand what you mean? The only external label we add that's different between replicas, for deduplication, is the replica label. We run 2 replica statefulsets, so each prometheus sts should produce the following series:
prometheus_build_info{cluster="foo",replica="prometheus-0"}
prometheus_build_info{cluster="foo",replica="prometheus-1"}

Which we deduplicate by specifying a replica label of replica. In some other clusters, the label is prometheus_replica which is the preferred nomenclature. We're de-duplicating on both labels.

I mean could you please execute an instant query prometheus_build_info[5m] with disabled deduplication and paste the result here so that we could understand what kind of labels are you getting exactly?

{branch="HEAD", container="prometheus", endpoint="http-web", goarch="amd64", goos="linux", goversion="go1.20.5", instance="<IP_ADDRESS>:9090", job="ops-system/monitoring-stack-kube-prom-prometheus", location="global", namespace="ops-system", pod="prom-agent-monitoring-stack-kube-prom-prometheus-0", prometheus="ops-system/monitoring-stack-kube-prom-prometheus", prometheus_replica="prom-agent-monitoring-stack-kube-prom-prometheus-0", receive="true", region="core", replica="thanos-receive-1", revision="8ef767e396bf8445f009f945b0162fd71827f445", tags="netgo,builtinassets,stringlabels", tenant_id="k3s", version="2.45.0"}
0
{branch="HEAD", container="prometheus", endpoint="http-web", goarch="amd64", goos="linux", goversion="go1.20.5", instance="<IP_ADDRESS>:9090", job="ops-system/monitoring-stack-kube-prom-prometheus", location="global", namespace="ops-system", pod="prom-agent-monitoring-stack-kube-prom-prometheus-0", prometheus="ops-system/monitoring-stack-kube-prom-prometheus", prometheus_replica="prom-agent-monitoring-stack-kube-prom-prometheus-0", receive="true", region="core", revision="8ef767e396bf8445f009f945b0162fd71827f445", tags="netgo,builtinassets,stringlabels", tenant_id="k3s", version="2.45.0"}
0
{branch="HEAD", container="prometheus", endpoint="http-web", goarch="amd64", goos="linux", goversion="go1.20.5", instance="<IP_ADDRESS>:9090", job="ops-system/monitoring-stack-kube-prom-prometheus", location="global", namespace="ops-system", pod="prom-agent-monitoring-stack-kube-prom-prometheus-0", prometheus="ops-system/monitoring-stack-kube-prom-prometheus", prometheus_replica="prom-agent-monitoring-stack-kube-prom-prometheus-0", receive="true", region="core", revision="8ef767e396bf8445f009f945b0162fd71827f445", tags="netgo,builtinassets,stringlabels", tenant_id="k3s", version="2.45.0"}
here with out dedup. This explicit fails with activated dedup.

@farodin91 and what kind of parameters do you have on Thanos Query?

rate(prometheus_build_info[330h])

Hey; are you able to provide some offending blocks? That would help me trying to reproduce and understand this!

@farodin91 is there a reason why these series have receive="true" but don't have any replica label? Could you share some of your receive configs?

branch="HEAD", container="prometheus", endpoint="http-web", goarch="amd64", goos="linux", goversion="go1.20.5", instance="<IP_ADDRESS>:9090", job="ops-system/monitoring-stack-kube-prom-prometheus", location="global", namespace="ops-system", pod="prom-agent-monitoring-stack-kube-prom-prometheus-0", prometheus="ops-system/monitoring-stack-kube-prom-prometheus", prometheus_replica="prom-agent-monitoring-stack-kube-prom-prometheus-0", receive="true", region="core", revision="8ef767e396bf8445f009f945b0162fd71827f445", tags="netgo,builtinassets,stringlabels", tenant_id="k3s", version="2.45.0"}
0
{branch="HEAD", container="prometheus", endpoint="http-web", goarch="amd64", goos="linux", goversion="go1.20.5", instance="<IP_ADDRESS>:9090", job="ops-system/monitoring-stack-kube-prom-prometheus", location="global", namespace="ops-system", pod="prom-agent-monitoring-stack-kube-prom-prometheus-0", prometheus="ops-system/monitoring-stack-kube-prom-prometheus", prometheus_replica="prom-agent-monitoring-stack-kube-prom-prometheus-0", receive="true", region="core", revision="8ef767e396bf8445f009f945b0162fd71827f445", tags="netgo,builtinassets,stringlabels", tenant_id="k3s", version="2.45.0"}

- receive
- '--log.level=info'
- '--log.format=json'
- '--grpc-address=<IP_ADDRESS>:10901'
- '--http-address=<IP_ADDRESS>:10902'
- '--remote-write.address=<IP_ADDRESS>:19291'
- '--objstore.config=$(OBJSTORE_CONFIG)'
- '--tsdb.path=/var/thanos/receive'
- '--label=replica="$(NAME)"'
- '--label=receive="true"'
- '--tsdb.retention=12h'
- >-
  --receive.local-endpoint=$(NAME).thanos-receive-headless.$(NAMESPACE).svc.cluster.local:10901
- '--tsdb.out-of-order.time-window=120s'
- '--tsdb.too-far-in-future.time-window=60s'
- '--tsdb.max-exemplars=1000'

Isn't the replica removed in the storegateway?

- receive
- '--log.level=info'
- '--log.format=json'
- '--grpc-address=<IP_ADDRESS>:10901'
- '--http-address=<IP_ADDRESS>:10902'
- '--remote-write.address=<IP_ADDRESS>:19291'
- '--objstore.config=$(OBJSTORE_CONFIG)'
- '--tsdb.path=/var/thanos/receive'
- '--label=replica="$(NAME)"'
- '--label=receive="true"'
- '--tsdb.retention=12h'
- >-
  --receive.local-endpoint=$(NAME).thanos-receive-headless.$(NAMESPACE).svc.cluster.local:10901
- '--tsdb.out-of-order.time-window=120s'
- '--tsdb.too-far-in-future.time-window=60s'
- '--tsdb.max-exemplars=1000'

Isn't the replica removed in the storegateway?

Only after compaction i think. New blocks will still have it

in 330h their should be a compaction

I updated allow thanos components to main-2023-09-05-d1edf74. No improve, i see the same issue.

@GiedriusS Do you have any idea to help you? How I can debug this issue?

Now, it also fails for some queries, if use dedup is activated or not.

I'm fairly sure it might be https://github.com/thanos-io/thanos/pull/6702 this

@MichaHoffmann Do you want to release it as 0.32.3?

This is running good for us.


Is there any plan to support the ESP8266?

The ESP8266 by Espressif-Systems is currently the (by far) cheapest System-on-chip for IoT-purposes with around 40k of available RAM and usually >500kB of flash-memory. With nodeMCU there already exists a firmware that sports a LUA-Interpreter so I would really love to see a JS-interpreter doing the same.
Is this possible at all, and is there any available Documentation on the steps needed to make jerryscript run on this Hardware?

@usefulthink IMHO, JerryScript can running on ESP8266. But, first we have to check up the ESP8266 by ourselves.
Please reference the (https://github.com/Samsung/iotjs/issues/136) also.
Thanks!

i'm curious as well, as it seems is @maxogden - do you have a timeframe on when you'd be able to try it on an esp8266?

@JerrySievert , We already ordered the ESP8266 but not delivered yet. So, it's hard to estimate the schedule now. I will keep update the progress here.

To whom interested, I'm now working to make JerryScript run in ESP8266.
First thing is getting used to the build system.

\o/ Thank you so much!

that's great news!
/cc @maxogden, @kenichi

Hello, I've uploaded initial development branch esp8266-dev for ESP-01 board. There are some patches to the SDK that may be not correct. Please add comments.
First commit just blinks LED from the JS. APIs not just for testing.
I'll try to bind network API so that we can use it from the JS codes.
But I am not sure where to start from, so anyone who knows please leave a comment.

About the memory usage...
JerryHeap is set to 20KB and task stack size is 8K and free system heap memory is about 10K.

Awesomeness @seanshpark . I'm on Mac OS and will try and figure out how to get the ESP SDK working and report back if I succeed

@maxogden , Nice !

Howdy ... I am a keen ESP8266 developer and have a free book on the subject available here ... http://neilkolban.com/tech/esp8266/
I would love to offer any free assistance I can on getting JerryScript running on the ESP8266 and ESP32.
I can be reached by email at<EMAIL_ADDRESS>

@nkolban do you have a source for esp32's?

@nkolban , Wow, glad to hear from you. I've read the book and it helped a lot!. I've made a branch embedding-dev, previously esp8266-dev but now merged also with mbed, and JerryScript itself runs in ESP8266. I was working to enable network, in my personal repo, but have little time to do this while working with others.

@JerrySievert Earlier this year I worked hard and created a free book on the ESP8266.  I listed this in a previous post.  Each month I continued to update it.  The good folks at Espressif were pleased with the result and I have offered to update it and/or re-write it for the ESP32.  As such, they have invited me to their beta programme.  I have no idea when I'll receive an instance but when I do, I'll be using it for working on a PDF of notes for us all to build upon.   So ... to your question ... I have no source other than Espressif themselves and I don't expect to receive more than one and that would be for my study to allow me to write the PDF notes.  When it arrives, I plan to go dark on it for months and simply work on the write-up for release when it itself becomes generally available.
@seanshpark I'll be delighted to participate in any way I can.  I assisted with porting the Espruino open source JavaScript to ESP8266 and that is working well, am also tinkering with Smart.js JavaScript .... so I'm growing more and more knowledge on what it takes to get JavaScript going on these ESP8266s.  If you don't have time just now to work any further on the ESP8266 and there is no-one else contributing, then I'll step back until such time as work on it should restart.  I'm keen to collaborate ... but collaboration is the operative words here.  I'll be delighted to bring any and all ESP8266 skills and experience to the table, but I don't know anything yet about the internals of JerryScript ... so would be looking to be part of the community and not so much an active leader.

@nkolban , first thing, thank you for writing down your kind thoughts. As english is not my first language writings may seem dry and somethings it's hard for to express my thoughts and emotions.
YES it would be a big help if you can guide me and others with JerryScript running on ESP8266 and may be yourself with the codes. Current status is that just running JerryScript in ESP8266 is somewhat done, and it would be an honor if you can look the codes here and give comments.
Also wrote some summary I've done with in here and here. It would be wonderful if you can give some notes about it.
But after that I had some problems with enabling network, but it was my AP that was working improperly and now I'm waiting for the new one. I've tried also at home and connection itself is ok, but not sure my test codes was proper or not. I've reference nodemcu codes. So if possible can you give some informations how to implement this? I'm thinking of exposing JS APIs so that users can control AP connection with JavaScript, or maybe is this a bad idea? Currently I cannot find my code. May be at home...
The next step I'm thinking is more difficult cause as memory is short I can't make IoT.js run so have to build-up more compact JS APis with TCP, UDP and HTTP or maybe CoAP...

Hello, JerryScript on ESP8266 now in master branch, #733.

@seanshpark thank you!  that's fantastic news!

A patch is recently landed wich adds the support.


Missing License

Could you please add a LICENSE? I want to use this for a gif optimizer I've been working on, but the lack of a LICENSE file makes me hesitant.
The code is presumably MIT as https://github.com/gfiumara/CIEDE2000 is MIT
Thanks!

Added README.md and LICENSE.

Thanks!


[SMALLFIX] Use units for time values

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15864/
Test PASSed.


reactjs.net certificate expired

Hello, I can't see better place to report it, but https://reactjs.net website use expired SSL certificate.
Steps to reproduce
visit https://reactjs.net

Thanks, we're taking a look 😃

Not sure if there was a temporary problem, but it appears to be valid now.

Please let us know if you see this again... Netlify is supposed to auto renew the certificate, so I'll contact their support if it breaks again.

Hi,
This still seems to be a problem for me when trying to access the site on all major browsers.

This server could not prove that it is reactjs.net; its security certificate expired 12 days ago. This may be caused by a misconfiguration or an attacker intercepting your connection. Your computer's clock is currently set to Thursday, February 28, 2019. Does that look right? If not, you should correct your system's clock and then refresh this page.

above from chrome, my timezone is UTC +13
Thank you

I'm reaching out to Netlify's support team. I used this tool to check it: https://asm.ca.com/en/checkit.php and it looks like it's okay on some servers, but expired on others:

@glasody or @kpkozak - Can you please re-test this? Netlify's support have mentioned that it shouldn't be broken any more.

Still broken:

Thanks! I'm able to verify that an expired cert is being served from that server, using this command:
openssl s_client -connect <IP_ADDRESS>:443 -servername reactjs.net

verify error:num=10:certificate has expired
notAfter=Feb 16 21:02:45 2019 GMT

I'll get in touch with Netlify again.

@weltmeyer This should be fixed now - Could you please check?

@weltmeyer This should be fixed now - Could you please check?

It works:

Jepp. Working for me too.

Thanks for checking!


Handle Long Petinfo Email

Hello, this is my solution of issue #255  to handle some emails of petInfo that could get too long. I "break" the words, so that it will not go over the box border.
This is an example:

@redxzeta, can you please take a look at this? Thank you


use_2to3 is invalid

I encountered the following error when installing this package. It seems that it is not compatible with setuptools version >58.0.0.

Hi! I'm running into the same issue; were you able to find a solution?


attempt to limit bolt memory usage

I think this PR may limit the amount of memory that siad is using by a factor of 2 or 3. Having Sia sit at 800MB is a lot better than 2GB.
I'm not completely sure though, testing has been unclear/incomplete, trying it on my live nodes. Wanted @VoidingWarranties to give it a shot on his nodes as well, see if it makes much of a difference.

*if memory usage does not decrease substantially then this PR is not worth merging.

what's the status on this?

I have been pretty sucked into the host I/O stuff, haven't had time to verify whether or not RAM usage is reduced. Would be very helpful if someone else could run the code on their machine, compare RAM usage.
The easiest test I can think of is to take a fully synced machine with a new wallet (no renter or host or miner), then unlock the wallet. On the master branch, the RAM usage should be much higher than on this branch. If that is the case, we merge it. If RAM usage is high or moderate on both, we don't merge it.

Further testing suggests that this PR does not reduce memory usage.


CallNodes = nnkCallKinds

https://github.com/nim-works/cps/blob/5645eb5838e6d30d484fbe23d8c590201e520630/cps/transform.nim#L9-L10
https://github.com/nim-lang/Nim/pull/21833
https://github.com/nim-lang/Nim/pull/21829

Do you feel like creating a PR?

Should I remove all of the nnkHiddenCallConv stuff or make a new type to emulate what it was?

 I'll stare at the code some more.

Basically, we only want to rewrite certain kinds of calls in certain circumstances...

Right, I got that. I don't understand why the set would be changed without the behavior changing, but you do seem to know, so don't let me waste too much of your time.

Yeah it does, I meant to imply your second option.


Safari: flex-basis with flex-direction: column and justify-content: center causes elements to overflow parent

When using justify-content: center and flex-direction: column, Safari seems to miscalculate the height of the flex parent when some of the flex items have a flex-basis specified. The result is that some items can spill out of the box at the flex-start.
Has anyone else run into this? I had a page where my heading (the first element in my flex container) was spilling up out of the parent and became white text on white background. It took a long time to figure out what exactly was going on. I see it in Safari 10.0.2 and Mobile Safari on iOS 10.2.
I'm not sure if this is a bug or not, so I haven't submitted it to the WebKit team. If there's any sort of validation in here that this is a true bug (and not just some part of the spec I don't understand), then I'll go ahead and submit it.
Test case: https://codepen.io/awayken/pen/wgazpb/ - in the problem browsers, Line 1 will be cut off as it overflows upward out of the <body>.
Work-around: either eliminate flex-basis on flex items or use justify-content: flex-start or justify-content: flex-end. There might be other justify-content values that work, too.

This looks like a bug to me, I'd recommend opening a bug on Webkit or Apple BugReporter.

@danielcompton Submitted to Safari. We'll see if they kick it back as a WebKit problem or not.

Have you tried to use min-height with the same value as the flex-basis? I think it could work.

@awayken Can you paste the bug link in this issue?

@philipwalton This is my first submission to the Safari bug tracker, but as far as I can see, they don't offer public links to the bugs. When I log in, it has the appearance of an email in an inbox rather than a forum post or BugZilla listing. If anyone has insight into how I'd find the public link, I'd be more than happy to share it in this thread.

@awayken if you look at this project's README, you'll notice lots of links to Safari bugs. Is that where you're submitting?

@philipwalton It looks like the Safari bug links are actually WebKit bug links. I submitted mine straight to Safari because I wasn't sure if it was truly WebKit or Safari that had the issue. I figured I'd start where I knew I was seeing the issue, and they would tell me if I should resubmit elsewhere. (And I've never tried downloading or compiling WebKit on its own.)
Of course, now that it's a month on and I've heard nothing back, I'm starting to wonder if I should just submit to WebKit anyway, even just for some feedback on the bug.

FYI: Safari is the browser and Webkit is the rendering engine Safari uses. If it's an issue with flexbox then it's definitely a Webkit issue. (A Safari issue would be something like if the back button isn't working.)

Submitted bug to WebKit: https://bugs.webkit.org/show_bug.cgi?id=168130

Is it possible that this is the reason I'm seeing a bug like this on my website?

It looks like this has been addressed.

Safari, Chrome, and Firefox all agree on rendering for both test cases. I don't believe there is any remaining compatibility issue.
-- Brent Fulgham, 2022-07-15 11:26:15 PDT, Permalink


cc is passing wrong kind of flags to compiler

I'm cross compiling from linux to windows-msvc with the mingw tool chain. Dependencies that use cc fail with
error: failed to run custom build command for `ring v0.16.20`

Caused by:
  process didn't exit successfully: `/home/morganamilo/rust/target/debug/build/ring-7e626d6f394fedab/build-script-build` (exit status: 101)
  --- stdout
  OPT_LEVEL = Some("0")
  TARGET = Some("x86_64-pc-windows-msvc")
  HOST = Some("x86_64-unknown-linux-gnu")
  CC_x86_64-pc-windows-msvc = None
  CC_x86_64_pc_windows_msvc = None
  TARGET_CC = None
  CC = Some("x86_64-w64-mingw32-cc")
  CFLAGS_x86_64-pc-windows-msvc = None
  CFLAGS_x86_64_pc_windows_msvc = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("true")
  CARGO_CFG_TARGET_FEATURE = Some("crt-static,fxsr,sse,sse2")

  --- stderr
  running "x86_64-w64-mingw32-cc" "-O0" "-ffunction-sections" "-fdata-sections" "-g" "-fno-omit-frame-pointer" "-m64" "-static" "-I" "include" "-Wall" "-Wextra" "/GS" "/Gy" "/EHsc" "/GR-" "/Zc:wchar_t" "/Zc:forScope" "/Zc:inline" "/Zc:rvalueCast" "/sdl" "/Wall" "/wd4127" "/wd4464" "/wd4514" "/wd4710" "/wd4711" "/wd4820" "/wd5045" "/Od" "/RTCsu" "-DNDEBUG" "-c" "/Fo/home/morganamilo/rust/target/x86_64-pc-windows-msvc/debug/build/ring-6cb21a5c5dffdbf7/out/aes_nohw.obj" "crypto/fipsmodule/aes/aes_nohw.c"
  x86_64-w64-mingw32-cc: error: -E or -x required when input is from standard input
  thread 'main' panicked at 'execution failed', /home/morganamilo/rust/cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/build.rs:656:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Never mind these flags look to be hard coded in ring's build file.

Indeed I don't think those are coming from this crate, so closing.


Integrate to OpenDAL to allow manage files on s3/azblob/gcs/oss/dopbox/gdrive...

Is your feature request related to a problem? Please describe
yazi is really great on local fs. I'm thinking about if we can extand those features to more storage services like s3, azblob, oss, dropbox, gdrive and so on.
Will you be willing to contribute this feature?

[X] Yes, I'll give it a shot

Describe the solution you'd like
OpenDAL is an Apache project that allows users to easily and efficiently retrieve data from various storage services in a unified way.

By integrate with opendal, we can add support for different storage services at once.
Describe alternatives you've considered
No response
Additional context
No response

Very Useful Feature :))

Hi @sxyazi, what do you think about this feature? How can we get involved? I feel like we can add s3 support first.

Hmm I've thought of 3 ways to integrate OpenDAL:

Replace Yazi's current data access layer with OpenDAL completely.
Use "opendal-fuse" for external integration, just like archivemount does.
Abstract a virtual file system for Yazi, with OpenDAL and other external tools/libraries (such as archiver, fd, rg) as separate providers.

For this:

The first method essentially shifts the work Yazi needs to OpenDAL, meaning we have to integrate the functionalities Yazi requires into OpenDAL, so it's not the preferred option.
The second one, inspired by @og900aero recently, seems to be the simplest and can be implemented in the short term. The downside is its performance isn't ideal.
The last one is the most ideal choice. It could fundamentally solve all the long-term issues Yazi faces, like https://github.com/sxyazi/yazi/issues/62. I've been working on achieving this (e.g. refactored all PathBuf to Url), but it's still a long way off.

Please supplement any information I'm unaware of. Maybe we can discuss further details on Yazi's Discord server/Telegram group, such as:

How to retrieve the mime-type of a network file through file(1)? It's currently the only essential requirement.
How to listen for changes in network files, like actively triggering (deletion, copying, etc.) or passively when files disappear?
How to handle multiple file open requests; do we need to add a download queue for this?

Added to the Feature Requests, closing this issue in favor of that list.


Shops adding undesirable nbt tags

I have a spongeforge server and carrot shop became essential as it is used in the bank for players to buy and sell coins for Custom NPC trading. The problem is that after a while, coins bought via carrot shop come with an nbt tag wich makes them useless for custom NPC trading.
I want to keep items without any change when bought, why is carrot shop changing them?

Hey. What mod are the coins coming from?
What sign are you using? [iBuy]?
What nbt tag has been added? iirc the plugin do not change that

Firstly I was using coins from gregtech, now from ordinary coins, is that this plugin is not meant for mods?

I can confirm this. It seems any items purchased with CarrotShop do not work with any modded menus. Here is a screenshot of what we're talking about. I purchased some emeralds from the shop but the CustomNPCs menu doesn't recognize them despite them having the same item ID.


[zephyr] Makefile tuning

Read the zephyr crosscompile settings earlier so correct values are used.
Currently, the crosscompilation does not work on OSX. With this fix it does.
JerryScript-DCO-1.0-Signed-off-by: Sakari Poussa<EMAIL_ADDRESS>

@sergioamr @pfalcon PTAL

LGTM

LGTM

@poussa, you have two LGTMs, but I'd like to wait for @sergioamr or @pfalcon to check it, before we merge it.

LGTM

@sergioamr, thanks for checking. @poussa, could you rebase the PR to the current master, so we can merge it properly?

@LaszloLango rebase done

@poussa, thank you.


cloudbase-init on Windows 7 miss restart

Hello,
We created a Windows 7 Enterprise 64bit Image and installed the latest cloudbase-init msi.
At boot we see that the cloudbase-init script is running. But the hostname isn't set. When we start the cloudbase-init service manually the system restarts and the hostname is set properly.
On Windows 2012 Server we have no issues.

Since the project is moved to StackForge, we are going to mark the issue as closed here.


feat(*): Support for RC6

Closes #604

I noticed it is failing, I believe this is do to the testing stuff changing, ie needing to use testbed to make a module with what the code needs etc. I did mess around and seemed to get the test code partway updated but I was getting an obscure 404 tracuer error.

@Tempus35 fixed it. Merging now..


pkg/query: Fix jaeger tags for query selects

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
This makes the tags added in #2184 actually work.
Verification
Started local jaeger this time and added the jaeger config to the quickstart script for next time :wink: .
@bwplotka @squat @metalmatze @GiedriusS @povilasv

hello friend, please sign the DCO and then we'll be happy to merge the commit :)


Cross compilation with w64-mingw32 compilers under fedora 36

Hi,
I tried to cross-compile openblas with w86_64-w64-mingw32 compilers under fedora 36 make BINARY=64 CC=x86_64-w64-mingw32-gcc FC=x86_64-w64-mingw32-gfortran HOSTCC=gcc TARGET=LOONGSON3A but it got this error when archiving
 ar  -ru ../libopenblas_loongson3r3p-r0.3.20.a [list obj files]
 ar: sgemm_kernel.obj: No such file or directory
sgemm_kernel.obj file doesn't exist...
This is a bug ?

Are you sure that you got the correct compiler for cross-compiling to Loongson3 target ? This is a MIPS cpu
so I would expect the cross-compiler name to be something like mips-linux-gnu-gcc - yours looks like the pc linux-to-windows toolchain.

Or to put it differently, are you sure you want to cross-compile to a Loongson3A system at all ? The section on cross-compiling in our README uses this particular example as it was what users were struggling with at the time, but the important information there is the use of HOSTCC (some build tools still need to be created on the system where the compiler is installed), and the use of proper paths in the CC and FC options. The TARGET on the other hand always needs to reflect the cpu you actually want to run the code on (which the build files cannot guess). MIPS hardware is nowadays usually found in routers and similar appliances...

if you need Windows DLL to rename into blas.dll you need to set TARGET=GENERIC DYNAMIC_ARCH=1 and probably more cpu threads than you will have in near future in a single system. If you target embedded system, you must use SDK/BSP compilers supplied with it unless tkhat system runs full Linux.

assuming solved (based on your recent scivision issue), please comment if you need further assistance


Create winit windows before app.initialize()

This is required so startup systems have access
to Windows and WinitWindows resources.

This commit restores code that was removed in #879

Haha this one is my fault. @bjorn3 mentioned that the line wasn't necessary and I totally forgot that we added it for a reason. Can you add a comment above that line to indicate why its there to protect future contributors from future me?

Sure. Done.

I cannot see the comment being added, are you sure you pushed it properly?

I did, then I force-pushed it gone. I force-pushed it back again now.
I really should not be doing PRs from master.
Unfortunately GH does not allow me to change the source branch for PR.


Current Parser does not Allow for Multiple Regexs

When we create parsers to implement new implementations we sometimes find that the regex we need to process a line is close to, but not exactly matching, a regex of a preexisting parser implementation.
For example, tag-change.ts handles parsing of the line
[Power] GameState.DebugPrintPower() -     TAG_CHANGE Entity=[entityName=Mecharoo id=54 zone=PLAY zonePos=1 cardId=BOT_445 player=2] tag=NUM_TURNS_IN_PLAY value=1
through the regex
/^\[Power\] GameState.DebugPrintPower\(\) -\s+TAG_CHANGE Entity=\[entityName=(.*) id=(\d*) zone=.* zonePos=\d* cardId=(.*) player=(\d)\] tag=(.*) value=(\d*)/
but if we want to parse the line
[Power] PowerTaskList.DebugPrintPower() -     TAG_CHANGE Entity=manitu#1864 tag=TIMEOUT value=55
we would have to create a completely new regex like this
\[Power\] GameState.DebugPrintPower\(\) -\s+TAG_CHANGE Entity=(.*) tag=(.*) value=(\d*)
which we would also like to handle in tag-change.ts. However, our current implementation only supports one regex, and if we try to use the | operator, and use this regex:
/^\[Power\] GameState.DebugPrintPower\(\) -\s+TAG_CHANGE Entity=(?:(?:\[entityName=(.*) id=(\d*) zone=.* zonePos=\d* cardId=(.*) player=(\d)\])|(.*)) tag=(.*) value=(\d*)/
we encounter a new problem when we have to represent this line in data as a typescript object Parts https://github.com/Tespa/hearthstone-parser/blob/46392bd07cd9cdaa52589adc0b020491da5bbf7f/src/line-parsers/tag-change.ts#L4. When we try to add new fields to the object and try to fill them, we have to leave some of them blank, which causes the typescript compiler to complain. We should try to design our interfaces such that this will not be an issue.
Alternatively, we could try to create a new parser for each of the individual regexes.

My gut feeling right now is that we should continue with our existing model of "one regex per line parser". It's possible that a better design exists, but I don't know if we have the time to experiment with new approaches right now.
I'm also interested in hearing what @Hoishin thinks here

I don't know if I completely understand the issue, but if you want to handle two (partially) different types in the Parts type, you can use union types.
I'm not sure if combining two regexes with | would resolve the issue you mentioned in the first line, which is why I don't know if I'm understanding this issue correctly.

actually this might be specific to how we handle it in tag-change and zone-change where we try to serialize the log line into a javascript object. Different regexes require different representations, which is why using a single interface Parts as in the code is incompatible with multiple regexes.

Possible solution would be making another line parser with same event name.


Define package.repository in Cargo.toml

Needed by cargo-bitbake. Also make sure we are not missing other important fields.

Done in #33.


[backport] Increase CPU memory for test instance in PFN CI

Backport of #7951

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit f30825ad453943543351ed5caba9676f0cf2c0d3, target branch v6) failed with status FAILURE.


Can I use this package in Nuxt.js ?

I want to use this package in Nuxt.js.
But I've got a error below.
TypeError: Vue.component is not a function

I think src/index.js need to add this line
const Vue = require('vue')

I found the solution. thanks.
 import {VueCkeditor} from 'vue-ckeditor2'
Vue.component('vue-ckeditor', VueCkeditor)


Get rid of WithNetNS*Unsafe

All occurrences of WithNetNS*Unsafe should be replaced by the safe version introduced in #2475 for the safety reasons.

No longer relevant due to https://github.com/weaveworks/weave/pull/3291.


Let VS do its thing

newline after BOM and slight reordering of Mvc.sln
add Service/Include properties to some test .xproj files
also add BOM in a few cases

/cc @davidfowl any of this that should not be checked into the repo?

@BillHiebert will newer VS versions keep making changes like this?  if yes, I'll get it in.  if no, guess we'll try to avoid mixing these temp changes into other commits...

FWIW, I'm seeing this on dnx as well with the latest VS builds. It's pretty damn annoying.

trying to find the thread but think @BillHiebert or someone said this related to letting VS know there's an associated test project.  the upshot might have been along the lines of "well, these files are for VS".
probably means we need an aspnet/DNX PR similar to this one.  but let's wait 'til we hear...

Seems like it might be every test project

found the thread.  helpful though @BillHiebert didn't mention permanence.
@sayedihashimi asked

@billhiebert do you know how the Service item is added to the project file?

and @BillHiebert responded

It is a VS thing. It is a way to have a project which is using a specific service load the service when the project opens. This avoids the service having to be loaded for all projects.

wow, and someone named @davidfowl had earlier commented

It's ok.


Full website

Milestone: Build a complete website
The following changes are being introduced:

A website consisting of 3 pages: Home, Calculator, and Quote.
React basic styling was used.

Thanks🤝


Does the calendar handle multiple day events? [Question]

@alan-craftbrewerysolutions As of now calendar by default does not handle multiple day events.
But If you have algorithm/code for multiple day event, you can provide it on initialisation of EventController.
ex,
final controller = EventControler(
   eventFilter: (date, events){
      // Your code goes here.
     // This function will return list of events that will be displayed on given date.
   },
);

We are planning to implement recurring events functionality in near future.
for now I am closing this issue. Feel free to reopen it if you need more info or it does not solve your query.

Thank you. I will test out that suggestion.


Authentication, tenant restrictions and Secure Links sharing

How is authentication looking when a file is shared via Secure Link (ad-hoc user)? Would Tenant Restrictions policies apply? Imagine organization A has configured tenant restrictions at their web proxy. Now user from organization B invites user from organization A as ad-hoc user via Secure Link. Would tenant restrictions block access to organization B?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f75d2b5a-bc14-e0f3-1269-716383939212
Version Independent ID: 879c8636-ab9a-0440-039a-f3eac8d41a1f
Content: Secure external sharing in SharePoint Online
Content Source: SharePoint/SharePointOnline/what-s-new-in-sharing-in-targeted-release.md
Service: sharepoint-online
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

@officedocsbot assign @scanum

@pawp81 Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

@officedocsbot close


ValueError: min() arg is an empty sequence

Describe the bug
When I run pdftotree on a PDF file, I get a runtime exception: ValueError: min() arg is an empty sequence.
To Reproduce
Steps to reproduce the behavior:

Download this PDF file: performance-smart-networks.pdf

Execute the following code: html = pdftotree.parse(pdf_file="performance-smart-networks.pdf", html_path=None, model_type=None, model_path=None, favor_figures=True, visualize=False)

Expected behavior
The variable html should contain the HTML mark-up with the text from the PDF.
Error Logs/Screenshots
Here is the full error stack trace:
~/anaconda3/lib/python3.6/site-packages/pdftotree/core.py in parse(pdf_file, html_path, model_type, model_path, favor_figures, visualize)
     63     if not extractor.is_scanned():
     64         log.info("Digitized PDF detected, building tree structure...")
---> 65         pdf_tree = extractor.get_tree_structure(model_type, model, favor_figures)
     66         log.info("Tree structure built, creating html...")
     67         pdf_html = extractor.get_html_tree()

~/anaconda3/lib/python3.6/site-packages/pdftotree/TreeExtract.py in get_tree_structure(self, model_type, model, favor_figures)
    236                 ref_page_seen,
    237                 tables[page_num],
--> 238                 favor_figures,
    239             )
    240         return self.tree

~/anaconda3/lib/python3.6/site-packages/pdftotree/utils/pdf/pdf_parsers.py in parse_tree_structure(elems, font_stat, page_num, ref_page_seen, tables, favor_figures)
    760     # Figures for this page
    761     figures_page = get_figures(
--> 762         mentions, elems.layout.bbox, page_num, boxes_figures, page_width, page_height
    763     )
    764

~/anaconda3/lib/python3.6/site-packages/pdftotree/utils/pdf/pdf_parsers.py in get_figures(boxes, page_bbox, page_num, boxes_figures, page_width, page_height)
   1244
   1245     for fig_box in boxes_figures:
-> 1246         node_fig = Node(fig_box)
   1247         nodes_figures.append(node_fig)
   1248

~/anaconda3/lib/python3.6/site-packages/pdftotree/utils/pdf/node.py in __init__(self, elems)
     45         #     # self.sum_elem_bbox = self.sum_elem_bbox + len(elem.get_text())
     46         self.table_area_threshold = 0.7
---> 47         self.set_bbox(bound_elems(elems))
     48         # self.table_indicator = True
     49         self.type_counts = Counter(map(elem_type, elems))

~/anaconda3/lib/python3.6/site-packages/pdftotree/utils/pdf/vector_utils.py in bound_elems(elems)
    119     Finds the minimal bbox that contains all given elems
    120     """
--> 121     group_x0 = min(map(lambda l: l.x0, elems))
    122     group_y0 = min(map(lambda l: l.y0, elems))
    123     group_x1 = max(map(lambda l: l.x1, elems))

ValueError: min() arg is an empty sequence

Environment (please complete the following information):

OS: Ubuntu 18.04
Python: 3.6.4 (Anaconda distribution)
pdftotree Version: v0.4.0

I have run into same issue with my pdf and it is not a scanned document. I have checked all the bug fixes and the problem still persists.

I had an similar error and found out that my pdf simulated empty LTFigures. These empty objects will cause your error, since l.x0, l.y0, l.x1 and l.y1 just don't exists, and therefore your mapping will be empty, i.e. min() arg is an empty sequence.
I solved it by not adding empty LTFigures while constructing the elements of the pdf. You need to add a single if statement in function processor(m) of the package pdf_utils.py (pdftotree.utils.pdf.pdf_utils). See # ADD THIS.
def processor(m):
        # Normalizes the coordinate system to be consistent with
        # image library conventions (top left as origin)
        if isinstance(m, LTComponent):
            m.set_bbox(normalize_bbox(m.bbox, height, scaler))

            if isinstance(m, LTCurve):
                m.pts = normalize_pts(m.pts, height, scaler)
                # Only keep longer lines here
                if isinstance(m, LTLine) and max(m.width, m.height) > pts_thres:
                    segments.append(m)
                    return
                # Here we exclude straight lines from curves
                curves.append(m)
                return

            if isinstance(m, LTFigure):
                if len(m) > 0: # ADD THIS
                    figures.append(m)
                    return

            # Collect stats on the chars
            if isinstance(m, LTChar):
                chars.append(m)
                # fonts could be rotated 90/270 degrees
                font_size = _font_size_of(m)
                font_size_counter[font_size] += 1
                return

            if isinstance(m, LTTextLine):
                mention_text = keep_allowed_chars(m.get_text()).strip()
                # Skip empty and invalid lines
                if mention_text:
                    # TODO: add subscript detection and use latex underscore
                    # or superscript
                    m.clean_text = mention_text
                    m.font_name, m.font_size = _font_of_mention(m)
                    mentions.append(m)
                return

Duplicate of #42, which was fixed by #49.


PI-8393 Changed the styling of lists and links inside of product desc…

…riptions. Increased click area of textlinks in description and loginpage. Fixed linespacing for title in loginpage.

Pull Request Test Coverage Report for Build 1102

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.624%

Totals

Change from base Build 1101:
0.0%

Covered Lines:
1787

Relevant Lines:
4030

💛  - Coveralls


Container ImagePullPolicy builds an incompatible type

Pre-bug-report checklist
1. This bug can be reproduced using pure Argo YAML

[ ] Yes 👉 Please report a bug to the Argo Workflows GitHub 👈
[X] No

If yes, it is more likely to be an Argo bug unrelated to Hera. Please double check before submitting an issue to Hera.
2. This bug occurs in Hera when...

[X] exporting to YAML
[ ] submitting to Argo
[ ] running on Argo with the Hera runner
[X] other: creating a workflow

Bug report
Describe the bug
When applying an image_pull_policy to a Container, the resulting attribute is not compatible with the pydantic model. The model expects a string, but the _build_image_pull_policy returns an enum type instead. The same function in the UserContainer model works correctly.
This seems to have been a bug since 5.5.0.
Error log if applicable:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/x/Library/Caches/pypoetry/virtualenvs/hera-bug-z6maGZWj-py3.11/lib/python3.11/site-packages/hera/workflows/workflow.py", line 369, in to_yaml
    return _yaml.dump(self.to_dict(), *args, **kwargs)
                      ^^^^^^^^^^^^^^
  File "/Users/xLibrary/Caches/pypoetry/virtualenvs/hera-bug-z6maGZWj-py3.11/lib/python3.11/site-packages/hera/workflows/workflow.py", line 353, in to_dict
    return self.build().dict(exclude_none=True, by_alias=True)
           ^^^^^^^^^^^^
  File "/Users/x/Library/Caches/pypoetry/virtualenvs/hera-bug-z6maGZWj-py3.11/lib/python3.11/site-packages/hera/workflows/workflow.py", line 349, in build
    return _WorkflowModelMapper.build_model(Workflow, self, model_workflow)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/x/Library/Caches/pypoetry/virtualenvs/hera-bug-z6maGZWj-py3.11/lib/python3.11/site-packages/hera/workflows/_mixins.py", line 1217, in build_model
    getattr(hera_obj, mapper.builder.__name__)()
  File "/Users/x/Library/Caches/pypoetry/virtualenvs/hera-bug-z6maGZWj-py3.11/lib/python3.11/site-packages/hera/workflows/workflow.py", line 131, in _build_templates
    templates.append(template._build_template())
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/xLibrary/Caches/pypoetry/virtualenvs/hera-bug-z6maGZWj-py3.11/lib/python3.11/site-packages/hera/workflows/container.py", line 80, in _build_template
    container=self._build_container(),
              ^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/x/Library/Caches/pypoetry/virtualenvs/hera-bug-z6maGZWj-py3.11/lib/python3.11/site-packages/hera/workflows/container.py", line 49, in _build_container
    return _ModelContainer(
           ^^^^^^^^^^^^^^^^
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for Container
imagePullPolicy
  str type expected (type=type_error.str)

To Reproduce
Full Hera code to reproduce the bug:
from hera.workflows import Workflow, Container, UserContainer
from hera.workflows.models import ImagePullPolicy

# Using the enum
with Workflow(name="my-workflow", namespace="argo") as w:
    Container(image_pull_policy=ImagePullPolicy.always)

w.to_yaml()
# !!error

# Using a string
with Workflow(name="my-workflow", namespace="argo") as w:
    Container(image_pull_policy="Always")

w.create()
# !!error

# Applying the ImagePullPolicy to a sidecar container instead:
with Workflow(name="my-workflow", namespace="argo") as w:
    Container(name="main",
        sidecars=UserContainer(name="sidecar", image="python:3", image_pull_policy=ImagePullPolicy.always)
    )

w.to_yaml()
# no error

Expected behavior
The workflow should be built successfully with the specified imagePullPolicy whether it was provided as an enum or a string as allowed by the Container class.
Environment

Hera Version: 5.10.1
Python Version: 3.11.6
Argo Version: NA

Looks related to #730 and #797, which should have been fixed by #798 cc @flaviuvadan

I don't think #798 fixed this for Container and I see a review comment from @flaviuvadan acknowledging there are different _build_image_pull_policy methods that have differing return values.


Example/sinabs

Added a quick example in the docs for sinabs - nir interaction

I've already done that here https://github.com/neuromorphs/NIR/tree/main/example/sinabs
I think such examples should only exist once and then be linked if necessary

see also https://github.com/neuromorphs/NIR/issues/26

@biphasic Yes I have seen this example and pretty much copy pasted it here. But this is not referenced in the documentation esp. in the structure that @Jegp has now added. What do you suggest we do for consistency?

easiest way is to push a symlink. But actually if we integrate the examples in the documentation, we might be able to delete the top level examples


Horizental rules invisible in exported PDF

investigating...

Here is a another interesting test:
Open this page: https://gist.github.com/tylerlong/556196d7a5dba488c138
Press Cmd - P to invoke print preview, You can see that the horizental rules are invisible too!
So this might be an universal issue which has something to do with the printing on Mac.

http://www.w3schools.com/tags/tag_hr.asp
In HTML5, the
 tag defines a thematic break.

In HTML 4.01, the
 tag represents a horizontal rule.

However, the
 tag may still be displayed as a horizontal rule in visual browsers, but is now defined in semantic terms, rather than presentational terms.

http://stackoverflow.com/questions/9140585/hr-not-seen-when-printing

Issue fixed. Please wait for the next release of our Mac app. :beer:


Args to set the max shard size in WriteToParquet

Following https://github.com/apache/beam/pull/22130 I added max_records_per_shard and max_bytes_per_shard to WriteToParquet
Ping @robertwb: let me know if it sounds good to you and I can add the appropriate tests :)

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

@johnjcasey could you weigh in on this one?

Are there any meaningful tests to be written here?

I can add a similar test that the one that was added in textio_test.py if it's good for you

Are there any meaningful tests to be written here?

I can add a similar test that the one that was added in textio_test.py if it's good for you

sounds good

No plans to merge this?

Feel free to re-open a PR with these changes (and possibly the missing test), I don't think I'll continue this PR


ChillPlayer sample doesn't compile on iOS

/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(3,3): Error:   Bundle Resource<EMAIL_ADDRESS>not found on disk (should be at<EMAIL_ADDRESS>(ChillPlayer.iOS)
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(3,3): Error:   Bundle Resource<EMAIL_ADDRESS>not found on disk (should be at<EMAIL_ADDRESS>(ChillPlayer.iOS)
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(3,3): Error:   Bundle Resource<EMAIL_ADDRESS>not found on disk (should be at<EMAIL_ADDRESS>(ChillPlayer.iOS)

Duplicate of #109 and will be tracked there.

This issue should be resolved now with the latest commit.


WORK IN PROGRESS - Fix preview - attempt 5

[x] Closes #45

@jbusecke the new trigger preview.yml doesn't seem to be triggered yet. But it should work once merged in the next PR. This is ready to be merged


Internal server error when location field not set

This is a follow up for https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/issues/760. The issue with logs being silently dropped has been resolved and has exposed the real issue I am encountering.
When sending a k8s_container metric to Cloud Monitoring, I get an "internal server error". It is resolved by setting cloud.availability_zone (or the region resource attribute).
With logging, I can get by without setting the location field. It seems that this should be the case with metrics as well. My cluster is not part of a cloud and has no reasonable region / zone value. This is also true for the GCP customers that we (observiq) support. They have on premise clusters.
This is the error text, formatted to be easily readable:
One or more TimeSeries could not be written: Internal error encountered.
Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs.:

k8s_container{
    container_name:coredns,
    location:,
    pod_name:coredns-787d4945fb-r9fk5,
    namespace_name:kube-system,
    cluster_name:stage
}

timeSeries[0]: workload.googleapis.com/core.log.count{
    k8s_pod_name:coredns-787d4945fb-r9fk5,
    k8s_node_name:minikube,
    k8s_cluster_name:stage,
    host_name:bindplane-gateway-agent-2,
    instrumentation_source:logcount,
    k8s_container_name:coredns,
    k8s_namespace_name:kube-system
}

error details: name = Unknown  desc = total_point_count:1 errors:{status:{code:13} point_count:1}

The error's metric descriptor does make it clear that the location field is unset.
This is the log from the collector (will the error value removed.
{
  "level":"error",
  "ts":"2023-12-20T16:41:34.815Z",
  "caller":"exporterhelper/queue_sender.go:123",
  "msg":"Exporting failed. No more retries left. Dropping data.",
  "kind":"exporter",
  "data_type":"metrics",
  "name":"googlecloud/jsirianni-12202023-temp",
  "error":"<see error>",
  "dropped_items":1,
  "stacktrace":"go.opentelemetry.io/collector/exporter/exporterhelper.(*queueSender).consume\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.91.0/exporterhelper/queue_sender.go:123\ngo.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue[...]).Consume\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.91.0/exporterhelper/internal/bounded_memory_queue.go:55\ngo.opentelemetry.io/collector/exporter/exporterhelper/internal.(*QueueConsumers[...]).Start.func1\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.91.0/exporterhelper/internal/consumers.go:43"
}

Exporter config:
googlecloud/jsirianni-12202023-temp:
    log:
        compression: gzip
        resource_filters:
            - regex: .*
    metric:
        compression: gzip
    project: jsirianni-12202023-temp
    sending_queue:
        enabled: true
        num_consumers: 10
        queue_size: 5000

I just encountered this with some generic node metrics as well, which is interesting because they were fine previously.
I was getting this error over and over again until I added the location resource attribute.
{"level":"error","ts":"2023-12-20T12:29:02.935-0500","caller":"exporterhelper/queue_sender.go:123","msg":"Exporting failed. No more retries left. Dropping data.","kind":"exporter","data_type":"metrics","name":"googlecloud/jsirianni-12202023-temp","error":"rpc error: code = Internal desc = Internal error encountered. Please retry after a few seconds. If internal errors persist, contact support at https://cloud.google.com/support/docs.","dropped_items":12,"stacktrace":"go.opentelemetry.io/collector/exporter/exporterhelper.(*queueSender).consume\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.91.0/exporterhelper/queue_sender.go:123\ngo.opentelemetry.io/collector/exporter/exporterhelper/internal.(*boundedMemoryQueue[...]).Consume\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.91.0/exporterhelper/internal/bounded_memory_queue.go:55\ngo.opentelemetry.io/collector/exporter/exporterhelper/internal.(*QueueConsumers[...]).Start.func1\n\t/home/runner/go/pkg/mod/go.opentelemetry.io/collector/exporter@v0.91.0/exporterhelper/internal/consumers.go:43"}

Are you explicitly setting cloud.availability_zone to ""?  We should be falling back to "global" if none is set: https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/main/internal/resourcemapping/resourcemapping.go#L155

This might be a regression

I don't think it is a regression, since I don't think the fallbacks in question have been changed.  But I do think it is best to fall back to global where it makes sense.  I opened https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/pull/795

Are you explicitly setting cloud.availability_zone to ""? We should be falling back to "global" if none is set: https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/blob/main/internal/resourcemapping/resourcemapping.go#L155

Sorry for the late reply, no we do not set cloud.availability_zone to "". If we do set it, we use a valid zone.
https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/pull/795 sounds good to me, I think that would be helpful.

The error message should be improved to actually indicate that the location is the problem.  That change should roll out in the next week or two.
But i've talked with some folks from cloud monitoring, and they don't think falling back to global is a good idea.  It isn't actually a global location, which is misleading, and can make users think the data is replicated globally, which it isn't.  It is strongly recommended that users pick a location that is at least reasonably close to them so it doesn't cause problems on the query side of things.
If you really want to use global, which I don't recommend, you can hard-code it using the resource processor:
processors:
  resource/defaultglobal:
    attributes:
    - key: cloud.availability_zone
      value: "global"
      action: upsert
    - key: cloud.region
      value: "global"
      action: upsert

Closing as won't fix.  Feel free to reopen if you have other questions.


About the code

Dear Authors,
Do you release all the code and dataset for training and evaluation?
Thanks

Dear @AmingWu ,
Yes, the code and the dataset are already available and the documentation will be added in June.
Specifically, the run.py script can be used for both training and evaluation using appropriate Hydra configs from the configs directory. The PPIRef repository contains the pre-training dataset and the SKEMPI v2.0 dataset used for fine-tuning and testing is available here.
Please let me know if you have any question before the documentation is available. I am aiming to add it as soon as possible, which was also blocked by the maintenance break of the infrastructure we used for the development.

Hi @AmingWu ! I have added examples of training and testing. Please let me know if you encounter any issues. I apologise for the delay.


November 15, 2018 AAD Update

Has this document taken the following issue into consideration?
https://social.msdn.microsoft.com/Forums/en-US/4192e141-309a-4dd6-a5c9-f1a8ce32f4ca/aadsts54005-oauth2-authorization-code-was-already-redeemed?forum=WindowsAzureAD
https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/whats-new#change-notice-authorization-codes-will-no-longer-be-available-for-reuse

Hi, @sweetlapeet -- I'm not sure how your comment ended up in the Power BI docs. I'm adding @eross-msft, one of the authors of  https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/whats-new#change-notice-authorization-codes-will-no-longer-be-available-for-reuse
Hope that helps. Thanks for your comment!

@sweetlapeet  I'm speaking with the product group about your question and will get back to you as soon as I can. With the holiday, there will be a bit of a lag. Thanks!!!

@sweetlapeet  For the best answer to your question, you should speak with @hpsin on the product group side. Again, with the holidays, responses might be delayed.

@maggiesMSFT this is a powerbi question as it is the power bi access token sample that I am referring to.
AAD had an update and it seems that pbi sample code on the doc has not been updated. Can you confirm?
Regards,
Aharon Najafi

On Nov 21, 2018, at 9:53 AM, Elizabeth Ross<EMAIL_ADDRESS>wrote:
@sweetlapeet For the best answer to your question, you should speak with @hpsin on the product group side. Again, with the holidays, responses might be delayed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ah, OK, thanks @sweetlapeet. In which article did you come across the Power BI access token sample? That info will help me direct your question to the right author.
thanks!

Closing this one out, but @sweetlapeet feel free to reopen if you have the Power BI doc you were referring to. CC @eross-msft, @maggiesMSFT


[cinder-csi-plugin] enable fs resize for any volume for Stage Volume Step

What this PR does / why we need it:
enable resize fs for all volumes.
Which issue this PR fixes(if applicable):
I'm in a scenario where the volume source is a block storage device, not a snapshot or another volume. We want to enable filesystem resizing to fully utilize the entire disk in this case.
Special notes for reviewers:

Release note:

NONE

/retest

I'm in a scenario where the volume source is a block storage device

the resize is required only when a volume has a FS, and such cases are possible only when a volume was created from a backup or a snapshot. Can you provide a step-by-step instructions on how to reproduce an issue, when a volume already has a FS and requires a resize?
And please sign an CLA.

I'm in a scenario where the volume source is a block storage device

the resize is required only when a volume has a FS, and such cases are possible only when a volume was created from a backup or a snapshot. Can you provide a step-by-step instructions on how to reproduce an issue, when a volume already has a FS and requires a resize?
And please sign an CLA.
P.S. The FS resize without the snapshot/backup conditions happens in the NodeExpandVolume method.

thanks for your reactivity @kayrus , Indeed creating a fresh fs from disk will get the disk size by default so no need to resize it. let me close this PR for the moment


Infer spec type on validate and generate commands, instead of using bruteforce by loading all of them as a chain of fallbacks

This PR changes how we load the specs on the validate and generate commands. Before this, we would try loading every type as a chain of spec loaders. Now we instead infer the spec type before loading them.

It should improve the performance because we don't try loading all the spec, just match some small precompiled regexes.
The errors are cleaner because now we know that when a spec loader fails, is because is not a valid, not because is not of the type trying to load.

Codecov Report

Merging #107 (b7e36c3) into main (6e6cc31) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #107      +/-   ##
==========================================
+ Coverage   80.53%   80.60%   +0.06%
==========================================
  Files          16       16
  Lines         894      897       +3
==========================================
+ Hits          720      723       +3
  Misses        122      122
  Partials       52       52

Impacted Files
Coverage Δ

internal/k8sprometheus/spec.go
93.42% <100.00%> (+0.08%)
:arrow_up:

internal/openslo/spec.go
90.47% <100.00%> (+0.15%)
:arrow_up:

internal/prometheus/spec.go
100.00% <100.00%> (ø)

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 6e6cc31...b7e36c3. Read the comment docs.


Waymo evaluation sequence

Hi! Thanks for this nice work.
Which sequences did you use for results reported in Table 2. Novel view synthesis of static scenes on Waymo?

Hi, sorry for the delay reply.  We use segment-14004546003548947884_2331_861_2351_861_with_camera_labels.tfrecord and  segment-16608525782988721413_100_000_120_000_with_camera_labels.tfrecord in Table 2, same as in S-NeRF.

thanks!


Diagrams usage highlights problems for MANY_SEP bug

The second usage in a repetition with separator will not be drawn with a yellow background
on hover.

nor will it trigger scrolling to it's definition.


Create customDropETH.sol

Instead of transferring specific amount of ETH to each recipient, the contract distributes ETH by weight, specified as an input to the dropETH function.
Rinkeby testing:
2 recipients - https://rinkeby.etherscan.io/tx/0x2a37c0d555383a9abda2eeef091aa291558d9858c156cbaccc0397b0ba147fa7
4 recipients - https://rinkeby.etherscan.io/tx/0x3acff2bd00eb5afead11c0f166aa640ef238537e47d089186dcdfcc75b8d8406

nice work! will take a swing through tmrw

lol, sorry for delays. Merged!


update for lspsaga

Version confirmation

[X] Confirm

Neovim version
NVIM v0.8.2
Operating system/version
Archlinux, wsl2
Terminal name/version
wezterm
$TERM environment variable
tmux-256color
Branch info
main (Default/Latest)
Fetch Preferences
SSH (use_ssh = true)
How to reproduce the issue
Lspsaga introduced breaking change at https://github.com/glepnir/lspsaga.nvim/commit/afbd5718ffd453662ada49e9c520df60efc8f444
So tons of current configs are invalid for its new version.
Expected behavior

[ ] config.lspsaga need to be refactor following its readme.
[ ] config.lualine need to be refactor following its readme.
[x] Lspsaga outline don't provide toggle feature, so need to implement it by ourselves.

Actual behavior
No response
Additional information
No response

Finally!

https://github.com/glepnir/lspsaga.nvim/commit/dfa4eee7f6eefff74038df416d911c21940f87fd

Will refactor associated code.

https://github.com/ayamir/nvimdots/pull/418
Updated, need more tests.


How to retrieve probability values

Hi everyone,
I was wondering if there is a way to extract the probability value associated with a predicted token when we compute the MRR metric. In other words, let's consider the following prediction:
static1.000000	clockid_t0.000000
I want to get for the 'static' token(where the MRR is 1) the probability or the confidence level --so to speak-- of the model.
Any ideas?
Thank you all in advance :)

Hi!
It sounds like you're looking for the entropy, which is itself just a simple transformation of probability, associated with each token. That's easy enough if you've already got the predict mode set up, as you seem to. Assuming you're doing this from the command-line (where you use the --verbose option to write to file), you'd simply change the run mode from train-predict to train-model (or both without train- if applicable).
If you're using the programmatic interface, the change is much the same; once the model is trained, just call the ModelRunner's modelX methods instead of the predictX ones.
Hope this helps!
-Vincent


Question about how to modify the code to support multi-GPU training?

I encountered an issue while attempting to modify your code to support multi-GPU training and I'm seeking your assistance. Initially, I tried using DP for distributed training, but during execution, I encountered the error 'return torch._C._gather(tensors, dim, destination) RuntimeError: Input tensor at index 1 has invalid shape [8, 23, 256], but expected [8, 36, 256]'. After debug, I found that the issue arises from text encoding due to varying sequence lengths. However, after resolving this issue the forward pass seems to work fine, the code gets stuck during the backward pass (self._running_log["loss"].backward() )without any error messages. I'm unsure how to address this. If possible, could you please provide code for multi-GPU training? Thank you!"

I have solved this problem.


vagrant trigger failing?

Any ideas?
kubernetes-vagrant-coreos-cluster jsindy$ vagrant up
Installing the 'vagrant-triggers' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
An error occurred while installing nokogiri (<IP_ADDRESS>), and Bundler cannot continue.
Make sure that gem install nokogiri -v '<IP_ADDRESS>' succeeds before bundling.

Fixed environment with brew update; brew upgrade on OSX and reinstall of vagrant.


Transaction amount field in BTC does not accept decimal values

sparrow_1.7.3-1_amd64.deb
When sending a transaction and selecting BTC as the amount unit, the amount field does not accept decimal value.
If I try to type 0.1 it's converted to 1.
This bug was not present in previous releases.
At the moment, I'm forced to use sats.

My mistake. I didn't realize that by changing the fiat display format also change the bitcoin amount format. I should have used a comma instead of the dot.


add test for flash store

Set the same key more than one time, and then get the size, the size not equal 1.

related issue: https://github.com/huan/flash-store/issues/50


'notifier.url' always set even when 'notifier.blackhole' is set to true

Hello,
'notifier.url' parameter is not longer needed by default in Victoria Metrics.
When we would like to disable, we need to set the notifier.blackhole parameter to true. Since Victoria Metrics 1.96, when this parameter is set, we cannot set notifier.url parameter in the same time (source)
However, in the server-deployment template of the victoria-metric-alerts chart, the notifier-url is always set whatever the extra arguments.
How to reproduce it? Deploy VM alert with notifier.blackhole extraArgs set to true.
Fix suggestion: I suggest to add a condition to set the notifier.url parameter when there is no -notifier.blackhole or -notifier.config extra arguments.

All is good for me! Great job! Thank you very much 😄 🥳


Support 256 color display

Prerequisites
affected version: 0.28.2
make sure to check this before filing an issue:

[x] I am running the latest version
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed

Expected Behavior
ANSI color sequences are displayed as in a terminal
Current Behavior
Only the 8 Colors are supported in the displays.
Steps to Reproduce
Print something that outputs more than 8 colors. e.g. rogcat. Some other bug prevents rogcat from being run so please do this workaround: rogcat --color always > /tmp/rogcat and run tail -f /tmp/rogcat in logviewer.
Context

Operating System: macos


Bug: Balances persists when transactions are deleted

I have an issue here with my group. I have added some transactions in a group before that led me to a balance, then deleted the all the group  transactions hoping for the balance to be zero. Nope it did not despite having empty transactions in the group. I can't delete the group as well because i have to "settle balances" first before i can delete.

yes this is an issue with group expense calculation but it won't actually affect the balance between your friends, if you go to balances page it should be calculated correctly.
this is a problem with group where i don't know which balance get canceled and i recalculate those only on settle up events for hroups.
may be i can handle this for delete event. that being said you don't have to worry about this. once you settle up a payment this will be reset for the group!

I cant really reproduce this bug? Even how many times I have tried to add and remove expenses with multiple people in a group I cant seem to reproduce the issue?

Hmm, if i remember correctly, i added expenses in the group, then i deleted
the transactions in the Activity tab
On Sun, 27 Oct 2024, 7:15 pm Alexander Wassbjer, @.***>
wrote:

I cant really reproduce this bug? Even how many times I have tried to add
and remove expenses with multiple people in a group I cant seem to
reproduce the issue?
—
Reply to this email directly, view it on GitHub
https://github.com/oss-apps/split-pro/issues/130#issuecomment-2439971848,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKNFSGWPFWXQGVKTGM6HVTZ5S4NRAVCNFSM6AAAAABQQHONZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZHE3TCOBUHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@ptsimon Thanks
@KMKoushik I saw that when clicking in the activity tab on an expense its always redirecting to /expenses/id.
If it would redirect to /groups/id/expenses/id in group expense type and /expenses/id on friend expense type, and the delete would be from that page group expense page instead I think it would work with the calculation, or? 😃


Pilot EDS, ADS, CDS not updated when remote cluster removed

Describe the bug
In a multicluster scenario when a secret is deleted EDS and ADS is not updated properly.
The logs show that the cluster is properly deleted:
2018-09-07T12:41:01.190718Z     info    Deleting cluster member: ds82.conf
2018-09-07T12:41:01.190752Z     info    Registry for the cluster ds82.conf has been deleted.
2018-09-07T12:41:01.190797Z     info    Number of clusters in the cluster store: 0
But when curling debug/cdsz, debug/edsz or debug/adsz the endpoints and services for the remote cluster are still shown
Expected behavior
When a remote cluster is removed from the cluster registry the associated services and endpoints from that cluster should also be deleted.
Steps to reproduce the bug
Deploy a multicluster scenario.  Deploy services and endpoints on the remote.   Then delete the remote cluster.  Check that the cds, eds, and ads in pilot to check for full removal of remote cluster resources.
Version
This was confirmed on master from Sept 4th, 2018.
kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:13:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.7", GitCommit:"0c38c362511b20a098d7cd855f1314dad92c2780", GitTreeState:"clean", BuildDate:"2018-08-20T09:56:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
root@bxb-ds-84:~# go/out/linux_amd64/release/istioctl version
Version: 4e5e14668a62e0b1a3c2d1d6fc763d14fa7ad4e1
GitRevision: 4e5e14668a62e0b1a3c2d1d6fc763d14fa7ad4e1
User: root@bxb-ds-84
Hub: docker.io/istio
GolangVersion: go1.10
BuildStatus: Clean
Is Istio Auth enabled or not?
No pertinent to this issue
Environment
Developer baremetal single node cluster.
Cluster state
{{ If you're running on Kubernetes, consider following the
instructions
to generate "istio-dump.tar.gz", then attach it here by dragging and dropping
the file onto this issue. }}

That's really not acceptable. Let me have a look.


Use systeminformation package to get memory data

This resolves #19 and shows real available memory on Linux.

Changed so systeminformation  is used only by Linux in bbf7679295df0a5af6a527d0e8dd3bb3551afc1d.
And caching memory data for 30 seconds in e23f58d99e45ba802d0569142683d20f8e0cf193.

Made systeminformation be used only on Linux and added 30 seconds cache for host status data.