Less warn / info

Hello!
The adapter writes heaps of logs (both warnings and info) in my log.
Could be nice to turn off or reduce it...
Greetings
Michael
2019-03-23 20:24:40.086 - info: chromecast.0 Wohnzimmer - Playing playlist with 1 items
2019-03-23 20:24:40.364 - info: chromecast.0 Aurelia - Playing - http://<IP_ADDRESS>:8082/state/sayit.1.tts.mp3
2019-03-23 20:24:40.365 - info: chromecast.0 Aurelia - Playing playlist with 1 items
2019-03-23 20:24:40.930 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:24:40.931 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:24:41.148 - info: chromecast.0 Wohnzimmer - Finished playing announcement
2019-03-23 20:24:41.149 - info: chromecast.0 Wohnzimmer - setting volume to same value 40 - ignored
2019-03-23 20:24:42.085 - info: chromecast.0 Aurelia - Finished playing announcement
2019-03-23 20:24:42.085 - info: chromecast.0 Aurelia - setting volume to same value 80 - ignored
2019-03-23 20:24:50.866 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:24:50.867 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:24:50.868 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:24:50.869 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:25:01.001 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:25:01.001 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:25:10.934 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:25:10.935 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:25:20.969 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:25:20.970 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:25:30.899 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:25:30.900 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:25:40.938 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:25:40.938 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:25:50.874 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:25:50.874 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:26:01.008 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:26:01.008 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:26:10.941 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:26:10.941 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:26:20.976 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:26:20.977 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:26:30.906 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:26:30.907 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:26:40.942 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:26:40.942 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:27:01.016 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:27:01.016 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:27:20.986 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:27:20.987 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:27:27.228 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:27:27.228 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:27:40.952 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:27:40.952 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:28:01.020 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:28:01.021 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:28:20.990 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:28:20.991 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:29:01.027 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:29:01.028 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:29:41.067 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:29:41.068 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:29:41.180 - info: chromecast.0 Wohnzimmer - Detached player
2019-03-23 20:29:42.115 - info: chromecast.0 Aurelia - Detached player
2019-03-23 20:29:42.116 - info: chromecast.0 Aurelia - Detached player
2019-03-23 20:30:01.033 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:30:01.033 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:30:21.000 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:30:21.001 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:30:41.074 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:30:41.078 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:31:01.040 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:31:01.040 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:31:21.008 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:31:21.009 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:32:01.048 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:32:01.049 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:32:21.015 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:32:21.015 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:32:41.086 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:32:41.086 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:33:01.055 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:33:01.056 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:33:21.022 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:33:21.023 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:33:41.099 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:33:41.100 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:34:01.060 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:34:01.061 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:34:18.469 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:34:18.470 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:34:18.473 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:34:18.473 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:34:20.005 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:34:20.005 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:34:21.031 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:34:21.032 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:34:21.133 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:34:21.134 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:34:29.734 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:34:29.735 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:34:30.656 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:34:30.656 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:34:41.103 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:34:41.104 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:35:01.070 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:35:01.071 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:35:21.138 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:35:21.139 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:35:41.107 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:35:41.108 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:36:01.074 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:36:01.075 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:36:09.779 - error: zigbee.0 Zigbee publish to '0xd0cf5efffeef3ebd', genOnOff - off - {} - 1 failed with error Error: AF data request fails, status code: 233. MAC no ack.
2019-03-23 20:36:21.144 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:36:21.144 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:36:41.114 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:36:41.115 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:37:01.082 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:37:01.082 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:37:21.153 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:37:21.154 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:37:27.196 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:37:27.196 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:37:41.121 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:37:41.121 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:38:01.191 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:38:01.191 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:38:21.160 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:38:21.160 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:38:41.128 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:38:41.129 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:39:01.198 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:39:01.198 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:39:21.166 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:39:21.166 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:39:41.134 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:39:41.135 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:40:01.204 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:40:01.205 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:40:21.174 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:40:21.174 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:40:41.142 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:40:41.143 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:41:01.216 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:41:01.216 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:41:21.179 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:41:21.180 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:41:41.148 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:41:41.149 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:42:01.218 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:42:01.219 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:42:21.186 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:42:21.187 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:42:41.166 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:42:41.167 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:43:01.225 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:43:01.226 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:43:21.298 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:43:21.298 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:43:41.265 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:43:41.266 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:44:01.233 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:44:01.234 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:44:17.925 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:44:17.926 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:44:21.304 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:44:21.304 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:44:41.374 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:44:41.375 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:45:01.240 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:45:01.241 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:45:21.309 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:45:21.310 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:45:41.487 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:45:41.488 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:46:01.246 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:46:01.247 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:46:21.317 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:46:21.317 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:46:24.963 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:46:24.963 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:46:41.696 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:46:41.698 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:47:01.357 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:47:01.358 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:47:02.077 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:47:02.078 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:47:21.328 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:47:21.328 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:47:27.163 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:47:27.166 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:47:41.704 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:47:41.705 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:48:01.407 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:48:01.408 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:48:21.334 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:48:21.334 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:48:41.302 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:48:41.303 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:49:01.370 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:49:01.371 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:49:21.346 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:49:21.346 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:49:41.305 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:49:41.306 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:50:01.377 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:50:01.378 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:50:21.346 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:50:21.347 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:50:41.437 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:50:41.437 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:51:01.383 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:51:01.384 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:51:21.354 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:51:21.355 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:51:41.423 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:51:41.423 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:52:01.391 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:52:01.392 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:52:21.359 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:52:21.360 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:52:41.430 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:52:41.430 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:53:01.401 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:53:01.402 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:53:21.276 - info: telegram.0 getMe (reconnect): {"id":625983600,"is_bot":true,"first_name":"GreinerHome","username":"Greiner_bot"}
2019-03-23 20:53:21.367 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:53:21.367 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:53:41.437 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:53:41.438 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:54:01.403 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:54:01.403 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:54:21.373 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:54:21.374 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:54:41.441 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:54:41.442 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:55:01.412 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:55:01.412 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:55:21.481 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:55:21.482 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:55:41.450 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:55:41.450 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:56:01.417 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:56:01.417 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:56:21.489 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:56:21.489 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:56:41.456 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:56:41.457 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:57:01.425 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:57:01.425 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:57:21.496 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:57:21.497 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:57:27.229 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:57:27.230 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:57:41.463 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:57:41.464 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:58:01.433 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:58:01.433 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:58:21.503 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:58:21.504 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:59:01.438 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:59:01.438 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:59:21.509 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:59:21.510 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 20:59:41.479 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 20:59:41.480 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:00:01.444 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:00:01.445 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:00:21.518 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:00:21.518 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:00:41.484 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:00:41.485 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:01:01.455 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:01:01.455 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:01:21.523 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:01:21.524 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:01:41.502 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:01:41.502 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:02:01.459 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:02:01.460 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:02:21.531 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:02:21.531 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:02:41.499 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:02:41.500 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:03:01.569 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:03:01.569 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:03:21.538 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:03:21.539 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:03:41.505 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:03:41.506 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:04:21.544 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:04:21.545 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:04:41.512 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:04:41.513 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:05:01.583 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:05:01.584 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:05:21.553 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:05:21.554 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:05:41.622 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:05:41.623 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:06:00.053 - info: host.ioBroker-RasPi instance system.adapter.yr.0 started with pid 1606
2019-03-23 21:06:01.589 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:06:01.589 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:06:07.094 - info: host.ioBroker-RasPi instance system.adapter.yr.0 terminated with code 0 (OK)
2019-03-23 21:06:21.559 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:06:21.559 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:06:41.630 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:06:41.630 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:07:01.597 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:07:01.598 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:07:21.566 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:07:21.566 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:07:27.197 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:07:27.198 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:07:41.635 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:07:41.636 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:08:01.603 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:08:01.604 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:08:21.573 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:08:21.573 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:08:41.642 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:08:41.643 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:09:01.609 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:09:01.610 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:09:21.580 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:09:21.580 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:09:41.651 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:09:41.652 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:10:01.620 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:10:01.620 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:10:21.587 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:10:21.588 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:10:41.662 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:10:41.663 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:11:01.625 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:11:01.625 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:11:21.696 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:11:21.697 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:11:41.663 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:11:41.663 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:12:01.632 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:12:01.633 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:12:21.702 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:12:21.703 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:12:41.672 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:12:41.673 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:13:01.638 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:13:01.639 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:13:21.709 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:13:21.710 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:13:41.677 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:13:41.677 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:14:01.645 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:14:01.646 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:14:21.715 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:14:21.715 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:14:41.684 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:14:41.684 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:15:01.653 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:15:01.653 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:15:21.724 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:15:21.724 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:15:41.691 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:15:41.692 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:16:01.763 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:16:01.763 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:16:21.730 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:16:21.730 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:16:41.698 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:16:41.698 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:17:01.769 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:17:01.769 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:17:21.736 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:17:21.737 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:17:27.166 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:17:27.167 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:17:41.704 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:17:41.705 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:18:01.775 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:18:01.776 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:18:21.744 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:18:21.744 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:18:41.711 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:18:41.711 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:19:01.783 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:19:01.784 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:19:21.752 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:19:21.753 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009
2019-03-23 21:19:41.718 - info: chromecast.0 Received keep alive for disconnected device Chromecast
2019-03-23 21:19:41.718 - info: chromecast.0 Reconnecting Chromecast to <IP_ADDRESS>:8009

I am also getting the Reconnecting event very frequently (I expect this is the annoying one). I just restarted the adapter in debug mode so I am not longer getting but I am sure it will come again: I will debug it then.
I suspect the reconnect is being ignored (or the data not updated so it tries to reconnect again) but I cannot tell for sure without the debug messages.

The reconnect error is solved so the logs are quite again.


Request for large sample dataset to test onboarding

What is the name of your project?
Test-Onboarding
What is the purpose of your project?
I'm working with Ken Haase on getting some simulated data from pseudoPeople into the Census data warehouse to use for testing.  We thought it would be a good idea to just get a large, static dataset that we can review and use for now before testing the full pseudoPeople program.
How hard would it be for you to generate a test set of 100,000,000 simulated people distributed across the US and make it available for upload?  I'm still working with the team here that will actually upload it but getting it generated on your end would be a good first step.
Thanks,
Jon White, Ph.D., P.E.
AAAS STPF Fellow
Who is involved in the project? Which of these people will have direct access to the pseudopeople input data?
Jonathan White, Kenneth Haase
What funding is the project under? What expectations with respect to open access and access to data come with that funding?
n/a
We commit to:

[X] be responsive to further questions from interested parties
[X] deprecate and replace our version of the pseudopeople input data when a new version is released

What data would you like to request?

[X] Full US
[ ] Rhode Island
[ ] Other (may not be available immediately)

Other data - more explanation
Can this be a uniquely generated set of 100,000,000 million people that is different than the previously generated Full US set?

This looks good to me! If I'm understanding correctly the data itself is not so much of interest as the format and volume?

Yes, storage is the primary concern for this.  We talked about not having employees making voluminous amounts of data; having a static test set with all the data elements present would be more efficient for testing.  If employees want to do something different, they can then go through the generation process themselves.
I'm not sure of the best way to get this data to the Census - I'll work on this once I get a sense of the size of the data.  In the past when I've done something like this, it was actually most efficient to compress and password protect the file and then burn it onto multiple DVDs.  These were then mailed or given to in person.
Thanks,
Jon
Jon White, Ph.D., P.E.
AAAS STPF Fellow
Center for Optimization & Data Science
Research and Methodology Directorate
U.S. Census Bureau

From: Os Keyes @.>
Sent: Tuesday, October 10, 2023 4:25 PM
To: ihmeuw/pseudopeople @.>
Cc: Jonathan White (CENSUS/CODS FED) @.>; Author @.>
Subject: Re: [ihmeuw/pseudopeople] Request for large sample dataset to test onboarding (Issue #321)
This looks good to me! If I'm understanding correctly the data itself is not so much of interest as the format and volume?
—
Reply to this email directly, view it on GitHubhttps://github.com/ihmeuw/pseudopeople/issues/321#issuecomment-1756286427, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDDCPYTH2VB5PPAA2Z7TRALX6W4L7AVCNFSM6AAAAAA5WIE4PSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJWGI4DMNBSG4.
You are receiving this because you authored the thread.Message ID: @.***>

Makes sense! Good by me then - CC @aflaxman

Great.  I think the best way forward now is for me to generate a compressed csv containing a random sample of 100M rows from the dataset generated by one of the psp.generate_* functions.  Which one would you like?  psp.generate_decenial_census?  See https://pseudopeople.readthedocs.io/en/latest/datasets/index.html#datasets for the alternatives.

US Decennial Census
Jon White, Ph.D., P.E.
AAAS STPF Fellow
Center for Optimization & Data Science
Research and Methodology Directorate
U.S. Census Bureau

From: Abraham Flaxman @.>
Sent: Wednesday, October 11, 2023 11:00 AM
To: ihmeuw/pseudopeople @.>
Cc: Jonathan White (CENSUS/CODS FED) @.>; Author @.>
Subject: Re: [ihmeuw/pseudopeople] Request for large sample dataset to test onboarding (Issue #321)
Great. I think the best way forward now is for me to generate a compressed csv containing a random sample of 100M rows from the dataset generated by one of the psp.generate_* functions. Which one would you like? psp.generate_decenial_census? See https://pseudopeople.readthedocs.io/en/latest/datasets/index.html#datasets for the alternatives.
—
Reply to this email directly, view it on GitHubhttps://github.com/ihmeuw/pseudopeople/issues/321#issuecomment-1758018084, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDDCPYQBNHPQQ42VRBVYHE3X627CNANCNFSM6AAAAAA5WIE4PQ.
You are receiving this because you authored the thread.Message ID: @.***>

I have shared this data with Jon through Census Bureau's secure platform.

Thanks, I saw them coming in and I've received them.  Thanks again for doing this.
Jon White, Ph.D., P.E.
AAAS STPF Fellow
Center for Optimization & Data Science
Research and Methodology Directorate
U.S. Census Bureau

From: Abraham Flaxman @.>
Sent: Sunday, October 15, 2023 11:03 AM
To: ihmeuw/pseudopeople @.>
Cc: Jonathan White (CENSUS/CODS FED) @.>; Author @.>
Subject: Re: [ihmeuw/pseudopeople] Request for large sample dataset to test onboarding (Issue #321)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
I have shared this data with Jon through Census Bureau's secure platform.
—
Reply to this email directly, view it on GitHubhttps://github.com/ihmeuw/pseudopeople/issues/321#issuecomment-1763434001, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDDCPYSZNGR4YZV7DH3XCW3X7QCLZANCNFSM6AAAAAA5WIE4PQ.
You are receiving this because you authored the thread.Message ID: @.***>


Not an issue more a question for add_task arg

Thanks for the lib, it does the job but I'm not clear on how I can pass arg/kwarg(f"{await self.trend.fetch_key_feed()}")  to my scheduled fn (self.send_notification).
I created a secondary function for now send_news which work:
I have the following
async def send_news(self):
    """News"""
    await self.send_notification(f"{await self.trend.fetch_key_feed()}")

async def plugin_schedule_task(self):
    """Handles task scheduling"""

    self.scheduler.add_task(
        fn=self.send_news,
        trigger=IntervalTrigger(minutes=2),
        max_instances=1,
        replace_existing=True,
        coalesce=True,
        is_enabled=True
    )

thanks for your guidance @tarsil

Ok so I think I might I found the way:
async def plugin_schedule_task(self):
    feed_data = await self.trend.fetch_key_feed()
    self.scheduler.add_task(
        fn=self.send_notification,
        args=[feed_data],
        trigger=IntervalTrigger(minutes=5),
        max_instances=1,
        replace_existing=True,
        coalesce=True,
        is_enabled=True
        )

Hey @mraniki thank you for your question. Seeing both comments, the second option seems indeed the correct way or approaching and the reason for it it's because the fn receives a sync function.
This is actually something to be considered as a possible feature. Adding the async task as a possibility for the fn parameters.
What do you think? Are you willing to create a PR or propose that change?

Oh wait, @mraniki i was mistaken with something else. Ignore my comment. The second option you did looks correct to me

It will be good to add it in the doc as an example 👍

Oh wait, @mraniki i was mistaken with something else. Ignore my comment. The second option you did looks correct to me

Thanks for the confirmation 👌

It will be good to add it in the doc as an example 👍

Are you willing to open a PR and add that? :) You can be a contributor

Sure I will prep that and send it

@mraniki merged. Thank you very much. It should be live in the next 5 minutes. I hope Asyncz is doing well for you


Infinite $digest Loop on $stateChangeStart redirect if state has templateUrl

This is a weird error that I've been having on my production app, but found it very hard to accurately reproduce. For now the fix in https://github.com/angular-ui/ui-router/issues/600#issuecomment-47228922 works for me.
You can see the error happening on this plunkr: http://plnkr.co/edit/L8DhCNG7cyipBsBypWg3
The app has secure and unsecure states, defined by some extra data on the state definition. On $stateChangeStart I check if the state is marked as secure, and if so, if the current user is authenticated.
If an unauthenticated user is trying to access a secure resource, he gets redirected to the unsecured state.
Upon loading the app, the user is directed to a secured state by default (via $urlRouterProvider.otherwise) because he might already be logged previously.
The problem happens here. A user enters the app, the $stateChangeStart gets fired, I detect he is not authenticated, call event.preventDefault() and $state.go('unsecure-state'). This sends angular into a infinite digest loop bouncing back between the secure and unsecured states.
What makes this odd is that it seems to be dependent on the target state having a templateUrl instead of an inline template. On the plunker, change the template of the secure state from templateUrl: "./unsecure.html" to template: "unsecure" and infinite digest dissapears.

You have to have a state with url: '/' defined. Its weird but documented at #2238
See http://plnkr.co/edit/r6xPdrC7AncxyGGJ4z3K?p=preview

Fix coming http://plnkr.co/edit/kXKWHJChSCVf9iBXFE0H?p=preview


False positive on F811 "Redefinition of unused" when using contextlib.suppress

I assume this is a generalised problem with context managers being able to influence control flow but I figure contextlib.suppress could be special-cased maybe?
import contextlib

foo = None
with contextlib.suppress(ImportError):
    from some_module import foo

bar = None
try:
    from some_module import bar
except ImportError:
    pass

print(foo, bar)

the two bits setting "foo" and "bar" are functionally equivalent, but in the first one Ruff reports
test.py:5:29: F811 Redefinition of unused `foo` from line 3
  |
3 | foo = None
4 | with contextlib.suppress(ImportError):
5 |     from some_module import foo
  |                             ^^^ F811
  |
  = help: Remove definition: `foo`

while the second one works fine.

This is interesting, agree that it's a bug.


[RFC] Add imperativeHandle construct

In React: https://reactjs.org/docs/hooks-reference.html#useimperativehandle
Usage in Muban: As a last resort when using props doesn't work.
Example: setting the focus of an input element wrapped in a component.
Questions to answer:

Child –  In React the imperativeHandle is attached to the passed ref using forwardRef. In Muban we have nor need either of those currently. So how do we "expose" the handle to the outside?
Parent – In React, the imperativeHandle will be attached to the passed ref, and can be used after the first render (after the useEffect). In Muban, we we either have to pass something (like a built-in ref prop), or we can "retrieve" the handle from the refComponent (just like we extract props).

Suggestions
1. using bindings
Adding a custom forwardRef param that can be passed to a bind.
// parent
const handleRef = ref<TypeOfHandle>();

watch(handleRef, () => {
  handleRef.value.focusInput();
});

// this needs to be a custom propType so we can pass a `ref` (instead of a `computed` that gets `unwrapped`
bind(refs.child, { forwardRef: handleRef });

// child
// depending on timings, the forwardRef might not be passed from the parent yet
// so internally we would have to wrap it inside a computed, and double-wrap it to not auto-resolve
setup({ forwardRef }) {
  // this will attached it to the `forwardRef` `ref`
  useImperativeHandle(forwardRef, {
    focusInput() {
      // implementation details
    }
  });
}

2. using the refComponent
This setup is a bit more integrated, and doesn't require a user-defined ref to pass along.
The (only?) downside is that it doesn't let you watch for when the "imperativeHandle" is available. Although in almost all cases I don't see this as an issue, as you won't use them immediately in the setup function anyway, but rather on different async events.
// parent
setup({ refs }) {
  // Depending on the timing, this might not exist yet.
  // Otherwise the `useMounted` might need to be used, or any other "async handler".
  // For lazy components this might be more unclear when it can be used?
  refs.child.component?.imperativeHandle?.focusInput();

  // or even just:
  refs.child.component?.focusInput();
}

// child
setup() {
  // this gets registered internally
  useImperativeHandle({
    focusInput() {
      // implementation details
    }
  })
}

2.5. providing the useImperativeHandle from the setup params, so it can be typed
This setup has the same "usage", but a more integrated "register", to better make used of types (see further below).
// child
setup({ registerImperativeHandle }) {
  // this gets registered internally, and it type matches that of the component
  registerImperativeHandle({
    focusInput() {
      // implementation details
    }
  })
}

Challenges
Timing
Since the "imperativeHandle" contains runtime code that could interact with objects inside the setup function, it must be "registered" there as well.
For 1⃣ it would make life easier of the parent was executed before the child, but that's not the case. So both the user and the framework implementation is more cumbersome.
For 2⃣ it would make life easier if the setup function of a child component is called before the setup of a parent component, which should be the case. So to me, that sounds like the best option for multiple reasons – user and framework simplicity.
Typing
Most of the component's types can be inferred/extracted from the object definition (the refs and props). But the "imperativeHandle" would be defined in the setup at "runtime", and cannot be used automatically.
For this we would most likely need to provide additional types to the defineComponent and the useImperativeHandle.
type FooHandle = {
  focusInput: () => void;
};

// specify here to add to the component type
const Foo = defineComponent<FooHandle>({
  setup({ registerImperativeHandle }) {
    // this is already typed, so the passed object must match the `FooHandle` specified for the `defineComponent`
    registerImperativeHandle({ ... });
  }
});

Naming
Having imperative in there is probably good, since it "escapes" into the imperative programming model. Not sure if handle is a good fit here, since that might be more specific to how React attaches that to a passed ref.
But I can't think of anything better a.t.m., so registerImperativeHandle is currently the best option.
Implementation details

In React, the object you pass to useImperativeHandle is a function. Most likely this is because the render function is executed multiple times, and you don't want to re-create these objects every time. – In Muban, the setup gets only executed once, and individually for each component, so passing the object directly is totally fine.

We must think of scenarios where the ref itself is lazy / optional, and the component might not exist yet. But since the imperative handle is attached to the component, as soon as the component exists, the handle should also exist. However, for lazy/optional components, the timing of where we assign the component to the internal ref (which could trigger a watch) should ideally be after the setup of the new child component is called.

We need to make sure that types are properly resolved. defineComponent already has some generics, so they need to "shift" to make room for this one one, and also probably should get default values, since you cannot just pass 1 of the non-optional ones – you would have to pass all of them.

@psimk @jspolancor @larsvanbraam @ThijsTyZ any thoughts, preferences, opinions?

Would it be an option to have the imperative handle defined outside the setup function in its own node in the defineComponent? This would make it more explicit and also makes sure you can only define this once (because in the setup you could call the registerImperativeHandle twice).
export const MyComponent = defineComponent({
  name: 'my-component',
  props: {
    // ...
  },
  refs: {
    inputField: refElement('input-field'),
    // ...
  },
  imperativeHandle({ props, refs }) {
    return {
      focus() {
        refs.inputField.element?.focus();
      },
    }
  },
  setup({ props, refs }) {
    // ...

    return [
      // ...
    ];
  },
});

Technically yes, but it would limit the usage of it. You might want to interact with other variables from your setup function, which you can't access.
So no, that's not something we want to do..

Yes, you are right. You need access to all variables in the setup function


[Feature]:  Component

What problem does this feature solve?
Requesting for a Straight angle pie component which can be an extension of the current DonutChart component.
Which can be achieved by opening up the startAngle and endAngle for customization.

What does the proposed API look like?
The following would be the 2 options I believe we can take this forward:

Open up the props startAngle & endAngle of the current <DonutChart /> Component
Create a new component for the same

Here's an example from the recharts docs :

If approved, I'm ready to build and contribute to the same. Thank you!

Duplicate of #474

Duplicate of #474

Is this being worked on? Or is open for contribution?

There is already a PR for it, but this feature is not a priority right now, hence not merged but still open.

Cf. #474


Google Summer of Code

This work was part of my Google Summer of Code project. The following are the major contributions of the project.

Addition of multiple negatives ranking loss
Addition of an example notebook for fine-tuning CLIP using multiple negatives ranking loss

Thanks for the PR! I'll review the notebook soon and I left a few comments on the loss.

@abhisharsinha, let me know your thoughts on the PR comments and we can get this merged into the dev branch.

Meant to revert the changes to pyproject.toml but deleted the file. Can you please add it back with the following
[tool.isort]
profile = "black"

[tool.black]
 line-length = 119

Looks like the Black and Isort formatting checks are failing for tensorflow_similarity/losses/multinegrank_loss.py. Otherwise looks good to go, thanks.


This item isn't working?

CommonPick:
item:
type: CHEST
name: "&7&lRandom Stone Tool"
lore: ["&6Right Click&b to claim tool!"]
glow: true
consumed: true
cooldown: 1
actions:
- { action: COMMAND, by: CONSOLE, command: "give {player} stone_pickaxe{Enchantments:[{id:efficiency,lvl:3},{id:unbreaking,lvl:1}]} 1" }
- { action: MESSAGE, to: PLAYER, message: "&6You got:&a&l Common&7 Stone&a Pickaxe!" }

Could you please provide me with an error message or some indication as to what has gone wrong?
In the meantime, try if this works:
CommonPick:
  item:
  type: CHEST
  name: "&7&lRandom Stone Tool"
  lore: ["&6Right Click&b to claim tool!"]
  glow: true
  consumed: true
  cooldown: 1
  actions:
   - { action: COMMAND, by: CONSOLE, command: 'give {player} stone_pickaxe\{Enchantments:[\{id:efficiency,lvl:3},\{id:unbreaking,lvl:1}]} 1' }
   - { action: MESSAGE, to: PLAYER, message: '&6You got:&a&l Common&7 Stone&a Pickaxe!' }

Error without the change you pasted: https://hastebin.com/alexaziqoy.apache
Error with the change you pasted:

Ahh yes, the indentation is wrong - how about this:
CommonPick:
  item:
    type: CHEST
    name: "&7&lRandom Stone Tool"
    lore: ["&6Right Click&b to claim tool!"]
    glow: true
  consumed: true
  cooldown: 1
  actions:
   - { action: COMMAND, by: CONSOLE, command: 'give {player} stone_pickaxe\{Enchantments:[\{id:efficiency,lvl:3},\{id:unbreaking,lvl:1}]} 1' }
   - { action: MESSAGE, to: PLAYER, message: '&6You got:&a&l Common&7 Stone&a Pickaxe!' }


Add Persian characters in Str::charsArray()

Add Persian characters and missing Arabic characters to Str::charsArray()

Please send this to the stringy library. I will periodicity sync us up with them.

I also create a pull request for stringy.
I don't understand why you reject this, when you don not use that library directly

Yeah, should just wait for Stringy to merge this and then do the same here. It's still is @behzadsh contribution.

Not going to happen since we're already out of sync with stringy.

@behzadsh +1

The next time stringy does a release, I'll sync up with it.

@GrahamCampbell  come on men why you are trying to be hero gozo khan

@GrahamCampbell I agree with @ra3oul, you are not a laravel hero for us, don't try!

@GrahamCampbell Your work and speaking is not acceptable for merging policy in open source world!

I'm a bit confused what you're talking about? This PR will only make it into the core when it goes into stringy, in the same way that code only goes into our 5.2 by automatic merge from 5.1.

I'll retain the commit authors when possible, in the same way I cherry-pick changes when merging PRs targeted to the wrong branch. No further discussion is required here.
Consider this code to be read only, like all our illuminate components.

it should be clear who has committed.
it's not true just get the code and commit yourself.
it's about being selfish.

@mhndev At no point did I say I would be doing that!

@ahmadina Laravel is cheap framework and person is not hero, the framework should be hero.

Locking this because the conversation has strayed away from the PR. When stringy releases, laravel will sync up. Commit authors WILL be retained.

@behzadsh Thank you for your contribution, it's much appreciated. It's a shame your PR got hijacked.

This PR is also impossible to merge into laravel as is due to merge conflicts with https://github.com/danielstjules/Stringy/commit/b85a84d0b91e6940edaa183b2f73714998450a51.


Make dialog boxes and drop-down menus more visible (mainnet)

Change background color to #00446c
https://zpl.io/aRWMexN
https://zpl.io/bJWnNGE

Done, but currently we can implement rounded corners

Cheked


iox-1391 move buffer and container classes

Pre-Review Checklist for the PR Author

[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[ ] All checks have passed (except task-list-completed)
[x] All touched (C/C++) source code files from iceoryx_hoofs are added to ./clang-tidy-diff-scans.txt
[x] Assign PR to reviewer

Notes for Reviewer

See PR title.
Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior
[ ] Public API changes are documented via doxygen
[ ] Copyright owner are updated in the changed files
[ ] All touched (C/C++) source code files from iceoryx_hoofs have been added to ./clang-tidy-diff-scans.txt
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Closes #1391 (partially)

@elBoberido @mossmaurice I had to rebase.

@FerdinandSpitzschnueffler

All touched (C/C++) source code files from iceoryx_hoofs have been added to ./clang-tidy-diff-scans.txt

I think the new paths need to be added, right?

@mossmaurice

I think the buffer path needs to be added, right?
I will buy all contributer a beer once we just have iceoryx_hoofs/*/** on that list


remove pilot v1 support

Pull Request Test Coverage Report for Build 1375

0 of 0   changed or added relevant lines in 0 files are covered.
17 unchanged lines in 7 files lost coverage.
Overall coverage increased (+0.2%) to 63.878%

Files with Coverage Reduction
New Missed Lines
%

core/registry/healthz.go
1
47.01%

core/router/router_config.go
1
3.85%

core/loadbalancer/randam.go
2
64.29%

core/rest_invoker.go
2
91.84%

core/config/sr_config.go
2
0.0%

core/registry/index.go
4
78.75%

core/router/cse/translate.go
5
33.8%

Totals

Change from base Build 1373:
0.2%

Covered Lines:
5185

Relevant Lines:
8117

💛  - Coveralls


Set the DNS Service name to kube-dns for net-exporter

Towards https://github.com/giantswarm/roadmap/issues/725

@kopiczko why do we use the test catalog here? is it for only testing this PR?

@kopiczko why do we use the test catalog here? is it for only testing this PR?

I use it for testing.

Requires rebase after https://github.com/giantswarm/default-apps-openstack/pull/16

Replaced with https://github.com/giantswarm/default-apps-openstack/pull/26


Fix for critical issue #19916 (influxdb server crashed when reading a…

… corrupt file)
Added check on indexOfsStart, to make index slice length fit in int32, and count should have >0 value otherwise it is corruption.

[ ] CHANGELOG.md updated

[*] Rebased/mergable

[*] Tests pass

[*] Sign CLA (if not already signed)

Closes #

Required checklist

[ ] Sample config files updated (both /etc folder and NewDemoConfig methods) (influxdb and plutonium)
[ ] openapi swagger.yml updated (if modified API) - link openapi PR
[x] Signed CLA (if not already signed)

Description
1-3 sentences describing the PR (or link to well written issue)
Context
Why was this added? What value does it add? What are risks/best practices?
Affected areas (delete section if not relevant):
List of user-visible changes. As a user, what would I need to see in docs?
Examples:
CLI commands, subcommands, and flags
API changes
Configuration (sample config blocks)
Severity (delete section if not relevant)
i.e., ("recommend to upgrade immediately", "upgrade at your leisure", etc.)
Note for reviewers:
Check the semantic commit type:

Feat: a feature with user-visible changes
Fix: a bug fix that we might tell a user “upgrade to get this fix for your issue”
Chore: version bumps, internal doc (e.g. README) changes, code comment updates, code formatting fixes… must not be user facing (except dependency version changes)
Build: build script changes, CI config changes, build tool updates
Refactor: non-user-visible refactoring
Check the PR title: we should be able to put this as a one-liner in the release notes

Added two checks for indexOfsStart,and count against corruption, to avoid influxdb exit with panic. on start.
More details are here in issue #19916.
The following PR is opened for 1.8 branch only, but it would be good to consider to include fix other branches as well.

@gggevorgyan I would like to merge this PR and for you to get credit for it, but we have some checks on commit messages that are failing.  Starting the commit message with fix: should work. Would it be possible for you to rewrite the commit messages and then force push those to your pull request branch? Thanks!

Thank you @gwossum,
I have added fix: prefixes to boith commits


Styling from widget removes variable size when having a point layer styled by size and color

Steps to Reproduce

Create a map with a points layer
Style that layer by color and size using columns
Add two widgets, one based on a numeric column and another one based on a string column
style using one of the widgets

Current Result
Variable size is not applied anymore.
Expected result
Variable size should be kept.

It just worked as expected, not being able ton consistently replicate

Spotted, and fixed in https://github.com/CartoDB/deep-insights.js/pull/502

In ded08, with the rest of autostyle changes.


Visualization improvement

Dear Community,
I believe that the visualization may be improved with some settings to specify the minimum distance between the flows, for example.
When the number of elements increase, the quality of the visualization drops significantly as the number of flows increase.
It would be nice to find some way to improve, eventually personalizing the minimum distance of the flows.

I implemented the compact keyword, illustrated in the second example in the README. Let me know if this does not solve the issue for you.

Thank you for the improvement, I haven't had the time to check yet, but I'll do in the next days and I am sure this has solved my issue.
Thank you


getapplicationlog error

dotnet neo-cli.dll --rpc --log

curl -X POST \
  http://<IP_ADDRESS>:10332 \
  -H 'Content-Type: application/json' \
  -d '{
  "jsonrpc": "2.0",
  "method": "getapplicationlog",
  "params": ["0xd1c7ea5f406e0f3ade3e8a9cd575a7b08a73f440ede947d16c325c09eaedb33e"],
  "id": 1
}

result
{
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
        "code": -100,
        "message": "Unknown transaction"
    }
}

this is  a right  InvocationTransaction， but get a error.
right result
“contract" : "0xac116d4b8d4ca55e6b6d4ecce2192039b51cccc5"
"txid" : "0xd1c7ea5f406e0f3ade3e8a9cd575a7b08a73f440ede947d16c325c09eaedb33e"

and contain 3 transactions
cli version : 2.7.3

If you start NEO-CLI without the startup parameter --log, it will not record the logs of the InvocationTransaction in the new blocks.

I had  add --log   parameter

curl -X POST \
  http://<IP_ADDRESS>:10332 \
  -H 'Cache-Control: no-cache' \
  -H 'Content-Type: application/json' \
  -H 'Postman-Token: b08e40e2-bd74-445b-a97b-de01b2ded044' \
  -d '{
  "jsonrpc": "2.0",
  "method": "getapplicationlog",
  "params": ["f9771aff6d011f57e245f89e6a85ed80c5fbd5036ecd3bf1ece6ccc3cadb8701"],
  "id": 1
}
'

return json
{
    "jsonrpc": "2.0",
    "id": 1,
    "error": {
        "code": -100,
        "message": "Unknown transaction"
    }
}

‘’‘
https://neotracker.io/tx/f9771aff6d011f57e245f89e6a85ed80c5fbd5036ecd3bf1ece6ccc3cadb8701
’‘’

@503945930 this is a InvocationTransaction that transfer global asset gas. It didn't change any status in neo  blockchain storage. So it will not be recorded in application log. If this tx change nep5 asset status or any status in vm then it will be recorded in application log.

@erikzhang my node returned "Unknown transaction" too, it's not caused by --log. I check the transaction again, I doubt about my answer a little bit.

It will record every InvocationTransaction, even if the contract fails.

My node saved the transaction log and rpc call working as intended.
@503945930 I think --log has to be active at the time when the block of the given transaction (block 1870453) is beeing processed by neo-cli. You cannot get the application log of InvocationTransactions in blocks that were saved by neo-cli without having --log active.
So is there a way to get application logs for already saved blocks, except for a full resync? For example after rebuilding the database with chain.acc?

Rebuilding the database with chain.acc and full resync are equivalent.

@kokahunter  you node  rpc ?

@erikzhang Yes I agree. But still the resync with chain.acc and --log active won't save any application log  since the ApplicationExecuted event is registered after ImportBlocks.
https://github.com/neo-project/neo-cli/blob/master/neo-cli/Shell/MainService.cs#L825-L851
So maybe check for --log and do event registration before looking for chain.acc file?
@503945930 No public node currently. But you may just put LevelDBBlockchain.ApplicationExecuted += LevelDBBlockchain_ApplicationExecuted; before this line (https://github.com/neo-project/neo-cli/blob/master/neo-cli/Shell/MainService.cs#L811) and resync with chain.acc file. Neo-Cli will then save every application log. I just did this and it worked fine.

So maybe check for --log and do event registration before looking for chain.acc file?

Good suggestion. Have done in e3c95e2a5f42f33c5b31d8dc306f721a878cb364


Odd behavior of ERA001 on code-like comments

I understand how this could look like code, although it's a bit noisy to have this flagged. Even if django were a variable, this would do nothing as a standalone expression.
That being said, why does it get flagged when the = is included, but not without it? I tested all 4 permutations of </> and = or not.

It's just a quirk of the implementation, which comes from Eradicate. We detect snippets that contain =, but not > or <.

We can probably special-case these version marker comments (though low priority).

I have encountered this false positive with ERA001:
> head -n 5 search.py
#! /usr/bin/env python3
# External program requirements:
# - gum(1) (https://github.com/charmbracelet/gum)
# - less(1) (common)
# - rg(1) with PCRE2 support (`sudo apt install ripgrep`)
> ruff search.py
search.py:4:1: ERA001 Found commented-out code
Found 1 error.

More false-positives on what doesn't even look like valid code:
indico/modules/events/abstracts/blueprint.py:98:1: ERA001 Found commented-out code
    |
 96 |                  methods=('GET', 'POST'))
 97 |
 98 | # Emailing (management)
    | ^^^^^^^^^^^^^^^^^^^^^^^ ERA001
 99 | _bp.add_url_rule('/manage/abstracts/api/email-roles/metadata', 'api_email_abstract_roles_metadata',
100 |                  abstract_list.RHAbstractsAPIEmailAbstractRolesMetadata, methods=('POST',))

indico/modules/attachments/models/folders.py:110:5: ERA001 Found commented-out code
    |
108 |     # relationship backrefs:
109 |     # - all_attachments (Attachment.folder)
110 |     # - legacy_mapping (LegacyAttachmentFolderMapping.folder)
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ERA001
111 |
112 |     @property
    |
    = help: Remove commented-out code

And an interesting case that's not an FP, but maybe commented-out code that has a TODO, FIXME, etc. comment in the same line should be allowed?
indico/modules/events/registration/util.py:61:5: ERA001 Found commented-out code
   |
59 |     text: str
60 |     icon_name: str
61 |     # _: dataclasses.KW_ONLY  # TODO uncomment once we require python3.10+; until then consider everything below kw-only
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ERA001
62 |     weight: int = 0
63 |     dialog_title: str = None  # defaults to `text`
   |
   = help: Remove commented-out code

Clearly removing something like this would not be in the spirit of the rule which asks you to use source control in case you need to bring removed code back, instead of keeping a commented-out version. But when you know that you'll have to bring it back (hence the TODO comment), then it makes no sens to rely on your VCS for this.

Those does look like code where line 98 could be a function / class call and so on. Although, I do think we should probably allow if it has a TODO comment on the commented line.

I think the logic to determine what's code and what isn't should be pretty strict - you really don't want to have to put noqa on your comments just so they are considered comments. Even more so when it's a single-line comment. With multi-line it's probably less likely to get a block of valid Python code that's not actually code.
For things that look like valid function/class call statements, one possibility could be checking if the function name exists in the scope. If not, don't consider it a statement.
IMHO this kind of rule is the one where you should rather get false negative than false positives: There's no harm/annoyance in missing some commented-out code. But it's very annoying if your valid comments trigger this rule

I have another false positive:
# The first entry uses "65 CC 81", second one uses "C3 A0"

It seems like it's detecting the hexadecimals as code. A reason as to why it was flagged as such would also be really useful


Update st2 revision

We are at 179.
https://downloads.stackstorm.net/releases/st2/0.14dev/SHAMAP.txt

Updated to 179.


Typo in lvl2

No need to create the "Simulator2" class, "Simulate2" is the only one needed and can pass codecrunch~ can take note
Screenshots (if any):

nice thank you

thank you!

Thanks for the heads up!

Thank you!

thanks!

thank you!!!

Thanks!

thank youuu

thanks for informing sir!


Open the calendar app when a day cell is clicked

I haven't add a selector on the cells because of the custom background. I see that everywhere else the system selector is used so it will feel weird overriding the colour just for the cells. Something more subtle like drawing a circle around the day would probably be a better selector than changing the background.

Why does this PR include 2 things? I think you should separate the circle feature in another PR.

Like this is ever gonna be merged...

Good point :)


Envoy-S, home error: Error: self-signed certificate,

[homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, home error: Error: self-signed certificate, reconnect in 15s.
i have no idea how to solve this.

Same here #60


Ability to show only one build per branch/project.

Current implementation shows multiple builds for branches and subprojects.
A simple ko.observablearray could be implemented to allow showing only the latest build per each branch and subproject.

I might create a pull request from this if I have time.

This feature is the default in the 'most maintained' fork:
https://github.com/zlamma/tc-radiate
It also contains many other improvements.


sysupgrade: dirty fix, do not check new version if -n option is used

TODO: Find a better solution

Thank you !


mocking failure doesnt work for google?

I am trying with google and invalid credentials doesnt work. It successfully authenticates from google account. It works on facebook but not google. For google should i do something different? I appreciate any help! Thanks!

 it "can handle authentication error" do
    OmniAuth.config.mock_auth[:google] = :invalid_credentials
    visit '/'
    page.should have_content("Sign in with Twitter")
    click_link "Sign in"
    page.should have_content('Authentication failed.') #this fails
  end

Have the same issue, auth_hash is set to the :invalid_credentials and still goes to the callback_path. It doesn't trigger the configured on_failure proc.
Facebook provider works fine btw.

please find solution here. https://stackoverflow.com/questions/52169390/how-to-mock-failure-for-google-oauth

Nope, it was different for me as I was trying to make the callback path be dynamic. Works fine on on development but was acting weird on specs. It was the mock calls that were failing due to on_path? in omniauth not returning correctly.


Reference to HTTP Swagger operation's output includes extra body level

Describe the Bug with repro steps

Add an action to a Logic App flow and select the "HTTP + Swagger" action
Enter the URL for a Swagger specification that contains at least one operation that returns a non-empty response body
Select the Swagger operation that will return a non-empty body
Fill in values for any required inputs to the Swagger operation and complete the creation of the "HTTP + Swagger" action
Add another action to the Logic App flow using any action that can consume the output of the "HTTP + Swagger" action (e.g. "Initialize variable"
For the value entry, click on the lightning bolt icon to reference data from the previous step
Select a property from within the output of the previous "HTTP + Swagger" option and finish creation of the second action
Try running the Logic App and confirm that the field from the output of the Swagger option does not work as expected

If you examine the code view for the second action. It will look something like:
"value": "@body('httpswaggeraction')?['body']?['id']"

It appears that the use of the @body function at the beginning of this expression removes the need for the [body]? segment near the end of the expression. By manually removing that extra body component in the code view, the Logic App flow will work as expected.
What type of Logic App Is this happening in?
Consumption (Portal)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
MS Edge
Additional context
No response

Actually just found that this is a duplicate of #4675


Great work

Sorry for using this issues section to comment on the fantastic job you have done putting this together. Good stuff!
I would love to be able to control shaders through an ADC on the raspberry pi. Is there some way to launch a shader file from the cli using python and have python read an ADC (like the mcp3008) and pass this on to a shader so that for example you can use an external knob to control a colour in the shader code? This project has great potential to be turned into a cool module that can act as a backdrop for (electronic) musicians. See my website also: www.erikoostveen.co.uk

Thanks a lot for the feedback!
I agree it'd be awesome to enable interactivity and provide inputs to the shaders. Originally, I thought about feeding shaders with the mouse uniform, keyboard, and audio / video textures, but the idea to feed them using the Raspberry Pi GPIO is even cooler.
It seems interfacing the ADC would be easier using a C library. It seems WiringPi supports the MCP3008: https://www.raspberrypi.org/forums/viewtopic.php?t=54366. Otherwise, it might be possible to use any GPIO C library to interface the DAC with the SPI bus, and feed a float uniform to the shaders.

I'd love to figure out how that could work. I am not a software engineer and most of my projects are with the Arduino/ESP32 so working now with Raspberry is a bit of a learning curve :-)
With the help of your cool code, we can create an amazing open source video synthesizer (Eurorack) module for artists to use as a visual for when they do their online or on-stage performances you see.
... so, let's say that I want to be able to change, on the fly, any of the variables in the attached .glsl  ... let's say the number "200.0" in the line: "float modAmount = mod(float((px))/200.0, 3.0);" how would I go about reading that from a python script?
I have a working MCP3008 setup for which I can read 8 analog channels and capture those in variables ... my struggle is now to figure out how can I pass that on to the .glsl ?
test14.zip

Just wanted to say thanks as well! This project enabled me to finish a Christmas present for a friend.
Also was able to get this to run on a Raspberry Pi 1 B+. Quite a few of the examples are broken, but I think it's less with this library and more with the driver. I ended up having to downgrade a lot of the stuff in my own shader to run it on this platform.

First of all thank you very much for your work! Impressive!
Second just to report it is working in a RPi 2B with the the fake driver (vc4-fkms-v3d) and analog composite video output through the RPi minijack. It is probably silly, but I tried to run it with X server running and it gave the error xcb_randr_create_leas failed then I shutdown X with sudo service lightdm stop and it worked like a charm.
Following the conversation, what about MIDI integration? I know openframeworks has this addon. If you achieve audio reactivity and midi integration I "make you an statue" hehe
Thank you!

@k10z thanks a lot for the positive feedback!
User input / interactivity is the next major area I'd like to focus on. I've started thinking about it, and have few ideas. Hopefully I'll be able to work on it soon.

I've finally been able to iterate on this, and developed a Python wrapper around the native library in #21.
I've updated the README, and you'll be able to find some examples on how to bring your own inputs specifically in the glsl.py file:
https://github.com/astefanutti/kms-glsl/blob/f85385532afdddbd0f42e554c94047e8d203f06c/glsl.py#L19-L126
Hopefully this will meet your needs, and I'm eager to see what you guys will built with this 🤩.


DL: Refactor code to move some constants to helper file

Define MINIBATCH_OUTPUT_DEPENDENT_COLNAME_DL and
MINIBATCH_OUTPUT_INDEPENDENT_COLNAME_DL in madlib_keras_helper.py_in
instead of in input_data_preprocessor.py_in. Importing these from
input_data_preprocessor was also doing other imports that are not
necessary for madlib_keras.py_in.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/912/


Stale devices cause weird behavior

I didn't get to fully investigate this issue, but the device list gets corrupted when devices expire. I think this is a mistake.
I think the foundDevicesFlow should be filtered to remove stale devices. Alternatively, the two flows could be combined and lost devices filtered from the found devices (but that seems needlessly complicated). I'll suggest a change tomorrow if I have time.
It's possible that I'm misunderstanding exactly what is happening. In my example, I'm seeing the list fluctuate between two different lists after about 2 minutes.

It's possible that I'm misunderstanding exactly what is happening. In my example, I'm seeing the list fluctuate between two different lists after about 2 minutes.
Can you provide some logs? The operator may not be the correct one, but I do filter out devices every second if they haven't received a packet in a certain amount of time.

flowOf(foundDevicesFlow, lostDevicesFlow)
            .flattenMerge()

That's the culprit. It emits a series of lists that can alternate between found devices and stale devices, not a combination of them in a single list. I committed a fix to my branch.

The fact that empty lists are filtered is a workaround for the behavior of this bug when devices aren't expiring. When they do expire, instead of an empty list, you get a list with the expired device. I hope my branch https://github.com/sproctor/lighthouse/tree/time_refactor explains it well.

For visibility - this has been fixed locally for a bit now, I just haven't properly tested this/finished documentation. It's going out in the next release. 🚀

To me, this logic still doesn't make sense. You're creating two flows from backingDeviceList then combining them. There's not really any point to combining them except you're making changes to state in a cold flow. I still recommend something like my changes here: https://github.com/sproctor/lighthouse/blob/f15cf6df54c1be45435db1f41bfeb503c945d267/lighthouse/src/main/java/com/ivanempire/lighthouse/core/RealDiscoveryManager.kt

Yeah I meant that this issue in general is something I've been working on - I ended up doing something really similar to your PR.

I finally got around to upgrading and this issue is now fixed. I still prefer my method as it allows unit testing that the stale device removal works.


tooling support: socket repl

Several editors have integration with the repl as is, which is great. I've implemented an integration in Light Table (https://github.com/rundis/elm-light). However communication via stdin/stdout/stderr is somewhat limiting.
It would be great if it was possible to integrate with the repl through for example a tcp/ip socket. That way we could have a json api which would provide opportunities for much richer integrations I think. It would obviously also be nicer to work with than parsing string output from out/err as well.
One concrete example is error-messages. With a json-api, errors might be returned in the same format as elm-make ?

:+1:


security disclosure notice in CONTRIBUTING.md

Our Contribution Guidelines have been updated to incorporate instructions on security disclosure.


Export/Import multiple WSPs and MPGW - Functionality yet.??

Just this week I made a kinda hacky DCM export feature because I needed one in a hurry. It takes as input an XML file listing the required export objects, optionally including referenced objects and files. In other words just like the GUI export function. Happy to tidy it up and share but it might be a week or two before I find the time.

Oh wait the features was apparently just added in the latest merge so when the build is fixed you should be good to go :-)

I did customized one for me too by creating service names as a comma
separated list and the calling the export-service task looping using
groovy. Since DCM doesn't not have any contrib in it. I preferred to loop
through using groovy.
Thanks,
Vineet
On Sat, Sep 10, 2016, 7:33 AM samdjones<EMAIL_ADDRESS>wrote:

Oh wait the features was apparently just added in the latest merge so when
the build is fixed you should be good to go :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ibm-datapower/datapower-configuration-manager/issues/25#issuecomment-246114862,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASnyHcAyKKVwgjqHCvahx-fCw41LggXxks5qor-cgaJpZM4J5ezP
.

Yes, please!
On Sat, Sep 10, 2016 at 7:02 AM, samdjones<EMAIL_ADDRESS>wrote:

Just this week I made a kinda hacky DCM export feature because I needed
one in a hurry. It takes as input an XML file listing the required export
objects, optionally including referenced objects and files. In other words
just like the GUI export function. Happy to tidy it up and share but it
might be a week or two before I find the time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ibm-datapower/datapower-configuration-manager/issues/25#issuecomment-246105812,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADuMmpWPlrLxtGHCOikXlKA0nCaH6Yqrks5qoo5igaJpZM4J5ezP
.

Ah I see now - the new (to me at least) export feature only exports a single object, not multiple objects as my hack does. OK I'll look merging the two appoaches.

Hi Sam,
I have similar requirement to upload multiple services. Can you please share the files you modified and a sample command?
Thanks.

Hello,
I now have it on my list to contribute the feature to DCM hopefully by the end of this week hopefully (next week latest). Sorry I can't share sooner - better done properly.
Cheers.

Done: https://github.com/ibm-datapower/datapower-configuration-manager/pull/39

Thank you So much Sam. I will take a look at this.


Support for rails 6

@sumitdey035 https://github.com/domaindrivendev/rswag/pull/228

Thanks, @aadityamaheshwari for your help. Closing the issue here then.


A way to obtain file_id from media documents

Is there a way to recieve file_id from Media types (TypeMessageMedia) to send it through bot API without downloading? For example, in bot API for sharing existing photo required string file_id, but in core API only can be found (TypeFileLocation) fields, like VolumeId, Secret and so on.

@DenisAltruist Thanks for your interest in this repository. I am not so sure files would be interoperable between core API and bot API, because their ID system is quite different. Can you let me know if you ever heard of a case sharing files between APIs?

I don't know such cases. Yes, probably it's impossible to get file_id in core API (Moreover, file_id is different for different bot entities in bot API). The tricky solution is to forward message to particular bot or download file with providing accessible url for Telegram or upload again with bot.


API Returns Incorrect Values

e.g. it will report null consensus hashes in the /blocks/<block_height> route, and if you look in the sqlite3 db you'll see that the values are there and correct. Similar issues were reported with MINTS' supply.

This happens when a block is currently being parsed. The blocks are initially inserted with null hashes, and the hashes are updated at the end of the parsing process. Additionally, the API database may take some time to be updated as all events need to be parsed. If this only occurs with the last block, it is not a bug.

I think this should be fixed, but it's not urgent.

fixed here https://github.com/CounterpartyXCP/counterparty-core/pull/2700/commits/2c3dec63bbd805cbc2ef6adcb8b02ba59713442e


[terra-infinite-list] Cannot read property 'scrollHeight' of null

Bug Report
"Cannot read property 'scrollHeight' of null"
Description
When resizing there is a debounce timeout set in the InfiniteList, if it is umounted during the timeout the reference to "this" or "this.contentNode" will become null and the subsequent call for it's scrollHeight will cause an error.
Steps to Reproduce

Resize browser
Either programmatically remove the infinite list or use the dev-stie to select another tab

Possible Solution
Adding additional clearTImeout to the cleaup should fix it:
clearTimeout(this.timer);
https://github.com/cerner/terra-framework/blob/master/packages/terra-infinite-list/src/InfiniteList.jsx#L233

Closed #849


3.9 Recovery 1

Issues

[ ] https://github.com/OHIF/Viewers/issues/4499
[ ] https://github.com/OHIF/Viewers/issues/4485

Make it should be this.requestType.


Bug report: not compatible with blender 3.3

Please upgrade your add-on to the latest version = 2.5.1


Docs fix the storybook-manager-events.js, which is used for google tag manager.

          We need to fix the `storybook-manager-events.js`, which is used for `google tag manager`.

Originally posted by @oliverschuerch in https://github.com/swisspost/design-system/pull/2797#pullrequestreview-1938595843

Caused by #2797


Add ability to add values to the testing URL

My current function requires me to add extra values in the URL, since the actually body is sent from a system that I do not control. it works fine. but it would be great to be able to test that in the test pane
Example of URL:
https://graphhelper.azurewebsites.net/api/webhooks?code=asdasd434df3434sd&token=thisisthevalue

Related to #34. We've had discussions around this before, and decided against it. The reasoning is that we don't want to become as right as PostMan, as that would start making the UI too complex. There are many things one might want to tweak in the request:

query string
method
content type
all kind of other headers

The suggestion is to just use PostMan (or similar tool) and get the full power from them.


Bot not announcing after it went down

The bot won't announce the streamers I've added anymore. What do I need to do so I can make them announce again? It only announces for Twitch. Not Beam at all. For YouTube Gaming I don't know yet.

Greeting Message: Default
Goodbye Message: Default
Mention Role: Everyone
Time Zone Offset: 0
---- [Unused At The Moment] ----
Broadcast Sub Goals: False

Same here it only works for a Myself and a one other streamer(who isn't in my Discord) but I've added several to the list, I wonder if they have to be part of your discord server.

I too am having the same issue. none of the people that I have set up for beam are showing up, except for a select few. here is my configuration

Announcements Channel: Not Set
Go Live Channel: streampromote
Greetings Channel: rules
Published/VOD Channel: Not Set
Allow @ Everyone: True
Allow Thumbnails: True
Allow Broadcast Others: True
Allow Greetings: True
Allow Goodbyes: True
Allow VOD Content: False
Allow Others VOD Content: False
Use Text Announcements: False
Use YTG URLS For VOD Content: False
Use Whitelist: False
Current Whitelist: Empty
Live Message: Default
Published Message: Default
Greeting Message: Welcome to The Soul Army!!!
Goodbye Message: Farewell
Mention Role: Everyone
Time Zone Offset: -5
---- [Unused At The Moment] ----
Broadcast Sub Goals: False

Same issue, I imagine, across the board for you guys AND in the other issue that's along these lines.
Constellation and Beam as a whole are getting hammered. There is reconnect logic for the websocket connection to Constellation - but it clearly has issues :)
I can say, 100%, that it's not skipping people - it's probably just that the Constellation connection dropped.

I've added additional reconnect logic - I've validated it subscribes to the channel above accounts on launch of the Bot. So there is no issue there. There should be 0 need to remove-readd streamers. I will monitor the Constellation issues and validate my reconnect logic. If it continues - please re-open this issue.
Thanks so much for being patient with our special lil bot <3 :P


how to write compatible applications

Hi,
I'm looking for informations on how to write web applications and libraries that could be easily switched between .net core and .net framework.
The problem I see that in this first period, until most the 3rd party libraries are compatible with .net core, could be possibile I have to add libraries that are not ready for core, so I can solve or moving all the application to .net framework or move the code to another web app using .net framework and sharing for example the data model already wrote, but at this point I need to be able to compile a lib both for core and .net fx, but I haven't found any documentation about this.

@lucamorelli You can write .NET Core libraries which will run on .NET Framework.  There are two ways to do this:

Target the .NET Standard version which matches your targets - this is the preferred approach if you won't be using APIs unavailable in the .NET Standard
Multitarget and use #if directives in your code for platform-specific APIs

This article should help you out.

thanks for the link to the article. I changed the project.json of the library this way
"frameworks": {
"netstandard1.4": {
"imports": [
"dnxcore50",
"portable-net451+win8"
]
}
If I understand the situation using netstandard1.4 I ensure the same api level of net461, and now runs both in the .net core app and .net framework 4.6.1
I have just only one problem: even running if I open the startup class of the .net core app in the vs editor I have errors with all the type used in the startup class but declared inside the library, saying that couldn't be found.
I suppose that the problem is that in the json I find
"frameworks": {
"netcoreapp1.0": {
"imports": [
"dotnet5.6",
"dnxcore50",
"portable-net45+win8"
]
}
},
and netcoreapp1.0 is paired to netstandard1.6.
How can I solve this?

PR #2860  might address this since it will cover the new .NET Framework compatibility mode


Explinations

What does your feature do?
Provides explanations for what each feature does as well as how to use it.
How would people use it?
Some of the current GUI features are a bit hard to understand and its hard to play with them if you dont really understand what they do -  I've read over the spiggot and Bukkit pages as well as watched a few tutorials. I understand it a bit better but there are still several features I'm confused on and will likely never use because i dont know what they do.

Thanks for your input, but I'm not sure I understand. Which GUI are you referencing? If it's part of QuestsGUI, then this is the wrong issue tracker. There's also Gitbook wikis for both Quests and QuestsGUI which explain most features in detail.


Feature Request: Plotting Helpers

First thing I wanted to do when I saw graphs in the book is make some myself using Racket's wonderful plot library. Sadly, its a bit cumbersome since behind the scenes, 1.0 is not a number?.
Some kind of helper that takes a dataset, target function, and guessed theta and displays the dataset as points and the target function would be ideal.
This is my current workaround for context:
;; line is already defined, from malt
(require (except-in plot line))

;; (U Tensor Scalar) -> (U List Number)
;; Convert the tensor/scalar into a list/number
(define (tensor->datum t)
  (cond [(scalar? t) (ρ t)]
        [else (map (curry tref t) (range (tlen t)))]))

;; Do the book!
(match-define θ
  (with-hypers
    ((revs 1000)
     (α 0.01)
     (batch-size 10))
    (gradient-descent
     (sampling-obj
      (l2-loss line) line-xs line-ys)
     (list 0.0 0.0))))

;; Target Parameters -> (Real -> Real)
;; Assumes the target function computes a scalar value.
(define (target->plottable-function target θ)
  (λ (x)
    (tensor->datum ((target x) θ))))

(plot (list
           (axes)
           (points (map list (tensor->datum line-xs) (tensor->datum line-ys)))
           (function (target->plottable-function line θ))))

Hi @rymaju Thanks for the suggestion. Your solution works fine. Adding built-in renderer support for tensor representations will definitely allow for some good plotting of many different things. I will take it into consideration for a future release.


Fix Routes

Remove duplicate post route

Two nearly identical post routes in user_routes.py. One of the post routes updates database schema, the other doesn't. Removed the route that doesn't update database.


Migrate Grafana to Domain Layer

Description
Migrate all existing Grafana dashboard to use Domain Layer Entity

[ ] Design doc for all levels of domain layer integration

All existing dashboards are labelled with data sources