text:
Unable to get anything to trigger record.

So I've been working on getting Viseron to work (thanks for all the hard work by the way).  I've got what I THINK is suppose to be working, however I can't get anything to trigger record. Initially when I installed Viseron there was a few recordings, but I have no clue what I changed to get back to that. Since the update I haven't been able to do anything at all other than stream.
So to give you a breakdown of Hardware and setup.
Hardware/Software:
OS: Ubuntu 22.04.2 LTS x86_64/CasaOS (If you want to see what CasaOS is about check here: https://casaos.io/)
Host: B550 AORUS ELITE AX
Kernel: 5.15.0-70-generic
CPU: AMD Ryzen 5 3600 (12) @ 3.600GHz
GPU: AMD ATI Radeon RX 5500/5500M / Pro 5500M
Memory: 6594MiB / 64211MiB
Cameras: Anbiux A8SB https://www.aliexpress.us/item/3256804753989807.html?spm=a2g0o.productlist.main.3.44133502z8rSwM&algo_pvid=631787c7-5efa-4985-9f54-cb0888704e93&algo_exp_id=631787c7-5efa-4985-9f54-cb0888704e93-1&pdp_npi=3%40dis!USD!90.58!42.57!!!!!%40212243c016822844120603866d06cc!12000031093088702!sea!US!2131105761&curPageLogUid=YzC1BAn2bBqQ
Wait for this one to come in: https://www.aliexpress.us/item/3256804881846727.html?spm=a2g0o.order_list.order_list_main.28.457d1802wWNjNr&gatewayAdapt=glo2usa&_randl_shipto=US
Not sure if the software will be able to handle the 180 degree angle view.
Example of Camera Domain:
ffmpeg:
camera:
camera_1: # This value has to be unique across all cameras
name: a name
host: ipaddress
port: 554
path: /user=admin_password=1bpcecDK_channel=0_stream=0&onvif=0.sdp?real_stream
username: pass
password: word
protocol: rtsp
width: 2560
height: 1440
fps: 10
codec: hevc
audio_codec: aac
recorder:
codec: hevc
audio_codec: aac
idle_timeout: 1
lookback: 15
thumbnail:
save_to_disk: true
Config for Motion, Object Detector, Face Recognition:
(I'll be switching back to darknet however it didn't trigger with that either)
deepstack:  (Its actually CodeProject.AI https://www.codeproject.com/Articles/5322557/CodeProject-AI-Server-AI-the-easy-way)
host: ipaddress
port: 32168
object_detector:
cameras:
camera_1:
scan_on_motion_only: false
fps: 10
labels:
- label: person
confidence: 0.75
height_min: 0
height_max: 1
width_min: 0
width_max: 1
require_motion: true
trigger_recorder: true
- label: dog
confidence: 0.8
require_motion: true
height_min: 0
height_max: 1
width_min: 0
width_max: 1
trigger_recorder: true
- label: cat
confidence: 0.8
require_motion: true
height_min: 0
height_max: 1
width_min: 0
width_max: 1
trigger_recorder: true
Face Recognition (from CodeProject.AI)
face_recognition:
save_unknown_faces: false
unknown_faces_path: /config/face_recognition/faces/unknown
face_recognition_path: /config/face_recognition/faces
cameras:
camera_1:
labels:
- person
(Posting so you could see my darknet settings)
darknet:
object_detector:
model_path: /detectors/models/darknet/yolov7-tiny.weights
model_config: /detectors/models/darknet/yolov7-tiny.cfg
label_path: /detectors/models/darknet/coco.names
cameras:
camera_1:
scan_on_motion_only: false
fps: 10
labels:
- label: person
confidence: 0.75
height_min: 0
height_max: 1
width_min: 0
width_max: 1
require_motion: true
trigger_recorder: true
- label: dog
confidence: 0.8
require_motion: true
height_min: 0
height_max: 1
width_min: 0
width_max: 1
trigger_recorder: true
- label: cat
confidence: 0.8
require_motion: true
height_min: 0
height_max: 1
width_min: 0
width_max: 1
trigger_recorder: true
mog2:
motion_detector:
cameras:
camera_1:
detect_shadows: true
trigger_recording: true (If I uncomment this, it breaks everything)
    recorder_keepalive: true
    learning_rate: -1
    max_recorder_keepalive: 30
    fps: 10
    width: 2560
    height: 1440

nvr:
camera_1: # Run NVR for camera_1
Now, no matter what I've tried I have not gotten this to record except before the update and the config had different settings.
Even then, when it did, it recorded the audio and not the video. It did however took a thumbnail. Any help would be great. I appreciate everything that has been done in this project and those who are help out.
Logs from Portainer on the container for Viseron when booting and running
https://pastebin.com/6xxgbxYD
Also this seems to happen from time to time. Not sure why a connection loss or time out is happening
[2023-04-23 21:43:43] [ERROR   ] [viseron.components.ffmpeg.stream.camera_2] - [tcp @ 0x55b7677f5500] Connection to tcp://ipaddress9:554?timeout=5000000 failed: Connection timed out
[2023-04-23 21:43:43] [ERROR   ] [viseron.components.ffmpeg.stream.camera_2] - rtsp://:@ipaddress:554/user=admin_password=1bpcecDK_channel=0_stream=0&onvif=0.sdp?real_stream: Connection timed out
[2023-04-23 21:43:43] [ERROR   ] [viseron.components.ffmpeg.camera.camera_2] - FFmpeg process has exited
[2023-04-23 21:43:48] [ERROR   ] [viseron.components.ffmpeg.camera.camera_2] - Restarting frame pipe
OH!!! 3 cups of coffee your brother. You honestly deserve more.

THanks for the detailed report, will have a deeper look.
Can you repost your config between triple back-ticks? (```)
It keeps indentation so its easier to read, like this:
ffmpeg:
  cameras:
    camera_one:

OH!!! 3 cups of coffee your brother. You honestly deserve more.

Thanks! Means a lot :)

Also regarding the logs, can you restart, walk infront of the camera in a way that should trigger recordings and then send the logs? Then i should be able to figure out what is wrong.

Also regarding the logs, can you restart, walk infront of the camera in a way that should trigger recordings and then send the logs? Then i should be able to figure out what is wrong.

I've been trying that, even when I walk in front of the camera, wave and everything, no logs are produced.

Also regarding the logs, can you restart, walk infront of the camera in a way that should trigger recordings and then send the logs? Then i should be able to figure out what is wrong.

I've been trying that, even when I walk in front of the camera, wave and everything, no logs are produced.

Enable debug logging and try again. You can do that like this:
logger:
  default_level: debug

require_motion: false

Yep, I have that enabled along with viseron.components.mog2: debug
Here is what I got
[2023-04-24 20:30:45] [ERROR   ] [viseron.components] - Error validating config for component mog2: extra keys not allowed @ data['mog2']['motion_detector']['cameras']['camera_1']['require_motion']. Got False
Traceback (most recent call last):
File "/src/viseron/components/init.py", line 114, in validate_component_config
return component_module.CONFIG_SCHEMA(self._config)  # type: ignore
File "/usr/local/lib/python3.8/dist-packages/voluptuous/schema_builder.py", line 272, in call
return self._compiled([], data)
File "/usr/local/lib/python3.8/dist-packages/voluptuous/schema_builder.py", line 594, in validate_dict
return base_validate(path, iteritems(data), out)
File "/usr/local/lib/python3.8/dist-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: extra keys not allowed @ data['mog2']['motion_detector']['cameras']['camera_1']['require_motion']
[2023-04-24 20:30:45] [ERROR   ] [viseron.components] - Setup of component mog2 failed
[2023-04-24 20:30:45] [ERROR   ] [viseron.components] - Failed setup of component mog2
everytime I've gotten it to trigger, I had to have the record settings codec set to h264 audio I keep at aac, but extension mkv.

Here is a screen shot on the info of the one recording that actually recorded

After some more tinkering, it seems like its hit or miss. I've turned on each component debug that I'm using. I'm not getting errors when monitoring. I've played with the codec and audio codec. When I have hevc and aac set, when I did finally get it to trigger, the player only plays the audio. I downloaded the video to my computer and the video as well as the audio works.  I had loopback set as well, and when the detector triggers, it would only record the length of the loop back. I didn't think of it before deleting them, but on v2.1.1, it seem it recorded, but I didn't think to download to my pc to view. Its like something is causing lag maybe?  I couldn't tell ya.

Was able to pull this log during testing.
[2023-04-24 21:51:46] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: frame I:      1, Avg QP:21.41  kb/s: 31861.92
[2023-04-24 21:51:46] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: frame P:     14, Avg QP:23.69  kb/s: 5297.65
[2023-04-24 21:51:46] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: frame B:     45, Avg QP:30.60  kb/s: 360.03
[2023-04-24 21:51:46] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: Weighted P-Frames: Y:0.0% UV:0.0%
[2023-04-24 21:51:46] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: consecutive B-frames: 6.7% 6.7% 6.7% 40.0% 40.0%
[2023-04-24 21:51:46] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] -
[2023-04-24 21:51:46] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - encoded 60 frames in 2.92s (20.57 fps), 2037.17 kb/s, Avg QP:28.84
[2023-04-24 21:51:46] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_1] - Removing segment: 20230424215132.mkv
[2023-04-24 21:51:46] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_1] - Segments concatenated
[2023-04-24 21:51:46] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_1] - Resuming segment cleanup

[2023-04-24 22:06:29] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: frame I:      2, Avg QP:24.49  kb/s: 11223.84
[2023-04-24 22:06:29] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: frame P:     33, Avg QP:29.18  kb/s: 77.69
[2023-04-24 22:06:29] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: frame B:     72, Avg QP:31.57  kb/s: 19.49
[2023-04-24 22:06:29] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: Weighted P-Frames: Y:0.0% UV:0.0%
[2023-04-24 22:06:29] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - x265 [info]: consecutive B-frames: 28.6% 11.4% 17.1% 11.4% 31.4%
[2023-04-24 22:06:29] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] -
[2023-04-24 22:06:29] [ERROR   ] [viseron.components.ffmpeg.recorder.camera_1] - encoded 107 frames in 2.50s (42.72 fps), 246.87 kb/s, Avg QP:30.70

Info update:
So to give you the info that worked with the recording info above
object detector: edgetpu (m.2)
motion detector: background subtractor
face recognition: compreface
Now the experience that I'm having is anytime I switch the object det or mot det, it would render record triggering dead. I can go outside and see that my cameras are tripping, but no recording happens.
I switched from background to mog2 to test, but it will not record. I would completely not add mot det, but viseron errors and says a object det and a mot det must be enabled.
I was able to get very little done with darknet. Even if I switch, because of the behavior it may or may not work. So even if it start working, it may not if I switch to something else to test.
As you see above, even when it would record no matter the file extension I used, it came as an error.
What I have noticed is that darknet and mog2 seem to take  a lot of resource to run. Leaving my cpu usage at 58% when running it. Wouldn't be an issue if I can get consistent trippers.
Still have the issue of loopback being the majority of whats recorded and MAYBE a couple of seconds and then end. I have.
If I switch the codec to h264 and get it to record, then I'm able to view the recording in the browser and hear audio. I heard there is an issue with h265 video being viewed in browsers. Anyway, I hope this helps and gives you as much info as needed. For the time being or at least when I go to bed, Ill switch back to frigate, but I am determined to see viseron work consistent as possible.
Thanks for all the work your doing and research going into this.

Motion detection is not required, and i think the best way is to first test without motion detection.
I need you to post your config between triple backticks(```), then i can help you out with the config

Motion detection is not required, and i think the best way is to first test without motion detection.
I need you to post your config between triple backticks(```), then i can help you out with the config

Sorry for taking so long to reply. Been pretty busy.
'''
mqtt:
broker:
port:
home_assistant:
discovery_prefix: homeassistant
retain_config: true
Start by adding some cameras
ffmpeg:
camera:
camera_1: # This value has to be unique across all cameras
name: Front Door
host:
port: 554
path: /user=admin_password=1bpcecDK_channel=0_stream=0&onvif=0.sdp?real_stream
username:
password:
protocol: rtsp
width: 2560
height: 1440
fps: 10
codec: hevc
audio_codec: aac
recorder:
codec: hevc
audio_codec: aac
idle_timeout: 1
lookback: 10
thumbnail:
save_to_disk: true
Then add an object detector
darknet:
object_detector:
model_path: /detectors/models/darknet/yolov7-tiny.weights
model_config: /detectors/models/darknet/yolov7-tiny.cfg
label_path: /detectors/models/darknet/coco.names
cameras:
camera_1:
scan_on_motion_only: false
fps: 10
labels:
- label: person
confidence: 0.75
height_min: 0
height_max: 1
width_min: 0
width_max: 1
require_motion: true
trigger_recorder: true
- label: dog
confidence: 0.8
require_motion: true
height_min: 0
height_max: 1
width_min: 0
width_max: 1
trigger_recorder: true
- label: cat
confidence: 0.8
require_motion: true
height_min: 0
height_max: 1
width_min: 0
width_max: 1
trigger_recorder: true
#edgetpu:
object_detector:
device: pci
cameras:
camera_1:  # Attach detector to the configured camera_1 above
fps: 10
scan_on_motion_only: false  # Scan for objects even when there is no motion
labels:
- label: person
confidence: 0.75
trigger_recorder: true
- label: dog
confidence: 0.8
trigger_recorder: false
- label: cat
confidence: 0.8
trigger_recorder: false
image_classification:
device: cpu
label_path: /classifiers/models/edgetpu/labels.txt
cameras:
camera_1:
camera_2:
camera_3:
labels:
- person
- dog
- cat
Then add an Face Recognition
compreface:
face_recognition:
host:
port:
recognition_api_key:
train: true
face_plugins: age,gender
save_unknown_faces: true
status: true
cameras:
camera_1:
camera_2:
camera_3:
labels:
- person
Then add an Motion Detection
#background_subtractor:
motion_detector:
cameras:
camera_1:
detect_shadows: true
recorder_keepalive: true
max_recorder_keepalive: 30
fps: 10
width: 2560
height: 1440
camera_2:
detect_shadows: true
recorder_keepalive: true
max_recorder_keepalive: 30
fps: 10
width: 2560
height: 1440
camera_3:
detect_shadows: true
recorder_keepalive: true
max_recorder_keepalive: 30
fps: 10
width: 2560
height: 1440
##Debugging and logs
logger:
default_level: debug
logs:
viseron.components.ffmpeg: debug
viseron.components.nvr: debug

viseron.components.edgetpu: debug
viseron.components.darknet: debug

viseron.components.background_subtractor: debug
viseron.components.compreface: debug

viseron.components.mog2: debug
cameras:
camera_1: debug
camera_2: debug
camera_3: debug
To tie everything together we need to configure one more component.
nvr:
camera_1: # Run NVR for camera_1
camera_2: # Run NVR for camera_2
camera_3: # Run NVR for camera_3
Now you can restart Viseron and you should be good to go!
'''

LOL, so not only is darknet working, it is trying to record every rain drop that is coming down today. So removing motion did work. However, how do I keep it from doing that and just recording what I've placed in labels?
usermod: no changes
************************ UID/GID *************************
User uid:    0
User gid:    0
************************** Done **************************
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-gid-video-device: executing...
[cont-init.d] 20-gid-video-device: exited 0.
[cont-init.d] 30-edgetpu-permission: executing...
************** Setting EdgeTPU permissions ***************
Coral Vendor IDs:
"1a6e"
"18d1"
No EdgeTPU USB device was found
************************** Done **************************
[cont-init.d] 30-edgetpu-permission: exited 0.
[cont-init.d] 40-set-env-vars: executing...
****** Checking for hardware acceleration platforms ******
OpenCL cannot be used
VA-API is available!
CUDA cannot be used
*********************** Done *****************************
[cont-init.d] 40-set-env-vars: exited 0.
[cont-init.d] 50-check-if-rpi: executing...
********** Checking if we are running on an RPi **********
Not running on any supported RPi
*********************** Done *****************************
[cont-init.d] 50-check-if-rpi: exited 0.
[cont-init.d] 55-check-if-jetson: executing...
****** Checking if we are running on a Jetson Board ******
Not running on any supported Jetson board
*********************** Done *****************************
[cont-init.d] 55-check-if-jetson: exited 0.
[cont-init.d] 60-ffmpeg-path: executing...
****************** Getting FFmpeg path *******************
FFmpeg path: /home/abc/bin/ffmpeg
*********************** Done *****************************
[cont-init.d] 60-ffmpeg-path: exited 0.
[cont-init.d] 70-gstreamer-path: executing...
***************** Getting GStreamer path *****************
GStreamer path: /usr/bin/gst-launch-1.0
*********************** Done *****************************
[cont-init.d] 70-gstreamer-path: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2023-05-04 13:46:14] [INFO    ] [viseron.core] - -------------------------------------------
[2023-05-04 13:46:14] [INFO    ] [viseron.core] - Initializing Viseron
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setting up component logger
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setup of component logger took 0.0 seconds
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setting up component data_stream
[2023-05-04 13:46:14] [DEBUG   ] [viseron.watchdog] - Registering <RestartableThread(data_stream, initial daemon)> in the watchdog
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setup of component data_stream took 0.0 seconds
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setting up component webserver
[2023-05-04 13:46:14] [DEBUG   ] [asyncio] - Using selector: EpollSelector
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/domain/registered/camera, <bound method Webserver.camera_registered of <Webserver(Tornado Webserver, initial daemon)>>
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/domain/setup/domain_failed/camera/*, <bound method Webserver.camera_registered of <Webserver(Tornado Webserver, initial daemon)>>
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method Webserver.stop of <Webserver(Tornado Webserver, initial daemon)>>
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setup of component webserver took 0.0 seconds
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setting up component nvr
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setting up component ffmpeg
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setting up component mqtt
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setup of component nvr took 0.0 seconds
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setting up component darknet
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setting up component compreface
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setup of component ffmpeg took 0.0 seconds
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.darknet] - Using OpenCV DNN Darknet
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.darknet] - Using weights /detectors/models/darknet/yolov7-tiny.weights and config /detectors/models/darknet/yolov7-tiny.cfg, 416x416
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.darknet] - DNN backend: 0
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.darknet] - DNN target: 0
[2023-05-04 13:46:14] [DEBUG   ] [viseron.watchdog] - Registering <RestartableThread(viseron.components.mqtt.publisher, initial daemon)> in the watchdog
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setup of component darknet took 0.0 seconds
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.mqtt] - MQTT connected with returncode 0
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/entity_added, <bound method MQTT.entity_added of <viseron.components.mqtt.MQTT object at 0x7f5fe80578b0>>
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/state_changed, <bound method MQTT.state_changed of <viseron.components.mqtt.MQTT object at 0x7f5fe80578b0>>
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method MQTT.stop of <viseron.components.mqtt.MQTT object at 0x7f5fe80578b0>>
[2023-05-04 13:46:14] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/mqtt/entity_added, <bound method HassMQTTInterface.entity_added of <viseron.components.mqtt.homeassistant.HassMQTTInterface object at 0x7f5fe8050af0>>
[2023-05-04 13:46:14] [INFO    ] [viseron.components] - Setup of component mqtt took 0.0 seconds
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setup of component compreface took 0.0 seconds
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain camera for component ffmpeg with identifier camera_1
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain object_detector for component darknet with identifier camera_1
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain nvr for component nvr with identifier camera_1
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain camera for component ffmpeg with identifier camera_2
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain nvr for component nvr with identifier camera_2
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain camera for component ffmpeg with identifier camera_3
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain nvr for component nvr with identifier camera_3
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain face_recognition for component compreface with identifier camera_1
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain face_recognition for component compreface with identifier camera_2
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setting up domain face_recognition for component compreface with identifier camera_3
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components] - Domain face_recognition for component compreface with identifier camera_1 will wait for dependencies ['domain: camera, identifier: camera_1']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components] - Domain object_detector for component darknet with identifier camera_1 will wait for dependencies ['domain: camera, identifier: camera_1']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components] - Domain nvr for component nvr with identifier camera_2 will wait for dependencies ['domain: camera, identifier: camera_2']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components] - Domain nvr for component nvr with identifier camera_3 will wait for dependencies ['domain: camera, identifier: camera_3']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components] - Domain face_recognition for component compreface with identifier camera_3 will wait for dependencies ['domain: camera, identifier: camera_3']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components] - Domain face_recognition for component compreface with identifier camera_2 will wait for dependencies ['domain: camera, identifier: camera_2']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components] - Domain nvr for component nvr with identifier camera_1 will wait for dependencies ['domain: camera, identifier: camera_1']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components] - Domain nvr for component nvr with identifier camera_1 will wait for optional dependencies ['domain: object_detector, identifier: camera_1']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Connected from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/camera/status, <bound method ConnectionStatusBinarySensor.handle_event of <viseron.domains.camera.entity.binary_sensor.ConnectionStatusBinarySensor object at 0x7f5fb0076f40>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_connected to state: off, attributes {'name': 'Front Door Connected', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Storage Room Connected from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/camera/status, <bound method ConnectionStatusBinarySensor.handle_event of <viseron.domains.camera.entity.binary_sensor.ConnectionStatusBinarySensor object at 0x7f5fb007b070>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_2_connected to state: off, attributes {'name': 'Storage Room Connected', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Connection from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/camera/start, <bound method CameraConnectionToggle.handle_start_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb007b340>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/camera/stop, <bound method CameraConnectionToggle.handle_stop_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb007b340>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/camera/started, <bound method CameraConnectionToggle.handle_started_stopped_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb007b340>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/camera/stopped, <bound method CameraConnectionToggle.handle_started_stopped_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb007b340>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of toggle.camera_1_connection to state: off, attributes {'name': 'Front Door Connection', 'domain': 'toggle'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Storage Room Connection from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/camera/start, <bound method CameraConnectionToggle.handle_start_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb007b790>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/camera/stop, <bound method CameraConnectionToggle.handle_stop_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb007b790>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/camera/started, <bound method CameraConnectionToggle.handle_started_stopped_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb007b790>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/camera/stopped, <bound method CameraConnectionToggle.handle_started_stopped_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb007b790>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of toggle.camera_2_connection to state: off, attributes {'name': 'Storage Room Connection', 'domain': 'toggle'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Backyard Connected from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/camera/status, <bound method ConnectionStatusBinarySensor.handle_event of <viseron.domains.camera.entity.binary_sensor.ConnectionStatusBinarySensor object at 0x7f5fb007b910>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_3_connected to state: off, attributes {'name': 'Backyard Connected', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Backyard Connection from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/camera/start, <bound method CameraConnectionToggle.handle_start_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb0080130>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/camera/stop, <bound method CameraConnectionToggle.handle_stop_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb0080130>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/camera/started, <bound method CameraConnectionToggle.handle_started_stopped_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb0080130>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/camera/stopped, <bound method CameraConnectionToggle.handle_started_stopped_event of <viseron.domains.camera.entity.toggle.CameraConnectionToggle object at 0x7f5fb0080130>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of toggle.camera_3_connection to state: off, attributes {'name': 'Backyard Connection', 'domain': 'toggle'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Backyard Access Token from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_3_access_token to state: dafd8b23bfcc5f0d716c23c7b844d1a5e1ccdd47d999f99720640b74c53014094043dc2b2837a11ccfb050f8bfb3d1b06c45927db81d1ba7ad4541e1e6ca397b, attributes {'name': 'Backyard Access Token', 'domain': 'sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Access Token from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_1_access_token to state: 980f5c2e15fcf89e272ec10a63cffa68f1d5f8d6e3edc38835273d61bb3e1bbc4064769ab977a3c2bacdf4af483fd8f6ff4cb6916705aa40eaf761e0728495dc, attributes {'name': 'Front Door Access Token', 'domain': 'sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_1_access_token to state: 933f6c4f0483325bab50354947406d1a5ad1313e1f077b0d7f07404b56394062bcbc7c51004b85c23b0449634d4cddd47e0aedaaad78a49662862317fc44d3e4, attributes {'name': 'Front Door Access Token', 'domain': 'sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Storage Room Access Token from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_2_access_token to state: 9c961d332cfdecff370c04549178ef41bb74325d28a95782d9d9203332b677cba695862e7f4b5cfe9023619c28e305294716c86d5a2d216d180d8deb71f4794d, attributes {'name': 'Storage Room Access Token', 'domain': 'sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_2_access_token to state: a037af232af24347298be1854aa8e962af21cc801772e66d666e1e6dcdd4eb5ad40846986a60eb69be99d89ce91599e7f7d7d2910b0d6e3de6fae8bbce86e605, attributes {'name': 'Storage Room Access Token', 'domain': 'sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_3_access_token to state: cd91741fc8475421eaf93fbcfa7482d1747e0ff9f4ff88497343c459872385e983025d9fe4f494f4427f21750cf426631cb7df5360dc207938d47bd7c7e05dd3, attributes {'name': 'Backyard Access Token', 'domain': 'sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.mqtt] - Subscribing to topic viseron/toggle/camera_1_connection/command
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.mqtt] - Subscribing to topic viseron/toggle/camera_2_connection/command
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.mqtt] - Subscribing to topic viseron/toggle/camera_3_connection/command
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_2] - Running cleanup
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_3] - Running cleanup
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_1] - Running cleanup
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Backyard Recorder from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/recorder/start, <bound method RecorderBinarySensor.handle_start_event of <viseron.domains.camera.entity.binary_sensor.RecorderBinarySensor object at 0x7f5fb0024160>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/recorder/stop, <bound method RecorderBinarySensor.handle_stop_event of <viseron.domains.camera.entity.binary_sensor.RecorderBinarySensor object at 0x7f5fb0024160>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_3_recorder to state: off, attributes {'name': 'Backyard Recorder', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Backyard Latest Thumbnail from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/recorder/start, <bound method ThumbnailImage.handle_event of <viseron.domains.camera.entity.image.ThumbnailImage object at 0x7f5fb0080ac0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of image.camera_3_latest_thumbnail to state: unknown, attributes {'name': 'Backyard Latest Thumbnail', 'domain': 'image', 'start_time': None, 'path': None, 'thumbnail_path': None}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_3] - Initializing recorder
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method SegmentCleanup.shutdown of <viseron.components.ffmpeg.segments.SegmentCleanup object at 0x7f5fb0026b20>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_3] - Initializing camera Backyard
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_3] - Resolution: 2560x1440 @ 10 FPS
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_3] - Camera Backyard initialized
[2023-05-04 13:46:15] [DEBUG   ] [viseron.core] - Registering domain camera with identifier camera_3
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setup of domain camera for component ffmpeg with identifier camera_3 took 0.0 seconds
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.compreface.face_recognition.camera_3] - Post processor will run for labels: ['person']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.watchdog] - Registering <RestartableThread(viseron.domains.post_processor, initial daemon)> in the watchdog
[2023-05-04 13:46:15] [ERROR   ] [viseron.components.nvr.nvr] - Failed setup of domain nvr for camera camera_3. At least one object or motion detector has to be configured
[2023-05-04 13:46:15] [ERROR   ] [viseron.components] - Setup of domain nvr for component nvr with identifier camera_3 failed
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/objects, <queue.Queue object at 0x7f5fb007be80>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/zone/*/objects, <queue.Queue object at 0x7f5fb007be80>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Storage Room Recorder from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/recorder/start, <bound method RecorderBinarySensor.handle_start_event of <viseron.domains.camera.entity.binary_sensor.RecorderBinarySensor object at 0x7f5fb00240d0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/recorder/stop, <bound method RecorderBinarySensor.handle_stop_event of <viseron.domains.camera.entity.binary_sensor.RecorderBinarySensor object at 0x7f5fb00240d0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_2_recorder to state: off, attributes {'name': 'Storage Room Recorder', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Storage Room Latest Thumbnail from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/recorder/start, <bound method ThumbnailImage.handle_event of <viseron.domains.camera.entity.image.ThumbnailImage object at 0x7f5fb0080c10>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of image.camera_2_latest_thumbnail to state: unknown, attributes {'name': 'Storage Room Latest Thumbnail', 'domain': 'image', 'start_time': None, 'path': None, 'thumbnail_path': None}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_2] - Initializing recorder
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Backyard Face Detected Keith from component compreface
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/face/detected/keith, <bound method FaceDetectionBinarySensor.face_detected of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0039040>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/face/expired/keith, <bound method FaceDetectionBinarySensor.face_expired of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0039040>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_3_face_detected_keith to state: off, attributes {'name': 'Backyard Face Detected Keith', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Backyard Face Detected Lorri from component compreface
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/face/detected/lorri, <bound method FaceDetectionBinarySensor.face_detected of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb00392b0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/face/expired/lorri, <bound method FaceDetectionBinarySensor.face_expired of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb00392b0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_3_face_detected_lorri to state: off, attributes {'name': 'Backyard Face Detected Lorri', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Backyard Face Detected Leah from component compreface
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/face/detected/leah, <bound method FaceDetectionBinarySensor.face_detected of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0039520>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_3/face/expired/leah, <bound method FaceDetectionBinarySensor.face_expired of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0039520>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_3_face_detected_leah to state: off, attributes {'name': 'Backyard Face Detected Leah', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setup of domain face_recognition for component compreface with identifier camera_3 took 0.0 seconds
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method SegmentCleanup.shutdown of <viseron.components.ffmpeg.segments.SegmentCleanup object at 0x7f5fb0118a00>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_2] - Initializing camera Storage Room
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_2] - Resolution: 2560x1440 @ 10 FPS
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_2] - Camera Storage Room initialized
[2023-05-04 13:46:15] [DEBUG   ] [viseron.core] - Registering domain camera with identifier camera_2
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setup of domain camera for component ffmpeg with identifier camera_2 took 0.0 seconds
[2023-05-04 13:46:15] [ERROR   ] [viseron.components.nvr.nvr] - Failed setup of domain nvr for camera camera_2. At least one object or motion detector has to be configured
[2023-05-04 13:46:15] [ERROR   ] [viseron.components] - Setup of domain nvr for component nvr with identifier camera_2 failed
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.compreface.face_recognition.camera_2] - Post processor will run for labels: ['person']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.watchdog] - Registering <RestartableThread(viseron.domains.post_processor, initial daemon)> in the watchdog
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/objects, <queue.Queue object at 0x7f5fb00267c0>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/zone/*/objects, <queue.Queue object at 0x7f5fb00267c0>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Storage Room Face Detected Keith from component compreface
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/face/detected/keith, <bound method FaceDetectionBinarySensor.face_detected of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fe8057880>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/face/expired/keith, <bound method FaceDetectionBinarySensor.face_expired of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fe8057880>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_2_face_detected_keith to state: off, attributes {'name': 'Storage Room Face Detected Keith', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Storage Room Face Detected Lorri from component compreface
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/face/detected/lorri, <bound method FaceDetectionBinarySensor.face_detected of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb00473a0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/face/expired/lorri, <bound method FaceDetectionBinarySensor.face_expired of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb00473a0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_2_face_detected_lorri to state: off, attributes {'name': 'Storage Room Face Detected Lorri', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Storage Room Face Detected Leah from component compreface
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/face/detected/leah, <bound method FaceDetectionBinarySensor.face_detected of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0047610>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_2/face/expired/leah, <bound method FaceDetectionBinarySensor.face_expired of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0047610>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_2_face_detected_leah to state: off, attributes {'name': 'Storage Room Face Detected Leah', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setup of domain face_recognition for component compreface with identifier camera_2 took 0.0 seconds
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_1] - Items in /recordings/camera_1/2023-05-04: 99
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Recorder from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/recorder/start, <bound method RecorderBinarySensor.handle_start_event of <viseron.domains.camera.entity.binary_sensor.RecorderBinarySensor object at 0x7f5fb0024c10>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/recorder/stop, <bound method RecorderBinarySensor.handle_stop_event of <viseron.domains.camera.entity.binary_sensor.RecorderBinarySensor object at 0x7f5fb0024c10>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_recorder to state: off, attributes {'name': 'Front Door Recorder', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Latest Thumbnail from component ffmpeg
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/recorder/start, <bound method ThumbnailImage.handle_event of <viseron.domains.camera.entity.image.ThumbnailImage object at 0x7f5fe805e6a0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of image.camera_1_latest_thumbnail to state: unknown, attributes {'name': 'Front Door Latest Thumbnail', 'domain': 'image', 'start_time': None, 'path': None, 'thumbnail_path': None}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.recorder.camera_1] - Initializing recorder
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method SegmentCleanup.shutdown of <viseron.components.ffmpeg.segments.SegmentCleanup object at 0x7f5fb003faf0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_1] - Initializing camera Front Door
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_1] - Resolution: 2560x1440 @ 10 FPS
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_1] - Camera Front Door initialized
[2023-05-04 13:46:15] [DEBUG   ] [viseron.core] - Registering domain camera with identifier camera_1
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setup of domain camera for component ffmpeg with identifier camera_1 took 0.0 seconds
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.compreface.face_recognition.camera_1] - Post processor will run for labels: ['person']
[2023-05-04 13:46:15] [DEBUG   ] [viseron.watchdog] - Registering <RestartableThread(viseron.domains.post_processor, initial daemon)> in the watchdog
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/objects, <bound method ObjectDetectedBinarySensorLabel.handle_event of <viseron.domains.object_detector.binary_sensor.ObjectDetectedBinarySensorFoVLabel object at 0x7f5fb00390d0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Object Detected Person from component darknet
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/nvr/object_detector/scan, <bound method ObjectDetectedBinarySensorLabel.handle_stop_scan of <viseron.domains.object_detector.binary_sensor.ObjectDetectedBinarySensorFoVLabel object at 0x7f5fb00390d0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_object_detected_person to state: off, attributes {'name': 'Front Door Object Detected Person', 'domain': 'binary_sensor', 'count': 0, 'objects': []}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/objects, <bound method ObjectDetectedBinarySensorLabel.handle_event of <viseron.domains.object_detector.binary_sensor.ObjectDetectedBinarySensorFoVLabel object at 0x7f5fb0039340>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Object Detected Dog from component darknet
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/nvr/object_detector/scan, <bound method ObjectDetectedBinarySensorLabel.handle_stop_scan of <viseron.domains.object_detector.binary_sensor.ObjectDetectedBinarySensorFoVLabel object at 0x7f5fb0039340>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_object_detected_dog to state: off, attributes {'name': 'Front Door Object Detected Dog', 'domain': 'binary_sensor', 'count': 0, 'objects': []}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/objects, <bound method ObjectDetectedBinarySensorLabel.handle_event of <viseron.domains.object_detector.binary_sensor.ObjectDetectedBinarySensorFoVLabel object at 0x7f5fb0047160>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Object Detected Cat from component darknet
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/nvr/object_detector/scan, <bound method ObjectDetectedBinarySensorLabel.handle_stop_scan of <viseron.domains.object_detector.binary_sensor.ObjectDetectedBinarySensorFoVLabel object at 0x7f5fb0047160>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_object_detected_cat to state: off, attributes {'name': 'Front Door Object Detected Cat', 'domain': 'binary_sensor', 'count': 0, 'objects': []}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.watchdog] - Registering <RestartableThread(camera_1.object_detection, initial daemon)> in the watchdog
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/objects, <queue.Queue object at 0x7f5fb0030d60>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/zone/*/objects, <queue.Queue object at 0x7f5fb0030d60>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic object_detector/camera_1/scan, <queue.Queue object at 0x7f5fb003f9a0>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/nvr/object_detector/scan, <bound method AbstractObjectDetector.handle_stop_scan of <viseron.components.darknet.object_detector.ObjectDetector object at 0x7f5fb003fd30>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method AbstractObjectDetector.stop of <viseron.components.darknet.object_detector.ObjectDetector object at 0x7f5fb003fd30>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/objects, <bound method ObjectDetectedBinarySensor.handle_event of <viseron.domains.object_detector.binary_sensor.ObjectDetectedBinarySensorFoV object at 0x7f5fb003ff10>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Object Detected from component darknet
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/nvr/object_detector/scan, <bound method ObjectDetectedBinarySensor.handle_stop_scan of <viseron.domains.object_detector.binary_sensor.ObjectDetectedBinarySensorFoV object at 0x7f5fb003ff10>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_object_detected to state: off, attributes {'name': 'Front Door Object Detected', 'domain': 'binary_sensor', 'count': 0, 'objects': []}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Object Detector FPS from component darknet
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_1_object_detector_fps to state: 0, attributes {'name': 'Front Door Object Detector FPS', 'domain': 'sensor', 'preprocessor_fps': 0, 'inference_fps': 0, 'theoretical_max_fps': 0}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.core] - Registering domain object_detector with identifier camera_1
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setup of domain object_detector for component darknet with identifier camera_1 took 0.0 seconds
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.nvr.nvr.camera_1] - Initializing NVR for camera Front Door
[2023-05-04 13:46:15] [INFO    ] [viseron.components.nvr.nvr.camera_1] - Motion detector is disabled
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Face Detected Keith from component compreface
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic object_detector/camera_1/result, <queue.Queue object at 0x7f5fb00808b0>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/face/detected/keith, <bound method FaceDetectionBinarySensor.face_detected of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0105610>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/face/expired/keith, <bound method FaceDetectionBinarySensor.face_expired of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0105610>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_face_detected_keith to state: off, attributes {'name': 'Front Door Face Detected Keith', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Face Detected Lorri from component compreface
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/face/detected/lorri, <bound method FaceDetectionBinarySensor.face_detected of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0049310>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/face/expired/lorri, <bound method FaceDetectionBinarySensor.face_expired of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0049310>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_face_detected_lorri to state: off, attributes {'name': 'Front Door Face Detected Lorri', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Face Detected Leah from component compreface
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/face/detected/leah, <bound method FaceDetectionBinarySensor.face_detected of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0049cd0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/face/expired/leah, <bound method FaceDetectionBinarySensor.face_expired of <viseron.domains.face_recognition.binary_sensor.FaceDetectionBinarySensor object at 0x7f5fb0049cd0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_face_detected_leah to state: off, attributes {'name': 'Front Door Face Detected Leah', 'domain': 'binary_sensor'}
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setup of domain face_recognition for component compreface with identifier camera_1 took 0.0 seconds
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic camera_1/camera/frame_bytes, <queue.Queue object at 0x7f5fb0054970>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.watchdog] - Registering <RestartableThread(<viseron.components.nvr.nvr.NVR object at 0x7f5fb006ec70>, initial)> in the watchdog
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.nvr.nvr.camera_1] - Waiting for first frame
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Adding entity Front Door Operation State from component nvr

[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/camera_1/nvr/operation_state, <bound method OperationStateSensor.handle_event of <viseron.components.nvr.sensor.OperationStateSensor object at 0x7f5fb00808e0>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_1_operation_state to state: unknown, attributes {'name': 'Front Door Operation State', 'domain': 'sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method NVR.stop of <viseron.components.nvr.nvr.NVR object at 0x7f5fb006ec70>>
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.camera.camera_1] - Starting capture thread
[2023-05-04 13:46:15] [DEBUG   ] [viseron.watchdog] - Registering <RestartableThread(viseron.camera.camera_1, initial daemon)> in the watchdog
[2023-05-04 13:46:15] [DEBUG   ] [viseron.components.ffmpeg.stream.camera_1] - FFmpeg decoder command: ffmpeg_camera_1 -hide_banner -loglevel error -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts -use_wallclock_as_timestamps 1 -vsync 0 -timeout 5000000 -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -c:v hevc -rtsp_transport tcp -i rtsp://*****:*****@10.0.0.237:554/user=admin_password=1bpcecDK_channel=0_stream=0&onvif=0.sdp?real_stream -f segment -segment_time 5 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac /segments/camera_1/%Y%m%d%H%M%S.mp4 -f rawvideo -pix_fmt nv12 pipe:1
[2023-05-04 13:46:15] [INFO    ] [viseron.components.nvr.nvr.camera_1] - NVR for camera Front Door initialized
[2023-05-04 13:46:15] [INFO    ] [viseron.components] - Setup of domain nvr for component nvr with identifier camera_1 took 0.0 seconds
[2023-05-04 13:46:15] [INFO    ] [viseron.core] - Viseron initialized in 1.5 seconds
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_1_operation_state to state: idle, attributes {'name': 'Front Door Operation State', 'domain': 'sensor'}
[2023-05-04 13:46:15] [DEBUG   ] [viseron.states] - Setting state of toggle.camera_1_connection to state: on, attributes {'name': 'Front Door Connection', 'domain': 'toggle'}
[2023-05-04 13:46:16] [DEBUG   ] [viseron.states] - Setting state of sensor.camera_1_operation_state to state: scanning_for_objects, attributes {'name': 'Front Door Operation State', 'domain': 'sensor'}
[2023-05-04 13:46:16] [DEBUG   ] [viseron.components.webserver.websocket_api] - WebSocket opened
[2023-05-04 13:46:16] [DEBUG   ] [viseron.components.webserver.websocket_api] - Received {"type":"subscribe_event","event":"domain/registered/camera","command_id":1}
[2023-05-04 13:46:16] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/domain/registered/camera, <function subscribe_event.<locals>.forward_event at 0x7f5fb0027ca0>
[2023-05-04 13:46:16] [DEBUG   ] [viseron.components.webserver.websocket_api] - Received {"type":"subscribe_event","event":"*/recorder/complete","command_id":2}
[2023-05-04 13:46:16] [DEBUG   ] [viseron.components.data_stream] - Subscribing to data topic event/*/recorder/complete, <function subscribe_event.<locals>.forward_event at 0x7f5fb0027790>
[2023-05-04 13:46:18] [ERROR   ] [viseron.components.ffmpeg.stream.camera_1] - [hevc @ 0x560d09a52a40] Could not find ref with POC 1
[2023-05-04 13:46:18] [DEBUG   ] [viseron.states] - Setting state of binary_sensor.camera_1_connected to state: on, attributes {'name': 'Front Door Connected', 'domain': 'binary_sensor'}

Oh and I believe you had asked on reddit about using darknet with AMD GPU and CPU? I'm running AMD RX 5500XT GPU and AMD Ryzen 5 3600 CPU

To reduce the false positivies you can increase the confidence and set the min/max heights to filter out unreasonable small or large objects

repo: roflcoopter/viseron


text:
Documentation for installing on Windows

Could you please add an example command and advice for installing Viseron on Windows 10?
There are only linux examples on https://viseron.netlify.app/docs/documentation/installation#running-viseron.
Context: I have Docker desktop installed with WSL 2, and an Nvidia GPU for CUDA (https://docs.docker.com/desktop/features/gpu/). I'd like to move away from Frigate to Viseron to take advantage of my GPU.
Thank you for your work!
EDIT: I was unclear above - I have docker desktop installed as a windows application, and also have WSL 2 installed (in order to do the GPU stuff, as that's what docker says it needs in the link above).

Sorry I was unclear - I have docker desktop installed as a windows application, not in WSL. I installed WSL just so that docker can use my GPU - that's one of the requisites it mentioned in https://docs.docker.com/desktop/features/gpu/.
I did try the linux command (just for fun, I knew it wouldn't work on windows anyway as it was looking for /etc/localtime).
I hope the above makes sense. I'm looking to run this container on a windows machine, from a windows command line (or via the docker UI / configuration pages, with some way to just make it run on computer boot). Thank you :)

I see.
Sadly i dont have a machine to test this so you are gonna have to do some digging on your own.
Seems to be possible tho: https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/linux-containers
But why cant you run Viseron in WSL instead?

I finally got some time to give this another go - you're right, it's possible, and actually docker desktop for windows automatically integrates with WSL 2 if it's present. That allows calling docker commands in the WSL2 linux environment, which means I can use your example configurations. I've managed to get a container with Viseron going.
I'm having trouble actually picking up my camera stream, and it looks like it's not talking to my GPU yet, but I'll raise separate issues for that. Thanks!

source: gharchive/issue

authors: Aralox roflcoopter

license: MIT

license_type: permissive

license_source: github-api


text:
Rhl title overlaps hamburger on smart phone

Galaxy Note 4.

Fixed 60ffaf1

missread commit message.
and didn't test enough... 🥇

repo: rogue-hack-lab/rhl-new

license: mit

license_source: bigquery


text:
Can suggestions be mandatory?

If I type something that is not in the suggestion field, it can be saved. Can that be prevented? That is, force acceptance of a suggestion or reject the entry?

@mauricev you mean if suggestion list is empty after search then remove the search text?

Yes, this is the behavior of selective.js.

@mauricev not able to see your attachment. Please verify your file.

I haven't posted any attachment. In my previous message I am referring to this, https://selectize.dev/

@mauricev  can you share any recording or something with me. So, I can understand what exactly you want me to add.


text:
Test README

We might need to write something in the README file in the test folder inside src.

Done!

repo: rohitgeddam/FindMyRoomie


text:
Segmentation fault on RaspberryPi Zero

Hi,
I found your guide here and it worked great all the way up to running the binaries on the Pi Zero... after which I got
Segmentation fault
I tried pulling down your most recent update and recompiling with the same effect. Am I missing something glaring me in the face? I've seen online that there are quite a few posts about grpc not working on Pi's, but it seems to be running ARMv6 (your compile doesn't seem to be version specific?)
Any help or guidance much appreciated

leaving answer here in case someone comes looking... seems like rPi Zero has an ARMv6Z, which is not supported by the compiler used in this doc (linux-gnueabihf supports armhf, which requires your ARM be v7 or higher...).
TLDR
./Dockerfile
ENV GNU_HOST=arm-linux-gnueabihf
-->
ENV GNU_HOST=arm-linux-gnueabi

Hi @parksj10. Sorry for the late reply, but my wife and I just had a 👶 and I suddently don't have time to do anything. Your suggestion makes sense, just use a different compiler (maybe the one in raspberrypi/tools). You may also find more info here.

repo: rolandjitsu/grpc-cross-arm


text:
Generate system messages for the Message Board

Automatically generate system messages, like:

There are X messages on the board.
The time is XX:XX.
The last user messages has been posted XX minutes ago.
X user messages have dropped from the board so far.
... more useless statistics ...

Depends on issue #16: support slots for system messages.
Note that the default implementation MixedMessageBoard is not thread-safe. Either use a thread-safe wrapper (similar to java.util.Collections.synchronizedSortedMap), or trigger message generation synchronously from the SimplisticSocketHandler. The purpose of this task is to see changes of the board messages, even if testing on a local system with a single user. At the same time, the board should not flow over from pointless system messages, so these should use only a few slots and replace older system messages.

Won't be implemented with the current Message Board.

repo: rolandweber/pityoulish


text:
Bug Report: CPU usage is > 10%

Describe the bug
The CPU usage seems to be extremely high for a timer app.
To Reproduce
Run the timer, check Activity Monitor on macOS.
Expected behavior
To have sub 1% CPU usage.
Screenshots

Desktop (please complete the following information):

OS: macOS Catalina
Version 10.15.4 (19E287)

Additional context
This only happens Timer tab is open. If I switch the tab to another one (e.g. Settings), then the usage subsides. So I am guessing it's the countdown timer itself that is taking up all of the CPU.

Describe the bug
The CPU usage seems to be extremely high for a timer app.
To Reproduce
Run the timer, check Activity Monitor on macOS.
Expected behavior
To have sub 1% CPU usage.
Screenshots

Desktop (please complete the following information):

OS: macOS Catalina
Version 10.15.4 (19E287)

Additional context
This only happens Timer tab is open. If I switch the tab to another one (e.g. Settings), then the usage subsides. So I am guessing it's the countdown timer itself that is taking up all of the CPU.

You're right @moltar. It is mention also here #62 by @sekwah41 .
Just try to disabled Timer Animation. It might due to High Frame Rate.
I just noticed that It happened to users laptop with High Graphics Card.
I hope disabling Timer Animation will help.

I can confirm. The issue is electron is trying to animate it at as many frames a second as it can. Due to the type of elements, it is redrawing electron isn't exactly the most efficient at doing this which I doubt is an issue in their eyes as most animations are only temporary. Disabling this setting changes it to a fraction of the performance hit.

Yes, that does make it better. Thanks! :)

If this issue is resolved id suggest closing it :)
Some benefits may be found in launch arguments for electron though I don't believe this sort of fine-tuning should be a general issue for this application as it seems more of an electron issue unless there are specific launch arguments that could be configured though I believe by default it has things such as vsync enabled.

Thank you @sekwah41 .

I would suggest to make a performance improvement by trying to set FPS to 1 (it doesn't have to draw it faster than once a second). Or even once per minute or something. I would still like to see the progress bar :)

repo: roldanjr/pomatez


text:
Endless loading of folders

When I put the code from google, the loading starting. After one hour I still have this:
100   552    0   287  100   265    775    716 --:--:-- --:--:-- --:--:--  1500   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   967    0   967    0     0   2375      0 --:--:-- --:--:-- --:--:--  2393   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   552    0   287  100   265    872    805 --:--:-- --:--:-- --:--:--  1698   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   967    0   967    0     0   2134      0 --:--:-- --:--:-- --:--:--  2134   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   552    0   287  100   265    867    800 --:--:-- --:--:-- --:--:--  1677   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   967    0   967    0     0   2286      0 --:--:-- --:--:-- --:--:--  2296   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   552    0   287  100   265    580    536 --:--:-- --:--:-- --:--:--  1117   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   967    0   967    0     0   2318      0 --:--:-- --:--:-- --:--:--  2324   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   552    0   287  100   265    769    710 --:--:-- --:--:-- --:--:--  1479   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   967    0   967    0     0   1981      0 --:--:-- --:--:-- --:--:--  1981   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   552    0   287  100   265    829    765 --:--:-- --:--:-- --:--:--  1628   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   967    0   967    0     0   2202      0 --:--:-- --:--:-- --:--:--  2202   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   552    0   287  100   265    836    772 --:--:-- --:--:-- --:--:--  1623   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   967    0   967    0     0   2330      0 --:--:-- --:--:-- --:--:--  2335   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   552    0   287  100   265    741    684 --:--:-- --:--:-- --:--:--  1430   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   967    0   967    0     0   2341      0 --:--:-- --:--:-- --:--:--  2370   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   552    0   287  100   265    839    774 --:--:-- --:--:-- --:--:--  1618   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   967    0   967    0     0   2275      0 --:--:-- --:--:-- --:--:--  2324   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed 100   552    0   287  100   265    914    843 --:--:-- --:--:-- --:--:--  1774

I hope it'll be finished before you answer @roleoroleo :)

I found this issue:

Processing with it

I solved it by enabling the Drive API. Sorry, my fault. Or google's (I did it yesterday)


text:
Fix exclude-caches directive

It's called --exclude-caches, not --exclude-cache
see https://restic.readthedocs.io/en/latest/040_backup.html#excluding-files

thanks :kissing_heart:

source: gharchive/pull-request


text:
use spawn instead of fork method

spawn is cleaner https://stackoverflow.com/a/66113051/1658314
work around an issue in s3fs https://github.com/fsspec/s3fs/issues/464#issuecomment-830846568

using get_context might be cleaner


text:
Create SVGO module to preprocess SVG strings

LMK what you think of this! :)
BTW, I'm not sure which plugins we should actually run... haven't thought much about it. So I just included all of them for now and maybe we can decide later or something. IDK I'm fine with whatever.

Let's revisit this if and when there's a concrete need to use svgo (for example to simplify paths or something).

FWIW, ShapeShifter's SVG importer has been working significantly better ever since I started pre-processing the SVGs using svgo.
The plugins I am currently using are listed here.

authors: alexjlockwood romannurik

repo: romannurik/AndroidIconAnimator


text:
feat: add mean and stdev to stats

feat: add mean and stdev to stats
Summary:
Currently, zsh-bench records the minimum value of each metric.
This commit adds the more precise metrics mean and standard deviation.
Test plan:
Before:
$ ./zsh-bench
==> benchmarking login shell of user max ...
creates_tty=0
has_compsys=1
has_syntax_highlighting=1
has_autosuggestions=0
has_git_prompt=1
first_prompt_lag_ms==22.610
first_command_lag_ms==140.186
command_lag_ms==7.516
input_lag_ms==4.275
exit_time_ms==98.705

After:
$ ./zsh-bench
==> benchmarking login shell of user max ...
creates_tty=0
has_compsys=1
has_syntax_highlighting=1
has_autosuggestions=0
has_git_prompt=1
first_prompt_lag_ms==22.610±0.67
first_command_lag_ms==140.186±3.61
command_lag_ms==7.516±0.52
input_lag_ms==4.275±0.25
exit_time_ms==98.705±3.48

What's the motivation for the PR?

What's the motivation for the PR?

I saw a video by Sabine Hossenfelder who said, "Data without error bars isn't science.".  Ever since then I've had this nagging voice in my head whenever I see data without error bars.
When I used this tool to measure my own zsh config I saw my command lag was "7.5ms", but I wasn't sure if it was exactly 7.5ms every time or if there was some variance.  I added the standard deviation calculation to check the variance of the command lag.

We aren't doing science here. The purpose of zsh-bench is to optimize code. Neither mean nor stddev help with this.

We aren't doing science here. The purpose of zsh-bench is to optimize code. Neither mean nor stddev help with this.

Why wouldn't knowing whether or not a metric has a high variance help with optimizing code?

The purpose of zsh-bench is to optimize code.

If the measurement before a change is min=39, and the measurement after a change is min=37, did the change improve performance, make it worse, or have no effect?
If the tool then told you ±6, would that change your conclusion?

The noise comes from all sort of sources that are unrelated to the code we care about: from other applications, from CPU frequency scaling, etc. We don't want noise, so we want to somehow get rid of it. One option is to compute mean, the other is to compute min. The latter converges a whole lot faster, meaning that we can run the benchmark for less time.

Why wouldn't knowing whether or not a metric has a high variance help with optimizing code?

You are sending a patch to my code. If you cannot convince me why it's a good change, I won't merge it. This of course should not stop you from using your code yourself. Then, if I send you a patch, you won't merge it unless you'll believe it makes your code better.

@strager The answer to your first question is "it depends". The second is an easy "no": stddev is irrelevant when looking at the min. You should see it if you imagine looking at many samples of a random variable and picking the minimum. With ±6 stddev, it won't take long for the min to converge.

We don't want noise, so we want to somehow get rid of it. One option is to compute mean, the other is to compute min. The latter converges a whole lot faster, meaning that we can run the benchmark for less time.

Point taken for mean.  I agree min could be a better metric.  However, I still thing stddev is helpful.  The stddev can help identify the inherent "noise" that you mention.  The stddev can help point users to what their real lag will be instead of the best case.  As strager pointed out, it can also help identify whether changes to your config affects performance.
I agree with "We don't want noise, so we want to somehow get rid of it".  If I run the zsh-bench in master rn twice without changing any configs and set the iterations to 32, I'll still get slightly different results.  Therefore, how can I know if changes to my config actually make a difference?  The stddev is one tool I can use to inform my decision.  Ideally I'd want some sort of p-value too, but as you said, "We aren't doing science here." 😛

I presume that we all agree that > The purpose of zsh-bench is to optimize code.
Though, the opinions on what the optimization target is vary apparently:
I got the impression that @romkatv so far intended to reduce the minimal execution time as a measure of factual overhead a shell extention such as z4h introduces.
Others like @vegerot want to utilize zsh-bench to empirically inform their decision on whether (and in which way) a certain change in their shell configuration has impact on the their future shell experience.
As @romkatv mentioned himself: > We don't want noise, so we want to somehow get rid of it.
I agree that indeterministic behaviour is unfavorable in most circumstances, I can't agree though that one actually get's rid of the noise by > comput[ing the] mean, [or the] min.
It's just a way of not reporting the observed noise by choosing a specific metric. Some care about the actual behaviour of their shell and noise is part of it.
I understand where @romkatv is coming from as they mention their assumption that  > the noise comes from all sort of sources that are unrelated to the code we care about
I have to disagree with this assumption though, as changing the shell configuration won't necessarily only impact the minimal overhead (for this the min metric is totally adequate and sufficient) but can also contribute to the variance of the actual overhead.
Example:
Say one changes the shell config and thus makes the shell depend on some data that most of the time is fetched quite fast but sometimes with high latency, then this might change one's decision to opt-in for this change.
IMHO it's not trivial or obvious that z4h runs perfectly deterministic (actually it does not, hence the min metric), so the question is what should be optimized for?
Many software projects relied on timing sh -lic "exit" before zsh-bench was introduced and as it turns out, this metric has not actually been a useful proxy for optimizing what users value.
I can't help myself but see the parallel in the way zsh-bench currently measures the min metric while users don't care about the optimal scenario only, but want to know what to actually expect in total.
It's a bit like a company selling some ultra fast storage medium with "up to 10GB/s". Technical users often want to know how the storage performs across the spectrum and not under ideal and lab controlled circumstances.
So while not arguing over whether the scientific method is relevant here or whether error bars are required for it, I must say that zsh-bench should somehow report what it actually measures.
Like "Those are the minimal timings observed when running the measurment for X number of times."
I myself ran zsh-bench multiple times to observe the variance in the reported timings. Also, till I viewed this pull request, I thought those timings report the average timing, not the min.
Maybe a good solution would be to either provide an option to

) report/log all measured values, or
) report the min, the meadian, and the max

Either way, I think zsh-should inform the user along the data what the meaning of the data is (no pun intended).

zsh-bench is a tool that I use to optimize my code. This code's performance variance comes solely from the outside. Hence min gets rid of unwanted noise.

As mentioned in the wall of text before,
I have to disagree with the assumption that "variance comes solely from the outside":
Changing the shell configuration won't necessarily only impact the minimal overhead but can introduce variance itself.

I might be wrong. Can you show the part of my code that has intrinsic performance variance?

I submit to the Unix philosophy of "Doing one thing and doing it well".
Neither the calculation of distribution metrics nor optimizing code is the primary purpose of zsh-bench (the latter being the job of the programmer).
The goal of zsh-bench AFAIK is to offer a good benchmark. Whether offering a min metric as a default is a good UX design choice is a different topic.
Since zsh-bench offers the --raw flag, the data can be piped it into any program (e.g. like zsh-bench-hist) for further processing or visualization.
@vegerot I hope the tool suits your needs just as it suits mine.

I want to share some real data (although sadly unrelated to zsh4humans) with you:
When benchmarking unrelated projects, it's noteworthy that optimizing for reduced mean time, reduced variance of the mean time, and achieving the global minimum (among larger timings) can lead to different solutions being selected.Consider the following results from 100,000 samples each:

Method
Mean Time
Standard Deviation Time
Minimum Time

Using np.tile
40.181 µs
1110.338 µs
8.821 µs

Using np.full
30.678 µs
1058.533 µs
6.199 µs

Using np.broadcast_to
42.571 µs
1341.520 µs
5.960 µs

Using list and np.array
396.100 µs
3509.649 µs
95.367 µs

@romkatv, I appreciate your inclusion of --raw, recognizing that there isn't typically a singular "correct" solution.
@vegerot,
In regards to this PR, while displaying the standard error of the chosen metric could enhance comprehension, revealing the mean and standard deviation of the timings may not be as beneficial.
This is because the distribution is not necessarily Gaussian, and analyzing the spread of the samples won't offer definitive insight into the standard error of the mean.
To present data with "error bars," one would need to execute the benchmark multiple times (or segment it), aggregating samples to the metric (such as mean/min, etc.) for each run, and then report the variance of the metric using an appropriate estimator.
However, this approach differs from providing the standard deviation of the samples themselves.
For those seeking a general sense of the distribution, it might be more informative to report the minimum, maximum, as well as some intermediary percentiles like the 5th, 50th (median), and 95th percentile.

authors: Semnodime romkatv strager vegerot

repo: romkatv/zsh-bench


text:
Downgrade indexmap in CI for MSRV

Alternative to #384 and #385
Fixes #383
* [ ] I've included my change in CHANGELOG.md

@torkleyy This would be a fix to just get CI to work again, we could then add docs or switch to a different fix later

Codecov Report

Merging #386 (04f09ce) into master (46dc2b6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #386   +/-   ##
=======================================
  Coverage   89.65%   89.65%
=======================================
  Files          48       48
  Lines        5228     5228
=======================================
  Hits         4687     4687
  Misses        541      541

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 46dc2b6...04f09ce. Read the comment docs.

authors: MomoLangenstein codecov-commenter

repo: ron-rs/ron


text:
Ignore Feature

Improved syntax

@kurtisnelson Sorry, I haven't had a chance to look at this.  GIven the changes in #8, would that help with the failures here?

It still fails with that stuff merged in.

authors: kurtisnelson ronen

repo: ronen/rspec-page-regression


text:
add u/d keybindings

This adds the u/d keybindings (scroll up/down half a page) found in less.
Test this in a julia repl with the working directory at the root of this repository:
include("src/TerminalPager")
[i for i in 1:100] |> TerminalPager.pager

Thanks @pohzipohzi !!
Is it possible to add tests for those keybindings here:
https://github.com/ronisbr/TerminalPager.jl/blob/main/test/internals/key_bindings.jl

Hi @pohzipohzi !
Sorry for the delay, I missed that you had pushed the tests. Thanks!!

authors: pohzipohzi ronisbr


text:
Better error reporting in rooki

Hi @cehbrecht and @agstephens,
I've just been looking over our first day of live CMIP6 requests, and it looks like we got a total of 167 requests. 85% of these were successful, but we have 27 failed requests, and there's a consistent theme - most of the failed requests asked for a very small area subset for their data (possibly in an attempt to extract just a single point).
How we want to handle these kind of requests is one problem, but more imminently important is that we properly report to users what went wrong with their request. We had a single user who made most of those failed requests, because the error they received simply said 'Sorry, process failed' (inherited from rooki). If this had said something like 'Invalid spatial subset', that would have been much more useful and the user would probably have corrected their mistake.
I assume clisops is actually raising a useful error somewhere, so the question is - is it possible to get that error propagated down into the final rooki error?
Many thanks!

Actually we should already capture the errors. I have no "sorry" ones in my list from today:

For the stats: on dkrz side I have:

@agstephens do you have other failures on your side than those we have collected, like process rejected  ... or so ...

Thanks a lot @cehbrecht - I've integrated the response.status into the exceptions raised by the CDS adaptor.
The one issue I would raise is that the exception I get for requesting a bad area subset is not very infortmative - it simply says:
Process error: float divmod

@agstephens is this inherited from clisops? Would it be possible to have something a bit more informative for the users?
Thanks!

Hi @JamesVarndell: here is an update from our end:

We haven't been able to find where the 'Sorry, process failed' has come from. Please send us a request if you have one so we can track this down.
We are creating a fix for the bounding box issue so that if no grid boxes are found it will raise an appropriate exception.
We have also seen some errors when selecting to YYYY-12-31 on a 360-day calendar, we are writing a fix to nudge the selection to a valid date so that these will just work.

Thanks a lot @cehbrecht - I've integrated the response.status into the exceptions raised by the CDS adaptor.
The one issue I would raise is that the exception I get for requesting a bad area subset is not very infortmative - it simply says:
Process error: float divmod

@agstephens is this inherited from clisops? Would it be possible to have something a bit more informative for the users?
Thanks!

@JamesVarndell this is the issue where the user selects a bounding box that is so small it falls between the grid box centres. @ellesmith88 is creating a suitable exception for this.

authors: JamesVarndell agstephens cehbrecht

repo: roocs/rook


text:
🛑 API is down

In 07633eb, API (https://alpha.rookoo.ai/api) was down:

HTTP code: 0
Response time: 0 ms

Resolved: API is back up in b458ebb after 3 hours, 22 minutes.

repo: rookoo-ai/statuspage


text:
🛑 TROJAN 🇩🇪 Germany DEH 1 is down

In 804028c, TROJAN 🇩🇪 Germany DEH 1 (https://det-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇩🇪 Germany DEH 1 is back up in 336a6fb.

repo: roosterkid/opentunnel-status-server


text:
🛑 V2RAY 🇸🇬 Singapore SGO 3 is down

In 57b511b, V2RAY 🇸🇬 Singapore SGO 3 (https://sgv-4.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇸🇬 Singapore SGO 3 is back up in 59b0a52.


text:
🛑 V2RAY 🇮🇩 Indonesia IDA 2 is down

In 08e91b6, V2RAY 🇮🇩 Indonesia IDA 2 (https://idv-3.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇮🇩 Indonesia IDA 2 is back up in 2c38977.


text:
🛑 SSH 🇬🇧 United Kingdom UKO 1 is down

In e1bf998, SSH 🇬🇧 United Kingdom UKO 1 (http://uks-2.optnl.com:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇬🇧 United Kingdom UKO 1 is back up in f729eb5.


text:
🛑 TROJAN 🇺🇸 United States USO 1 is down

In 3b21139, TROJAN 🇺🇸 United States USO 1 (https://ust-2.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇺🇸 United States USO 1 is back up in 54cc3a3.


text:
🛑 OVPN 🇸🇬 Singapore SGC 2 is down

In ad867ed, OVPN 🇸🇬 Singapore SGC 2 (http://sgo-2.optnl.com:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OVPN 🇸🇬 Singapore SGC 2 is back up in cb71add.


text:
🛑 TROJAN 🇬🇧 United Kingdom UKH 2 is down

In 4ce3d68, TROJAN 🇬🇧 United Kingdom UKH 2 (https://ukt-2.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKH 2 is back up in 183b576.


text:
🛑 TROJAN 🇸🇬 Singapore SGP 1 is down

In f9f46ec, TROJAN 🇸🇬 Singapore SGP 1 (https://sgt-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇸🇬 Singapore SGP 1 is back up in 334d959.


text:
🛑 V2RAY 🇺🇸 United States USP 4 is down

In ab0007b, V2RAY 🇺🇸 United States USP 4 (https://usv-4.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇺🇸 United States USP 4 is back up in 8b775ee.


text:
🛑 SSH 🇮🇩 Indonesia IDJ 1 is down

In ec26c1b, SSH 🇮🇩 Indonesia IDJ 1 (http://ids-1.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇮🇩 Indonesia IDJ 1 is back up in 68a6cf8.


text:
🛑 V2RAY 🇮🇩 Indonesia IDG 1 is down

In e846dcd, V2RAY 🇮🇩 Indonesia IDG 1 (https://idv-2.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇮🇩 Indonesia IDG 1 is back up in ebf1bcd.


text:
🛑 TROJAN 🇭🇰 Hong Kong HKE 1 is down

In 2dabbab, TROJAN 🇭🇰 Hong Kong HKE 1 (https://hkt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇭🇰 Hong Kong HKE 1 is back up in 41e2bb4.


text:
🛑 TROJAN 🇭🇰 Hong Kong HKE 1 is down

In 93a62e2, TROJAN 🇭🇰 Hong Kong HKE 1 (https://hkt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇭🇰 Hong Kong HKE 1 is back up in 1340503.


text:
🛑 SSH 🇮🇩 Indonesia IDA 1 is down

In a688856, SSH 🇮🇩 Indonesia IDA 1 (http://ids-2.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇮🇩 Indonesia IDA 1 is back up in c3e5e40.


text:
Feature Request: Key to trigger Notification badge on Extension A/B

Please add an option to display a notification badge on Extension A or B based on whatever condition is determined in the OnAppearAction script. This notification badge should display on the Extension A or B tile as well as on the menu bar icon.

Will be added in v2.5

You can now set ExtensionAlertA or ExtensionAlertB to true to trigger a warning in the extension and menu bar icon. An example is here: https://github.com/root3nl/SupportApp#how-to-populate-support-app-extensions


text:
docs: update README.md

minor fix

Thank you for your contribution.

authors: eltociear vizsatiz

repo: rootflo/flo-ai


text:
Add Code of Conduct

https://www.contributor-covenant.org/

Thank you for your effort to create an inclusive environment.  These issues are incredibly important to trans identified people.  Welcoming language is definitely a good idea and we always welcome constructive criticism.  One thing we noticed is your use of sexualized language in the code of conduct.  Placing special attention on gender-queer people can be otherizing and bring unwanted and unwelcome sexual attention.  It is also demeaning for trans people to be treated as less-than or incapable of equal treatment without discriminatory protections from patriarchal dominance.  The trivialization of suffering of non binary identified folks cannot be resolved by condescending policies and may result in polarization and brinksmanship between friendly peoples.  The contributor covenant may itself be considered a political attack on marginalized groups and inappropriate for a professional setting - in violation of its own stated mission.  As your policy is discriminatory, not in the best interest of the community, as well as the other issues listed, we request your rescission of said policy.

authors: retlehs transcomnow

repo: roots/sage


text:
MarkerTapBehavior.togglePopupAndHideRest doesnt work as expected

Hi.
MarkerTapBehavior.togglePopupAndHideRest doesnt work as expected.
When I tap to the Marker popUp is appear, but when I tap one more time to that marker, popUp doesnt dissapear.
popupState.selectedMarkers is always empty and contains(marker) is always return false
This was tested for the example code of the flutter_map_marker_cluster

I've just tried this in the example and it seems to work fine for me. Did you make any changes to the example? Make you can make a video or give me more details to be able to reproduce it?

No problem, I will close the issue here as I see there is one open on flutter_map_marker_cluster.

authors: Pepslee rorystephenson


text:
Add documentation about docker-py integration

Document how to use hypothesis-ros with the higher level rospbt package (for Python to serialization/node level conversion if required) and docker-py (Docker SDK for Python). (This fits probably better in rospbt.)

How to use with docker-py is done with minimal notebook example in docs/source/notebooks/core_pub_sub.ipynb and docs/source/notebooks/core_pub_sub_hypothesis_ros.ipynb.
How to use with rospbt obsolete because the converters will be merged into hypothesis-ros. Show how to use rospy and ros_param converters still reasonable.

repo: ros-testing/hypothesis-ros


text:
Update maintainers for the crystal-devel branch

Signed-off-by: Michael Jeronimo michael.jeronimo@openrobotics.org

@mjeronimo It would be good to remove my name as a maintainer.

authors: dirk-thomas mjeronimo

repo: ros-visualization/rqt


text:
pyros_utils: 0.1.2-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository pyros_utils to 0.1.2-0:

upstream repository: https://github.com/asmodehn/pyros-utils.git
release repository: https://github.com/asmodehn/pyros-utils-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.5.22
previous version for package: null

pyros_utils
* fixing travis file to check multiple distros.
* fixing python package version not matching catkin package version.
* Contributors: alexv

This needs to be rebased.

authors: asmodehn dirk-thomas

repo: ros/rosdistro


text:
catkin: 0.7.24-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository catkin to 0.7.24-1:

upstream repository: git@github.com:ros/catkin.git
release repository: https://github.com/ros-gbp/catkin-release.git
distro file: melodic/distribution.yaml
bloom version: 0.9.3
previous version for package: 0.7.23-1

catkin
* stamp env hook before copying (#1075 <https://github.com/ros/catkin/issues/1075>)
* set egg-base for setuptools packages (#1073 <https://github.com/ros/catkin/issues/1073>) (#1077 <https://github.com/ros/catkin/issues/1077>)
* [Windows] Accommodate different drives for --root (#1071 <https://github.com/ros/catkin/issues/1071>)
* [Windows] stop setuptools egg packaging (#1070 <https://github.com/ros/catkin/issues/1070>)

Waiting for other Melodic releases...


text:
librealsense2: 2.43.0-1 in 'foxy/distribution.yaml' [bloom]

Increasing version of package(s) in repository librealsense2 to 2.43.0-1:

upstream repository: https://github.com/IntelRealSense/librealsense.git
release repository: https://github.com/IntelRealSense/librealsense2-release.git
distro file: foxy/distribution.yaml
bloom version: 0.10.2
previous version for package: 2.42.0-1

CI is complaining that it can't find a package.xml. I'm not sure exactly why, but it looks like the release repository is missing tags for the latest Foxy release, perhaps something went wrong during the bloom process? I suggest trying to run bloom-release again.

I'm gonna close this until the issue can be resolved. Feel free to continue commenting.

authors: doronhi jacobperron wjwwood


text:
python3-deprecated added to rosdep dependencies

Please add the following dependency to the rosdep database.
Package name:
Deprecated
Package Upstream Source:
https://github.com/tantale/deprecated
Purpose of using this:
This dependency is Python @deprecated decorator to deprecate old python classes, functions, or methods
Links to Distribution Packages

Debian: https://packages.debian.org/bullseye/python3-deprecated
Ubuntu: https://packages.ubuntu.com/jammy/python3-deprecated

There are several changes that need to be made.
This entry does not follow our conventions for pip keys, which should be of the form python3-deprecated-pip rather than deprecated-pip regardless of which major python versions are supported by the package.
Furthermore, you've linked to the debian and ubuntu repository listings for this package which means that pip keys should not be used and instead keys for the system packages should be added instead. For example:
python3-deprecated:
  debian:
    '*': [python3-deprecated]
    buster: null
  ubuntu:
    '*': [python3-deprecated]
    bionic: null

Changes made as requested.