Error fetching information from http://ccab4aaf-frigate-fa:5000/api/stats

Hello there! I have two separate and independent instances of Home Assistant running HA OS and core on RPi5 with Google Coral. On both of them I run Frigate custom component and official addon and I have the same error log on both instances. The two instances are in different cities, so in different networks.
Version of the custom_component
v.5.4.0 on HACS and 0.14.1 for the full access addon
Debug log
Log entry
Error fetching information from http://ccab4aaf-frigate-fa:5000/api/stats: Cannot connect to host ccab4aaf-frigate-fa:5000 ssl:default [None]

Need to see the logs of the addon itself

So sorry @NickM-27, here it is.
2024-11-01 08:52:03.723739662  <IP_ADDRESS> - - [01/Nov/2024:09:52:03 +0100] "" 400 0 "-" "-" "-"
2024-11-01 08:53:03.767511486  <IP_ADDRESS> - - [01/Nov/2024:09:53:03 +0100] "" 400 0 "-" "-" "-"
2024-11-01 08:53:49.079131499  <IP_ADDRESS> - - [01/Nov/2024:09:53:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 08:54:03.811722933  <IP_ADDRESS> - - [01/Nov/2024:09:54:03 +0100] "" 400 0 "-" "-" "-"
2024-11-01 08:55:03.861432737  <IP_ADDRESS> - - [01/Nov/2024:09:55:03 +0100] "" 400 0 "-" "-" "-"
2024-11-01 08:55:49.083551001  <IP_ADDRESS> - - [01/Nov/2024:09:55:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 08:56:03.903294151  <IP_ADDRESS> - - [01/Nov/2024:09:56:03 +0100] "" 400 0 "-" "-" "-"
2024-11-01 08:57:03.951381023  <IP_ADDRESS> - - [01/Nov/2024:09:57:03 +0100] "" 400 0 "-" "-" "-"
2024-11-01 08:57:49.089409685  <IP_ADDRESS> - - [01/Nov/2024:09:57:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 08:58:03.994692149  <IP_ADDRESS> - - [01/Nov/2024:09:58:03 +0100] "" 400 0 "-" "-" "-"
2024-11-01 08:59:04.040365191  <IP_ADDRESS> - - [01/Nov/2024:09:59:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 08:59:49.093636995  <IP_ADDRESS> - - [01/Nov/2024:09:59:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:00:04.084694987  <IP_ADDRESS> - - [01/Nov/2024:10:00:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:01:04.126396716  <IP_ADDRESS> - - [01/Nov/2024:10:01:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:01:49.097853470  <IP_ADDRESS> - - [01/Nov/2024:10:01:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:02:04.170576354  <IP_ADDRESS> - - [01/Nov/2024:10:02:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:03:04.215059277  <IP_ADDRESS> - - [01/Nov/2024:10:03:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:03:49.102662930  <IP_ADDRESS> - - [01/Nov/2024:10:03:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:04:04.259697532  <IP_ADDRESS> - - [01/Nov/2024:10:04:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:04:12.969252207  10:04:12.969 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:45868->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:04:18.124351427  10:04:18.124 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:44268->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:04:23.290180340  10:04:23.289 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:44292->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:04:23.320222934  [2024-11-01 10:04:23] frigate.video                  ERROR   : cam_one: Unable to read frames from ffmpeg process.
2024-11-01 09:04:23.320298656  [2024-11-01 10:04:23] frigate.video                  ERROR   : cam_one: ffmpeg process is not running. exiting capture thread...
2024-11-01 09:04:32.034747879  [2024-11-01 10:04:32] watchdog.cam_one            ERROR   : Ffmpeg process crashed unexpectedly for cam_one.
2024-11-01 09:04:32.044041560  [2024-11-01 10:04:32] watchdog.cam_one            ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-01 09:04:32.044795404  [2024-11-01 10:04:32] ffmpeg.cam_one.detect       ERROR   : [swscaler @ 0x55a065cd60] deprecated pixel format used, make sure you did set range correctly
2024-11-01 09:05:04.303075052  <IP_ADDRESS> - - [01/Nov/2024:10:05:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:05:49.108457715  <IP_ADDRESS> - - [01/Nov/2024:10:05:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:06:04.348356889  <IP_ADDRESS> - - [01/Nov/2024:10:06:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:07:04.392840717  <IP_ADDRESS> - - [01/Nov/2024:10:07:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:07:49.112276618  <IP_ADDRESS> - - [01/Nov/2024:10:07:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:08:04.439364883  <IP_ADDRESS> - - [01/Nov/2024:10:08:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:09:04.485755993  <IP_ADDRESS> - - [01/Nov/2024:10:09:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:09:49.117148661  <IP_ADDRESS> - - [01/Nov/2024:10:09:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:10:04.529596508  <IP_ADDRESS> - - [01/Nov/2024:10:10:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:11:04.576820273  <IP_ADDRESS> - - [01/Nov/2024:10:11:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:11:49.121353194  <IP_ADDRESS> - - [01/Nov/2024:10:11:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:12:04.623453758  <IP_ADDRESS> - - [01/Nov/2024:10:12:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:12:44.612425220  10:12:44.612 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:48802->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:12:49.774156922  10:12:49.773 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:36392->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:12:54.961910351  [2024-11-01 10:12:54] frigate.video                  ERROR   : cam_one: Unable to read frames from ffmpeg process.
2024-11-01 09:12:54.962124149  [2024-11-01 10:12:54] frigate.video                  ERROR   : cam_one: ffmpeg process is not running. exiting capture thread...
2024-11-01 09:13:02.089042945  [2024-11-01 10:13:02] watchdog.cam_one            ERROR   : Ffmpeg process crashed unexpectedly for cam_one.
2024-11-01 09:13:02.089228575  [2024-11-01 10:13:02] watchdog.cam_one            ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-01 09:13:02.089232890  [2024-11-01 10:13:02] ffmpeg.cam_one.detect       ERROR   : [swscaler @ 0x55824527e0] deprecated pixel format used, make sure you did set range correctly
2024-11-01 09:13:04.668779289  <IP_ADDRESS> - - [01/Nov/2024:10:13:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:13:19.802395754  10:13:19.802 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:39330->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:13:25.033983369  10:13:25.033 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:34196->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:13:30.152213809  [2024-11-01 10:13:30] frigate.video                  ERROR   : cam_one: Unable to read frames from ffmpeg process.
2024-11-01 09:13:30.152500422  [2024-11-01 10:13:30] frigate.video                  ERROR   : cam_one: ffmpeg process is not running. exiting capture thread...
2024-11-01 09:13:32.103771712  [2024-11-01 10:13:32] watchdog.cam_one            ERROR   : Ffmpeg process crashed unexpectedly for cam_one.
2024-11-01 09:13:32.103983880  [2024-11-01 10:13:32] watchdog.cam_one            ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-01 09:13:32.104801441  [2024-11-01 10:13:32] ffmpeg.cam_one.detect       ERROR   : [swscaler @ 0x55a27c9210] deprecated pixel format used, make sure you did set range correctly
2024-11-01 09:13:49.127416664  <IP_ADDRESS> - - [01/Nov/2024:10:13:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:13:49.792781096  10:13:49.792 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:37192->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:13:54.937580403  10:13:54.937 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:60376->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:14:00.097239183  10:14:00.097 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:60392->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:14:00.138743617  [2024-11-01 10:14:00] frigate.video                  ERROR   : cam_one: Unable to read frames from ffmpeg process.
2024-11-01 09:14:00.139030267  [2024-11-01 10:14:00] frigate.video                  ERROR   : cam_one: ffmpeg process is not running. exiting capture thread...
2024-11-01 09:14:02.120141741  [2024-11-01 10:14:02] watchdog.cam_one            ERROR   : Ffmpeg process crashed unexpectedly for cam_one.
2024-11-01 09:14:02.120146667  [2024-11-01 10:14:02] watchdog.cam_one            ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-01 09:14:02.120148649  [2024-11-01 10:14:02] ffmpeg.cam_one.detect       ERROR   : [swscaler @ 0x55930ca930] deprecated pixel format used, make sure you did set range correctly
2024-11-01 09:14:04.712137848  <IP_ADDRESS> - - [01/Nov/2024:10:14:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:15:04.760361824  <IP_ADDRESS> - - [01/Nov/2024:10:15:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:15:49.133808059  <IP_ADDRESS> - - [01/Nov/2024:10:15:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:16:04.805939835  <IP_ADDRESS> - - [01/Nov/2024:10:16:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:17:04.849952791  <IP_ADDRESS> - - [01/Nov/2024:10:17:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:17:49.138577748  <IP_ADDRESS> - - [01/Nov/2024:10:17:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:18:04.894211361  <IP_ADDRESS> - - [01/Nov/2024:10:18:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:19:04.938186870  <IP_ADDRESS> - - [01/Nov/2024:10:19:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:19:49.143458712  <IP_ADDRESS> - - [01/Nov/2024:10:19:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:20:04.980824964  <IP_ADDRESS> - - [01/Nov/2024:10:20:04 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:21:05.025290335  <IP_ADDRESS> - - [01/Nov/2024:10:21:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:21:49.146511259  <IP_ADDRESS> - - [01/Nov/2024:10:21:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:22:05.070564761  <IP_ADDRESS> - - [01/Nov/2024:10:22:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:23:05.115780000  <IP_ADDRESS> - - [01/Nov/2024:10:23:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:23:49.149472527  <IP_ADDRESS> - - [01/Nov/2024:10:23:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:24:05.163761129  <IP_ADDRESS> - - [01/Nov/2024:10:24:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:25:05.205943477  <IP_ADDRESS> - - [01/Nov/2024:10:25:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:25:49.152958349  <IP_ADDRESS> - - [01/Nov/2024:10:25:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:26:05.250343449  <IP_ADDRESS> - - [01/Nov/2024:10:26:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:27:05.295353238  <IP_ADDRESS> - - [01/Nov/2024:10:27:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:27:21.729826185  10:27:21.729 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:42082->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:27:26.897942330  10:27:26.897 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="read tcp <IP_ADDRESS>:51312->cam_one_ip:554: i/o timeout" url=rtsp://admin:my_password@cam_one_ip:554/cam/realmonitor?channel=1&subtype=1
2024-11-01 09:27:32.079601308  [2024-11-01 10:27:32] frigate.video                  ERROR   : cam_one: Unable to read frames from ffmpeg process.
2024-11-01 09:27:32.079847862  [2024-11-01 10:27:32] frigate.video                  ERROR   : cam_one: ffmpeg process is not running. exiting capture thread...
2024-11-01 09:27:32.191265177  [2024-11-01 10:27:32] watchdog.cam_one            ERROR   : Ffmpeg process crashed unexpectedly for cam_one.
2024-11-01 09:27:32.191271140  [2024-11-01 10:27:32] watchdog.cam_one            ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-11-01 09:27:32.191273659  [2024-11-01 10:27:32] ffmpeg.cam_one.detect       ERROR   : [swscaler @ 0x559e1398f0] deprecated pixel format used, make sure you did set range correctly
2024-11-01 09:27:49.157209913  <IP_ADDRESS> - - [01/Nov/2024:10:27:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:28:05.339994111  <IP_ADDRESS> - - [01/Nov/2024:10:28:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:29:05.383378752  <IP_ADDRESS> - - [01/Nov/2024:10:29:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:29:49.161358998  <IP_ADDRESS> - - [01/Nov/2024:10:29:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:30:05.427135631  <IP_ADDRESS> - - [01/Nov/2024:10:30:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:31:05.470004684  <IP_ADDRESS> - - [01/Nov/2024:10:31:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:31:49.165479203  <IP_ADDRESS> - - [01/Nov/2024:10:31:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-01 09:32:05.513512899  <IP_ADDRESS> - - [01/Nov/2024:10:32:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:33:05.559283273  <IP_ADDRESS> - - [01/Nov/2024:10:33:05 +0100] "" 400 0 "-" "-" "-"
2024-11-01 09:33:49.178497435  <IP_ADDRESS> - - [01/Nov/2024:10:33:49 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"

Looks like the camera connection is timing out

Damn, is there anything I could do? Thank you Nick for helping me out :)

There are things to try like increasing timeout

Which I can change by using this from what I found in the documentation. Is that right?
ffmpeg:
  retry_interval: 30

De : Nicolas Mowen @.>
Envoyé : vendredi 1 novembre 2024 19:31
À : blakeblackshear/frigate-hass-integration @.>
Cc : Mathieu Gimenez @.>; Author @.>
Objet : Re: [blakeblackshear/frigate-hass-integration] Error fetching information from http://ccab4aaf-frigate-fa:5000/api/stats (Issue #754)
There are things to try like increasing timeout
—
Reply to this email directly, view it on GitHubhttps://github.com/blakeblackshear/frigate-hass-integration/issues/754#issuecomment-2452378757, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOK7FD6JHZFJO3SSMD5JKLDZ6PCJBAVCNFSM6AAAAABQ7HN5OOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGM3TQNZVG4.
You are receiving this because you authored the thread.

As a #timeout on the go2rtc streams

Ok, it seems to work for the moment. However, I still get the error log in HA when I restart Frigate addon:
This error originated from a custom integration.

Logger: custom_components.frigate
Source: helpers/update_coordinator.py:386
integration: Frigate (documentation, issues)
First occurred: 9:57:09 PM (1 occurrences)
Last logged: 9:57:09 PM

Error fetching frigate data:

This error originated from a custom integration.

Logger: custom_components.frigate.api
Source: custom_components/frigate/api.py:259
integration: Frigate (documentation, issues)
First occurred: 9:22:58 PM (4 occurrences)
Last logged: 9:57:14 PM

Error fetching information from http://ccab4aaf-frigate-fa:5000/api/stats: Cannot connect to host ccab4aaf-frigate-fa:5000 ssl:default [None]
Error fetching information from http://ccab4aaf-frigate-fa:5000/api/stats: 500, message='Internal Server Error', url='http://ccab4aaf-frigate-fa:5000/api/stats'

And in the starting process in the Frigate addon log:
s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service certsync-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2024-11-05 20:57:12.774703219  [INFO] Preparing Frigate...
2024-11-05 20:57:12.777508305  [INFO] Starting NGINX...
2024-11-05 20:57:12.788014468  [INFO] No TLS certificate found. Generating a self signed certificate...
2024-11-05 20:57:12.870975463  [INFO] Preparing new go2rtc config...
2024-11-05 20:57:12.878396992  [INFO] Starting Frigate...
2024-11-05 20:57:12.914499329  [INFO] Got IP address from supervisor: my_IP
2024-11-05 20:57:12.956384093  [INFO] Got WebRTC port from supervisor: 8555
2024-11-05 20:57:13.448408697  [INFO] Starting go2rtc...
2024-11-05 20:57:13.541152028  21:57:13.541 INF go2rtc platform=linux/arm64 revision=b2399f3 version=1.9.2
2024-11-05 20:57:13.541207341  21:57:13.541 INF config path=/dev/shm/go2rtc.yaml
2024-11-05 20:57:13.541922210  21:57:13.541 INF [rtsp] listen addr=:8554
2024-11-05 20:57:13.542038484  21:57:13.541 INF [api] listen addr=:1984
2024-11-05 20:57:13.542262774  21:57:13.542 INF [webrtc] listen addr=:8555/tcp
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
2024-11-05 20:57:14.218622771  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2024-11-05 20:57:14.324741484  2024/11/05 21:57:14 [error] 173#173: *2 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://<IP_ADDRESS>:5001/auth", host: "ccab4aaf-frigate-fa:5000"
2024-11-05 20:57:14.324748688  2024/11/05 21:57:14 [error] 173#173: *2 auth request unexpected status: 502 while sending to client, client: <IP_ADDRESS>, server: , request: "GET /api/stats HTTP/1.1", host: "ccab4aaf-frigate-fa:5000"
2024-11-05 20:57:14.335159206  <IP_ADDRESS> - - [05/Nov/2024:21:57:14 +0100] "" 400 0 "-" "-" "-"
2024-11-05 20:57:14.810469313  [2024-11-05 21:57:14] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-11-05 20:57:14.810601105  [2024-11-05 21:57:14] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-11-05 20:57:14.810688029  [2024-11-05 21:57:14] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-11-05 20:57:14.839259825  [2024-11-05 21:57:14] frigate.util.config            INFO    : frigate config does not need migration...
2024-11-05 20:57:15.217165776  [2024-11-05 21:57:15] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2024-11-05 20:57:15.256750204  [2024-11-05 21:57:15] peewee_migrate.logs            INFO    : Starting migrations
2024-11-05 20:57:15.257730806  [2024-11-05 21:57:15] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-11-05 20:57:15.293147575  [2024-11-05 21:57:15] frigate.app                    INFO    : Recording process started: 378
2024-11-05 20:57:15.293153816  [2024-11-05 21:57:15] frigate.app                    INFO    : Recording process started: 387
2024-11-05 20:57:15.295436232  [2024-11-05 21:57:15] frigate.app                    INFO    : go2rtc process pid: 105
2024-11-05 20:57:15.340760312  [2024-11-05 21:57:15] detector.coral                 INFO    : Starting detection process: 407
2024-11-05 20:57:15.356220131  [2024-11-05 21:57:15] frigate.app                    INFO    : Output process started: 410
2024-11-05 20:57:15.496418471  [2024-11-05 21:57:15] frigate.app                    INFO    : Camera processor started for cam_mazot: 438
2024-11-05 20:57:15.496432563  [2024-11-05 21:57:15] frigate.app                    INFO    : Camera processor started for cam_chalet: 439
2024-11-05 20:57:15.514197650  [2024-11-05 21:57:15] frigate.app                    INFO    : Capture process started for cam_two: 447
2024-11-05 20:57:15.533291995  [2024-11-05 21:57:15] frigate.app                    INFO    : Capture process started for cam_one: 455
2024-11-05 20:57:17.722750571  2024/11/05 21:57:17 [error] 172#172: *4 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://<IP_ADDRESS>:5001/auth", host: "<IP_ADDRESS>:5000"
2024-11-05 20:57:17.722775089  2024/11/05 21:57:17 [error] 172#172: *4 auth request unexpected status: 502 while sending to client, client: <IP_ADDRESS>, server: , request: "GET /api/version HTTP/1.1", host: "<IP_ADDRESS>:5000"
2024-11-05 20:57:18.015741292  [2024-11-05 21:57:15] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2024-11-05 20:57:18.022648430  [2024-11-05 21:57:18] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2024-11-05 20:57:22.773154956  [INFO] Starting go2rtc healthcheck service...
2024-11-05 20:57:31.070794441  <IP_ADDRESS> - - [05/Nov/2024:21:57:31 +0100] "GET / HTTP/1.1" 200 2651 "-" "HomeAssistantSupervisor/2024.10.3 aiohttp/3.10.10 Python/3.12" "-"
2024-11-05 20:58:14.383640767  <IP_ADDRESS> - - [05/Nov/2024:21:58:14 +0100] "" 400 0 "-" "-" "-"
2024-11-05 20:59:14.429939802  <IP_ADDRESS> - - [05/Nov/2024:21:59:14 +0100] "" 400 0 "-" "-" "-"

Tengo el mismo problema desde la ultima Actualizacion de HA, llevaba funcionando mas de 1 año sin problemas.


Where to put 'auth' => [ 'jwt' => 'Dingo\Api\Auth\Provider\JWT', ] ? Laravel 5.3

Hi, right now I have this problem where I can generate a token just fine, but I get this message Failed to authenticate because of bad credentials or an invalid authorization header.
I searched a little and found out people got this problem fixed by adding
'auth' => [ 'jwt' => 'Dingo\Api\Auth\Provider\JWT', ]
in config/api.php, but I don't have this file.
I'm using Laravel 5.3
Thanks for helping.

https://github.com/dingo/api#support


Curatory Group Changes

I have noticed that when a curatory group is deleted in the GOKb packages, those changes are not automatically reflected in LAS:eR in ALL PACKAGES.

It seems that changes made for the curatory groups do not automatically trigger a "last updated" - it would be necessary, however, that changes within the curatory groups trigger such an update. Otherwise, the information regarding the packages in LAS:eR would be outdated and of little use because it is not a reliable information.

It seems that the inner-GOKb-Sync (so the mirroring) is not considering curatory groups ...

It seems that changes made for the curatory groups do not automatically trigger a "last updated"

Fixed in v8.5.0 (#141 ). Both systems need to be running the new version for this to work, and the latest version of sync scripts has to be used.

When can we expect a deploy of 8.5.0?

Gokb.org is already running on 8.5.0, phaeton should be following shorty I imagine.


Refresh UI crashed in iOS 9

When refreshing the image view's image when the view is not showing, I used
[view performSelectorOnMainThread:@selector(setImage:) withObject:[UIImage imageWithData:imageData] waitUntilDone:NO];
But still crashed, Xcode reports:
This application is modifying the autolayout engine from a background thread, which can lead to engine corruption and weird crashes.  This will cause an exception in a future release.

dispatch_async(get_main_queue()...


Revise documentation covering usage together with IHttpClientFactory

I was reading through the documentation that describes how to use HttpClientInterception together with IHttpClientFactory, and I found the recommended solution to be a bit misleading and quite over-engineered, especially having to handroll your own implementation of IHttpMessageHandlerBuilderFilter.
I was able to make it work just by doing this:
var builder = new HttpRequestInterceptionBuilder();

builder.Requests()
       .ForGet()
       .ForAnyHost()
       .Responds()
       .WithStatus(HttpStatusCode.OK)
       .RegisterWith(options);

var services = new ServiceCollection();
services.AddHttpClient("myclient")
        .AddHttpMessageHandler(options.CreateHttpMessageHandler));    // 👈🏻 This line is all you need

var serviceProvider = services.BuildServiceProvider();

var httpClientFactory = serviceProvider.GetRequiredService<IHttpClientFactory>();
var client = httpClientFactory.CreateClient("myclient");

Perhaps the documentation could be updated to reflect this?

Thanks for raising this!
I can see your point, but I think your example here applies to a different use-case than the example in the readme.
In your case, you'd apply the message handler to your one client called "myclient". In the example IHttpMessageHandlerBuilderFilter is used to ensure that the interception is applied to all clients instantiated throughout the application via the client factory.
In .NET 8, a more similar example to what we're currently showing might be
var builder = new HttpRequestInterceptionBuilder();

builder.Requests()
       .ForGet()
       .ForAnyHost()
       .Responds()
       .WithStatus(HttpStatusCode.OK)
       .RegisterWith(options);

var services = new ServiceCollection();
services.ConfigureHttpClientDefaults()
    .ConfigureAdditionalHttpMessageHandlers((handlerList, _) => handlerList.Add(options.CreateHttpMessageHandler()));
services.AddHttpClient("myclient");

var serviceProvider = services.BuildServiceProvider();

var httpClientFactory = serviceProvider.GetRequiredService<IHttpClientFactory>();
var client = httpClientFactory.CreateClient("myclient");

However, we currently target older TFM's that wouldn't support this, so I think our documentation should reflect that for now.

The advantage of IHttpMessageHandlerBuilderFilter is that it can be registered once and it will hook-up interception for all usages of IHttpClientFactory without the tests having to know any of the implementation details of how you use it in the application under test. It also plays nicely with the case where there are lots of other delegating handlers configured, as you can (mostly) ensure that the interception runs last, so your tests still cover the other handlers, rather than causing them to be short-circuited by the interception.
If you have an application where you have multiple named HTTP clients and wish to integration test them, using the approach in your original comment requires you to repeat the setup for each of those clients in order to intercept their calls, as well as knowing (and then repeating) all of the client registration calls in the tests.
For a concrete example of the above case, in one of my open source projects I configure HTTP clients for each OAuth provider I have, which in this case is 5-7 depending on the application's configuration. All of that detail is hidden from the integration test, which intercept the calls for all of them (and other usages of HttpClient not to do with OAuth) in these 3 lines of code using the IHttpMessageHandlerBuilderFilter approach. For a more extreme example, there's this project - we maintain over 90 OAuth providers, and all their HTTP calls are intercepted with these 2 lines of code.
In a simple application though, you're right, it could be done the other way if you were doing some unit testing where you just want a simple HttpClient that intercepts the calls.
We'd accept a pull request that suggests the approach you give as an alternative for a simple case like you describe, but I still feel that the current approach is the best overall recommendation as for just a few lines of code to add to your tests, it's the simplest way to integrate the library into an existing test suite.

Thanks both of you for providing your opinions and knowledge on the subject, I feel much wiser now on how everything works together and the advantages of using the filter when working with a collection of tests.

@martincostello Just a question. When using a shared fixture/collection like shown in the example, how does HttpClientInterceptor keep the registrations apart so that each test-specific registration doesn't conflict with the others? Especially as tests are run in parallell in each test class?

It doesn't by default, but you can use a scope to constrain the lifetime of the matches where the matches can't otherwise be discriminated by more specific matches (e.g. looking at a header, a part of the path, etc.).


Frontend - connect views with mock ui

Main pages that actually need mockups:

[x] Main page - paginated list of threads
[x] Thread page - paginated list of posts

[ ] Each post should have an associated edit button, only visible for the post's author
[ ] Each post should have an associated delete post buttons, visible only for thread's moderators and post's author
[ ] Each post should have an associated ban user thread-wide button, only visible for the thread's moderators
[ ] Each post should have an associated ban user site-wide button, only visible for the administrators

[ ] Login page
[x] Create thread page
[x] Create post page
[ ] Thread management page - accessible from the thread page for moderators, where they can manage banned users and appoint/remove moderators
[ ] Global management page - where administrators can manage banned users

Think of a traditional forum, here are some examples:

https://www.skyscrapercity.com/
https://forum.paradoxplaza.com/forum/forums/cities-skylines.859/

Main page was added in #128

Basic thread view, create thread and create post pages added in #149

Login more-or-less completed in #168

Voting & editing added in #191

Global management page, site wide ban user button - scrapped, will be handled through Keycloack UI

User banning and thread management added in #205, this concludes the UI.


Inconsistent sorting - make more obvious

Thinking of adding a sort parameter to these functions to make it more obvious to what's happening under the hood.
One issue is that when sorting, the order of the groups are changing. So maybe make this optional.

Switched from using data.apply(lambda x: x) to data.obj.copy(). The former sorts groups alphabetically. The latter maintains the order of the original data.

Next on my list is to tackle these. Make them optional with sort = True as default.
 df.sort_values(by=[*group_names, date_column], inplace=True)


[5.6] Ability to set custom encryption key

This PR will allow developers to use "external" encryption key instead of key from env file. For example developer could allow his app's users to encrypt their data by their own encryption key.
$key = random_bytes(32);

$encrypted = Crypt::key($key)->encrypt('foo');
$data = Crypt::key($key)->decrypt($encrypted);

This is best way I found, there is no impact on people's apps.

You should manually construct the Encrypter yourself. Relying on the application's key configuration, which you might want to change independently from this, for a different key is probably not a good idea unless the requirement on it is made explicit.
Imo, it would be better to be explicit about which key type you are using. In which case you can use: new Encypter($key, "AES-256-CBC")
If you must to rely on the app's config, this would also work: new Encypter($key, config("app.cipher"))
I like the idea of Crypt::key but I think it's hiding a piece of config for little benefit.
These are just my two cents. ¯_(ツ)_/¯

See @thecrypticace comments.


PageFind search gives not results for emojis

When using the search bar, there is no results for any emojis. My top emoji is 🔥 and I wanted to see the list of tweets containing it but it gives me "No results for 🔥".
@zachleat we seem to share the love for the use of emojis in content, and I'd love to be able to enable the indexation of emojis in my archive... if that's an option.
I suspect this is a PageFind issue, not a tweetback issue. If confirmed I can go point that out there.

@Julianoe thanks for opening the issue. I can confirm it also doesn't work in my own archive.
I couldn't find any issue in PageFind repo about emojis: https://github.com/CloudCannon/pagefind/issues?q=is%3Aissue+emoji
It doesn't work either on PageFind's demo: https://xkcd.pagefind.app/
A search for 🌋 should at least show this page: https://xkcd.pagefind.app/comics/2017-11-24-emoji-sports/
So I guess the best would be to open an issue in PageFind's repo.

👍 All right, I did not see that demo page to test it.
I'll go open an issue there then.

👋 Hey all!
Pagefind v1.0.0 now has emoji support ✨ 👾 🚀 ❤

Thanks a lot @bglw ! 🙏


Logging calls with expressions don't work

Example code:
var now = DateTime.Now;
_logger.LogInformation($"property: {now.Day}");
var day = now.Day;
_logger.LogInformation($"simple: {day}");

Expected output:
property: 24
simple: 24

Actual output:
property: {now.Day}
simple: 24

The property access expressions could also be for more levels, that should also be supported.
The last step could also be a method call instead of a property access.

This behavior depends on the underlying logging provider. I guess you use Serilog which requires the names to be valid C# identifiers.
The issues is that on one hand the expression can be anything, and on the other hand the expression can be transformed in different ways. For example, we can transform now.Day into Day or nowDay or even now_Day. That's why ISLE does not convert them by default, but allows the user to provide a custom delegate for the name conversion (see the end of the section Custom Argument Names).
At the moment, there are no conversions provided out-of-the-box, but I might provide some in the future versions.

Yes, I'm using Serilog. Thanks for the explanation.
I've fixed it in my code by using
config.WithNameConverter(name => name.Replace(".", String.Empty, StringComparison.Ordinal));
I strongly suggest to add this as a default behavior so that popular logging frameworks work out of the box. Because that's a really annoying bug if you only use such extressions rarely and then only notice the problem when you already need the logged values 😄

I've added this functionality in version 1.2 as a part of Isle.Converters.ValueNameConverters class. However, it is not enabled by default, so you still need to add the converter manually:
IsleConfiguration.Configure(b => b.WithNameConverter(ValueNameConverters.SerilogCompatible()));

Works fine, thanks.
I suggest to add this to the readme if it won't be enabled by default.


Azure.Core README.md Response sample does not dispose the response objects

Describe the bug
None of the Disposable objects are disposed of in the Azure.Core README.md. Both the Response here, Response<T> here, and Stream implement IDisposable.
Expected behavior
Dispose of all Disposable objects.  This will prevent any memory leaks.
Screenshots

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

This sample is correct, while the types do implement IDisposable none of the usages you've highlighted strictly require disposal in the current implementation.


Reflect removed from generated code

When generating a file which utilizes reflect, I noticed that reflect gets strips out of my import list.
Generated file
Source file

So it looks as though the imports library (stdlib) is not inserting reflect during it's fixImport func. That's very strange..

I got around this by creating a separate utilities library where code generation wasn't touching. It's a lame work-around, but it looks like it's out of our control right now.
I'm going to leave this open because I'd like to get your thoughts on this situation.

@itsmontoya One of the links are broken and I'm not sure whether the other one is still the same as the time you wrote the post. So I can not check what exactly has gone wrong. Do you mean you had imported reflect in your source and genny has not included it in the generated code?


Direct memory allocations and deallocations should communicate via Bits.reserveMemory() and Bits.unreserveMemory()

It's essential when app does drirect memory allocations via both ByteBuffers and Memory, to let ByteBuffer's allocation path "know" that there are not enough direct memory, if it's allocated via Memory, and call System.gc() if needed, etc. See the code of Bits.java.

I don't think this will work or may require more intrusive rewriting of Bits code that I'm not sure I want to undertake.
Bits.reserveMemory(long size, **int cap**) and Bits.unreserveMemory(long size, **int cap**) are intended for tracking the memory reserved by DirectByteBuffers and both methods limit the capacity for any one request to Integer.MAX_VALUE.    The off-heap space that these methods track against is specified by the -XX:MaxDirectMemorySize=<size> JVM arg.
I have a hunch that the Java folks implemented this tracking mechanism this because they wanted the space allocated by DirectByteBuffers to be independent of the heap and they didn't want users to be forced to close() DBBs.   So the JVM tracks the allocated DBBs using a ReferenceQueue and tracks the count and memory usage in Bits.  I presume this is a courtesy so that a user will get a "friendly" exception with a trace rather than causing an out-of-memory JVM crash, which could be hard to debug.
The irony here is that I looked at some of our back-end Druid systems to see how
-XX:MaxDirectMemorySize=<size> is being used.  Surprise! Most of these systems have it set to huge values like 100TB!  So this Bits tracking mechanism is effectively not being used and would never provide any warnings!
One of the important goals of Memory was to be able to allocate regions of off-heap memory larger than 2GB, and we already have tests to ensure that that works.  Attempting the simple approach of calling Bits.reserveMemory(...) and Bits.unreserveMemory(...) will limit our direct allocations to < 2GB.
The tracking counters that Bits uses are all AtomicLongs.  So, in theory, we could implement our own reserveMemory and unreserveMemory that would update those counters directly bypassing the Bits methods.  But why?  We already provide AutoCloseable and encourage engineers to proactively close their direct Memory objects or use TWR blocks, rather than waiting for the JVM to eventually find the lost reference and close it.   So, yes, using Memory with large off-heap allocations will require more discipline from users.
Meanwhile, the off-heap memory reserved via MappedByteBuffers and FileChannel.map() does not use this tracking mechanism that I can find.  So why should we?

Bits.reserveMemory(long size, int cap) and Bits.unreserveMemory(long size, int cap) are intended for tracking the memory reserved by DirectByteBuffers and both methods limit the capacity for any one request to Integer.MAX_VALUE.

Since those methods just virtually reserve and unreserve memory, but don't do actual allocation and deallocation, I think when we allocate a direct Memory larger than Integer.MAX_VALUE, we could "split" the size and call reserveMemory() several times one after another.

Realistically we cannot make even Druid a walled garden, where only Memory is used. Druid uses Netty, that uses it's own direct memory framework. BTW I discovered this issue (#62) when I stumbled upon the Netty code that does call Bits.reserveMemory() and unreserveMemory(). So Netty participates this XX:MaxDirectMemorySize thing.

The irony here is that I looked at some of our back-end Druid systems to see how
-XX:MaxDirectMemorySize= is being used. Surprise! Most of these systems have it set to huge values like 100TB! So this Bits tracking mechanism is effectively not being used and would never provide any warnings!

It's interesting, but I don't think we could assume that everybody should follow this practice. Druid's docs about configuration of historical and realtime nodes include recommendations about how to set XX:MaxDirectMemorySize. Also your colleague @akashdw shared a configuration recently that seems to configure XX:MaxDirectMemorySize to about 130 GB.

Meanwhile, the off-heap memory reserved via MappedByteBuffers and FileChannel.map() does not use this tracking mechanism that I can find. So why should we?

This is interesting, thanks for noting. As an afterthought, I think it's a reasonable decision by JDK authors to include tracking of only direct, but not mapped memory. Applications generally have much better understanding, where and how they map files into memory, than just allocate direct memory. E. g. in Druid, we know that we map the segment files into memory, and that's it. We don't expect Netty or JDK's own HTTP library, etc. to map files into memory, but we cannot say anything about how do they use direct ByteBuffers. <Xmx + XX:MaxDirectMemorySize + total size of segment files on a Druid historical node> should be a reliable upper bound of total memory, consumed by a Druid historical process.

This is interesting, thanks for noting. As an afterthought, I think it's a reasonable decision by JDK authors to include tracking of only direct, but not mapped memory. Applications generally have much better understanding, where and how they map files into memory, than just allocate direct memory. E. g. in Druid, we know that we map the segment files into memory, and that's it. We don't expect Netty or JDK's own HTTP library, etc. to map files into memory, but we cannot say anything about how do they use direct ByteBuffers. <Xmx + XX:MaxDirectMemorySize + total size of segment files on a Druid historical node> should be a reliable upper bound of total memory, consumed by a Druid historical process.

... The conclusion of this part is that we should adapt this policy too, by calling Bits.reserveMemory() only on direct Memory allocation, but not file mapping.

Now that this is implemented aren't the currentDirectMemoryAllocations/Allocated fields in ResourceState duplicates of what we are tracking with NioBits?

I would expose both, more visibility of such things is always better.
BTW now the "count of allocations" could be imprecise in NioBits, because of chunking.

True.

I'm not sure what we could do about this.  We could track the extra counts due to chunking and subtract the extra from the hidden count field.  But that makes me nervous.
I'm not sure how the count field is used inside the JVM or how important it is.

It should be ok to have this "chunked number" and it's even more reasonable in some sense. Like we are allocating several ByteBuffers (max of 1GB), adjacent to each other in the address space.


Device registration type

Could you explain exactly what type of registration require?
Could be one of:
Azure Ad Join
Azure Ad registered
Azure Hybrid Join

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

ID: d87ba3ab-d8a7-d038-2f7d-886bed956394
Version Independent ID: cb2ea1fd-6a0d-8656-0bb4-0528c65ea03f
Content: Configure Device Registration for Hybrid Azure AD joined key trust Windows Hello for Business - Windows security
Content Source: windows/security/identity-protection/hello-for-business/hello-hybrid-key-trust-devreg.md
Product: m365-security
GitHub Login: @Gitprakhar13
Microsoft Alias: prsriva

I agree, it's unclear if it supports domain joined machines with aad registration, or if hybrid join is required.

Hi, thanks on the main page you say:
Device registration type: Azure AD join, Hybrid Azure AD join

@msbemba

This has been addressed by recent documentation updates


Incorrect authentication credentials results in server error

When a user enters the wrong username and password for code authentication, the response should be incorrect credentials rather then server error.

Which authenticator is used? Marketplace?

yes, currently when the user logins with invalid credentials null is returned:
logger.error("Failed to authenticate user '" + id + "' with LDAP");
return null;

This is also similar to the default authenticator:
if(!match) return null;

I will take a look this weekend. Thanks for bringing it up.

@auahmed If the credential is not matched, then a null account object is returned and in the basic authentication, the popup window will show up again. This repeats several times depending on the OS configuration and then fail the basic authentication. The Marketplace is using the form and the flow might be different. What is the behavior in your app?

The flow of the app is that the user credentials are passed in the headers to oauth2 as base64-encoded.
As the application is blocking the popup provided by light-oauth2 to use its own form rather, we get an internal server error rather then the popup window to try again. This way it becomes difficult for the user to differentiate if incorrect credentials were provided or any other issue.

Do you have a form to collect the username and password? Is it possible to just customize the marketplace auth? I am working on the light-portal now and will pick up the post authentication soon.

Will check into seeing if its possible to just update the marketplace auth


Add *propertiesOf names to iterators

Moves iterators to being called *propertiesOf as well as making sure they return properties instead of certificates.

Can you also update the API review folder with the latest API extraction?


Support for Xcode 13.0 (13A233)

Updated Xcode to 13 (stable version from App Store). Stuck at this compile error. Could you please help me out? Followed this thread #310 as well. Tried with the latest tag - 0.0.9. Still, doesn't solve for the particular Xcode version, which I am in.

@SagarUnagar I'm on the App Store version as well, you should update to master.

@SagarUnagar I also just confirmed by building it on Xcode 13, closing this ticket. Please reopen if this issue persists.

Hi Vatsal, Thank you for your response.
Issue is still persisted. I also tried using master but still getting same error.

@SagarUnagar which file is it failing on for you? Could you give me the exact file & line number?

Hi @vmanot
Error is in Sources/Intermodular/Helpers/UIKit/UIViewControllerLifecycleEvent.swift at line 77.

@SagarUnagar no idea why this is causing an issue. It's not even used in SwiftUIX (was unfinished code), so I've straight up removed it. I think this may've been a red herring and some other framework/dependency in your project could be causing issues though.


Fix: made footer center aligned

Issue that this pull request solves
Closes: #566
Proposed changes
made footer center aligned
Brief description of what is fixed or changed
made footer center aligned
Types of changes
style fix
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update (Documentation content changed)
[x] Other (please describe):

Checklist
Put an x in the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes does not break the current system and it passes all the current test cases.

Screenshots

Other information
Not needed
Any other information that is important to this pull request

Thanks for pointing it out @Kajol-Kumari working on it.

Thanks for pointing it out @Kajol-Kumari working on it.

Hey @nlok5923 I can still see the icon's grid distorted, can you please check it on your end and fix it?


Encapsulate operations

Encapsulate the get and set operations

Hi! Thanks for your interest in this little library. Sadly, I have to say no to your suggestions. This gem is a wrapper that adds Redis Cluster support to Redic, so these suggestions actually should be applied to that gem and not this one.
Note that also these definitions don't fully support Redis commands, particularly SET, as it doesn't support the EX, PX, NXandXX` flags.
Having said that, both gems are aimed to be as minimalist as possible, and these methods don't seem to add any extra value other than save some typing.
Thanks again for reaching out!

Hi @inkel, I understand! No problem!
Cheers!


channels: 23.11 is stable, 23.05 is deprecated

@vcunat

Deployed some time ago; I just forgot to merge afterwards.


Indicate that PR is automatic in title and body

On automatic releases, add [Automatic] to title and a message to the body of the PR
CSDK-424

This is great 👍🏻


new List.filled(rows, new List.filled(column, -1)) does not create matrices properly

The code
Initialising a 2d matrix:
int rows, columns;
<List<List<int>>> matrix;

rows = 4;
columns = 7;
matrix = new List.filled(rows, new List.filled(column, -1))

print(matrix);

Prints the following list:
[[-1, -1, -1, -1, -1, -1, -1], [-1, -1, -1, -1, -1, -1, -1], [-1, -1, -1, -1, -1, -1, -1], [-1, -1, -1, -1, -1, -1, -1]]

Consider the following snippet:
...

matrix[1][2] = 0;

print(matrix);

Expected output
You would expect the cell at in the 2nd row and 3rd column to has a value of 0:
[[-1, -1, -1, -1, -1, -1, -1], [-1, -1, 0, -1, -1, -1, -1], [-1, -1, -1, -1, -1, -1, -1], [-1, -1, -1, -1, -1, -1, -1]]

Actual output
It actually changes all the rows to have the same value in their 3rd column:
[[-1, -1, 0, -1, -1, -1, -1], [-1, -1, 0, -1, -1, -1, -1], [-1, -1, 0, -1, -1, -1, -1], [-1, -1, 0, -1, -1, -1, -1]]

Background
I found this bug while competing in the Google # Hashcode finals. During the competition we decided to switch to C++ because we found it a bit more reliable at this moment in time. We do love the Dart lang and hope we'll be able to submit a solution with it at Google # Hashcode in 2019.
Environment
Dart: v1.24.3
MacOS: v10.13.4

From documentation for List.filled:

All entries in the returned list point to the same provided fill value. That all items in the list are the same object is observable when the given value is a mutable object.
var shared = new List.filled(3, []);
shared[0].add(499);
print(shared);  // => [[499], [499], [499]]

You may use List.generate to create a new object for each position in in the list.
var unique = new List.generate(3, (_) => []);
unique[0].add(499);
print(unique); // => [[499], [], []]

https://api.dartlang.org/stable/1.24.3/dart-core/List/List.filled.html


[Question] How to get an operator-level profiling report？

❓ General Questions

I want to know the execution time of each operator in the process of prefill and decode. What should be done?
thanks

https://github.com/mlc-ai/mlc-llm/blob/main/python/mlc_llm/testing/debug_compare.py might help


PHOENIX-7015 Implementing CDCGlobalIndexRegionScanner: JSON Response for CDC

Implementing CDCGlobalIndexRegionScanner: JSON Response for CDC
This pull request introduces changes to the server-side CDCGlobalIndexRegionScanner, specifically focusing on capability to form JSON responses for Change Data Capture (CDC)

https://issues.apache.org/jira/browse/PHOENIX-7015

Closed in favor of PR #1813


[bug] Auto accessor fields are declared as regular properties in mixin abstract classes

🔎 Search Terms
abstract class mixin accessor field property declaration .d.ts ts(2611)
🕗 Version & Regression Information

This changed between versions ______ and _______
This changed in commit or PR _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _______

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.8.0-dev.20241203#code/PTAEAMEsDsBMFMAeA6WyAuBncpKdAObzTwBOAhuvLKAEYCeEWAxqALRvwC2k6AIvGYAbchXSQA9tADy0IfRwwIXemyGRaFUgoBQSAA4TS6UAmGj4ocrUzoKzE+cz4AQuUyWA3jtC+rzZnhnIysALlBoAFcuWjIAbh0AXz1EQ2NTQRFSSwAzSOgHSWhQHlhYIXgACgBlSP0yAH5w9Hp6iRzQNw8ASnDrW3sTEgB3UEru0ABeAD5Qbz8wiOjY0gTEhJBcLjSTTxLIMorQRNAc0gkuUAByFTUNLXorhIMjRxFnUAAxGHIhUCQqHB8KVylUJvM-OQAkFMCFyFNQAAmOK+TZYSqIgBsAEZsRMyOdSEkgA
💻 Code
// `index.d.ts` is generated by `tsc --emitDeclarationOnly` in `my-library`
declare abstract class Base {
    accessor a: number;
}
declare function middle(Super?: typeof Base): abstract new () => {
    a: number;
};
// import { middle } from 'my-library';
class Final extends middle() {
    accessor a = 2;  // ts(2611) error
}

🙁 Actual behavior
TS throws:
'a' is defined as a property in class '{ a: number; }', but is overridden here in 'Final' as an accessor. ts(2611)

but the library source code is:
export abstract class Base {
    accessor a = 1;
}

export function middle(Super = Base) {
    abstract class Middle extends Super {
    }
    return Middle;
}

🙂 Expected behavior
It has no type error while overrides auto accessor fields in sub classes of abstract mixins from 3rd-party libraries.
Additional information about the issue
This bug can be resolved if tsc generates .d.ts as shown below:
// `index.d.ts` is generated by `tsc --emitDeclarationOnly` in `my-library`
declare abstract class Base {
    accessor a: number;
}
declare function middle(Super?: typeof Base): abstract new () => {
-    a: number;
+    get a(): number;
+    set a(value: number);
};
// import { middle } from 'my-library';
class Final extends middle() {
    accessor a = 2;  // no error
}

https://www.typescriptlang.org/play/?ts=5.8.0-dev.20241203#code/PTAEAMEsDsBMFMAeA6WyAuBncpKdAObzTwBOAhuvLKAEYCeEWAxqALRvwC2k6AIvGYAbchXSQA9tADy0IfRwwIXemyGRaFUgoBQSAA4TS6UAmGj4ocrUzoKzE+cz4AQuUyWA3jtC+rzZnhnIysALlBoAFcuWjIAbh0AXz1EQ2NTQRFSSwAzSOgHSWhQHlhYIXgACgBlSP0yAH5w9Hp6iRzQNw8ASnDrW3sTEgB3UEru0ABeAD5Qbz9CeBNycfComPifPw9lyoA3ciFI+DXo2NJuhMSEkFwuNJNPEsgyitBE0BzSCS5QAHIVGoNFp6H8EgYjI4RM5QAAxGCHUBIKhwfClcpVCbzPzkAJBTAhchTUAAJjivluWEqJIAbABGOkTMjfUhJIA

I believe this is essentially a duplicate of https://github.com/microsoft/TypeScript/issues/44938 and https://github.com/microsoft/TypeScript/issues/58790


fixed lua error when area is zero size

Fixes cut-n-paste of "notes" maked by PickerExtended

Thanks!


Plugin Fails after Sanity Update

After running Sanity upgrade today, my compiling breaks on the plugin.
Error in ./node_modules/sanity-plugin-computed-field/node_modules/<EMAIL_ADDRESS>Module not found: Error: Can't resolve '@reach/utils/use-isomorphic-layout-effect' in '/Users/paddy/Documents/Projects/Afrofit/afrodata/node_modules/sanity-plugin-computed-field/node_modules/@sanity/ui/node_modules/@reach/auto-id/dist'
@ ./node_modules/sanity-plugin-computed-field/node_modules/<EMAIL_ADDRESS>2:0-86
<EMAIL_ADDRESS>@ ./node_modules/sanity-plugin-computed-field/lib/ComputedField.js
@ ./schemas/story_chapter.js
@ ./schemas/schema.js (part:@sanity/base/schema)
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>(part:@sanity/base/root)
<EMAIL_ADDRESS>(part:@sanity/base/sanity-root)
<EMAIL_ADDRESS>@ multi<EMAIL_ADDRESS>

hmm @afrofit - I'm testing with sanity 2.28.2, and things are working in my sample app.  I have tried every type of input
Can you try
rm -rf node_modules
yarn install # or npm install

My sample project dependencies:
    "@sanity/base": "^2.28.2",
    "@sanity/core": "^2.28.1",
    "@sanity/default-layout": "^2.28.2",
    "@sanity/default-login": "^2.28.2",
    "@sanity/desk-tool": "^2.28.2",
    "@sanity/eslint-config-studio": "^2.0.0",
    "@sanity/google-maps-input": "^2.28.2",
    "@sanity/vision": "^2.28.2",
    "eslint": "^8.6.0",
    "prop-types": "^15.7",
    "react": "^17.0",
    "react-dom": "^17.0",
    "react-icons": "^3.11.0",
    "sanity-plugin-computed-field": "^1.0.2",

Works great with "@sanity/base": "^2.30.1" ...thank you!

closing due to inactivity


[Extension] Add Collaborator Extension Point

Notes for Reviewers
This PR fixes #
This PR:

Adds new Collaborator Extension Point
Moves the prefs for un/activating Collaboration into the UserPrefs Extension so that its visible in Meshery UI at (/user/preferences)

Signed commits

[x] Yes, I signed my commits.

@senali-d, please understand that what you are creating is an extension point. The actual component will be remotely created, published, and loaded upon user sign-in. Please refer to other UI extension points as an example.

Have you reviewed the other UI extension points, @senali-d? Are you familiar with the approach - https://docs.meshery.io/extensibility/ui

@leecalcote Yes I'm reviewing other UI extension points and try to figure out it.

This PR is ready from my end

@senali-d
Once you are done with updating the loading animation component then lets merge this 👍

Docs has been updated for this new Collaborator Extension Point

@theBeginner86 Loading animation updated.

@theBeginner86 Loading animation updated.

Great!
Have you pushed the changes? I don't seem to see any new commit 😅

🚀 Preview for commit dcc2a34dd13d823917aa1cd9908122bee7da0c76 at: https://64d3f7eeafa90b0096ed4b81--meshery-docs-preview.netlify.app

Oh I miss it. Pushed now. 😅


Update: Introduction

This PR takes care of a bunch of updates related to documentation's Getting Started section and all sub-pages.
This PR takes care of Issue #358, #382, and #383.

https://github.com/amplication/docs/assets/3907745/4dfc8bbc-4433-44f3-9910-8134f0930e12
CC @GreenMachine01


vcpkg crash when upgrading

C:\vcpkg>vcpkg update
Using local portfile versions. To update the local portfiles, use `git pull`.
The following packages differ from their port versions:
        boost:x64-windows                1.82.0#1 -> 1.82.0#2
        boost-accumulators:x64-windows   1.82.0#1 -> 1.82.0#2
        boost-algorithm:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-align:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-any:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-array:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-asio:x64-windows           1.82.0#1 -> 1.82.0#3
        boost-assert:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-assign:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-atomic:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-beast:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-bimap:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-bind:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-build:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-callable-traits:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-chrono:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-circular-buffer:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-compatibility:x64-windows  1.82.0#1 -> 1.82.0#2
        boost-compute:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-concept-check:x64-windows  1.82.0#1 -> 1.82.0#2
        boost-config:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-container:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-container-hash:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-context:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-contract:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-conversion:x64-windows     1.82.0#1 -> 1.82.0#2
        boost-convert:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-core:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-coroutine:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-coroutine2:x64-windows     1.82.0#1 -> 1.82.0#2
        boost-crc:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-date-time:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-describe:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-detail:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-dll:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-dynamic-bitset:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-endian:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-exception:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-fiber:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-filesystem:x64-windows     1.82.0#1 -> 1.82.0#2
        boost-flyweight:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-foreach:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-format:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-function:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-function-types:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-functional:x64-windows     1.82.0#1 -> 1.82.0#2
        boost-fusion:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-geometry:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-gil:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-graph:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-hana:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-heap:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-histogram:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-hof:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-icl:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-integer:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-interprocess:x64-windows   1.82.0#1 -> 1.82.0#2
        boost-interval:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-intrusive:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-io:x64-windows             1.82.0#1 -> 1.82.0#2
        boost-iostreams:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-iterator:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-json:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-lambda:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-lambda2:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-leaf:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-lexical-cast:x64-windows   1.82.0#1 -> 1.82.0#2
        boost-local-function:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-locale:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-lockfree:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-log:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-logic:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-math:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-metaparse:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-modular-build-helper:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-move:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-mp11:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-mpl:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-msm:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-multi-array:x64-windows    1.82.0#1 -> 1.82.0#2
        boost-multi-index:x64-windows    1.82.0#1 -> 1.82.0#2
        boost-multiprecision:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-mysql:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-nowide:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-numeric-conversion:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-odeint:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-optional:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-outcome:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-parameter:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-parameter-python:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-pfr:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-phoenix:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-poly-collection:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-polygon:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-pool:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-predef:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-preprocessor:x64-windows   1.82.0#1 -> 1.82.0#2
        boost-process:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-program-options:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-property-map:x64-windows   1.82.0#1 -> 1.82.0#2
        boost-property-tree:x64-windows  1.82.0#1 -> 1.82.0#2
        boost-proto:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-ptr-container:x64-windows  1.82.0#1 -> 1.82.0#2
        boost-python:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-qvm:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-random:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-range:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-ratio:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-rational:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-regex:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-safe-numerics:x64-windows  1.82.0#1 -> 1.82.0#2
        boost-scope-exit:x64-windows     1.82.0#1 -> 1.82.0#2
        boost-serialization:x64-windows  1.82.0#1 -> 1.82.0#2
        boost-signals2:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-smart-ptr:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-sort:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-spirit:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-stacktrace:x64-windows     1.82.0#1 -> 1.82.0#2
        boost-statechart:x64-windows     1.82.0#1 -> 1.82.0#2
        boost-static-assert:x64-windows  1.82.0#1 -> 1.82.0#2
        boost-static-string:x64-windows  1.82.0#1 -> 1.82.0#2
        boost-stl-interfaces:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-system:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-test:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-thread:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-throw-exception:x64-windows 1.82.0#1 -> 1.82.0#2
        boost-timer:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-tokenizer:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-tti:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-tuple:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-type-erasure:x64-windows   1.82.0#1 -> 1.82.0#2
        boost-type-index:x64-windows     1.82.0#1 -> 1.82.0#2
        boost-type-traits:x64-windows    1.82.0#1 -> 1.82.0#2
        boost-typeof:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-ublas:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-uninstall:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-units:x64-windows          1.82.0#1 -> 1.82.0#2
        boost-unordered:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-url:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-utility:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-uuid:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-variant:x64-windows        1.82.0#1 -> 1.82.0#2
        boost-variant2:x64-windows       1.82.0#1 -> 1.82.0#2
        boost-vcpkg-helpers:x64-windows  1.82.0#1 -> 1.82.0#2
        boost-vmd:x64-windows            1.82.0#1 -> 1.82.0#2
        boost-wave:x64-windows           1.82.0#1 -> 1.82.0#2
        boost-winapi:x64-windows         1.82.0#1 -> 1.82.0#2
        boost-xpressive:x64-windows      1.82.0#1 -> 1.82.0#2
        boost-yap:x64-windows            1.82.0#1 -> 1.82.0#2
        curl:x64-windows                 8.0.1 -> 8.1.2
        gettext:x64-windows              0.21.1 -> 0.21.1#2
        glib:x64-windows                 2.76.1#1 -> 2.76.3#1
        gstreamer:x64-windows            1.20.5#8 -> 1.20.5#9
        libde265:x64-windows             1.0.11 -> 1.0.11#2
        libheif:x64-windows              1.15.1#1 -> 1.16.1#1
        liblzma:x64-windows              5.4.1#1 -> 5.4.3
        libraw:x64-windows               0.21.1 -> 0.21.1#1
        mpg123:x64-windows               1.31.3 -> 1.31.3#1
        openssl:x64-windows              3.1.0#4 -> 3.1.1
        pcre2:x64-windows                10.40#2 -> 10.42
        sqlite3:x64-windows              3.40.1#3 -> 3.42.0
        tbb:x64-windows                  2021.9.0 -> 2021.9.0#2
        tesseract:x64-windows            5.3.0#1 -> 5.3.1
        vcpkg-cmake:x64-windows          2022-12-22 -> 2023-05-04
        x265:x64-windows                 3.4#8 -> 3.4#9
To update these packages and all dependencies, run
.\vcpkg upgrade'
To only remove outdated packages, run
.\vcpkg remove --outdated

C:\vcpkg>vcpkg upgrade
The following packages will be rebuilt:
  * boost[core]:x64-windows -> 1.82.0#2
  * boost-accumulators[core]:x64-windows -> 1.82.0#2
  * boost-algorithm[core]:x64-windows -> 1.82.0#2
  * boost-align[core]:x64-windows -> 1.82.0#2
  * boost-any[core]:x64-windows -> 1.82.0#2
  * boost-array[core]:x64-windows -> 1.82.0#2
  * boost-asio[core]:x64-windows -> 1.82.0#3
  * boost-assert[core]:x64-windows -> 1.82.0#2
  * boost-assign[core]:x64-windows -> 1.82.0#2
  * boost-atomic[core]:x64-windows -> 1.82.0#2
  * boost-beast[core]:x64-windows -> 1.82.0#2
  * boost-bimap[core]:x64-windows -> 1.82.0#2
  * boost-bind[core]:x64-windows -> 1.82.0#2
  * boost-build[core]:x64-windows -> 1.82.0#2
  * boost-callable-traits[core]:x64-windows -> 1.82.0#2
  * boost-chrono[core]:x64-windows -> 1.82.0#2
  * boost-circular-buffer[core]:x64-windows -> 1.82.0#2
  * boost-compatibility[core]:x64-windows -> 1.82.0#2
  * boost-compute[core]:x64-windows -> 1.82.0#2
  * boost-concept-check[core]:x64-windows -> 1.82.0#2
  * boost-config[core]:x64-windows -> 1.82.0#2
  * boost-container[core]:x64-windows -> 1.82.0#2
  * boost-container-hash[core]:x64-windows -> 1.82.0#2
  * boost-context[core]:x64-windows -> 1.82.0#2
  * boost-contract[core]:x64-windows -> 1.82.0#2
  * boost-conversion[core]:x64-windows -> 1.82.0#2
  * boost-convert[core]:x64-windows -> 1.82.0#2
  * boost-core[core]:x64-windows -> 1.82.0#2
  * boost-coroutine[core]:x64-windows -> 1.82.0#2
  * boost-coroutine2[core]:x64-windows -> 1.82.0#2
  * boost-crc[core]:x64-windows -> 1.82.0#2
  * boost-date-time[core]:x64-windows -> 1.82.0#2
  * boost-describe[core]:x64-windows -> 1.82.0#2
  * boost-detail[core]:x64-windows -> 1.82.0#2
  * boost-dll[core]:x64-windows -> 1.82.0#2
  * boost-dynamic-bitset[core]:x64-windows -> 1.82.0#2
  * boost-endian[core]:x64-windows -> 1.82.0#2
  * boost-exception[core]:x64-windows -> 1.82.0#2
  * boost-fiber[core]:x64-windows -> 1.82.0#2
  * boost-filesystem[core]:x64-windows -> 1.82.0#2
  * boost-flyweight[core]:x64-windows -> 1.82.0#2
  * boost-foreach[core]:x64-windows -> 1.82.0#2
  * boost-format[core]:x64-windows -> 1.82.0#2
  * boost-function[core]:x64-windows -> 1.82.0#2
  * boost-function-types[core]:x64-windows -> 1.82.0#2
  * boost-functional[core]:x64-windows -> 1.82.0#2
  * boost-fusion[core]:x64-windows -> 1.82.0#2
  * boost-geometry[core]:x64-windows -> 1.82.0#2
  * boost-gil[core]:x64-windows -> 1.82.0#2
  * boost-graph[core]:x64-windows -> 1.82.0#2
  * boost-hana[core]:x64-windows -> 1.82.0#2
  * boost-heap[core]:x64-windows -> 1.82.0#2
  * boost-histogram[core]:x64-windows -> 1.82.0#2
  * boost-hof[core]:x64-windows -> 1.82.0#2
  * boost-icl[core]:x64-windows -> 1.82.0#2
  * boost-integer[core]:x64-windows -> 1.82.0#2
  * boost-interprocess[core]:x64-windows -> 1.82.0#2
  * boost-interval[core]:x64-windows -> 1.82.0#2
  * boost-intrusive[core]:x64-windows -> 1.82.0#2
  * boost-io[core]:x64-windows -> 1.82.0#2
  * boost-iostreams[bzip2,core,lzma,zlib,zstd]:x64-windows -> 1.82.0#2
  * boost-iterator[core]:x64-windows -> 1.82.0#2
  * boost-json[core]:x64-windows -> 1.82.0#2
  * boost-lambda[core]:x64-windows -> 1.82.0#2
  * boost-lambda2[core]:x64-windows -> 1.82.0#2
  * boost-leaf[core]:x64-windows -> 1.82.0#2
  * boost-lexical-cast[core]:x64-windows -> 1.82.0#2
  * boost-local-function[core]:x64-windows -> 1.82.0#2
  * boost-locale[core]:x64-windows -> 1.82.0#2
  * boost-lockfree[core]:x64-windows -> 1.82.0#2
  * boost-log[core]:x64-windows -> 1.82.0#2
  * boost-logic[core]:x64-windows -> 1.82.0#2
  * boost-math[core]:x64-windows -> 1.82.0#2
  * boost-metaparse[core]:x64-windows -> 1.82.0#2
  * boost-modular-build-helper[core]:x64-windows -> 1.82.0#2
  * boost-move[core]:x64-windows -> 1.82.0#2
  * boost-mp11[core]:x64-windows -> 1.82.0#2
  * boost-mpl[core]:x64-windows -> 1.82.0#2
  * boost-msm[core]:x64-windows -> 1.82.0#2
  * boost-multi-array[core]:x64-windows -> 1.82.0#2
  * boost-multi-index[core]:x64-windows -> 1.82.0#2
  * boost-multiprecision[core]:x64-windows -> 1.82.0#2
  * boost-mysql[core]:x64-windows -> 1.82.0#2
  * boost-nowide[core]:x64-windows -> 1.82.0#2
  * boost-numeric-conversion[core]:x64-windows -> 1.82.0#2
  * boost-odeint[core]:x64-windows -> 1.82.0#2
  * boost-optional[core]:x64-windows -> 1.82.0#2
  * boost-outcome[core]:x64-windows -> 1.82.0#2
  * boost-parameter[core]:x64-windows -> 1.82.0#2
  * boost-parameter-python[core]:x64-windows -> 1.82.0#2
  * boost-pfr[core]:x64-windows -> 1.82.0#2
  * boost-phoenix[core]:x64-windows -> 1.82.0#2
  * boost-poly-collection[core]:x64-windows -> 1.82.0#2
  * boost-polygon[core]:x64-windows -> 1.82.0#2
  * boost-pool[core]:x64-windows -> 1.82.0#2
  * boost-predef[core]:x64-windows -> 1.82.0#2
  * boost-preprocessor[core]:x64-windows -> 1.82.0#2
  * boost-process[core]:x64-windows -> 1.82.0#2
  * boost-program-options[core]:x64-windows -> 1.82.0#2
  * boost-property-map[core]:x64-windows -> 1.82.0#2
  * boost-property-tree[core]:x64-windows -> 1.82.0#2
  * boost-proto[core]:x64-windows -> 1.82.0#2
  * boost-ptr-container[core]:x64-windows -> 1.82.0#2
  * boost-python[core,python3]:x64-windows -> 1.82.0#2
  * boost-qvm[core]:x64-windows -> 1.82.0#2
  * boost-random[core]:x64-windows -> 1.82.0#2
  * boost-range[core]:x64-windows -> 1.82.0#2
  * boost-ratio[core]:x64-windows -> 1.82.0#2
  * boost-rational[core]:x64-windows -> 1.82.0#2
  * boost-regex[core]:x64-windows -> 1.82.0#2
  * boost-safe-numerics[core]:x64-windows -> 1.82.0#2
  * boost-scope-exit[core]:x64-windows -> 1.82.0#2
  * boost-serialization[core]:x64-windows -> 1.82.0#2
  * boost-signals2[core]:x64-windows -> 1.82.0#2
  * boost-smart-ptr[core]:x64-windows -> 1.82.0#2
  * boost-sort[core]:x64-windows -> 1.82.0#2
  * boost-spirit[core]:x64-windows -> 1.82.0#2
  * boost-stacktrace[core]:x64-windows -> 1.82.0#2
  * boost-statechart[core]:x64-windows -> 1.82.0#2
  * boost-static-assert[core]:x64-windows -> 1.82.0#2
  * boost-static-string[core]:x64-windows -> 1.82.0#2
  * boost-stl-interfaces[core]:x64-windows -> 1.82.0#2
  * boost-system[core]:x64-windows -> 1.82.0#2
  * boost-test[core]:x64-windows -> 1.82.0#2
  * boost-thread[core]:x64-windows -> 1.82.0#2
  * boost-throw-exception[core]:x64-windows -> 1.82.0#2
  * boost-timer[core]:x64-windows -> 1.82.0#2
  * boost-tokenizer[core]:x64-windows -> 1.82.0#2
  * boost-tti[core]:x64-windows -> 1.82.0#2
  * boost-tuple[core]:x64-windows -> 1.82.0#2
  * boost-type-erasure[core]:x64-windows -> 1.82.0#2
  * boost-type-index[core]:x64-windows -> 1.82.0#2
  * boost-type-traits[core]:x64-windows -> 1.82.0#2
  * boost-typeof[core]:x64-windows -> 1.82.0#2
  * boost-ublas[core]:x64-windows -> 1.82.0#2
  * boost-uninstall[core]:x64-windows -> 1.82.0#2
  * boost-units[core]:x64-windows -> 1.82.0#2
  * boost-unordered[core]:x64-windows -> 1.82.0#2
  * boost-url[core]:x64-windows -> 1.82.0#2
  * boost-utility[core]:x64-windows -> 1.82.0#2
  * boost-uuid[core]:x64-windows -> 1.82.0#2
  * boost-variant[core]:x64-windows -> 1.82.0#2
  * boost-variant2[core]:x64-windows -> 1.82.0#2
  * boost-vcpkg-helpers[core]:x64-windows -> 1.82.0#2
  * boost-vmd[core]:x64-windows -> 1.82.0#2
  * boost-wave[core]:x64-windows -> 1.82.0#2
  * boost-winapi[core]:x64-windows -> 1.82.0#2
  * boost-xpressive[core]:x64-windows -> 1.82.0#2
  * boost-yap[core]:x64-windows -> 1.82.0#2
  * breakpad[core]:x64-windows -> 2022-07-12#4
  * bzip2[core,tool]:x64-windows -> 1.0.8#4
  * curl[core,non-http,schannel,ssl,sspi]:x64-windows -> 8.1.2
  * expat[core]:x64-windows -> 2.5.0#3
  * faad2[core]:x64-windows -> 2.10.1
  * ffmpeg[avcodec,avdevice,avfilter,avformat,core,swresample,swscale]:x64-windows -> 5.1.2#6
  * freeglut[core]:x64-windows -> 3.4.0
  * gettext[core]:x64-windows -> 0.21.1#2
  * giflib[core]:x64-windows -> 5.2.1#3
  * glib[core]:x64-windows -> 2.76.3#1
  * gstreamer[core,dtls,faad,gpl,jpeg,libav,mpg123,openh264,openjpeg,openmpt,plugins-bad,plugins-base,plugins-good,plugins-ugly,png,speex,taglib,vpx,webp,x265]:x64-windows -> 1.20.5#9
  * hdf5[core,szip,zlib]:x64-windows -> 1.14.0#1
  * imath[core]:x64-windows -> 3.1.5
  * jasper[core,default-features,opengl]:x64-windows -> 4.0.0#2
  * lcms[core]:x64-windows -> 2.14
  * leptonica[core]:x64-windows -> 1.83.1
  * libarchive[bzip2,core,crypto,libxml2,lz4,lzma,zstd]:x64-windows -> 3.6.2
  * libde265[core]:x64-windows -> 1.0.11#2
  * libdisasm[core]:x64-windows -> 0.23#10
  * libffi[core]:x64-windows -> 3.4.4#1
  * libheif[core]:x64-windows -> 1.16.1#1
  * libjpeg-turbo[core]:x64-windows -> <IP_ADDRESS>#1
  * liblzma[core]:x64-windows -> 5.4.3
  * libogg[core]:x64-windows -> 1.3.5#1
  * libopenmpt[core]:x64-windows -> 0.6.7
  * libpng[core]:x64-windows -> 1.6.39#1
  * libraw[core]:x64-windows -> 0.21.1#1
  * libvorbis[core]:x64-windows -> 1.3.7#2
  * libwebp[core,libwebpmux,nearlossless,simd,unicode]:x64-windows -> 1.3.0
  * libxml2[core,iconv,lzma,zlib]:x64-windows -> 2.10.3#1
  * lz4[core]:x64-windows -> 1.9.4#1
  * mpg123[core]:x64-windows -> 1.31.3#1
  * opencv[contrib,core,default-features]:x64-windows -> 4.7.0#1
  * opencv4[contrib,core,default-features,dnn,jpeg,png,quirc,tiff,webp]:x64-windows -> 4.7.0#6
  * openexr[core]:x64-windows -> 3.1.7
  * openjpeg[core]:x64-windows -> 2.5.0
  * openssl[core]:x64-windows -> 3.1.1
  * pcre2[core,jit,platform-default-features]:x64-windows -> 10.42
  * protobuf[core]:x64-windows -> 3.21.12
  * python3[core]:x64-windows -> 3.10.7#6
  * quirc[core]:x64-windows -> 1.1#3
  * sqlite3[core,json1]:x64-windows -> 3.42.0
  * szip[core]:x64-windows -> 2.1.1#11
  * taglib[core]:x64-windows -> 1.13.0#1
  * tbb[core]:x64-windows -> 2021.9.0#2
  * tesseract[core]:x64-windows -> 5.3.1
  * tiff[core,jpeg,lzma,zip]:x64-windows -> 4.5.0#3
  * vcpkg-cmake[core]:x64-windows -> 2023-05-04
  * vcpkg-cmake-get-vars[core]:x64-windows -> 2023-03-02
  * x265[core]:x64-windows -> 3.4#9
  * yasm[core,tools]:x64-windows -> 1.3.0#5
  * yasm-tool-helper[core]:x64-windows -> 2020-03-11#1
  * zlib[core]:x64-windows -> 1.2.13
  * zstd[core]:x64-windows -> 1.5.5
The following packages will be built and installed:
  * gettext-libintl[core]:x64-windows -> 0.21.1#1
Additional packages (*) will be modified to complete this operation.
If you are sure you want to rebuild the above packages, run this command with the --no-dry-run option.

C:\vcpkg>vcpkg update --no-dry-run option
error: unexpected switch: --no-dry-run
error: the command 'update' does not accept any additional arguments
error: unexpected argument: option
example:
    vcpkg update
Options:
  --x-asset-sources=...           Add sources for asset caching. See 'vcpkg help assetcaching'.
  --binarysource=...              Add sources for binary caching. See 'vcpkg help binarycaching'.
  --x-buildtrees-root=...         (Experimental) Specify the buildtrees root directory.
  --downloads-root=...            Specify the downloads root directory.
                                  (default: VCPKG_DOWNLOADS)
  --host-triplet=...              Specify the host architecture triplet. See 'vcpkg help triplet'.
                                  (default: 'VCPKG_DEFAULT_HOST_TRIPLET')
  --x-install-root=...            (Experimental) Specify the install root directory.
  --overlay-ports=...             Specify directories to be used when searching for ports.
                                  (also: 'VCPKG_OVERLAY_PORTS')
  --overlay-triplets=...          Specifiy directories containing triplets files.
                                  (also: 'VCPKG_OVERLAY_TRIPLETS')
  --x-packages-root=...           (Experimental) Specify the packages root directory.
  --triplet=...                   Specify the target architecture triplet. See 'vcpkg help triplet'.
                                  (default: 'VCPKG_DEFAULT_TRIPLET')
  --vcpkg-root=...                Specify the vcpkg root directory.
                                  (default: 'VCPKG_ROOT')

C:\vcpkg>vcpkg upgrade --no-dry-run option
warning: Starting with the September 2023 release, the default triplet for vcpkg libraries will change from x86-windows to the detected host triplet (x64-windows). To resolve this message, add --triplet x86-windows to keep the same behavior.
error: The following packages are not installed:
    option:x86-windows
error: The following packages do not have a valid CONTROL or vcpkg.json:
    option:x86-windows
internal error: D:\a\_work\1\s\src\vcpkg\commands.upgrade.cpp(180): vcpkg has crashed; no additional details are available.
Please open an issue at https://github.com/microsoft/vcpkg/issues/new?template=other-type-of-bug-report.md&labels=category:vcpkg-bug with detailed steps to reproduce the problem.

C:\vcpkg>vcpkg upgrade --no-dry-run option  --triplet x86-windows
error: The following packages are not installed:
    option:x86-windows
error: The following packages do not have a valid CONTROL or vcpkg.json:
    option:x86-windows
internal error: D:\a\_work\1\s\src\vcpkg\commands.upgrade.cpp(180): vcpkg has crashed; no additional details are available.
Please open an issue at https://github.com/microsoft/vcpkg/issues/new?template=other-type-of-bug-report.md&labels=category:vcpkg-bug with detailed steps to reproduce the problem.

C:\vcpkg>

cd <vcpkg directory>
git pull to update local vcpkg repo
.\bootstrap-vcpkg.bat to update the vcpkg.exe aka vcpkg-tool
.\vcpkg upgrade --no-dry-run it will upgrade any installed ports with changes to the latest version

I accidentally copied the word "option" into the command.  I think this is a duplicate, but I can't find it.


Refine metadata drawer UI to match mocks

Need

Separating out final UI implementation/polishing to allow for refinement of design after functional implementation can be experienced.

Approach
Follow existing UI patterns:

Inline styles for small/short style definitions.
Locally-scoped classes for components requiring larger set of style definitions (possibly for BlueprintJS overrides as well).

Definition of Done

Metadata drawer UI adheres to specifications in mocks.

UI implementation with overrides:


AsyncParsableCommand & AsyncMainProtocol: Concurrency is only available in macOS 12.0.0 or newer

Xcode 13.1 on macOS 11.6.7 throws the compiler error "Concurrency is only available in macOS 12.0.0 or newer" since AsyncParsableCommand and AsyncMainProtocol are only marked with @available(macOS 10.15).
This should be changed to @available(macOS 12.0).
ArgumentParser version: 1.1.3
Swift version: swift-driver version: 1.26.9 Apple Swift version 5.5.1 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)
Checklist

[x] If possible, I've reproduced the issue using the main branch of this package
[x] I've searched for existing GitHub issues

Steps to Reproduce
Include latest version of ArgumentParser as dependency in command line project and build with Xcode 13.1 on macOS 11.6.7.
Expected behavior
ArgumentParser should build without errors on macOS 11.6.7.
Actual behavior
ArgumentParser can't be built on macOS 11.6.7.

Building a version of ArgumentParser that includes AsyncParsableCommand on macOS 11 requires a Swift compiler that supports concurrency back-deployment. The Swift included with Xcode 13.2 has that support, so that would be the minimum supported Xcode configuration for your use case. Alternatively, you can use version 1.0.3 of ArgumentParser, which does not require concurrency support.


Still iOS13 Problems with .NET Core 3.1 03.December 2019 Blazor update (WebAssembly)

There is still a problem with iOS13, also with the latest Blazor update.
Into my Blazor pages I inject around five singleton services.
When I open the browser on iOS13 and I load a page then it is working, but when I'm reload the page then it seems the stack problem returns and the page isn't loaded.
When I remove from my five injecting services three services then it is also working during reloading.
It is a problem because I have the following scenario:
The user connects to the Blazor site, accept the terms and is then redirected to a SAML provider. After authentication the user is redirected back to Blazor, and because the user is then the second time on the blazor app the page hangs and isn't loaded.
What I have done as workaround is to redirect the user after authentication to a intermediate page without any services injected, only with the NavigationHelper. Then I use the method OnAfterRender to redirect the user to the target page. But this is also only working when I'm put a Thread.Sleep with around 1 second before the redirect.
In fact a Blazor page can only once loaded in a browser tab when there are a few injecting services.
So the timing problems on iOS13 seems still to exist. Can you confirm this?
Thanks for the feedback.

This issue was moved to mono/mono#18300


add grpc example

When I tried to run the example, it gives me the following error:
examples/session/grpc/proto/hello_grpc.pb.go:11:2: missing go.sum entry for module providing package google.golang.org/grpc; to add:
	go mod download google.golang.org/grpc
examples/session/grpc/proto/hello_grpc.pb.go:12:2: missing go.sum entry for module providing package google.golang.org/grpc/codes (imported by github.com/nknorg/nkn-sdk-go/examples/session/grpc/proto); to add:
	go get github.com/nknorg/nkn-sdk-go/examples/session/grpc/proto
examples/session/grpc/proto/hello_grpc.pb.go:13:2: missing go.sum entry for module providing package google.golang.org/grpc/status (imported by github.com/nknorg/nkn-sdk-go/examples/session/grpc/proto); to add:
	go get github.com/nknorg/nkn-sdk-go/examples/session/grpc/proto

After I run go get github.com/nknorg/nkn-sdk-go/examples/session/grpc/proto and run example again, it throws another error:
# github.com/nknorg/nkn-sdk-go/examples/session/grpc/proto
proto/hello_grpc.pb.go:19:16: undefined: grpc.SupportPackageIsVersion7
proto/hello_grpc.pb.go:69:29: undefined: grpc.ServiceRegistrar

It could be a mismatch of grpc local version. What I think works best is that you create a go.mod and go.sum file in your example (and don't modify the project root go.mod/go.sum), and specify all the dependencies.

I added go mod

Thanks for the contribution! Merged now


colab real time nex not work

stays in starting and does not advance.

It works fine for me.
The error said rclone: command not found
Please try to rerun this highlighted line. rclone is required to upload the MPI to nex.mpi.workers.dev

How long will the starting page last? I am stucked there.

Should be load with in few seconds.
https://youtu.be/0L8dfzWkvVs
You might need to use a console f12 or ctrl+shift+i to see an error.


Table already exists

An exception occurred while executing 'CREATE TABLEoc_uc_storageusage(idBIGINT UNSIGNED AUTO_INCREMENT NOT NULL,createdDATETIME NOT NULL,usernameVARCHAR(255) NOT NULL,usageBIGINT NOT NULL,maximumusageBIGINT NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_bin ENGINE = InnoDB': SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'oc_uc_storageusage' already exists

If manually removed the tabled, now said
Error: this app cannot be enabled because it makes the server unstable

I get the same issue, however I am running owncloud 9.0 and it doesn't look like he has added 9.0 support. I can't  find much on migrating apps to 9.0 to help either.

Could be because the old Storage Usage / Activity Charts   3.4.5 (ocusagecharts on github) was installed before?


Fix gds creation for auradb

Thank you for your contribution to the Graph Data Science Client project.

Before submitting this PR, please read Contributing to the Neo4j Ecosystem.
Make sure:

[ ] You signed the Neo4j CLA (Contributor License Agreement) so that we are allowed to ship your code in our library
[ ] Your contribution is covered by tests

 [🍓] Client behaviour for cypher-based GDS features (run_cypher, native_projection)


Homepage tweaks

feat: Re-introduce the "create viz" CTA for homepage intro
feat: Remove icons in homepage intro

I am sad for the little icons :( Merging since it's simple but do not hesitate to tell me if there is a problem @bprusinowski @herrstucki .


OCM-2237: Fix path also to be used for the operator roles creation

/hold
This PR is blocked by 2 other PRs
https://github.com/terraform-redhat/terraform-aws-rosa-sts/pull/20 - after this merged need to create tag version 0.0.8 in the module
https://github.com/terraform-redhat/terraform-provider-ocm/pull/137 - Rebased on this PR, after rebase need to rebase on main

/hold cancel


Enable profiling with a command line switch.

Added a hidden no-op command that's used to quickly test the profiler.

Codecov Report

Merging #21 into master will increase coverage by 0.77%.
The diff coverage is 92%.

@@            Coverage Diff            @@
##           master     #21      +/-   ##
=========================================
+ Coverage   66.13%   66.9%   +0.77%
=========================================
  Files          14      14
  Lines         812     837      +25
=========================================
+ Hits          537     560      +23
- Misses        275     277       +2

Impacted Files
Coverage Δ

starfish/starfish.py
93.29% <92%> (-0.24%)
:arrow_down:

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 9310a1f...fc9a97e. Read the comment docs.


Adding toast notification during log in ,log out and sign up

as there is no toast like notification pops up when user get logged in or logged out.
to provide better user experience it is necessary to have these toast notification
@TejasNasre can you assign me these task

how you will do it i don't think its important  we are using kinde auth

By using a npm package .
It is kind of notification you have seen it in many websites for example gfg .
Whenever you logged in or logged out a pop like msg is appeared on a specific location where you decide

but bro we are using kind auth they manage state it self no need of this feature as of now please look to other issues


Update python stubs to match argument names

Fix the name of the session id argument in new_alias and new_trigger

Not sure if we wanted to update the docs or the function, but I realized I had this change locally and should get this fixed


why dose my code get Trying to get property of non-object?

Laravel Version: 5.2.41
PHP Version: 7.0.5-2+deb.sury.org~trusty+1 (cli) ( NTS )
Database Driver & Version: Ver 14.14 Distrib 5.7.12, for Linux (x86_64) using  EditLine wrapper

Description:

output:
ErrorException in PaperController.php line 223:

Trying to get property of non-object

but I used dd($user->papers()->find($pid)->pivot->score); it can outputed correct value..
there is my routes.php:
Route::get('scoreMgr/updateScores/{pid}', 'PaperController@updateScores');

Steps To Reproduce:

I found the problem, sorry.


About page borders are larger than other pages.

The content of the about.html page appears to be indented slightly further right than other pages.

Also applies to Credits page

I think this is just a side effect of the Bootstrap responsive design model.
Not going to try to fix.


3 buttons not in one row. 1 gets pushed to the next line

Sadly for some reason the button width is too big and as such the last one "gets sent" to the next line.

@Deejayfool


[stable/efs-provisioner] add support for mounting with IP

Is this a request for help?: no

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST
Version of Helm and Kubernetes:
Helm v2.12.1
K8S v1.12.5-gke.5
Which chart:
efs-provisioner
What happened:
I'd like to mount my EFS from outside my AWS VPC, but it's only possible with the IP address see this
The chart currently supports efsFileSystemId so I can't use for the above scenario.

This would also be very useful for us. It looks like the efs provisioner did add support for arbitrary DNS names which also works with IP addresses: https://github.com/kubernetes-incubator/external-storage/issues/422
If this chart could be extended to support that new env var then it would support IP address mounting.


How do you strip record prefix when using GenericEntity

I have a record that looks like this:
data Endpoint = Endpoint
  { enpCreatedAt :: ZonedTimestamp,
    enpUpdatedAt :: ZonedTimestamp,
    enpID :: UUID,
    enpProjectId :: UUID,
    endRequestHashes :: Vector Text,
     ...
  }
  deriving (Show, Generic)
  deriving anyclass (FromRow, ToRow)
  deriving
    (Entity)
    via (GenericEntity '[TableName "apis.endpoints", PrimaryKey "id"] Endpoint)

But the actual table columns do not include the enp prefix. How can I get pg-entity to strip the enp prefix?

For more context, I'm wondering if something like what is available for aeson exists, where you can strip prefix:
deriving
    (FromJSON)
    via CustomJSON '[OmitNothingFields, FieldLabelModifier '[StripPrefix "rm", CamelToSnake]] RequestMessage

Yes, it is entirely possible.
I'll come up with a PR next week. :)
Thank you for suggesting it!
Cordialement / Best Regards / Pozdrawiam
Théophile Choutri
Le 18 décembre 2021 18:11:41 Anthony Alaribe @.***> a
écrit :

For more context, I'm wondering if something like what is available for
aeson exists, where you can strip prefix:
deriving (FromJSON) via CustomJSON '[OmitNothingFields, FieldLabelModifier
'[StripPrefix "rm", CamelToSnake]] RequestMessage
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Awesome! Thanks!!

@tonyalaribe Are you satisfied with these ergonomics?
data Endpoint
  = Endpoint { enpID            :: UUID
             , enpProjectId     :: UUID
             , enpRequestHashes :: Vector Text
             }
  deriving (Generic, Show)
  deriving (Entity)
    via (GenericEntity '[TableName "apis.endpoints", PrimaryKey "id",
                         FieldModifiers '[StripPrefix "enp", CamelToSnake]] Endpoint)

fields @Endpoint `shouldBe` [[field| id |], [field| project_id |], [field| request_hashes |]]

Oh, this looks really good. It definitely removes the manual instances I had to write.
Thanks 🙌


insufficient marketing

Why this wonderful package is not listed here:
https://docs.flutter.dev/data-and-backend/state-mgmt/options
Are you aware of any reasons why this package would not be another state management option for an enterprise Flutter app?

Probably because it is newer! But happy to get it added to more places

https://docs.flutter.dev/data-and-backend/state-mgmt/options#june
just released 3 days ago and listed in official flutter docs
https://docs.flutter.dev/data-and-backend/state-mgmt/options#june

Good to know, will see what I can do!

A PR to the documentation site should do it. I could make the PR if its fine, hopefully it gets accepted 😃

For someone familiar with signal-based web frameworks like Vue.js, signal is very intuitive.
I'm currently struggling more with implementing Flutter itself,
but once I release the app with signal (in progress), I plan to write an article for the Japanese developper to promote this package.
Since there's only one article on Flutter signals in Japan, the awareness is very low.
(and I'm sorry I may not have much influence.)

Wow amazing! ❤🇯🇵
Would it help if the site and docs are localized? Maybe as it grows we can add more translations too.

Thats sounds good!
I've been wanting to promote the use of Signals in my own work as well,
so translating the official documentation seems like it could be very effective.
This would be my first time contributing, but I'm eager to try!
(The only concern is that I've been using Flutter for just about two months, so I'm a bit worried about conveying everything correctly. However, I plan to keep studying and cover any gaps in my knowledge.)


[documenation] why do you say subscribers are snapshoted?

I am not sure if it's an error in documentation or if it's because me lack of understanding how redux works.
here is the link
https://stackoverflow.com/questions/50440706/how-do-i-understand-subscriptions-are-snaphostted-before-dispatch
feel free to close it if the it's the latter case.

Yeah, looks like the phrasing in the docs might be slightly out of date.  The snapshotting looks like it happens in subscribe() and unsubscribe().
That said, it's an internal implementation detail, and shouldn't generally be a concern for you as an end user.

If it is internal implementation, it shouldn’t appear in documentation. Can you please take a look?


Python introduction for finance

https://github.com/jpmorganchase/python-training

@samdansk2 , another resource.