prometheus readiness probe keeps on failing

What did you do?
i did deployment of prometheus 2.27.1 .
What did you expect to see?
prometheus server up and running .
What did you see instead? Under which circumstances?
prometheus  container keep on restaring with readiness probe failures .
  Warning  Unhealthy  5s (x63 over 9m50s)  kubelet            Readiness probe failed: HTTP probe failed with statuscode: 503

prometheus-prometheus-operator-kube-p-prometheus-1       1/2     Running   3          12m

the readiness is configured like this
    Readiness:  http-get http://:web/-/ready delay=100s timeout=3s period=5s #success=1 #failure=1000

-> other configurations tried

keep original settings
increase timeout

Prometheus version:

2.27.1

Logs:

 Normal   Pulling    11m (x2 over 11m)    kubelet            Pulling image "quay.io/prometheus/prometheus:v2.27.1"
  Normal   Created    11m (x2 over 11m)    kubelet            Created container prometheus
  Normal   Started    11m (x2 over 11m)    kubelet            Started container prometheus
  Normal   Pulled     11m (x2 over 11m)    kubelet            Successfully pulled image "quay.io/prometheus/prometheus:v2.27.1"
  Warning  Unhealthy  5s (x63 over 9m50s)  kubelet            Readiness probe failed: HTTP probe failed with statuscode: 503

The /-/ready endpoint returns a 503 when the TSDB hasn't finished starting, in which the loading of the WAL is usually what takes the longest. If the instance is ingesting lots of samples, this can take a while. It's possible that there's an actual issue with Prometheus, but I suspect that it's just normal latency.
If you could please provide logs from the container that would help us determine what's going on.

@LeviHarrison thanks. unfortunately I lost the data as this was happening for a extended period and I had to clear pvcs's to get the system up and running as we are using metrics for our metering calculation.  Ideally , the container should not restart in this process.  it does not make sense to do a readiness check immediately  when we know for a fact that starting TSDB will take longer time .  I did try setting the initialDelaySeconds to 200seconds in one of the configuration but that does not seem to help either.

Can you provide the logs from the container? Thanks.

@roidelapluie I see the container is restarting again and again today as well.
prometheus-prometheus-operator-kube-p-prometheus-1       1/2     Running   2          26m

before starting I keep on seeing readiness probe failed with 503 errors . now I can understand that when there is start then the pod oscillates for some time and starts properly when the WAL is loaded . but this keeps on happening after again after 25 minutes which I don't understand .
prometheus-prometheus-operator-kube-p-prometheus-1       2/2     Running   2          32m
and weirdly I have too pods and the second one is quite stable since last 4 hours but other one keep on restarting and I see readiness probe issues all the time  :
prometheus-prometheus-operator-kube-p-prometheus-0       2/2     Running   1          3h56m
after starting  we get the proper  logs :
level=info ts=2021-08-10T12:22:36.421Z caller=main.go:426 msg="Starting Prometheus" version="(version=2.27.1, branch=HEAD, revision=db7f0bcec27bd8aeebad6b08ac849516efa9ae02)"
level=info ts=2021-08-10T12:22:36.423Z caller=main.go:431 build_context="(go=go1.16.4, user=root@fd804fbd4f25, date=20210518-14:17:54)"
level=info ts=2021-08-10T12:22:36.423Z caller=main.go:432 host_details="(Linux 5.4.0-5-cloud-amd64 #1 SMP Debian 5.4.68-1 (2020-09-28) x86_64 prometheus-prometheus-operator-kube-p-prometheus-1 (none))"
level=info ts=2021-08-10T12:22:36.423Z caller=main.go:433 fd_limits="(soft=1048576, hard=1048576)"
level=info ts=2021-08-10T12:22:36.423Z caller=main.go:434 vm_limits="(soft=unlimited, hard=unlimited)"
level=info ts=2021-08-10T12:22:36.428Z caller=query_logger.go:79 component=activeQueryTracker msg="These queries didn't finish in prometheus' last run:" queries="[{\"query\":\"rate(kube_pod_container_status_restarts_total{job=\\\"kube-state-metrics\\\",namespace=~\\\".*\\\"}[10m]) * 60 * 5 \\u003e 0\",\"timestamp_sec\":1628597764}]"
level=info ts=2021-08-10T12:22:36.432Z caller=web.go:540 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090
level=info ts=2021-08-10T12:22:36.433Z caller=main.go:803 msg="Starting TSDB ..."
level=info ts=2021-08-10T12:22:36.435Z caller=tls_config.go:191 component=web msg="TLS is disabled." http2=false
level=info ts=2021-08-10T12:22:36.454Z caller=repair.go:57 component=tsdb msg="Found healthy block" mint=1628517996246 maxt=1628524800000 ulid=01FCNY2RNMWBVDT7XCNES3DW7X
level=info ts=2021-08-10T12:22:36.462Z caller=repair.go:57 component=tsdb msg="Found healthy block" mint=1628524800000 maxt=1628532000000 ulid=01FCP4JCX51RM7ZJAF2VRQSVX7
level=info ts=2021-08-10T12:22:36.470Z caller=repair.go:57 component=tsdb msg="Found healthy block" mint=1628532000000 maxt=1628539200000 ulid=01FCPBE455EG3K22FXNH6C9PEY
level=info ts=2021-08-10T12:22:36.474Z caller=repair.go:57 component=tsdb msg="Found healthy block" mint=1628539200000 maxt=1628546400000 ulid=01FCPJ9VM0QMTK1APFC0GR4299
level=info ts=2021-08-10T12:22:36.533Z caller=db.go:728 component=tsdb msg="Found and deleted tmp block dir" dir=/prometheus/01FCQZRG5SD0RY2M3BJCG2CRMH.tmp-for-creation
level=info ts=2021-08-10T12:22:37.340Z caller=head.go:741 component=tsdb msg="Replaying on-disk memory mappable chunks if any"
level=info ts=2021-08-10T12:23:07.181Z caller=head.go:755 component=tsdb msg="On-disk memory mappable chunks replay completed" duration=29.840739587s
level=info ts=2021-08-10T12:23:07.181Z caller=head.go:761 component=tsdb msg="Replaying WAL, this may take a while"
level=info ts=2021-08-10T12:23:31.128Z caller=head.go:787 component=tsdb msg="WAL checkpoint loaded"
level=info ts=2021-08-10T12:23:35.116Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=81 maxSegment=205
level=info ts=2021-08-10T12:23:41.825Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=82 maxSegment=205
level=info ts=2021-08-10T12:23:44.121Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=83 maxSegment=205
level=info ts=2021-08-10T12:23:46.391Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=84 maxSegment=205
level=info ts=2021-08-10T12:23:48.831Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=85 maxSegment=205
level=info ts=2021-08-10T12:23:51.400Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=86 maxSegment=205
level=info ts=2021-08-10T12:23:54.356Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=87 maxSegment=205
level=info ts=2021-08-10T12:23:56.742Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=88 maxSegment=205
level=info ts=2021-08-10T12:23:59.159Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=89 maxSegment=205
level=info ts=2021-08-10T12:24:08.048Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=90 maxSegment=205
level=info ts=2021-08-10T12:24:10.270Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=91 maxSegment=205
level=info ts=2021-08-10T12:24:12.633Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=92 maxSegment=205
level=info ts=2021-08-10T12:24:15.208Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=93 maxSegment=205
level=info ts=2021-08-10T12:24:15.540Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=94 maxSegment=205
level=info ts=2021-08-10T12:24:18.078Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=95 maxSegment=205
level=info ts=2021-08-10T12:24:20.549Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=96 maxSegment=205
level=info ts=2021-08-10T12:24:22.821Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=97 maxSegment=205
level=info ts=2021-08-10T12:24:25.075Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=98 maxSegment=205
level=info ts=2021-08-10T12:24:27.401Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=99 maxSegment=205
level=info ts=2021-08-10T12:24:29.791Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=100 maxSegment=205
level=info ts=2021-08-10T12:24:38.903Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=101 maxSegment=205
level=info ts=2021-08-10T12:24:41.238Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=102 maxSegment=205
level=info ts=2021-08-10T12:24:43.563Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=103 maxSegment=205
level=info ts=2021-08-10T12:24:45.806Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=104 maxSegment=205
level=info ts=2021-08-10T12:24:48.009Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=105 maxSegment=205
level=info ts=2021-08-10T12:24:50.251Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=106 maxSegment=205
level=info ts=2021-08-10T12:24:54.046Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=107 maxSegment=205
level=info ts=2021-08-10T12:24:58.033Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=108 maxSegment=205
level=info ts=2021-08-10T12:25:02.037Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=109 maxSegment=205
level=info ts=2021-08-10T12:25:13.303Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=110 maxSegment=205
level=info ts=2021-08-10T12:25:17.311Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=111 maxSegment=205
level=info ts=2021-08-10T12:25:21.306Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=112 maxSegment=205
level=info ts=2021-08-10T12:25:25.320Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=113 maxSegment=205
level=info ts=2021-08-10T12:25:29.423Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=114 maxSegment=205
level=info ts=2021-08-10T12:25:33.604Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=115 maxSegment=205
level=info ts=2021-08-10T12:25:37.624Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=116 maxSegment=205
level=info ts=2021-08-10T12:25:41.653Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=117 maxSegment=205
level=info ts=2021-08-10T12:25:53.464Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=118 maxSegment=205
level=info ts=2021-08-10T12:25:57.721Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=119 maxSegment=205
level=info ts=2021-08-10T12:26:01.813Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=120 maxSegment=205
level=info ts=2021-08-10T12:26:03.130Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=121 maxSegment=205
level=info ts=2021-08-10T12:26:04.813Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=122 maxSegment=205
level=info ts=2021-08-10T12:26:06.338Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=123 maxSegment=205
level=info ts=2021-08-10T12:26:08.567Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=124 maxSegment=205
level=info ts=2021-08-10T12:26:10.929Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=125 maxSegment=205
level=info ts=2021-08-10T12:26:13.034Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=126 maxSegment=205
level=info ts=2021-08-10T12:26:15.204Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=127 maxSegment=205
level=info ts=2021-08-10T12:26:18.020Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=128 maxSegment=205
level=info ts=2021-08-10T12:26:27.430Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=129 maxSegment=205
level=info ts=2021-08-10T12:26:30.237Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=130 maxSegment=205
level=info ts=2021-08-10T12:26:32.347Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=131 maxSegment=205
level=info ts=2021-08-10T12:26:34.761Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=132 maxSegment=205
level=info ts=2021-08-10T12:26:36.339Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=133 maxSegment=205
level=info ts=2021-08-10T12:26:38.819Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=134 maxSegment=205
level=info ts=2021-08-10T12:26:41.446Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=135 maxSegment=205
level=info ts=2021-08-10T12:26:43.226Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=136 maxSegment=205
level=info ts=2021-08-10T12:26:44.834Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=137 maxSegment=205
level=info ts=2021-08-10T12:26:46.612Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=138 maxSegment=205
level=info ts=2021-08-10T12:26:48.008Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=139 maxSegment=205
level=info ts=2021-08-10T12:26:50.061Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=140 maxSegment=205
level=info ts=2021-08-10T12:26:59.943Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=141 maxSegment=205
level=info ts=2021-08-10T12:27:01.732Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=142 maxSegment=205
level=info ts=2021-08-10T12:27:03.430Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=143 maxSegment=205
level=info ts=2021-08-10T12:27:05.526Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=144 maxSegment=205
level=info ts=2021-08-10T12:27:07.317Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=145 maxSegment=205
level=info ts=2021-08-10T12:27:08.898Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=146 maxSegment=205
level=info ts=2021-08-10T12:27:10.330Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=147 maxSegment=205
level=info ts=2021-08-10T12:27:12.915Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=148 maxSegment=205
level=info ts=2021-08-10T12:27:14.526Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=149 maxSegment=205
level=info ts=2021-08-10T12:27:16.927Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=150 maxSegment=205
level=info ts=2021-08-10T12:27:18.372Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=151 maxSegment=205
level=info ts=2021-08-10T12:27:19.731Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=152 maxSegment=205
level=info ts=2021-08-10T12:27:21.261Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=153 maxSegment=205
level=info ts=2021-08-10T12:27:23.258Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=154 maxSegment=205
level=info ts=2021-08-10T12:27:31.016Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=155 maxSegment=205
level=info ts=2021-08-10T12:27:35.155Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=156 maxSegment=205
level=info ts=2021-08-10T12:27:36.648Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=157 maxSegment=205
level=info ts=2021-08-10T12:27:38.305Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=158 maxSegment=205
level=info ts=2021-08-10T12:27:40.006Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=159 maxSegment=205
level=info ts=2021-08-10T12:27:41.805Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=160 maxSegment=205
level=info ts=2021-08-10T12:27:43.503Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=161 maxSegment=205
level=info ts=2021-08-10T12:27:44.946Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=162 maxSegment=205
level=info ts=2021-08-10T12:27:46.898Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=163 maxSegment=205
level=info ts=2021-08-10T12:27:48.507Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=164 maxSegment=205
level=info ts=2021-08-10T12:27:50.041Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=165 maxSegment=205
level=info ts=2021-08-10T12:27:51.608Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=166 maxSegment=205
level=info ts=2021-08-10T12:27:52.897Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=167 maxSegment=205
level=info ts=2021-08-10T12:27:54.748Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=168 maxSegment=205
level=info ts=2021-08-10T12:27:56.522Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=169 maxSegment=205
level=info ts=2021-08-10T12:27:58.014Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=170 maxSegment=205
level=info ts=2021-08-10T12:28:05.518Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=171 maxSegment=205
level=info ts=2021-08-10T12:28:09.157Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=172 maxSegment=205
level=info ts=2021-08-10T12:28:10.597Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=173 maxSegment=205
level=info ts=2021-08-10T12:28:12.333Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=174 maxSegment=205
level=info ts=2021-08-10T12:28:13.948Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=175 maxSegment=205
level=info ts=2021-08-10T12:28:15.349Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=176 maxSegment=205
level=info ts=2021-08-10T12:28:16.949Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=177 maxSegment=205
level=info ts=2021-08-10T12:28:18.400Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=178 maxSegment=205
level=info ts=2021-08-10T12:28:19.622Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=179 maxSegment=205
level=info ts=2021-08-10T12:28:20.909Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=180 maxSegment=205
level=info ts=2021-08-10T12:28:22.137Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=181 maxSegment=205
level=info ts=2021-08-10T12:28:23.501Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=182 maxSegment=205
level=info ts=2021-08-10T12:28:25.104Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=183 maxSegment=205
level=info ts=2021-08-10T12:28:26.914Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=184 maxSegment=205
level=info ts=2021-08-10T12:28:28.157Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=185 maxSegment=205
level=info ts=2021-08-10T12:28:29.731Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=186 maxSegment=205
level=info ts=2021-08-10T12:28:32.909Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=187 maxSegment=205
level=info ts=2021-08-10T12:28:32.909Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=188 maxSegment=205
level=info ts=2021-08-10T12:28:40.801Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=189 maxSegment=205
level=info ts=2021-08-10T12:28:40.802Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=190 maxSegment=205
level=info ts=2021-08-10T12:28:40.802Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=191 maxSegment=205
level=info ts=2021-08-10T12:28:44.953Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=192 maxSegment=205
level=info ts=2021-08-10T12:28:46.650Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=193 maxSegment=205
level=info ts=2021-08-10T12:28:48.497Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=194 maxSegment=205
level=info ts=2021-08-10T12:28:50.329Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=195 maxSegment=205
level=info ts=2021-08-10T12:28:52.188Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=196 maxSegment=205
level=info ts=2021-08-10T12:28:53.873Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=197 maxSegment=205
level=info ts=2021-08-10T12:28:55.326Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=198 maxSegment=205
level=info ts=2021-08-10T12:28:57.048Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=199 maxSegment=205
level=info ts=2021-08-10T12:28:58.608Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=200 maxSegment=205
level=info ts=2021-08-10T12:28:59.643Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=201 maxSegment=205
level=info ts=2021-08-10T12:29:01.300Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=202 maxSegment=205
level=info ts=2021-08-10T12:29:02.926Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=203 maxSegment=205
level=info ts=2021-08-10T12:29:05.033Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=204 maxSegment=205
level=info ts=2021-08-10T12:29:05.033Z caller=head.go:813 component=tsdb msg="WAL segment loaded" segment=205 maxSegment=205
level=info ts=2021-08-10T12:29:05.033Z caller=head.go:818 component=tsdb msg="WAL replay completed" checkpoint_replay_duration=23.947133058s wal_replay_duration=5m33.905023689s total_replay_duration=6m27.692952367s
level=info ts=2021-08-10T12:29:15.151Z caller=main.go:828 fs_type=EXT4_SUPER_MAGIC
level=info ts=2021-08-10T12:29:15.151Z caller=main.go:831 msg="TSDB started"
level=info ts=2021-08-10T12:29:15.151Z caller=main.go:957 msg="Loading configuration file" filename=/etc/prometheus/config_out/prometheus.env.yaml
level=info ts=2021-08-10T12:29:15.160Z caller=kubernetes.go:266 component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config"
level=info ts=2021-08-10T12:29:15.181Z caller=kubernetes.go:266 component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config"
level=info ts=2021-08-10T12:29:15.183Z caller=kubernetes.go:266 component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config"
level=info ts=2021-08-10T12:29:15.183Z caller=kubernetes.go:266 component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config"
level=info ts=2021-08-10T12:29:15.184Z caller=kubernetes.go:266 component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config"
level=info ts=2021-08-10T12:29:15.185Z caller=kubernetes.go:266 component="discovery manager scrape" discovery=kubernetes msg="Using pod service account via in-cluster config"
level=info ts=2021-08-10T12:29:15.186Z caller=kubernetes.go:266 component="discovery manager notify" discovery=kubernetes msg="Using pod service account via in-cluster config"
level=info ts=2021-08-10T12:29:15.231Z caller=main.go:988 msg="Completed loading of configuration file" filename=/etc/prometheus/config_out/prometheus.env.yaml totalDuration=80.574555ms remote_storage=2.885µs web_handler=664ns query_engine=1.758µs scrape=2.984231ms scrape_sd=26.277185ms notify=19.794µs notify_sd=718.008µs rules=44.302812ms
level=info ts=2021-08-10T12:29:15.231Z caller=main.go:775 msg="Server is ready to receive web requests."

level=info ts=2021-08-10T12:29:15.231Z caller=main.go:775 msg="Server is ready to receive web requests."
After this log line, prometheus should never serve a 503.

Yes indeed . but again after some time it happens and the container restarts  . as you can see at 26m and 35m

So there must be something that's causing the instance to restart because there's literally no logic go back to the 503. It's impossible.
Do you have logs around the time the endpoint supposedly starts to return 503 again?

level=info ts=2021-08-10T13:11:31.916Z caller=main.go:426 msg="Starting Prometheus" version="(version=2.27.1, branch=HEAD, revision=db7f0bcec27bd8aeebad6b08ac849516efa9ae02)"
level=info ts=2021-08-10T13:11:31.917Z caller=main.go:431 build_context="(go=go1.16.4, user=root@fd804fbd4f25, date=20210518-14:17:54)"
level=info ts=2021-08-10T13:11:31.917Z caller=main.go:432 host_details="(Linux 5.4.0-5-cloud-amd64 #1 SMP Debian 5.4.68-1 (2020-09-28) x86_64 prometheus-prometheus-operator-kube-p-prometheus-1 (none))"
level=info ts=2021-08-10T13:11:31.917Z caller=main.go:433 fd_limits="(soft=1048576, hard=1048576)"
level=info ts=2021-08-10T13:11:31.917Z caller=main.go:434 vm_limits="(soft=unlimited, hard=unlimited)"
level=info ts=2021-08-10T13:11:31.923Z caller=query_logger.go:79 component=activeQueryTracker msg="These queries didn't finish in prometheus' last run:" queries="[{\"query\":\"histogram_quantile(0.99, sum without(instance, pod) (rate(apiserver_request_duration_seconds_bucket{job=\\\"apiserver\\\",subresource!=\\\"log\\\",verb!~\\\"LIST|WATCH|WATCHLIST|DELETECOLLECTION|PROXY|CONNECT\\\"}[5m])))\",\"timestamp_sec\":1628600946}]"
level=info ts=2021-08-10T13:11:31.927Z caller=web.go:540 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090
level=info ts=2021-08-10T13:11:31.927Z caller=main.go:803 msg="Starting TSDB ..."
level=info ts=2021-08-10T13:11:31.929Z caller=tls_config.go:191 component=web msg="TLS is disabled." http2=false
level=info ts=2021-08-10T13:11:31.931Z caller=repair.go:57 component=tsdb msg="Found healthy block" mint=1628517996246 maxt=1628524800000 ulid=01FCNY2RNMWBVDT7XCNES3DW7X
level=info ts=2021-08-10T13:11:31.932Z caller=repair.go:57 component=tsdb msg="Found healthy block" mint=1628524800000 maxt=1628532000000 ulid=01FCP4JCX51RM7ZJAF2VRQSVX7
level=info ts=2021-08-10T13:11:31.933Z caller=repair.go:57 component=tsdb msg="Found healthy block" mint=1628532000000 maxt=1628539200000 ulid=01FCPBE455EG3K22FXNH6C9PEY
level=info ts=2021-08-10T13:11:31.935Z caller=repair.go:57 component=tsdb msg="Found healthy block" mint=1628539200000 maxt=1628546400000 ulid=01FCPJ9VM0QMTK1APFC0GR4299
level=info ts=2021-08-10T13:11:31.942Z caller=db.go:728 component=tsdb msg="Found and deleted tmp block dir" dir=/prometheus/01FCR2SC90F8133B84D5VTFPAJ.tmp-for-creation
level=info ts=2021-08-10T13:11:32.620Z caller=head.go:741 component=tsdb msg="Replaying on-disk memory mappable chunks if any"

I will wait for it to happen again and then see the logs and attach here

Yes, a query is causing using up too much memory, causing the pod to crash due to OOM.
I think it might be:
histogram_quantile(0.99, sum without(instance, pod) (rate(apiserver_request_duration_seconds_bucket{job=\\\"apiserver\\\",subresource!=\\\"log\\\",verb!~\\\"LIST|WATCH|WATCHLIST|DELETECOLLECTION|PROXY|CONNECT\\\"}[5m])))\"

which we saw in the startup logs.

@LeviHarrison i observed a bit closer that during restarts always some queries fail and i think you are right . for example again this happened :
level=info ts=2021-08-24T13:56:57.126Z caller=query_logger.go:79 component=activeQueryTracker msg="These queries didn't finish in prometheus' last run:" queries="[{\"query\":\"sum without(cpu, mode) (rate(node_cpu_seconds_total{mode!=\\\"idle\\\",mode!=\\\"iowait\\\",mode!=\\\"steal\\\"}[5m])) / on(instance) group_left() count by(instance) (sum by(instance, cpu) (node_cpu_seconds_total))\",\"timestamp_sec\":1629813411},{\"query\":\"container_memory_rss{image!=\\\"\\\",job=\\\"kubelet\\\",metrics_path=\\\"/metrics/cadvisor\\\"} * on(namespace, pod) group_left(node) topk by(namespace, pod) (1, max by(namespace, pod, node) (kube_pod_info{node!=\\\"\\\"}))\",\"timestamp_sec\":1629813405},{\"query\":\"((sum(rate(apiserver_request_duration_seconds_count{job=\\\"apiserver\\\",verb=~\\\"LIST|GET\\\"}[1d])) - ((sum(rate(apiserver_request_duration_seconds_bucket{job=\\\"apiserver\\\",le=\\\"0.1\\\",scope=~\\\"resource|\\\",verb=~\\\"LIST|GET\\\"}[1d])) or vector(0)) + sum(rate(apiserver_request_duration_seconds_bucket{job=\\\"apiserver\\\",le=\\\"0.5\\\",scope=\\\"namespace\\\",verb=~\\\"LIST|GET\\\"}[1d])) + sum(rate(apiserver_request_duration_seconds_bucket{job=\\\"apiserver\\\",le=\\\"5\\\",scope=\\\"cluster\\\",verb=~\\\"LIST|GET\\\"}[1d])))) + sum(rate(apiserver_request_total{code=~\\\"5..\\\",job=\\\"apiserver\\\",verb=~\\\"LIST|GET\\\"}[1d]))) / sum(rate(apiserver_request_total{job=\\\"apiserver\\\",verb=~\\\"LIST|GET\\\"}[1d]))\",\"timestamp_sec\":1629813409}]"
level=info ts=2021-08-24T13:56:57.127Z caller=web.go:540 component=web msg="Start listening for connections" address=<IP_ADDRESS>:9090

now when i look at the blogpost by @brian-brazil :
https://www.robustperception.io/what-queries-were-running-when-prometheus-died
then i get to know that indeed this can happen . apologies for assuming that a query cant bring  pod down,  earlier.
As per this blog post :
https://giedrius.blog/2019/01/13/choosing-maximum-concurrent-queries-in-prometheus-smartly/ ,  these flags the controls the concurrent requests  :
–storage.remote.read-concurrent-limit=10
–query.max-concurrency=20

The number should be picked such that it does not exceed the number of threads of execution on your (virtual) machine. Ideally, it should be a bit lower because if your machine will encounter huge queries, it is (probably) going to also use the CPU for other operations such as sending the packets over a network.

is this flag still applicable  and assumption  with respect to concurrent requests  are still valid  ? .

Yes, the flags should still be applicable.

@navneet1075 you are suggested to give more disk space to Prometheus for it to function normally and recover from this disk space pile up.


feat: Added support for ephemeral storage (requires AWS provider version 4.8.0)

Description
Add support for configuring ephemeral storage size (/tmp file system) for lambda.
The changes include:

Upgrade AWS provider version to 4.8.0, which introduces support for the ephemeral storage size configuration feature.
Add a variable called ephemeral_storage_size and use this value in the main.tf.
Replace deprecated resource aws_s3_bucket_object to aws_s3_object.
Add an example for using the ephemeral_storage_size configuration.

Motivation and Context
The ephemeral storage configuration is a new feature in AWS lambda. I would like to be able to use this feature via Terraform.
Fixes #290
Breaking Changes

The Terffaform AWS provider version must be upgraded from >=3.6.9 to >=4.8.0.
This upgrade is required as the ephemeral_storage configuration is added in version 4.8.0 of the AWS provider plugin - hashicorp/terraform-provider-aws#23873.
Additionally I changed every use of aws_s3_bucket_object to aws_s3_object because aws_s3_bucket_object is deprecated - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_object.

How Has This Been Tested?
I have added a new exame for this feature at example/ephemeral-storage that uses the new feature.
I have tested the new change via the terraform validate command.

@antonbabenko

Good and quick one! Please remove the example folder you added but add just one argument (ephemeral_storage_size = 10240) to examples/complete/main.tf in module lambda_function.

Done

Merging like this. The feature is working as expected but currently examples/complete is failing due to the S3 bucket module is not being compatible with AWS provider v4 (https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/pull/139).

This PR is included in version 2.37.0 :tada:

@antonbabenko People's scripts are going to break even if they have pinned this to ~> 2 . Not all modules have updated to support provider v4.
Since its a breaking change, it could have been timed better or released as a major version (v3.0.0)

@jaikanthjay46 Good point! I missed this yesterday. I will make a major release instead.

This PR is included in version 2.37.0 :tada:

This PR is included in version 3.0.0 :tada:

Thanks @antonbabenko, appreciate your rapid response 🥳 . You have single handedly stopped a StackOverflow exodus from happening.


task: make output filename and voxel spacing configurable

@milesagraham great work here - it would be useful to make the output file and voxel spacings configurable for each program rather than hard coded
https://github.com/teamtomo/ttmask/blob/ef0d4f4d3f43e2d985b9f938ad85f924db1da7c5/src/ttmask/sphere.py#L41
https://github.com/teamtomo/ttmask/blob/ef0d4f4d3f43e2d985b9f938ad85f924db1da7c5/src/ttmask/cylinder.py#L46

Thanks, have done this now :)

Closed by #13


Remove Display Version from Azul.Zulu.11.JDK

Newer versions have the proper display version. Since the ISV has had the issue fixed for some time, it seems a better course of action to remove the DisplayVersion from the relatively few manifests that have it rather than updating the manifests without it.

microsoft/winget-cli#4459

Microsoft Reviewers: Open in CodeFlow

Intentionally didn't bump version

URL: https://cdn.azul.com/zulu/bin/zulu11.35.13-ca-jdk11.0.5-win_x64.msi
OK
(Automated message - build 882)


Performance improvement: add transition-delay to backdrop

I experienced some browser rendering hiccups with the current backdrop transition which is a combination out of a transformed popup and the backdrop and opacity transition in the background.
An improvement would be adding a transition-delay to .bubble-backdrop in the popup/styles.ts:
transition-delay: 0.1s;
So the browser don't have to blur the whole viewport and animate the transition, the animations are run much smoother on my iPhone to M1 and M2 Pro Macs in latest Chrome engines.

I've released a new beta with your fix! Thanks again!
https://github.com/Clooos/Bubble-Card/releases/tag/v2.0.0-beta.2


Add elasticache redis

doc related
[1] https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Clusters.ViewDetails.html
[2] https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Endpoints.html#Endpoints.Find.Redis
[3] https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Endpoints.html#Endpoints.Find.RedisCluster

I have changed the logic to resolve if it is a cluster or not due to ClusterCache.getConfiguration is not returned. Also, I have created a ticket https://github.com/aws/aws-sdk-java/issues/2419

I am thinking about having a property cluster-enabled @maciejwalkowiak WDYT?

Wouldn't it better to name module as spring-cloud-starter-aws-elasticache?

Currently, we will be building on top of spring-boot-starter-data-redis in order to provide the right configuration for elasticache redis nodes and clusters. Having a spring-cloud-starter-aws-elasticache module will make sense if we want to drop memcache support which is something we have not figure it out yet and having redis as the default which sometimes can be confused. I prefer to be explicit here.
/cc @maciejwalkowiak


(GitHub Toggle Expanders) When the content is expanded, the expander (…) to become dimmed/grayed out

Hi there @Mottie
It's a feature request about the 'GitHub Toggle Expanders' script:
when any expander (…) is clicked (i.e. either manually by the user or via the script's functionality) and the content is expanded, the relevant expander to become dimmed/grayed out.
I wanted to make this request since forever, but hesitated to ask because the cause is the GitHub layout itself:
currently, when clicking an expander and the content becomes expanded, there's no difference in the expander appearance, and so you can't distinguish the expand status by looking at the expander :

screenshot comparison
(using the 'GitHub Dark' style) -the same with GitHub's own dark/light themes -

Thank you

There really isn't much I can do within the userscript to fix this without messing up the color theme... If you're using the Stylus extension, you could create a GitHub auxillary style and include the following:
.Details--on .ellipsis-expander {
  background: var(--color-scale-blue-2);
}

Adjust the color as desired.

Thanks a lot! It works great!


five.async usage in browser

The current implementation of five.async uses process.nextTick, which is a nodejs specific API. This won't work in a browser apparently.
I'd fix this by checking if there is a process variable. I could make a PR soon.

If you need that in the browser, and it's not currently possible, feel free to put a PR in!

Indeed, it's pretty essential for the scalability of my application.

This method could return a promise.

I think we can now assume a fair amount of promise support. PR still welcomed?


studio.transaction set method is throwing error when same code used with old and new versions

Thanks for inventing this framework/lib.
Facing issues with studio.transaction set method.
Current package versions which is throwing error on set method
"@theatre/core": "^0.7.0",
"@theatre/studio": "^0.7.0",
"next": "14.1.0",

Old package versions - no error
"@theatre/core": "^0.4.7",
"@theatre/studio": "^0.4.7",
"react": "^17.0.2",
"react-dom": "^17.0.2"

TheatreSheetObject props(proxy object) shows diff implementation get(obj, props) vs get(pointerKey, prop)
Right-side old version - ^0.4.7
Left-side new version - ^0.7.0

TheatreSheetObject implementation is different across versions

Please help. Thanks.

Sure. @AriaMinaei
Setup with old package versions:
https://codesandbox.io/p/devbox/theatre-js-svg-animation-updated-forked-n63dy7
Setup with new package versions:
https://codesandbox.io/p/devbox/threatrejs-nextjs-latest-svg-l98nvw
Please drag the robot hand as pointed out on both of the above setup!

Thanks.


The Input Image Normalization Policy used in your pretrained backbone network

Thanks for sharing great works!
I have one question.
What is your input image normalization policy used in pretrained backbone network?
Did you put the image into model without normalization?
Is the range  [0, 255]? or you followed the normalization method proposed in VGG(Z-normalization using mean and std)?

Hi ! Nice to meet you !
I use ToTensor to normalize the input image. But during traing YOLO, I forgot to normlize the input image......only (input - means) . For more details about training dartnet-19 and darknet-53, I suggest you to see my another project https://github.com/yjh0410/pytorch-imagenet.
As for pretrained model file, I'm try to upload them to google drive.
Thanks for your help !

@yjh0410
Thank you!!

@yjh0410
If we re-train the yolov3 model with the normalization method used in a pre-training step, can we get the improvement? what do you think of this?

I tried. After data-augmentation, I divided it by 255, but it didn't bring any improvement. I got the almost same result.
------------------ 原始邮件 ------------------
发件人: "Yonghye<EMAIL_ADDRESS>发送时间: 2020年3月13日(星期五) 中午11:25
收件人<EMAIL_ADDRESS>抄送: "ら ．Secret"<1394571815<EMAIL_ADDRESS>主题: Re: [yjh0410/pytorch-yolo-v2] The Input Image Normalization Policy used in your pretrained backbone network (#4)
@yjh0410
If we re-train the yolov3 model with the normalization method used in a pre-training step, can we get the improvement? what do you think of this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@yjh0410
How do you modify the code?
To modify the code correctly, I think that we should follow below rules.

Do Not Subtract Mean during SSD Augmentation

Divided image by 255 after SSD Augmentation

Convert opencv bgr img([0, 1] to pytorch bgr format

Apply the normalization policy that we applied the backbone during pre-training.

Did you follow the above step???

In my data-augmentation code, its augmentation rules is as following:

it fisrt convert opencv BGR img into RGB format ( images = images[:, :, (2, 1, 0)]).
SSD Augmentation;
After step 2, it resize images and substract mean.
Finally, it convert opencv images into a torch.tensor type.

For more details, you could open utils/augmentation to check.
Besides those above, I added an extra step:
5. divide images by 255.
But I found there was no obvious improvement with step 5. So I removed it (Maybe I should keep it since it won't impair the performance).
"Apply the normalization policy that we applied the backbone during pre-training."
I'm sorry, I didn't follow this step.
I believe that there is a lot of room for improvement to make the model better and stronger. If I have enough time, I will try again.
------------------ 原始邮件 ------------------
发件人: "Yonghye<EMAIL_ADDRESS>发送时间: 2020年3月13日(星期五) 晚上9:13
收件人<EMAIL_ADDRESS>抄送: "ら ．Secret"<1394571815<EMAIL_ADDRESS>主题: Re: [yjh0410/pytorch-yolo-v2] The Input Image Normalization Policy used in your pretrained backbone network (#4)
@yjh0410
How do you modify the code?
To modify the code correctly, I think that we should follow below rules.
Do Not Subtract Mean during SSD Augmentation
Divided image by 255 after SSD Augmentation
Convert opencv bgr img([0, 1] to pytorch bgr format
Apply the normalization policy that we applied the backbone during pre-training.
Did you follow the above step???
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks!


Add Plotly.Blazor

This library packages the well-known charting library plotly.js into a Razor component that can be used in a Blazor project.

Thanks!


[Suggestion] Pre-made announcement messages

e.g.

We are currently in the process of updating the website, if something does not work properly wait a few minutes then try again

Announce doesn't need to be deleted, you can make them and reuse them by updating expire time?

Announce doesn't need to be deleted, you can make them and reuse them by updating expire time?

I'm sorry what? I didn't talk about deleting them, but adding pre-made announcement messages on top of that, that would be accessible in a <select>
By the way, @akuma06, could you add the possibility of choosing hour duration for announcement? So that we can do 1 day + 5h, or 0 day + 1h instead of having the minimum duration being one day


debounceEvent and google tag manager console error

This is a...

[x] :beetle: Bug Report
[ ] :rocket: Feature Request
[ ] :scroll: Documentation Request

Note: for support questions, please use stackoverflow with the redux-beacon tag. This repository's issues are reserved for feature requests and bug reports.
Which version of Redux Beacon are you using?

v2.0.3

Which target(s) are you using?

[ ] Google Analytics
[ ] Google Analytics (gtag)
[ ] React Native Google Analytics
[x] Google Tag Manager
[ ] React Native Google Tag Manager
[ ] Amplitude
[ ] Segment
[ ] Other/Third Party: ...(please specify here)

:beetle: What are the steps to reproduce your issue?

Using target google-tag-manager add debounceEvent in combination
Return undefined instead of fulfilled event, i.e.:

import debounceEvent from '@redux-beacon/debounce-event';
import { EventsMap } from 'redux-beacon';

return {
  MY_REDUX_ACTION: debounceEvent(100, () => {
    if (false) {
      return {
        event: 'event'
      };
    }
  })
};

:beetle:  What did you expect to happen?
No error is thrown into console, event should be omitted from the data layer.
:beetle: What happened instead?
...Error is thrown Uncaught (in promise) TypeError: Cannot read property 'event' of undefined..
Can you help out?

[x] :star2: I am a legend and can get started on a pull request right away given the go-ahead.
[ ] :star: I am a superstar and would like to help out given some guidance.
[ ] :disappointed: I won't be able to help out on this one.

Fixed in<EMAIL_ADDRESS>


feat(#142): Fix Bytecode in Tests

Fix byecode in tests in order to avoid some problems and redundant printing to stdout.
Closes: #142.

History:

feat(#142): fix invalid bytecode in DirectivesMethodTest
feat(#142): fix DirectivesClassTest

PR-Codex overview
Detailed summary

Added a method helloWorldMethod() in the BytecodeClass class in the DirectivesClassTest.java file.
Changed the verification parameter from true to false in the CheckClassAdapter.verify() method in the BytecodeClass.java file.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 3min)


Should update access to FilterManager since FXMaster update v1.1.2

Hi,
I made filterManager publicly accessible.
you should now access it this way.
FXMASTER.filters

Thanks! Fixed by #87.

This still needs a release! :(


Improve documentation about how to run tests

As discussed in #284, some users find it difficult to start using this track and start running tests.
Improve documentation on /docs/TEST.md by describing more or less this idea:

In the command line, go to the directory where exercism place test files (<EXERCISM_HOME_DIR>/<TRACK_ID>/<EXERCISE>), and run the jasmine-node . command.

It would be nice if an example is provided.

After #297 and #330, I think this can be closed.
If there is no problem, I'll close it in a few days.


PornHub: Extracting videos from GIF subcategory

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm requesting a site-specific feature
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
Croatia
Example URLs
https://www.pornhub.com/gif/40162861
Provide a description that is worded well enough to be understood
Is is possible to include downloading videos from the GIF portion of the site? They are effectively cut-down videos but are by default presented in video format but are not supported by default in yt-dlp. When inspecting the source of the site (see screenshot below) they are actually available in webp and mp4 formats directly so they could be downloaded without any recoding necessary.

Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['https://www.pornhub.com/gif/38661021', '-vU']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[b532a3481] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.22621-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 6.0-full_build-www.gyan.dev (setts), ffprobe 6.0-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.18.0, brotli-1.0.9, certifi-2023.05.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.3
[debug] Proxy map: {}
[debug] Loaded 1855 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 5ff3e702171a50175c34397494e2d18ce35d771c2110b1e59bd173ec2fb352aa
yt-dlp is up to date<EMAIL_ADDRESS>[PornHubPagedVideoList] Extracting URL: https://www.pornhub.com/gif/38661021
[download] Downloading playlist: gif/38661021
[PornHubPagedVideoList] gif/38661021: Downloading page 1
[PornHubPagedVideoList] Playlist gif/38661021: Downloading 0 items
[download] Finished downloading playlist: gif/38661021

In case anyone else was wondering/concerned about what they just saw: that is a human hand holding a ferret.

In case anyone else was wondering/concerned about what they just saw: that is a human hand holding a ferret.

Although the site itself is not so family-and-work friendly at least I can provide an example that is and can draw out a smile

Are they always 720p only (even if the source video is 1080p)?

Are they always 720p only (even if the source video is 1080p)?

Indeed, all the GIFs are generated at a maximum resolution of 720p regardless if the source video is of a higher resolution

well, gallery-dl already added this feature, so if you need a tool to download those gifs, just use that for now.


Collecting mongo dbstats for all databases can overload a cluster

We have attempted to roll back our fork of a very old Datadog mongo integration and use the current integration. What we found is that the current integration is overloading our database cluster, which contains 658 databases with about 65 collections each.
The problem is in this section of the code:
https://github.com/DataDog/integrations-core/blob/master/mongo/datadog_checks/mongo/mongo.py#L221
After collecting the database names, it runs the following code in refresh_collectors:
https://github.com/DataDog/integrations-core/blob/master/mongo/datadog_checks/mongo/mongo.py#L126
        for db_name in all_dbs:
            potential_collectors.append(DbStatCollector(self, db_name, tags))

When this is run through several mongos, it creates an overwhelming CPU load on all of the mongod in the cluster.
We had a similar problem that we addressed in our older fork, where we modified similar code to look like this:
dbnames = instance.get('dbnames', [])

That is, we could opt in to specific databases for which to monitor dbstats.
I think this integration needs something similar, or needs to detect when running through a mongos and not collect dbstats.

Hi @awestendorf, thank you for reporting this issue. I've added a task to our backlog to investigate this further.


Autoflake support

Codecov Report

Merging #442 (8a65fe2) into master (036332e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #442   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           12        12
  Lines          638       638
=========================================
  Hits           638       638

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 036332e...9958fe7. Read the comment docs.

When I run the tests locally using the command pytest tests/test_runtime_errors.py, test_runtime_errors:test_missing_root_dir is failing. This is expected __main__.py: error: the following arguments are required: root_dirs, but the actual message is pytest: error: the following arguments are required: root_dir. But if I run the same tests using python -m pytest tests/test_runtime_errors.py the tests are passing. Also when I run nbqa black, the message displayed is nbqa: error: the following arguments are required: root_dirs.  @nbQA-dev/nbqa-core Any idea why this is happening? How are the tests passing at your end? Tests are passing in CI as well.

ah, that failure happens because I usually just run tox -e py, so __main__.py: error: is what appears. changing it to a regex so we can simply call pytest seems like a good idea

Anyway, nice PR! Do you also want to add a pre-commit hook for this?

Anyway, nice PR! Do you also want to add a pre-commit hook for this?

Yes, I am planning to raise a different PR with autoflake pre-commit hook and docs updated.

awesome - thanks!


webui: connect to scheduler rpc error: error(111, 'Connection refused')

pyspider version:
0.3.9
Operating system:
Debian GNU/Linux 8.10 (jessie)
Start up command:
See /etc/init.d/pyspider and /opt/.pyspider/config.json below.
RabbitMQ info:
See below
pip Tornado version:
5.0

Probably related to Issue.
Expected behavior
Webui connects to scheduler
Actual behavior
Updated virtual machine with pyspider running on debian Jessie and got into trouble.
Webui doesn't connect and raises error:

[W 180305 19:33:32 index:108] connect to scheduler rpc error: error(111, 'Connection refused')

Also following error is shown if pyspider -c config.json scheduler is explicitly executed.
[I 180306 09:24:41 scheduler:647] scheduler starting...
Exception in thread Thread-5:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/local/lib/python2.7/dist-packages/pyspider/scheduler/scheduler.py", line 780, in xmlrpc_run
    self.xmlrpc_server = tornado.httpserver.HTTPServer(container, io_loop=self.xmlrpc_ioloop)
  File "/usr/local/lib/python2.7/dist-packages/tornado/util.py", line 312, in __new__
    instance.initialize(*args, **init_kwargs)
TypeError: initialize() got an unexpected keyword argument 'io_loop'

... normal output follows, listing projects and stats
How to reproduce

apt-get update
apt-get upgrade
installed latest rabbitmq
rabbitmq-server_3.7.3-1_all.deb
installed latest erlang
esl-erlang_20.2.2-1~debian~jessie_amd64.deb
apt-get update
added someusername and somepassword as shown here because without that got the error com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.

/opt/.pyspider/config.json
{
  "taskdb": "mysql+taskdb://someusername:somepassword@localhost:3306/taskdb",
  "resultdb": "mysql+resultdb://someusername:somepassword@localhost:3306/resultdb",
  "message_queue": "amqp://someusername:somepassword@localhost:5672/%2F",

  "webui": {
    "cdn": "//cdnjs.cloudflare.com/ajax/libs/",
    "port":80,
    "username": "someusername",
    "password": "somepassword",
    "need-auth": false
  }
}

/etc/init.d/pyspider
### BEGIN INIT INFO
# Provides:          pyspider
# Required-Start:    $remote_fs $network $syslog rabbitmq-server mysql
# Required-Stop:     $remote_fs $network $syslog rabbitmq-server mysql
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start pyspider daemon at boot time
# Description:       Enable pyspider service provided by daemon.
### END INIT INFO

# Some things that run always
touch /var/lock/pyspider

# Carry out specific functions when asked to by the system
case "$1" in
  start)
    echo "Starting PySpider"
    cd /opt/.pyspider

    # start **only one** scheduler instance
    pyspider -c config.json scheduler 2> scheduler.2.log > scheduler.log &

    # phantomjs
    pyspider -c config.json phantomjs 2> phantomjs.2.log >  phantomjs.log &

    # start fetcher / processor / result_worker instances as many as your needs
    pyspider -c config.json --phantomjs-proxy="localhost:25555" fetcher 2> fetcher.2.log > fetcher.log &
    pyspider -c config.json processor 2> processor.2.log > processor.log &
    pyspider -c config.json result_worker 2> result_worker.2.log > result_worker.log &

    # start webui, set `--scheduler-rpc` if scheduler is not running on the same host as webui
    pyspider -c config.json webui 2> webui.2.log > webui.log &

    ;;
  stop)
    echo "Stopping PySpider"
    (pgrep pyspider | xargs kill; pkill -f phantomjs; pgrep phantomjs | xargs kill; service rabbitmq-server stop)
    ;;
  *)
    echo "Usage: /etc/init.d/pyspider {start|stop}"
    exit 1
    ;;
esac

exit 0

rabbitmqctl status

Status of node rabbit@pyspider ...
[{pid,418},
 {running_applications,
     [{rabbit,"RabbitMQ","3.7.3"},
      {rabbit_common,
          "Modules shared by rabbitmq-server and rabbitmq-erlang-client",
          "3.7.3"},
      {xmerl,"XML parser","1.3.16"},
      {ranch_proxy_protocol,"Ranch Proxy Protocol Transport","1.4.4"},
      {ranch,"Socket acceptor pool for TCP protocols.","1.4.0"},
      {ssl,"Erlang/OTP SSL application","8.2.3"},
      {public_key,"Public key infrastructure","1.5.2"},
      {crypto,"CRYPTO","4.2"},
      {asn1,"The Erlang ASN1 compiler version 5.0.4","5.0.4"},
      {mnesia,"MNESIA  CXC 138 12","4.15.3"},
      {jsx,"a streaming, evented json parsing toolkit","2.8.2"},
      {os_mon,"CPO  CXC 138 46","2.4.4"},
      {inets,"INETS  CXC 138 49","6.4.5"},
      {recon,"Diagnostic tools for production use","2.3.2"},
      {lager,"Erlang logging framework","3.5.1"},
      {goldrush,"Erlang event stream processor","0.1.9"},
      {compiler,"ERTS  CXC 138 10","7.1.4"},
      {syntax_tools,"Syntax tools","2.1.4"},
      {sasl,"SASL  CXC 138 11","3.1.1"},
      {stdlib,"ERTS  CXC 138 10","3.4.3"},
      {kernel,"ERTS  CXC 138 10","5.4.1"}]},
 {os,{unix,linux}},
 {erlang_version,
     "Erlang/OTP 20 [erts-9.2] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-th                                                                                reads:64] [hipe] [kernel-poll:true]\n"},
 {memory,
     [{connection_readers,270192},
      {connection_writers,63056},
      {connection_channels,152112},
      {connection_other,490152},
      {queue_procs,282688},
      {queue_slave_procs,0},
      {plugins,5864},
      {other_proc,24010152},
      {metrics,217792},
      {mgmt_db,0},
      {mnesia,83368},
      {other_ets,1873712},
      {binary,34221544},
      {msg_index,28912},
      {code,24915284},
      {atom,1041593},
      {other_system,9198923},
      {allocated_unused,12606160},
      {reserved_unallocated,0},
      {strategy,rss},
      {total,[{erlang,96855344},{rss,71524352},{allocated,109461504}]}]},
 {alarms,[]},
 {listeners,[{clustering,25672,"::"},{amqp,5672,"::"}]},
 {vm_memory_calculation_strategy,rss},
 {vm_memory_high_watermark,0.4},
 {vm_memory_limit,630929817},
 {disk_free_limit,50000000},
 {disk_free,25049255936},
 {file_descriptors,
     [{total_limit,924},
      {total_used,15},
      {sockets_limit,829},
      {sockets_used,13}]},
 {processes,[{limit,1048576},{used,327}]},
 {run_queue,0},
 {uptime,83},
 {kernel,{net_ticktime,60}}]

Resolved by downgrading Tornado to 4.5 version from latest (5.0).
Apparently Tornado 5.0 API is incosnsistent with previous versions.

I got the same problem


Configuration large screen no response

Environment:
Success / Image loading completed, but no response

The problem is in dgiot-4.4.8 Resolved


Review search history (E.1)

E.1: The user clicks on the panel button to review the search history. Then the whole process is back to C.1-C.2.
The state should persist.

Need to create a new tab to show the search history.
We also need a new handler NotebookSearchHistoryHandler

Timeout


UserControl on a pin

Hi and thanks a lot to all the contributors for this hard work.
I have a question about visualize a usercontrol on a map.
The problem
I want to click on a pin and expand something like a control with buttons (a UserControl). Is it possible to do that ? I see the "Info" section into the sample demo but i understand  it use style only. Perhaps i don't look on the right side.
Please, can you tell me if there is an other sample demo to look, an other discussion or how i can make it ?
Thanks in advance.

Yes this is possible, but you have to write that code yourself.
I think we do not have a sample anymore for that because it requires implementations on each platform and we want to reduce the need for maintenance. I did something like this on MAUI with v4. The Info event will return the screen coordinates (and the tapped feature if you tapped one), you can use the screen coordinates to show the user control over the MapControl.
I did this on MAUI and I needed a transparent (input-transparent and color-transparent) AbsoluteLayout placed on top of the MapControl to be able to place the user control on the screen coordinates (Perhaps I should derive the MAUI MapControl from AbsoluteLayout to make this easier).
btw, In most of my projects I end up placing the user control to side or the bottom, because it is just nice UI to have it in a fixed position.

Thank you very much for the prompt response.
I will look into MAUI v4.
I noticed that you positioned the user control in the bottom corner. I'm accustomed to having information closer to the pin, but I will evaluate the advantage of placing it in a fixed position.

With 'UseControl' I assumed you are referring to a popup created with MAUI controls. We have no samples of that. About 'positioned the user control in the bottom corner', I think you are referring to the MapInfoWidget, this is just an option, mainly added to keep the samples simple. Another option would be to use a callout. Loot at the Info|SingleCallout sample.


Add printer nicknames and stored profiles

Add functionality to allow users to save multiple machine connection strings within TAMV, and not just a single URL with no nickname.
This framework is already set-up in settings.json but there is currently no method of handling multiple profiles, or for displaying printer names.

Done with dev_alpha release.


Installation problem (Windows 10)

Below is my output after doing "> quasar ext add @quasar/typescript"
Seems to be successful and then an error afterwards?  Perhaps related to this (https://stackoverflow.com/questions/37459717/error-spawn-enoent-on-windows)?

 app:extension Installing "@quasar/typescript" Quasar App Extension +0ms

 app:extension Retrieving<EMAIL_ADDRESS>+5ms
 app:spawn [sync] Running "npm install --save-dev @quasar/quasar-app-extension-typescript" +1ms

npm WARN<EMAIL_ADDRESS>requires a peer of typescript@* but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^5.0.0 but none is installed. You must install peer dependencies yourself.npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^3.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fork-ts-checker-webpack-plugin\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

+<EMAIL_ADDRESS>added 41 packages from 39 contributors and audited 16930 packages in 34.324s
found 0 vulnerabilities

   ╭────────────────────────────────────────────────────────────────╮
   │                                                                │
   │      New minor version of npm available! 6.9.0 -> 6.10.3       │
   │   Changelog: https://github.com/npm/cli/releases/tag/v6.10.3   │
   │               Run npm install -g npm to update!                │
   │                                                                │
   ╰────────────────────────────────────────────────────────────────╯
? Please choose how to derive webpack: Use the fork-ts-checker-webpack-plugin module for type-checking (recommended)
? Rename .js files to .ts (experimental) Yes
? Will you use VSCode for this project? (Adds ESLint and Vetur configuration quirks, you must manually install the extensions) Yes
? Generate prettier configuration (ESLint and VScode, if used)? Yes

 app:extension-manager Updating /quasar.extensions.json for "@quasar/typescript" extension ... +3m
 app:extension Running App Extension install script... +42ms

We could not automatically update your quasar.conf.js to
use typescript. Quasar looks for *.js files by default.
Please add this to your quasar.conf.js:

sourceFiles: {
  router: 'src/router/index.ts',
  store: 'src/store/index.ts'
}

 app:extension Updating dependencies... +1s
 app:spawn [sync] Running "npm install" +14ms

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>||
^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none
is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of eslint@*
but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\webpack-dev-server\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fork-ts-checker-webpack-plugin\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 16 packages from 14 contributors, updated 1 package and audited 16965 packages in 40.648s
found 0 vulnerabilities

 app:extension Quasar App Extension "@quasar/typescript" successfully installed. +46s

(node:42876) UnhandledPromiseRejectionWarning:   Error: spawn yarn ENOENT

  - enoent.js:6 notFoundError
    [client]/[cross-spawn]/lib/enoent.js:6:26

  - enoent.js:40 verifyENOENT
    [client]/[cross-spawn]/lib/enoent.js:40:16

  - enoent.js:27 ChildProcess.cp.emit
    [client]/[cross-spawn]/lib/enoent.js:27:25

  - child_process.js:248 Process.ChildProcess._handle.onexit
    internal/child_process.js:248:12

(node:42876) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:42876) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

And you please provide the output of Quasar Info?

I can confirm the problem, after just running the following commands:
quasar create <folder_name>
cd <folder_name>
quasar ext add @quasar/typescript
Unfortunately, in my case the setup doesn't finish properly. Let me know if you need more information.
Thanks for having a look into it!
console output
? Please choose how to derive webpack: Use vanilla ts-loader
? Rename .js files to .ts (experimental) Yes
? Will you use VSCode for this project? (Adds ESLint and Vetur configuration quirks, you must manually install the exten
sions) Yes
? Generate prettier configuration (ESLint and VScode, if used)? Yes
app:extension-manager Updating /quasar.extensions.json for "@quasar/typescript" extension ... +42s
app:extension Running App Extension install script... +14ms
? Overwrite ".eslintrc.js"? (Use arrow keys)

Overwrite
Overwrite all
Skip (might break extension)
Skip all (might break extension) (node:12716) UnhandledPromiseRejectionWarning:   Error: spawn yarn ENOENT

enoent.js:6 notFoundError
[codebase-quasar-12]/[cross-spawn]/lib/enoent.js:6:26

enoent.js:40 verifyENOENT
[codebase-quasar-12]/[cross-spawn]/lib/enoent.js:40:16

enoent.js:27 ChildProcess.cp.emit
[codebase-quasar-12]/[cross-spawn]/lib/enoent.js:27:25

child_process.js:272 Process.ChildProcess._handle.onexit
internal/child_process.js:272:12

(node:12716) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
quasar info
Operating System - Windows_NT(10.0.18362) - win32/x64
NodeJs - 12.8.0
Global packages
NPM - 6.9.0
yarn - Not installed
@quasar/cli - 1.0.0
cordova - Not installed
Important local packages
quasar - 1.0.5 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
@quasar/app - 1.0.4 -- Quasar Framework local CLI
@quasar/extras - 1.2.0 -- Quasar Framework fonts, icons and animations
vue - 2.6.10 -- Reactive, component-oriented view layer for modern web interfaces.
vue-router - 3.0.7 -- Official router for Vue.js 2
vuex - 3.1.1 -- state management for Vue.js
electron - Not installed
electron-packager - Not installed
electron-builder - Not installed
@babel/core - 7.5.5 -- Babel compiler core.
webpack - 4.35.3 -- Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
webpack-dev-server - 3.7.2 -- Serves a webpack app. Updates the browser on
changes.
workbox-webpack-plugin - 4.3.1 -- A plugin for your Webpack build process,
register-service-worker - 1.6.2 -- Script for registering service worker, with hooks
Quasar App Extensions  @quasar/quasar-app-extension-typescript - 1.0.0-beta.1 -- A Quasar CLI Extension

This happens because the extension is trying to spawn a yarn process but you don't have yarn installed. Ideally the extension should determine whether it should use npm or yarn. As a workaround for now, you can try to install yarn and run the script again.

I've just created a before and after project and can confirm that the suggested workaround works.
Thank you for your help, very much appreciated.

Should be fixed by #48


Visualization: handling long axis tick label with ellipsis and tooltip for Mosaic plot

This work is a kind of an extension of previous task, long axis tick labels for barplot and boxplot, which would apply to Mosaic plot.
note: this ticket was initially made at web-components repo expecting that it is shown at our project board, but somehow it does not work. So I made the same one here at web-eda.

well now I realized how it makes happen so I will close this

https://github.com/VEuPathDB/web-components/issues/214 is showing on the Kanban board under "this cycle".
ahahaha you got there first

@bobular yes I firstly didn't know how to make this show in the project board so I made this ticket assuming that the board only handles web-eda repo. But I got the point to make it happen by setting Projects at right hand menu 😄 thus I closed this duplicate issue


Input data structure

Unlike fMRIPost-AROMA or fMRIPost-tedana, this pipeline is going to require both the raw BIDS dataset (for the phase data) and the fMRIPrep derivatives dataset (for the transforms and preprocessed magnitude data).
One thing that I think might be tough will be linking preprocessed magnitude data to the original phase data. Hopefully it's just a matter of BIDSLayout.get_nearest using the preprocessed magnitude file, while explicitly dropping any derivatives-only entities, but I'm not optimistic.

We might just want to go preprocessed magnitude --> raw magnitude --> raw phase.


Power Toys still does not run nor any default shortcut key works

[Enter feedback here]

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

ID: 7c39e7c8-7ab6-3297-1554-d7ef10d46894
Version Independent ID: 021ad68a-284a-fd90-4404-463f08301b04
Content: PowerToys Shortcut Guide utility for Windows 10
Content Source: hub/powertoys/shortcut-guide.md
Product: dev-environment
Technology: powertoys
GitHub Login: @crutkas
Microsoft Alias: crutkas

Thanks for providing the link to the PowerToys repo, @crutkas. Closing this issue for now.


Add valid property to the result

Currently there are three properties which indicate results of three different aspects of validation:

card_type — whether the card prefix has been recognised (regardless of the below being valid or not)
luhn_valid — whether the Luhn checksum is valid
length_valid — whether the length of the card number is valid for the type of card

Having this breakdown is useful to provide the user the exact reason why the card number is invalid. For example:

Card type not recognised.
Card number appears to be invalid.
Card number length for Visa must be 16 characters.

However, in some cases all the developer needs to know is the combined result of validation, ie if all three validation tests were successful.
To indicate it, I propose adding a valid parameter which is set to true only if all validation tests have passed, and set to false otherwise.
The developer won’t have to check two properties anymore (two, because card_type doesn’t need to be checked — luhn_valid and length_valid are always false if card type is not recognised):
if (result.luhn_valid && result.length_valid) {
    // ...
}

Instead the developer will be able to do:
if (result.valid) {
    // ...
}

This is implemented in just released 1.0.


elm: Update elm-lang/core hash.

elm-lang/core tag 3.0.0 was moved.
See: https://groups.google.com/d/msg/elm-dev/K5eu8S5to-c/Bl4-Z_0QBQAJ

Nice, thanks. P.S. The bot is awesome.

@nbp GitHub says that you have added some labels after the merge. Why? (I ask because I usually don't add labels to a PR that I'm going to merge right away, but I'm willing to change the habit if needed).

@abbradar, having those labels available might be nice for purposes of statistics (i.e.: x% of our issues are package updates, y% report bugs, etc.). I usually don't add labels to quick-merge PRs either, but every now and then I do it, mostly when an issue/PR turns out to be invalid.

@abbradar because an issue which has no label is a bug.  This like having a pile of paper spread on the floor instead of having categorized piles of paper.
To make it simple, if you don't clean-up your issue tracker, people will lose track of issues, and if you don't keep track of the past, then you cannot predict the future.

Lesson learnt, I'll try to label things independent of their "quickliness". Thanks for explanations!


JarInfer bytecode rewriting should avoid adding redundant annotations

The @Nullable annotation is not repeatable. Currently, running JarInfer on libraries that already have annotations produces the following issue when processing with D8:
Error: Multiple annotations of type `javax.annotation.Nullable`
com.android.tools.r8.CompilationFailedException: Compilation failed to complete
	at com.android.tools.r8.utils.ExceptionUtils.withCompilationHandler(ExceptionUtils.java:72)
	at com.android.tools.r8.utils.ExceptionUtils.withD8CompilationHandler(ExceptionUtils.java:43)
	at com.android.tools.r8.D8.run(D8.java:73)

Suggestions:

Never duplicate an annotation. If @Nullable or @NonNull are already present on the input jar, keep them and don't add a redundant (or contradictory) annotation (fine to log an error in the second case).
We should consider providing a flag --skip-annotated that completely skips processing code that's already manually annotated. It's unclear to me at which level we should be looking, though. If we do full jar, we risk skipping many libraries because they fat-jar-include some class that has nullability annotations. An option would be to skip at the class level instead (e.g. any class that mentions @Nullable or @NonNull in the input jar is not re-written.

We don't need to implement these two at the same time. (1) is blocking internal deployment, (2) is a a nice to have :)

Good points. I can take 1, if you are not already on it.

Go for it. Currently looking at the CI failure for #334

Hey @navahgar , are you still looking at this one? It's the current blocker for re-enabling JarInfer internally (possibly not the only one, but the one I am first seeing triggering). I can take a look too, but wanted to check with you first.

@navahgar Is this issue resolved with the PR #341?

PR #341 fixed 1 but not 2. Currently, we are just ignoring the redundant annotations. Going forward, we have to figure out how to handle this best - error on such cases and / or add a flag to control this?

I think that is a good state to close this at for now. If we need any other changes in future, we can look into them at that point.


Add touch-action: manipulation

Removes the delay when tapping on clickable elements.
See this post for details on touch-action:
https://adactio.com/journal/10019

Great find, @zrothauser!


My squad page shows for platoon level slots

Describe the bug
Troopers in platoon level slots see a my squad button when they are not in a squad

Can not replicate. Made test user slotted in plt HQ, shows squad directory not my squad button. require further information.

Oops my bad


[Auto-generated] Update requirements.txt

Update requirements.txt
Automatically created PR from the ci_update_requirements.yml workflow.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (ci/dependabot-updates@525fb74). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                   Coverage Diff                    @@
##             ci/dependabot-updates     #369   +/-   ##
========================================================
  Coverage                         ?   59.47%
========================================================
  Files                            ?       20
  Lines                            ?      728
  Branches                         ?        0
========================================================
  Hits                             ?      433
  Misses                           ?      295
  Partials                         ?        0

Flag
Coverage Δ

pytest
59.47% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Class ol.style.RegularShape   didn't have Function  setRadius()

ol.style.RegularShape didn't have  Function setRadius() ,
now  i want to change the radius, so  i must create a new  ol.style.RegularShape,
is it right?

Yes, that's right. It is because the shape is rendered to a canvas. So instead of changing the radius dynamically in a style function, it is better to create a new RegularShape style for each radius and cache the styles with the radius as key.

thanks for you


kvm support?

Hi, thanks for creating this project! I'm pretty dissatisfied with the price/performance of dedicated aarch64 hardware compared to Apple Silicon, so I'm considering using one of our low-end M1 Macs to replace an aarch64-linux machine running NixOS.
What's the status of kvm support in M1 NixOS (as in nix.settings.system-features = [ "kvm" ...])? I'd like to be able to run NixOS tests and nixpkgs builders like pkgs.vmTools.runInLinuxVM that rely on this feature.
Based on some quick research, it sounds like there might be some issues with KVM support in QEMU on Asahi Linux, and maybe more specifically on vanilla M1 CPUs (as opposed to M1 Pro, Max, & Ultra), but most of the issues I've seen are with Windows, rather than just virtualizing NixOS on NixOS.

I tried building NixOS tests on the latest release and my M1 Max machine and there's definitely something wrong here. /dev/kvm is present, but the QEMU process seems to just hang at 100% CPU so something is completely broken with KVM and/or the software emulation is excruciatingly slow.
Would be interested to here from other Asahi users. I don't have time to debug this at this moment.

Thanks for testing it out. That's disappointing to hear that it doesn't work well on an M1 Max, which I'd been led to believe worked fine (per this comment).
Supposedly the problems have to do with QEMU not being able to deal with heterogenous CPUs (efficiency vs performance cores), and if you can manage to create a taskset/cpuset that contains only the peformance cores and run QEMU on that, it works.

I use virtualization heavily on my m1 max and i noticed only two problems:
1). https://www.reddit.com/r/AsahiLinux/comments/134g00u/strange_scheduling_latency_on_the_host_when_kvm/ Fixed in newer m1n1 version
2). Guest may fail to initialize cores if you don't pin them to only one type of cores. In libvirtd i just do <vcpu placement="static" cpuset="2-9">8</vcpu> (on m1 max efficency cores are 0-1 and the rest are performance ones)

KVM works ok for me.   I use virt-manager-qt to create and run VMs.
I recommend adding your main user to the kvm group within configuration.nix.
virt-manager-qt doesn't add video, graphics, mouse, or keyboard by default, it seems, so you'll need to manually add that hardware to your VM.  Expect the mouse experience to suck.


Matchmaking service page

xref: https://github.com/iodepo/odis-arch/issues/287

[ ] Explore how to implement a subscription service / continuous search / push notification when an offer  (approximately) matches a demand.
[ ] Consider implementing a UI page where offers and demands can be created and pushed into the OIH SOLR backend.
[ ] Consider registering this matchmaking service and its corpus in a dedicated ODIS node
[ ] Consider requiring an OceanExpert login and authentication to use the service, and identify where to send notifications.

[ ] Explore leveraging "knows about" and other properties to boost matchmaking

On the UI/UX dev side, this should be a question of creating a form-like interface. IODE to provide backend elements.

A note for integration with DCO Data:
The Decade DCO for Data has a requests page - we can attempt to have this point to our ODIS Matchmaking interface.

@fils - elements relevant to the backend here.
On Offers - the submitter of the offer should be able to delete it. As we're not using user management.
There's a field in the Offer pattern that is the expiration date of the offer. This should be mandatory, and the offer will expire after this date (i.e. the backend system will delete or disable it).
If the user enters a contact email (which we could verify, on submission), we can trigger an autoreminder that their offer is about to expire, and ask if they'd like to extend it. It would be very good if they could click a link to a pre-filled form that they can edit and resubmit.

@fils - elements relevant to the backend here.
On Offers - the submitter of the offer should be able to delete it. As we're not using user management.
There's a field in the Offer pattern that is the expiration date of the offer. This should be mandatory, and the offer will expire after this date (i.e. the backend system will delete or disable it).
If the user enters a contact email (which we could verify, on submission), we can trigger an autoreminder that their offer is about to expire, and ask if they'd like to extend it. It would be very good if they could click a link to a pre-filled form that they can edit and resubmit.


Enhance feature aggregation to manage forecast data

When providing forecast data for a measurement station each timestamp might appear multiple times as the forecast is updated continuously. For instance, if we have a 12H forecast updated each hour, a new forecast will be produced 12 times for each timestamp. At the current time all forecasts are stacked in the timeseries widget:

We should update the aggregation hook so that only the latest forecast is kept for visualization purpose.

We updated the aggregation hook to manage the runTime property and the timeseries widget to only display one value per time. This should be more flexible as we could further improve the timeseries widget to display different forecasts by selecting among the available run time.


Remove path from sendgrid and fix email-templates titiles

Description

Removes /v3 from bseUrl
Uses SuperfaceTest for communication/email-templates
Improves titles and descriptions for communication/email-templates

Motivation and Context

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I haven't repeated the code. (DRY)
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@lukas-valenta @Jakub-Vacek I am getting on this brach error saying that there might be an error in CLI or Parser.
Should I have closer look?

No, this is a bug/problem in validator not being able to handle some of new AST nodes. We (@martinalbert and i) know about it and we will try to handle it right after release. Or do you think it's blocker?

Does it mean sendgrid map isn't linted?

It explodes during process of linting - so no, map isn't linted - it can be ok or not 🤨 I will look in to it more.

@janhalama it should be fixed. It was caused by toString()


Emit signal when playback of SFX ends?

Is your feature request related to a problem? Please describe.
I want to playback random sound effects in a folder and start a timer after the sound effect ends. They are variable length so I can't just add that to the timer as a buffer. I want to be able to play sound effects at a set interval.
Describe the solution you'd like
There's a finished signal for AudioStreamPlayer, even being able to tap into that would work
Describe alternatives you've considered
Setting a longer timer, it's what I will do for now.

SoundManager.play_sound returns the AudioStreamPlayer that will play the sound so you can await the finished signal of that player.


docs: Design proposal for TTL scans

A start for a design proposal for ttl on scans #537
Signed-off-by: Edvin Norling<EMAIL_ADDRESS>

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

I have tried to make the explanation more verbose following your comments @danielpacak and @kfox1111.
Stopped talking about feature flags and instead talk about environment variable since this is something that is used today.
Also given a short example in the yaml to make it super clear.

I have created a PoC https://github.com/aquasecurity/starboard/pull/879 using the RequeueAfter functinallity.
This seems to work fine at least on a small cluster. Even if your cluster is big I don't think this should create any more issues than starting to listen for all replicasets in a cluster.
As discussed earlier I use the annotation starboard.aquasecurity.github.io/report-ttl but I don't support adding a time granularity instead I always assume that the ttl defined is in seconds. We could of course add a feature where we listen for hours, minutes etc.
annotations:
  starboard.aquasecurity.github.io/report-ttl: 24h

instead of:
annotations:
  starboard.aquasecurity.github.io/report-ttl: 86400

Another option could also be to keep only supporting seconds and instead of using a annotation we could add a new spec entry to the VulnerabilityReport spec and set the type to int.
Please have a look at the update design when you have time @danielpacak @kfox1111 and look at the PoC implementation.

Is it a good idea to use annotation or should we think about using the status field instead?
This could help us with doing less type conversion (not that it's a huge problem) but it solves some other potential issues as well, for example users won't be able to update the TTL value manually.
https://github.com/aquasecurity/starboard/pull/879#discussion_r782096294

Is it a good idea to use annotation or should we think about using the status field instead?
This could help us with doing less type conversion (not that it's a huge problem) but it solves some other potential issues as well, for example users won't be able to update the TTL value manually.
#879 (comment)

I believe that the annotation is good to experiment and prove that this solution makes sense and is being adopted. This is what Kubernetes does as well. Once we feel comfortable we can refactor from annotation to typed property.

I have rewritten the design document to match more the final implementation that we went for.
Remove old mentions of the old idea.


Changed listContainer to stop listing all files w/ prefix by default

Currently, the driver retrieves all files from the object store that matches with the prefix given by default. This is an issue because if you have a file named "File1" and "File10" and you want to read from "File1" only, the driver will read in both "File1" and "File10." This patch fixes this issue and returns only "File1".

This problem is fixed in another pull request I've submitted.


Merge all builder and verifier

Shall we merge the builder and verifier repos to make it simpler for users? We could rename this repo slsa-tools and have the builders and the verifier.
Some people have told me that a single repo makes it easy for users to discover the project, and for documentation to be in one place (well, we could have a dedicated repo for doc :-))
I don't know what the structure would look like though. Ideally the verifier should be easy to build and install via go install, and the generic API should also be easily accessible for public consumption. Yet we want the verifier and generic API to belong to 2 different "projects" to avoid sharing dependencies. Not sure this is feasible, unless the generic API is a private interface :/
Thoughts?
/cc @asraa @ianlewis @MarkLodato @joshuagl

It may be worth rethinking but I asked this previously and @MarkLodato responded in the negative.

Would it also make sense to include the verifier here as well? Might make it easier to manage potential breaking changes if they are both in one repo with one set of pre-submits etc.

My inclination is no, that is a different use case with different code. Plus, the verifier will hopefully support more than thus this generator in the future.

https://github.com/slsa-framework/slsa-github-generator/issues/36#issuecomment-1110989023

gotcha. I don't disagree with this comment. Thanks for linking to the issue, I had forgotten about this part :-)

Shall we close this issue?

Yeah, we can close but lets keep it in the back of our minds as the project develops. I suspect our thinking on this will change over time.


result for AP_GATEWAY contains newlines, causing looping

Hi
I am a little new to this, so sorry if my terminology is not 100% correct.
I was flashing some Arlec energy meters using Lubuntu 16.xx and an old 802.11g wifi dongle (8gb thin client machine and stuff I had lying around) and had a issue where on the second stage of the flash, after the exploit has been run but before wifi is put into AP mode, where the cloudcutter script was not detecting the expected IP propperly. I was getting the message:
`Expected AP gateway = <IP_ADDRESS> or <IP_ADDRESS> but got
<IP_ADDRESS>`
Note the newlines.
Looking at the script, I can see the check that is being performed in common.sh. I quickly modified line 91 to:
AP_GATEWAY=$(nmcli -f IP4.GATEWAY con show "${AP_MATCHED_NAME}" | awk -F ' ' '{print $2}' | grep 192\.168\.17[65]\.1)
, adding grep 192.168.17[65].1 to remove newlines and other nonprintable characters. It fixed the issue. Not sure if it is due to an old version of nmcli?
There is probably a more elegant way to achieve this fix, not that experienced using awk and other linux tools.

Running with -r should resolve this issue as well.

Running with -r should resolve this issue as well.

Ah righto.
Well, the script could easily be made more robust to this regardless, running in -r mode is not an obvious thing to try.
DT

Ah righto.
Well, the script could easily be made more robust to this regardless, running in -r mode is not an obvious thing to try.
DT

You're welcome to submit a PR, I haven't had a solid reproduction case to test against, so the FAQ has mostly covered it so far.

You're welcome to submit a PR, I haven't had a solid reproduction case to test against, so the FAQ has mostly covered it so far.


Develop policy for creating and using secrets in Luxoft repos

Is your feature request related to a problem? Please describe.
The goal is to publish gengen to npmjs.org to include it in the Node ecosystem of packages. To do so we need to have an authorization token from Node.
Describe the solution you'd like
We need to establish a policy for handling secrets in general and for npmjs.org specifically. Reusing GitHub's secrets API seems like a good approach and ought to be evaluated.

Hi Jeremiah,
We created NPM account for BSS department. And now we already pushed first package https://www.npmjs.com/package/@luxbss/gengen.
P.S.
We uses standart github CI/CD approach.


Improve propTypes for Peer and Peers through use of shape

Nice. Should probably do this throughout the application at some point. Also makes it easier to read code as data gets passed down through components


Call TB.Helper from Assert and Check

Assertions and Checks currently don't call TB.Helper() directly, which leads to test output like the following:
=== FAIL: . TestMapBatch/PerCPUArray (0.01s)
    quicktest.go:12:
        error:
          got non-nil value
        got:
          e"batch update: not supported"
        stack:
          /home/runner/actions-runner/_work/ebpf/ebpf/map_test.go:148
            qt.Assert(t, qt.IsNil(err))

Note that the first source location is that of qt.Assert. The correct location can still be found from the stack trace, but that is at the end of the message instead of at the start.
Invoke TB.Helper in Assert and Check so that the Go testing package reports a more accurate / interesting location.

The test is pretty brittle, but writing a bullet proof one would take a lot more work I think.

@frankban is anybody out there?


Update citation details in docs and add CITATION.cff file

Resolves #225 and resolves #217
Updates the citation BibTeX details in various places in documentation to reflected published and accepted version of JCP article and also adds a CITATION.cff file with this citation data.
The default behaviour of CITATION.cff is to list the citation metadata for the software itself however there is a preferred-citation field for adding details of another artefact that should be cited in preference first. I've added JCP article details to this field and some basic metadata for software to main fields. For now I've just listed @CosmoMatt and @jasonmcewen as authors on the software. An alternative would be to list all contributors for example.

@matt-graham While we're updating citation details, I just saw in the readme, in a couple of places we have:

Price & McEwen, in prep.).

This should also be updated to a hyperlink like in the opening sentence. Could you correct that while you're at it?

These in text citations are now updated to Price & McEwen 2024 (switched to publication date rather than pre-print date) and links added (I've stuck with arXiv link rather than linking to published article from an ease of access perspective).

Thanks a lot @matt-graham . Great to have this set up. Good to specify the paper as the preferred citation.
In terms of code authors, we should certainly extend this beyond @CosmoMatt and I. We should certainly include you, @ASKabalan and others that have made core contributions. We could also extend this to "all-contributors". What do you think best?

I would say either sticking to just you and @CosmoMatt or extending to all contributors (or possibly those having made commits to main / listed with code contributions in all-contributors entry) would probably be the simplest in the long run.
If we decide to include only a subset of contributors, my experience is it is difficult to decide how to do this consistently / fairly and creates issues with both having to make a manual decision every time someone new contributes whether to include as an author and also means we need to remember to keep CITATION.cff up to date. If we use existing all-contributors data then I think we could hook in to this to open PRs to have contributors added to CITATION.cff automatically or at least have a check that the details in .all-contributorsrc and CITATION.cff are consistent (we do something similar on another project I'm involved in).

@matt-graham imo we should just include all contributors  here. It is the most straightforward solution and highlights everyone's contributions to the code. But I'm ultimately happy with whatever people prefer!

Yep agreed, let's include all-contributors in the citation authors.


Quiz sample

Solves #371
This is using amp-bind.
@sebastianbenz PTAL

@sebastianbenz PTAL

Related to #587

@sebastianbenz I added a button "TRY AGAIN", what do you think?

This is covered pretty much by multi page flow sample, @sebastianbenz I think we can close this.


Fixed wallaby.js config

Wallaby doesn't support complex patterns, so I have simplified it a bit. Now all tests pass with wallaby.js.

Hey @ArtemGovorov. Thats strange! For me wallaby seems to be working fine with the complex pattern. But thanks for the tip!

You are actually right, it does work in Atom, not in WebStorm though, so the simplified one works across all editors.

@ArtemGovorov Just out of curiosity, how did you find this repo and the fact that the tests were failing in WebStorm? ;)

@TommyM I'm a creator of wallaby.js and occasionally search GitHub for repos with wallaby configs in them to see how people are using it, in order to get a better idea about what I can improve, what technologies people use with wallaby more, etc.

Alright, next-level support! Helping your users before they even realise they need help! :p Again, thanks for the PR.
We are really excited about wallaby.js and are planning on starting to leverage it in all our projects.

Heh, yes, kind of it :)
Awesome! You guys probably already know where to find me in case if I can help with any questions/issues regarding wallaby.