2022-08-01 02:42:01,623 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 02:42:01,623 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 02:42:01,723 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 02:42:01,723 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 02:48:46,584 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 02:48:46,583 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 02:48:46,683 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 02:48:46,683 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 02:48:46,784 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 02:48:46,783 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 02:55:31,626 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 02:55:31,625 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 02:55:31,626 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 02:55:31,626 - worker - Cleaning registries for queue: default
2022-08-01 02:55:31,724 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 02:55:31,724 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 02:55:31,825 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 02:55:31,825 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 02:55:31,826 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 02:55:31,826 - worker - Cleaning registries for queue: low
2022-08-01 03:02:16,695 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 03:02:16,695 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:02:16,795 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 03:02:16,795 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:02:16,896 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 03:02:16,895 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:09:01,777 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 03:09:01,776 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:09:01,877 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 03:09:01,877 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:09:01,977 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 03:09:01,977 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:15:46,865 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 03:15:46,864 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:15:46,965 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 03:15:46,965 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:15:47,065 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 03:15:47,065 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:22:31,947 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 03:22:31,946 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:22:31,947 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 03:22:31,947 - worker - Cleaning registries for queue: default
2022-08-01 03:22:32,048 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 03:22:32,048 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:22:32,148 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 03:22:32,148 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:22:32,149 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 03:22:32,148 - worker - Cleaning registries for queue: low
2022-08-01 03:29:17,005 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 03:29:17,005 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:29:17,106 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 03:29:17,106 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:29:17,206 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 03:29:17,206 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:36:02,085 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 03:36:02,084 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:36:02,185 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 03:36:02,185 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:36:02,285 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 03:36:02,284 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:42:47,143 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 03:42:47,143 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:42:47,244 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 03:42:47,243 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:42:47,344 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 03:42:47,344 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:49:32,219 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 03:49:32,219 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:49:32,220 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 03:49:32,220 - worker - Cleaning registries for queue: default
2022-08-01 03:49:32,320 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 03:49:32,319 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:49:32,421 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 03:49:32,420 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:49:32,421 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 03:49:32,421 - worker - Cleaning registries for queue: low
2022-08-01 03:56:17,311 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 03:56:17,311 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:56:17,412 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 03:56:17,412 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 03:56:17,513 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 03:56:17,513 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:03:02,364 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 04:03:02,364 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:03:02,465 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 04:03:02,464 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:03:02,566 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 04:03:02,566 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:09:47,450 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 04:09:47,450 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:09:47,550 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 04:09:47,550 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:09:47,651 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 04:09:47,651 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:16:32,512 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 04:16:32,511 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:16:32,513 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 04:16:32,512 - worker - Cleaning registries for queue: default
2022-08-01 04:16:32,613 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 04:16:32,613 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:16:32,713 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 04:16:32,713 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:16:32,714 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 04:16:32,714 - worker - Cleaning registries for queue: low
2022-08-01 04:23:17,560 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 04:23:17,560 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:23:17,660 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 04:23:17,660 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:23:17,762 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 04:23:17,761 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:30:02,628 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 04:30:02,627 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:30:02,728 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 04:30:02,728 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:30:02,828 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 04:30:02,828 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:36:47,701 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 04:36:47,700 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:36:47,802 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 04:36:47,801 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:36:47,901 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 04:36:47,901 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:43:32,756 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 04:43:32,755 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:43:32,757 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 04:43:32,756 - worker - Cleaning registries for queue: default
2022-08-01 04:43:32,857 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 04:43:32,856 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:43:32,957 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 04:43:32,957 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:43:32,958 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 04:43:32,958 - worker - Cleaning registries for queue: low
2022-08-01 04:50:17,823 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 04:50:17,823 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:50:17,924 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 04:50:17,923 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:50:18,025 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 04:50:18,024 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:57:02,897 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 04:57:02,897 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:57:02,998 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 04:57:02,997 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 04:57:03,099 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 04:57:03,099 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:03:47,987 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 05:03:47,986 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:03:48,086 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 05:03:48,086 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:03:48,186 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 05:03:48,186 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:10:33,066 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 05:10:33,066 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:10:33,067 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 05:10:33,067 - worker - Cleaning registries for queue: default
2022-08-01 05:10:33,167 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 05:10:33,166 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:10:33,267 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 05:10:33,266 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:10:33,268 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 05:10:33,267 - worker - Cleaning registries for queue: low
2022-08-01 05:17:18,149 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 05:17:18,148 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:17:18,249 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 05:17:18,249 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:17:18,350 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 05:17:18,350 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:24:03,223 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 05:24:03,223 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:24:03,324 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 05:24:03,323 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:24:03,424 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 05:24:03,424 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:30:48,318 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 05:30:48,317 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:30:48,417 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 05:30:48,417 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:30:48,517 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 05:30:48,517 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:37:33,396 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 05:37:33,396 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:37:33,397 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 05:37:33,397 - worker - Cleaning registries for queue: default
2022-08-01 05:37:33,497 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 05:37:33,497 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:37:33,598 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 05:37:33,597 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:37:33,598 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 05:37:33,598 - worker - Cleaning registries for queue: low
2022-08-01 05:44:18,476 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 05:44:18,476 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:44:18,576 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 05:44:18,576 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:44:18,677 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 05:44:18,677 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:51:03,561 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 05:51:03,560 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:51:03,661 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 05:51:03,661 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:51:03,761 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 05:51:03,761 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:57:48,648 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 05:57:48,648 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:57:48,749 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 05:57:48,748 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 05:57:48,849 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 05:57:48,849 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:04:33,729 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 06:04:33,728 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:04:33,730 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 06:04:33,729 - worker - Cleaning registries for queue: default
2022-08-01 06:04:33,829 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 06:04:33,829 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:04:33,930 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 06:04:33,929 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:04:33,930 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 06:04:33,930 - worker - Cleaning registries for queue: low
2022-08-01 06:11:18,820 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 06:11:18,820 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:11:18,920 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 06:11:18,919 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:11:19,021 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 06:11:19,021 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:18:03,901 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 06:18:03,900 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:18:04,001 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 06:18:04,000 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:18:04,101 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 06:18:04,101 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:24:48,988 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 06:24:48,988 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:24:49,088 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 06:24:49,088 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:24:49,190 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 06:24:49,190 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:31:34,070 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 06:31:34,070 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:31:34,071 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 06:31:34,071 - worker - Cleaning registries for queue: default
2022-08-01 06:31:34,170 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 06:31:34,170 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:31:34,271 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 06:31:34,270 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:31:34,272 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 06:31:34,271 - worker - Cleaning registries for queue: low
2022-08-01 06:38:19,162 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 06:38:19,161 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:38:19,263 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 06:38:19,262 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:38:19,364 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 06:38:19,363 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:45:04,248 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 06:45:04,248 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:45:04,348 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 06:45:04,348 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:45:04,448 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 06:45:04,448 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:51:49,253 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 06:51:49,253 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:51:49,354 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 06:51:49,353 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:51:49,455 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 06:51:49,454 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:58:34,337 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 06:58:34,337 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:58:34,338 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 06:58:34,338 - worker - Cleaning registries for queue: default
2022-08-01 06:58:34,437 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 06:58:34,437 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:58:34,538 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 06:58:34,537 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 06:58:34,539 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 06:58:34,538 - worker - Cleaning registries for queue: low
2022-08-01 07:05:19,420 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 07:05:19,420 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:05:19,521 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 07:05:19,520 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:05:19,622 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 07:05:19,621 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:12:04,507 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 07:12:04,506 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:12:04,607 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 07:12:04,606 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:12:04,708 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 07:12:04,707 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:18:49,590 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 07:18:49,590 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:18:49,691 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 07:18:49,690 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:18:49,792 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 07:18:49,791 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:25:34,595 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 07:25:34,595 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:25:34,596 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 07:25:34,596 - worker - Cleaning registries for queue: default
2022-08-01 07:25:34,696 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 07:25:34,696 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:25:34,797 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 07:25:34,796 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:25:34,797 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 07:25:34,797 - worker - Cleaning registries for queue: low
2022-08-01 07:32:19,694 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 07:32:19,694 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:32:19,795 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 07:32:19,795 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:32:19,896 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 07:32:19,895 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:39:04,794 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 07:39:04,793 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:39:04,894 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 07:39:04,894 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:39:04,995 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 07:39:04,994 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:45:49,886 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 07:45:49,886 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:45:49,987 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 07:45:49,986 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:45:50,087 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 07:45:50,087 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:52:34,893 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 07:52:34,893 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:52:34,894 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 07:52:34,894 - worker - Cleaning registries for queue: default
2022-08-01 07:52:34,994 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 07:52:34,993 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:52:35,095 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 07:52:35,095 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:52:35,096 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 07:52:35,096 - worker - Cleaning registries for queue: low
2022-08-01 07:59:19,903 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 07:59:19,903 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:59:20,004 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 07:59:20,003 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 07:59:20,105 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 07:59:20,104 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:06:05,000 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 08:06:05,000 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:06:05,101 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 08:06:05,100 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:06:05,199 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 08:06:05,199 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:12:50,083 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 08:12:50,082 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:12:50,184 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 08:12:50,183 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:12:50,283 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 08:12:50,283 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:19:35,132 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 08:19:35,131 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:19:35,133 DEBG 'rqworker_default_0' stderr output:
INFO - 2022-08-01 08:19:35,132 - worker - Cleaning registries for queue: default
2022-08-01 08:19:35,233 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 08:19:35,233 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:19:35,333 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 08:19:35,333 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:19:35,334 DEBG 'rqworker_low' stderr output:
INFO - 2022-08-01 08:19:35,333 - worker - Cleaning registries for queue: low
2022-08-01 08:26:20,193 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 08:26:20,193 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:26:20,293 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 08:26:20,293 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:26:20,394 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 08:26:20,393 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:33:05,289 DEBG 'rqworker_default_0' stderr output:
DEBUG - 2022-08-01 08:33:05,289 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:33:05,390 DEBG 'rqworker_default_1' stderr output:
DEBUG - 2022-08-01 08:33:05,389 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
2022-08-01 08:33:05,490 DEBG 'rqworker_low' stderr output:
DEBUG - 2022-08-01 08:33:05,490 - worker - Sent heartbeat to prevent worker timeout. Next one should arrive within 480 seconds.
Thanks! Sam

As the interface suggested, please share output from the Browser Console. I do not see any issues from docker output.

As the interface suggested, please share output from the Browser Console. I do not see any issues from docker output.

@bsekachev Sorry about that, here is the browser console output, hope it helps!

Additionally, try to check response for this request on Network tab: /api/restrictions/user-agreements in the browser console.

Additionally, try to check response for this request on Network tab: /api/restrictions/user-agreements in the browser console.

@bsekachev
Here it is:

@davodogster
Looks like CVAT instance has been improperly configured, since with "Disabled Cache" option you do not see login page anymore, it has been cached in your browser.
Try to open it using localhost:8080.

@nmanovic @bsekachev
Hi guys, here are the old docker volumes from before the machine died/broke. Do you know the easiest way to restore it?
I was using cvatv1.7.0

I have been trying:

I also added (is that the correct way for bind mounts?) and it didn't work.

But first I faced the errors above in previous comments.
Thanks, Sam

@davodogster ,
Sorry for the bad experience. It is something which should describe in our user guide for sure. Let's try to do step by step:

Clone CVAT v1.7.0
Modify the docker-compose.yml file to add v1.7.0 tag
Run it and check that it works (empty instance)
Create the superuser and check that you can login
Mount old volumes
Check that it works

Which step is broken?
--
Nikita.

Thanks @nmanovic! Here is what I tried: Specifically:

Clone CVAT v1.7.0 (sudo git clone -b release-1.7.0 --single-branch https://github.com/openvinotoolkit/cvat.git)
Modify the docker-compose.yml file to add v1.7.0 tag (I assume creating docker-compose.override.yml file is okay?)
Run it and check that it works (empty instance) - I  have been able to access login page but not create a user.
Create the superuser and check that you can login (Yes am able to create superuser but wasn't able to login with it). I want to retain all the old user logins aswell from the old docker volumes - is it possible?)
Docker-compose stop??
Mount old volumes (What is the best way to do this?)
Check that it works

Thanks! Sam

@davodogster , basically your empty CVAT v1.7.0 instance doesn't work. You cannot login. It doesn't make sense to mount new volumes. Try to run the procedure on an new machine (I don't want to ask you delete all old images and volumes). If it doesn't work, we will investigate and provide some instructions.
@azhavoro , please take a look.

@nmanovic It's working now and I don't know how. (I removed compose.overrride and used the raw docker-compose file, also ran it like: sudo CVAT_HOST=<IP_ADDRESS> docker-compose up -d)
But on the old machine I ran it with: -f components/serverless/docker-compose.serverless.yml
Will it matter if I omit this?

Now what is the best way to mount my old volumes?

Cheers, Sam

Close but no cigar @azhavoro

@azhavoro we originally started with an older version of cvat like 1.5 (we are attempting to restore our latest version 1.7), so some images were annotated using different versions. Will this matter for a successful restore? Cheers

Hi @nmanovic and @bsekachev Does the docker version or ubuntu version or linux kernel need to be identical when doing a CVAT restore?

Hi, @davodogster
Annotations are not stored in /home/django/data. They are stored in the database. ../data contains images and videos.

@davodogster , we are working on the guide how to upgrade CVAT. I hope it will answer on your questions.


Re-cretae-CIV-5673

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

void PR


Fix error 403 when refreshing the /home and /profile page.

Added a 403 error page to CloudFront distribution.
Issue #, if available:
Refreshing the page on /home and /profile is returning a 403 error from CloudFront.
Description of changes:
Added a new Error page to the CloudFront distribution
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Looks like checks fail in Actions: "SLACK_WEBHOOK is required."


Multiple bitrate

Hello
I'd like to know if ME.js support multiple bitrate sources (smil/m3u8) and auto select stream?
TIA
greg

Just wanted to see if there has been any movement on this front?  I am also looking into a way to do adaptive bitrate streaming.  On the same note is there any way to maybe not dynamically adjust the bitrate but to allow the user to select different streams in the media element ui?
Thanks,
Chris

Also thought maybe this would be worth a look.  https://github.com/dailymotion/hls.js

@johndyer I have a branch ready with the integration of hls.js with mediaelement; please let me know if you are interested in merging it. Thanks

+1 from me
I am presently working on a project where we need to publish videos in two resolutions for our church video archive (360p for users on cellphone networks with limited data plans and 720p for all the rest) . We do want to implement DASH at this phase as manual switching should perfectly cover our needs. Is  there any way to implement such a solution by means of mediaelement.js

Thanks for your response. Currently the player doesn't support DASH but we are working on a 3.x-dev branch and we can include it there. We'll keep you posted

Closing this issue to continue thread on #1609


[FLINK-19805] Revert "[FLINK-17295] Refactor the ExecutionAttemptID to consist of E…

What is the purpose of the change
This reverts commit b2e1c02db83e4eee6f561bb49feb9de70a445142 from FLINK-17295 (#11873)
While debugging FLINK-19805, we noticed that re-using the exact same ExecutionAttemptID across multiple leader sessions can lead to severe inconsistencies in the system.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

@tillrohrmann As the ExecutionAttemptID will be serialized, AbstractID might be a bit expensive. I suggest one of the following:

a random short (or even byte) is probably good enough.
replace the JobID with a random AbstractID. It might do a little bit of damage to the debugging in the session mode though.

@KarmaGYZ I was not talking about how to fix the problem but how to best revert the change. I think it should be fine to use AbstractID as it has been used before as well.

Thanks for the review Till! That's a good proposal! I'll investigate if a "light revert" is really turning out to be light. If that's the case, I'll close this PR in favor of a new one.

Closing this PR in favor of https://github.com/apache/flink/pull/13929.


feat: macro can customize importModuleName

If styled should come from a wrapper instead of directly from
styled-components, this enables users of the macro to customize the
import by configuring in packages.json:
"babelMacros": {
  "styledComponents": {
    "importModuleName": "my-styled-components"
  }
}

Previously similar functionality landed in
babel-plugin-styled-components so users of the plugin could use
a wrapper at that level, but it wasn't available to users of the macro.
This builds on that work by passing the customized module name through
to the plugin. Consequently we also update the dependency to ensure the
plugin supports topLevelImportPaths
See https://github.com/styled-components/babel-plugin-styled-components/commit/325167bb570362adfb5ff78aa84c460adeae32ac
Fixes https://github.com/gregberge/xstyled/issues/44

Another PR please

See #3432, thanks!


every few seconds discord tells me it has crashed.

i just installed better discord and when im not in the better discord menu or in the settings menu discord says it has crashed

Did you use the right betterdiscord installer?

Did you use the right betterdiscord installer?

What would be the right betterdiscord installer?

I'm having the same thing over here... every time I hover over the left bar, containing all the servers and BD Main Menu, I do get the error... I inspected with developer tools and it shows this:

Error: Unexpected missing parent container

https://0x71.cc/bd/guide/ use this installer

https://0x71.cc/bd/guide/ use this installer

Thanks for the link, I just installed Bandaged BD


Clone Failed

I am able to clone the repo, however I am unable to checkout the working tree. There is also a problem with one of the font paths.
error: invalid path 'moba/electron/src/mirror/fonts.googleapis.com/css?family=Lato:400,400italic,700'

Not sure what that means, sorry. It's a git repo with a single branch, I'm not sure what it means to be able to clone it but still not have it work. Maybe it's a problem with git on your computer?
Feel free to send a PR to fix broken URLs.

Haha, I wish I knew too. I've always been able to fork a repo and then just clone it but this repo didn't work. Basically I got the files but git would not make the link to the remote repo and I think it's directly related to the font error. I'll investigate and see if fixing the font error also fixes my inability to clone.

Created a pull request with the font deleted since it allowed me to clone properly. Also I'm a huge fan lol. Played Basketball gm for about 500+ hours and I love the work you did, you should be really proud. I also really like LOL GM but it was too slow so the reason why I am cloning is to see if I can do bug fixes on it, and possibly make it faster. Thanks!

Thanks! All the projects in this repo are very old and not in the best condition, so I wish you luck, but it'll probably be an uphill battle...

Yeah there's only about 8000 files to look through :). Oh well this is my first time trying to contribute to a project that's not my own so I'm gonna have a blast with this. Thanks for making this available to the community, you are a real one!


Feature request / implementation

Hello!
First of all: very nice server! It fits already 90% of my requirements. I´ve also spent days in the WWW to find a solution for my problem. My scenario: i´m receiving UDP / RTP streams and have to provide them via RTSP and authentification. Actually your server accepts only files as source. It´s possible to implement also UDP / RTP sources? Thx a lot for an answer. Greetings, Holger

Hi Holger,
Thanks for sharing your use-case. RTSPATT doesn't only support file inputs, the list of supported input methods is documented here.

INPUT | -i: Input used as video source. [default: pattern:smtpe]
If the argument starts with rtsp:// it will try to open it as an RTSP stream.
If it starts with pattern: it will create a test video with the given pattern (see this link for more information on this argument)
If the argument starts with /dev/video it will create a stream from the /dev/video device passed into docker at the launch of the instance. You will need to pass in the video device as follows: --device=/dev/video0:/dev/video0 where video0 is the video device.
Otherwise it will use the argument as an absolute link to file input. Remember to use the -v option to insert a video into your container if you want to read it.
Example: docker run -e INPUT=/tmp/video.mp4 -v /home/test/documents/myVideo.mp4:/tmp/video -p 8554:8554 ullaakut/rtspatt
The repository contains a 30 second sample video in the samples folder.

UDP/RTP sources are not supported at the moment though, but I won't be able to implement that feature. Are you able to look into it? You'll need to be familiar with gstreamer pipelines.
Here are some resources to get you started:

https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good/html/gst-plugins-good-plugins-udpsrc.html
https://stackoverflow.com/questions/1884204/playing-an-incoming-rtp-stream-with-gstreamer
https://gist.github.com/esrever10/7d39fe2d4163c5b2d7006495c3c911bb


Do not export '.percentile' and '.histogram' gauges to Dropwizard MetricRegistry

Related: https://github.com/micrometer-metrics/micrometer/blob/v1.0.0/micrometer-core/src/main/java/io/micrometer/core/instrument/dropwizard/DropwizardMeterRegistry.java#L77
Motivation:
Since 1.0.0, Micrometer registers additional gauges for percentile and
histogram values of Timers and DistributionSummarys for some monitoring
systems such as Dropwizard and Statsd.
I think it's not a sensible default to export additional gauges to
Dropwizard Timers and DistributionSummarys because Dropwizard already
provides its own percentile values via Timers and Histograms. Also,
because Dropwizard does not provide any aggregatation, such additional
gauges with tags will make things worse.
Modifications:

Make the DropwizardMeterRegistry created by DropwizardMeterRegistries
filter out the extra gauges registered when a Timer or a
DistributionSummary is created

Result:

Less surprising default

Thanks, reviewers!


Feat tooltip

Closes #89
Changes proposed

Created a Tooltip component which has the following properties:

placement - where to place the tooltip (up, down, left or right)
distanceInPx - distance from the tooltip to the element that activates the tooltip on hover
wrapperTag - name of the tag that wraps the tooltip (span or div)
wrapperClassName - string with class names for the element that wraps the tooltip
content - text of the tooltip
children

Style of the tooltip can be changed inside the component

Temporary added the tooltip in different places (Navigation and pages/index) so that it could be tested in preview deployment.

@VladBrok could you please check the build issue?

@VladBrok could you please check the build issue?

Yeah, of course! My bad, didn't noticed the build failure.

also please resolve the conflicts @VladBrok

Great PR @VladBrok

@rohitdasu Thank you!


Quadratic processing time for array responses

Consider the following contract:
contract Test {
  uint32 constant SIZE = // size here
  uint256[SIZE] private array;
  function get() external view returns (uint256[SIZE] memory) {
    return array;
  }
}

When SIZE is > ~1000 elements, the time spent waiting for a response to a web3 call() to get() starts to grow in a super-linear fashion.
NumElements: Time
1000: 1.0s
2000: 2.9s
3000: 5.6s
4000: 9.2s
5000: 13.9s
6000: 19.4s
7000: 25.9s
I've tested this both with the truffle web3js client as well as the rust-web3 client, both against ganache-cli and truffle develop and I see the same behavior. ganache-cli vs truffle develop have nearly the same response times, which makes leads me to believe there is some super-linear processing in ganache-core.
The cpu is spiked to 100% on a single core during the processing time.

Hi @domohawk we're not sure if this is due to a limitation of the vm in general or something with geth as well. This could be a problem with @ethereumjs/vm.
Can you try this with the Ganache canary release to see if the issue persists? You'll need to do the following:
npm uninstall ganache-cli -g && npm install ganache@canary -g

In the meantime we'll try to dig into this on our end. Thanks!

Thanks for the quick response. I tried out ganache@canary, and while the times are much better they are still growing super-linearly, and it's not really feasible to write tests for arrays larger than a few thousand elements:
ganache@canary

NumElements
Time

1
0.0017s

1000
0.9s

5000
4.6s

25k
40s

50k
114s

100k
388s

It seems like the websocket support in canary currently experimental?  Both rust-web3 and truffle web3js cause ganache-cli to crash when initiating the connection with TypeError: r.unmask is not a function

@domohawk interesting. My hunch is that this is an issue with @ethereum/vm, but i'll have to dig in a bit more.
As for the websocket support... are you on a mac M1 by any chance?

@davidmurdoch Nope, I'm running arch linux on Intel. If websockets is expected to work in canary I can file a different bug with the stack trace if that's helpful.

@domohawk which version of node?

@davidmurdoch node v16.6.1

@domohawk Ah ok, can you try v14?

@davidmurdoch So using node v14 improves the times more, but still same growth behavior. Both websockets and http have the same times.
ganache@canary, node v14.17.5 (both websockets & http)

NumElements
Time

1
0.0015s

1000
0.8s

5000
4.0s

25k
25s

50k
68s

100k
251s

I can confirm that geth does not seem to have this growth behavior, it seems to grow pretty linearly.
geth 1.10.6-stable, (both websockets & http)

NumElements
Time

1000
0.006s

5000
0.023s

25k
0.1s

50k
0.2s

100k
0.43s

500k
2.3s

1M
4.7s


What will be overridden by retry_budget in config.cluster.v3.CircuitBreakers.Thresholds

I'm reading the doc about the circuit breaker: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/cluster/v3/circuit_breaker.proto.html#envoy-v3-api-msg-config-cluster-v3-circuitbreakers-thresholds
There is a note for retry_budget:

If this field is set, the retry budget will override any configured retry circuit breaker.

I can't understand what it means. What will be overridden exactly?

I think this this refers to

max_retries:
(UInt32Value) The maximum number of parallel retries that Envoy will allow to the upstream cluster. If not specified, the default is 3.

See original PR: https://github.com/envoyproxy/envoy/pull/9069.


odeint (LSODA) fails if two t_crits occurs between two t_outs

I've found that in running integrate's odeint, LSODA will fail if, given an array of critical points tcrit and output times t,  there exists m, n such that t[m] <= tcrit[n] < tcrit[n+1] < t[m+1].  That is, if there are two critical points within a single span of t.
Reproducing code example:
import numpy as np
from scipy.integrate import odeint

def deriv(y,t):
    return np.zeros_like(y) + np.floor(t)

tc = np.arange(0,3,1.)

t1 = np.arange(0., 3.0, .5)
t2 = np.arange(0., 3.0, 1.5)

y0 = np.zeros(1)

for t in [t1, t2]:
    print 't = ' + str(t)
    r, e = odeint(deriv, y0, t, tcrit = tc, full_output=1)
    print e['message'] + '\n'

Error message:
t = [ 0.   0.5  1.   1.5  2.   2.5]
Integration successful.

t = [ 0.   1.5]
 lsoda--  itask = 4 or 5 and tcrit (=r1) behind tout (=r2)
      in above,  r1 =  0.1000000000000D+01   r2 =  0.1500000000000D+01
<path>/scipy-dev/local/lib/python2.7/site-packages/scipy-1.0.0.dev0+fe4ee43-py2..
  warnings.warn(warning_msg, ODEintWarning)
Illegal input detected (internal error).

Scipy/Numpy/Python version information:
<<('1.0.0.dev0+fe4ee43', '1.12.1', sys.version_info(major=2, minor=7, micro=12, releaselevel='final', serial=0))>>

I'm fairly certain the problem is in lines 697-710 of integrate/_odepackmodule.c
        tout_ptr = tout + k;
        /* Use tcrit if relevant */
        if (itask == 4 && *tout_ptr > *(tcrit + crit_ind)) {
            crit_ind++;
            rwork[0] = *(tcrit+crit_ind);
        }
        if (crit_ind >= numcrit) {
            itask = 1;  /* No more critical values */
        }

        LSODA(ode_function, &neq, y, &t, tout_ptr, &itol, rtol, atol, &itask,
              &istate, &iopt, rwork, &lrw, iwork, &liw,
              ode_jacobian_function, &jt);

and could be addressed by a evolving to the first internal tcrit without storing output, and so on until the next tcrit is greater than the next tout.  I don't know C well enough to implement it, though.

I'm not sure how if there is a convention being followd.  Looking more closely, I found that the behavior of tcrit is to me unexpected.
As mentioned above, two t_crits falling between t_outs causes failure.  But also, t_crit only has an effect when a t_out value falls within one step-size after a requested t_out.


Add support for OpenAI's gpt-4 turbo (gpt-4-1106-preview) model

Since OpenAI released the GPT-4 Turbo model (gpt-4-1106-preview) and reduced the prices of GPT-4 at their recent dev day, it would be cool if this tool was able to support using those as well.
Further Reading

https://openai.com/blog/new-models-and-developer-products-announced-at-devday
https://platform.openai.com/docs/models

New models launched at DevDay
We are excited to announce the preview release of GPT-4 Turbo (128k context window) and an updated GPT-3.5 Turbo (16k context window). Among other things, both models come with improved instruction following, JSON mode, more reproducible outputs, and parallel function calling.

https://openai.com/pricing

- Model
Input
Output

gpt-4-1106-preview
$0.01 / 1K tokens
$0.03 / 1K tokens

A quick search of the repo suggest changes would need to be made to at least the following files:

https://github.com/jehna/humanify/blob/main/src/index.ts#L38-L44
https://github.com/jehna/humanify/blob/main/src/openai/openai.ts#L30

Yes, great point! I think it would make sense to even parametrize the model as a command line argument 🤔

I think it would make sense to even parametrize the model as a command line argument

Yeah, I was thinking that too. Though maybe it can still have some 'friendly aliases' built in or similar so that the end user doesn't need to know the exact model name they need (specifically thinking about the current preview version of gpt-4-turbo in particular).
There are API's for querying the models available too, so if you wanted to get really fancy and not hardcode things, the CLI could potentially fetch the available models from that URL and cache them, then tell the user which ones could be used. Though that might be overkill.

GPT-4o mini was announced today; ~60% cheaper than GPT-3.5 Turbo:

https://openai.com/index/gpt-4o-mini-advancing-cost-efficient-intelligence/

GPT-4o mini scores 82% on MMLU and currently outperforms GPT-41 on chat preferences in LMSYS leaderboard(opens in a new window). It is priced at 15 cents per million input tokens and 60 cents per million output tokens, an order of magnitude more affordable than previous frontier models and more than 60% cheaper than GPT-3.5 Turbo

Hey! Seems that this PR got auto-closed because of the release of v2.
Thank you for your hard work and interest on improving humanify, especially @bilalba for maintaining a modernised fork while I've been unresponsive.
The v2 has now dependabot and automated merges for dependency updates that pass the tests, so dependencies should be easier to be kept up to date. I've also made gpt-4o-mini the default model and added the long awaited JSON mode with the new structured outputs.
The v2 does not count tokens anymore, but it uses the same AST-based precise approach that's been working for local renames. This should ensure that all the variable names are renamed, while not overloading the context limit of gpt-4o and others. I've experienced that some models (like Claude Opus) is much better at utilizing the full context window than others (like gpt-4o). By directing the LLM's focus to a small part that's only the fraction of its context window has worked the best in my testing. The v2 window size is super small now, but I'd be happy to increase it (or make it configurable via cli flag) if needed.
Originally posted by @jehna in https://github.com/jehna/humanify/issues/21#issuecomment-2282875396

Since the v2 CLI's OpenAI feature seems to allow the model name to be specified via --model, and defaults to gpt-4o-mini, I consider this issue implemented now:
https://github.com/jehna/humanify/blob/a6b09993dd93843a4a76556e4ed91b073f6a50b1/src/commands/openai.ts#L9-L12


Prettier improvements

Updated Prettier to 3.0.2
Deleted the prettier-ignore file since it can read the .gitignore file now
Added the prettier-tailwind-plugin, the repo will probably explain the pros better than me but it's basically for consistency and a visibility of classes priorities over each other
Added prettier-plugin-sort-imports for predictability (added a temporary config)
Didn't run prettier over the codebase for a cleaner PR

I'm not sure what's up with the lock file, it looks fine on my end 🤔

The warnings are expected since I didn't run prettier on purpose

Alright so I got the action to work on a copy if this repo (https://github.com/gawlk/mutiny-with-prettier-workflow/actions) without any token but I did need to allow create and approvals of PR which is supposed isn't great for you.
But you could use your own token for the PR so it shouldn't be an issue. I can try to see how it works if you want
So basically I made an optional config inside the prettier config file which is added only if the dependencies are installed. The workflow pull the repo and adds all unsafe deps and runs prettier, then it creates a branch and a PR which you.
The workflow runs once a week with the possibility to run it manually if needed

And if neither possibilities are secure enough for you
I see two more solutions:

Remove the workflow while keeping the rest, and move it to a synced fork of the repo which would do the PR automatically every week or so, which would be like any other contribution
Run a workflow in every PR but auto commit would probably be annoying

Hey @futurepaul, what would you like me do about the lock file ? Doing it manually would be a horror and there is an update so the file has to change

Appreciate all this effort to make this work. I think you're right about prettier-plugin-tailwindcss that can be added as a dev dep because it's from the same provenance...
The more that I think about this, the more comfortable I am with your original incarnation. Any diff will be evident in PRs, so as long as I keep reviewing PRs we should be good. Sorry for the run around. I am stoked to think of the possibilities of a workflow that creates prs, but for now I'd rather not have all that noise :)
some clarity about the pnpm lockfile, hopefully a rebase on top of this will work? (make sure you've updated pnpm): https://github.com/MutinyWallet/mutiny-web/pull/463

just to be clear: please change this back to how it was originally, with both the import sort and tailwind prettier added to the format command

No worries, I fully understand that security for such an app is extremely important

Squashed and rebased should be good to go (but still didn't run pnpm format, should I ?)

Ready to roll 🤙

appreciate this, long overdue cleanup, but hopefully this is the last in your series of diffsplosions!

Please don't hate me but I still have quite a few cleanups in mind 🥹


Periodically check Bevy's CI against the beta Rust channel

What problem does this solve or what need does it fill?
Most Rust releases, our CI breaks as new lints are stabilized, diagnostics change, or  causing confusion and work stoppage.
See #12620 for the latest.
What solution would you like?
Run all CI jobs against the beta channel of Rust every week.
It's not clear to me the best way to accomplish this or report it to the community at large. IIRC, Github's built-in feature for this only notifies a single person. Filing and tagging an issue would be ideal.
What alternative(s) have you considered?
Add more checks to CI.
This adds even more time to our already long CI jobs, and will confuse contributors due to failing changes in unrelated code.

There's a github action to create an issue, but I don't know if handing it our github token is a good idea safety wise.

this doc shows how to open an issue without depending on a custom action

My suggestion for this is to use discord webhooks
(I've been meaning to set the same thing up for Linebender, although of course with Zulip webhooks instead)


Typo 7.4.1

second sentence: tableau -> tableaux, I think this is meant to be plural.
"So far, especially for tableau and truth-tables, we’ve restricted ourselves to inferences with finite premise sets." should thus be "So far,especially for tableaux and truth-tables, we’ve restricted ourselves toinferences with finite premise sets."

Yes, you're right, @mvrozend ! Will fix later today.


Target Type in all jobs changed from compound to glob after updating to 3.0.0 from 2.1.0

Took me some time to figure out why (and then reconfigure) all jobs started failing after upgrade of the plugin.

Handling this as part of larger compatibility handling in #90


Centos6 python2-pycryptodomex with salt-api defunct processes when package upgraded or removed

When using centos6 setup with salt-api using the optional python2-pycryptodomex package, if you upgrade or remove the pycryptodomex package a defunct salt-api process shows up.
Replication Steps:

install salt 2017.7.5 or 7.6
install python2-pycryptodomex version 3.4: yum install python2-pycryptodomex
setup salt-master, salt-minion and salt-api. check process list:

[root@li1004-10 ~]# ps aux | grep -i salt-api
root     27787  0.7  1.8<PHONE_NUMBER>8 ?        S    21:59   0:00 /usr/bin/python2.7 /usr/bin/salt-api -d
root     27790  1.9  2.0 1777700 41788 ?       Sl   21:59   0:00 /usr/bin/python2.7 /usr/bin/salt-api -d

upgrade pycryptodomex to 3.6 yum upgrade python2-pycryptodomex
check process list:

[root@li1004-10 ~]# ps aux | grep -i salt-api
root     27787  0.0  1.8<PHONE_NUMBER>6 ?        S    21:59   0:00 /usr/bin/python2.7 /usr/bin/salt-api -d
root     27973  0.2  1.8<PHONE_NUMBER>2 ?        S    22:00   0:00 /usr/bin/python2.7 /usr/bin/salt-api -d
root     27975  1.4  1.8 1719632 37212 ?       Sl   22:00   0:00 /usr/bin/python2.7 /usr/bin/salt-api -d
root     28100  1.8  0.0      0     0 ?        Z    22:01   0:00 [salt-api] <defunct>

WORKAROUND: manually kill the salt-api process. Then restart salt-api process and everything works.

I manually tested this on centos7 to see if we were seeing the same thing even though our automated tests were passing. What i found after upgrading pycryptodomex from 3.4 to 3.6 was that there was now 3 salt-api processes showing up but it never becomes a defunct process. salt-api still continues to work. also when i try to restart the service it correclty kills the processes. I dont need to manually kill the service and can use the correct service manager to restart.

The problem also highlights itself if pycryptodomex is removed.  A dangling child process of the original salt-api process is left behind.  The same is happening with Salt 2018.3.1 on both Centos 7 & 6.  Salt-api is going to use the pycryptodomex version still in memory, even after yum erases it, and hence will not start using the basic pycrypto until it is restarted.
Requires further examination of salt-api and how it handles upgrade and removal of underlying packages that it is using.

@Ch3LL The problem is due to the use of cryptographic package not being hot-plug capable in Salt.  That is, adding a preferred cryptographic package, does not immediately imply its usage, similarly it's removal (parts of its removal are detected and a new user of it can be re-spun leading to additional processes.
It is best after the addition or removal of a cryptographic package, to restart all Salt packages which are currently installed and active, for example: salt-minion, salt-master, salt-api.  This is similar to changing a configuration parameter in a config file and having to restart the Salt component which utilizes the config file.
Preferred order of cryptographic packages utilized by Salt:
M2Crypto
pycryptodomex
pycrypto
If the preferred cryptographic package is unavailable, the next in the list is tried. Note: pycrypto is a required dependency, that is, at a minimum pycrypto must be available for Salt to install.

With removal of python2-pycryptodomex, CherryPy monitors system modules, see https://github.com/cherrypy/cherrypy/blob/master/cherrypy/process/plugins.py#L689-L690
which results in the following occurring (from systemd journal output)
Jun 20 11:43:00 localhost.localdomain salt-api[10721]: [20/Jun/2018:11:43:00] ENGINE Restarting because /usr/lib64/python2.7/site-packages/Cryptodome/IO/PEM.py changed.
Jun 20 11:43:00 localhost.localdomain salt-api[10721]: [20/Jun/2018:11:43:00] ENGINE Stopped thread 'Autoreloader'.

Jun 20 11:43:00 localhost.localdomain salt-api[10721]: [20/Jun/2018:11:43:00] ENGINE Re-spawning /usr/bin/salt-api
Jun 20 11:43:01 localhost.localdomain salt-api[10721]: [20/Jun/2018:11:43:01] ENGINE Listening for SIGHUP.
Jun 20 11:43:01 localhost.localdomain salt-api[10721]: [20/Jun/2018:11:43:01] ENGINE Listening for SIGTERM.
Jun 20 11:43:01 localhost.localdomain salt-api[10721]: [20/Jun/2018:11:43:01] ENGINE Listening for SIGUSR1.
Jun 20 11:43:01 localhost.localdomain salt-api[10721]: [20/Jun/2018:11:43:01] ENGINE Bus STARTING
Hence the previous recommendation of restarting salt-xxxx components after adding or removing a cryptographic package which Salt utilizes.
@Ch3LL With this information, can this  be closed and the doc's updated to reflect the need to restart the Salt components

Note the code in CherryPy is not limited to Cryptodome since it does a sys.modules.items() as demonstrated on an upgrade from 2017.7.6 to 20183.1 and ldap.py is noted as changed, from the systemd journal output:
398 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE Restarting because /usr/lib/python2.7/site-packages/salt/auth/ldap.py changed.
399 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE Stopped thread 'Autoreloader'.
400 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE Bus STOPPING
401 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('<IP_ADDRESS>', 8000)) shut down
402 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE Stopped thread '_TimeoutMonitor'.
403 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE Bus STOPPED
404 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE Bus EXITING
405 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE Bus EXITED
406 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE Waiting for child threads to terminate...
407 Jun 20 14:32:07 localhost.localdomain salt-api[21440]: [20/Jun/2018:14:32:07] ENGINE Re-spawning /usr/bin/salt-api
This is going to make any hot-plug changes interesting, in that how many other packages have such code which monitors what is used and detecting changes.  Note, that the install of Salt packages for packages that are already running causes a restart to be performed to pickup any configuration changes, hence we are back to two salt-api processes, in this instance.
root@localhost:~# ps -ef | grep salt-api
root     24436     1  0 14:32 ?        00:00:00 /usr/bin/python /usr/bin/salt-api
root     24612 24436  0 14:32 ?        00:00:00 /usr/bin/python /usr/bin/salt-api
root     25848 23810  0 14:33 pts/3    00:00:00 grep --color=auto salt-api
root@localhost:~#

My concern isn't that you need to restart the service. I understand that requirement. My concern was the process becoming defunct on cent6 as it does not occur on cent7. This requires manually stopping the process with a killsignal. Restarting the service with service salt-api restart does not work as the defunct process stays around.

zombie process. Guess we need to generate a list of packages with Salt where if you are going to install them, then kindly stop salt's running processes, then upgrade, then restart stopped running processes, or install packages xyz before installing salt.
Best analogy is , cannot change the engine while driving down the freeway.

@Ch3LL Is this still a concern or can we close it, since we don't do hot-plug, hence correct usage is shutdown, then start


Call Out to External BPF Programs

Not every valid BPF program can be expressed in BpfScript, so sometimes it is necessary to drop down to C/libbpf.
It would be useful to have a way to call out to externally written C-BPF programs from within BpfScript to enable more advanced functionality.
Example use cases:

Stack walkers for higher level languages, e.g. Python
More advanced statistics collection, e.g. t-digest

Details TBD.

This would be amazing, very excited. Happy to provide ideas and feedback here, would be great to be able to integrate other unwinders such as this one (technical write-up) I worked on for native code without frame pointers.
cc @danobi as we chatted about this in the past and I remember you had some thoughts.
Related issues #1744 and #1006.


[oc-id] Upgrade rails from 4.0.0 to a version receiving security patches.

The current version if Rails does not get any security patches.
Versions upto 5.2.0 will receive security fixes. https://guides.rubyonrails.org/maintenance_policy.html.
Rails will need to be updated  one version at a time:
4.0.2 -> 5.0 (https://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-4-2-to-rails-5-0)
5.0 -> 5.0.1
5.0.1 -> 5.0.2
It would be good to update all the way to 6.0.3, but that can be done as a separate issue if needed.
Some work to update rails to 5.0 was done as a part of https://github.com/chef/chef-server/compare/praj/upgrade_bundler_to_2?expand=1
Error  on that branch is :
Resolving dependencies.....
Bundler could not find compatible versions for gem "sprockets":
  In Gemfile:
    sprockets (~> 4.0)
    chef-web-core was resolved to 1.0.1, which depends on
      compass-rails (~> 2.0.4) was resolved to 2.0.5, which depends on
        sprockets (< 2.13)

That could be  resolved  by  copying app/assets to app/assets, lib/assets -> lib-> assets and vendor/assets to vendor/assets from chef-web-core to oc-id and removing the dependency on chef-web-core.
Useful resources:

https://blog.arkency.com/upgrading-a-trivial-rails-app-from-ruby-2-dot-3-dot-1-to-2-dot-7-and-from-rails-4-dot-2-dot-6-to-6-dot-0-dot-3/
https://rossta.net/blog/quiet-assets-in-rails-5.html
https://stackoverflow.com/questions/25983283/how-to-load-vendor-asset-folder-in-rails-4

Acceptance Criteria:

Rails can get the latests security upgrades(5.0.2)
Ideally on the latest version of rails (6.0.3)

Aha! Link: https://chef.aha.io/features/SH-180

https://github.com/chef/chef-server/pull/2059

https://github.com/chef/chef-server/pull/2125 and https://github.com/chef/chef-server/pull/2143


Should _add_parameter be public?

@jbednar and I agree this would be nice to have as part of the API


Can't play m3u8 video in Android

🔙 Regression

Old (and correct) behavior
Video played correctly
Current behavior
com.google.android.exoplayer2.source.UnrecognizedInputFormatException: None of the available extractors (MatroskaExtractor, FragmentedMp4Extractor, Mp4Extractor, Mp3Extractor, AdtsExtractor, Ac3Extractor, TsExtractor, FlvExtractor, OggExtractor, PsExtractor, WavExtractor, AmrExtractor) could read the stream.
Reproduction steps
await CrossMediaManager.Current.Play("http://devimages.apple.com/iphone/samples/bipbop/bipbopall.m3u8");
Configuration
Version: 0.5.3
Platform:

[ ] :iphone: iOS
[x] :robot: Android
[ ] :checkered_flag: WPF
[ ] :earth_americas: UWP
[ ] :apple: MacOS
[ ] :tv: tvOS
[ ] :monkey: Xamarin.Forms

Try: await CrossMediaManager.Current.Play(new MediaItem("http://devimages.apple.com/iphone/samples/bipbop/bipbopall.m3u8") { MediaType = MediaType.Hls });


Move changelog to a dedicated file

The normal way (in my experience) for this to work is to have a CHANGELOG text file at the root of the project. Like this for example.

Originally posted by @skeet70 in https://github.com/StarWarsFoundryVTT/StarWarsFFG/issues/443#issuecomment-732719905

Normal users don't read the readme file, unless instructed to do so.  I agree is confusing and probably needs to be revisited but this had no bearing on the functionality of the system.

That's fair, @cstadther. Users no longer need to navigate to the repo... but idk. It just looks kinda messy. The readme is a representation of your project and the giant changelog just doesn't mesh well.
If you're firmly for continuing it as-is, feel free to close the issue.

I'm was planning on leaving this issue open as a reminder, I just wanted to set expectations that this is probably one of the lowest priority items on the list and so probably won't be resolved in the immediate future.

Agreed, that's fair. I was confused. When I installed FoundryVTT and was looking for modules, I was mainly doing it through the "Install Modules" menu option. That shows you a very short description and a link to the Github w/README. I was primarily evaluating modules by following that link and reading the README, but I understand that users less comfortable with github may never click that link.
Is it primarily through this package page that people find the module? Avoiding the "Project URL" link?

I hope that is the link they are going to get get the system... Some users maybe grabbing the dev branch directly to help test new features that are being added.

I hate leaving people on HOLD, so I try to added comments to issues as I can.  Just so they know its been seen and is under consideration.


[WIP]Refactor the server and fix #106

Introduce simple middleware library

introduce 3 middlewares before onRequest:

locale detection - calculates the locale to use
logger - logs the requested urls;
static server - serves static whitelisted files. does not pass the control further if already able to serve the static file, so this part is now separate.

wraps the onRequest to work as a middleware. The idea is to move as much as possible from there to have separate easily testable steps.

Two suggestions:

Please keep middlewares similar to express.
Please separate #106 and Server refactoring, for the safe backout.

Thanks for tackling this, the result will be very helpful, but if you notice this is becoming quite tedious, you can check  https://github.com/Manvel/cmints/issues/113 - it's a quite useful functionality that currently is missing and I assume might be fun playing with.

@ZloeSabo #106 is fixed, but feel free to go ahead with the refactoring, otherwise I may get my hands on it after getting prio. issues/documentations fixed, basically one day :)

@Manvel the update is pushed. Still in progress and requires tests, but I changed the middleware format as requested.

Closing PR as seems like current PR is broken and not able to accept updates (CC: @ZloeSabo)


closes #982

What problem did you solve?
Closes #982  -  incorrect syntax highlighting for variables starting with the word function

Resolved by adding a negative lookahead to the function-declarations file to make sure there are no additional word characters following the function keyword
Added unit tests to show my code is working in the most basic settings

Unit tests work by reading in the regex pattern from the syntax file and then running them again pre-made strings
Added an environment variable to the tests launch file so that there is always an anchor to the root of the directory to get the syntax file (encase we change the test workspace in the future #990)

Please let me know if there's a better way to test this or if you need me to refactor the code (am still learning node/ts/js/vscode).
(If you have)Screenshot

Looks  like the unit tests have failed with:

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined

I'm assuming this is because the environment variable process.env.EXTENSION_ROOT isn't getting populated. I'm then guessing that this means the CICD job isn't using the same launch configuration as is being used by testing in vscode ?

@renkun-ken , fixed the bug with pathing for getting the config file, this is ready for review now. Please let me know if there is a better way of handling this.


[regression in 1.46] noDebug:true is lost when calling debug.startDebugging()

If you start a debug session dynamically, passing noDebug: true:
vscode.debug.startDebugging(
	vscode.workspace.workspaceFolders![0],
	{
		name: "Mock",
		request: "launch",
		type: "mock",
		program: '${file}',
		noDebug: true,
	},
);

In 1.46, this value gets lost when calling resolveDebugConfiguration:
resolveDebugConfiguration(folder: WorkspaceFolder | undefined, config: DebugConfiguration, token?: CancellationToken): ProviderResult<DebugConfiguration> {
	if (!config.noDebug) {
		vscode.window.showErrorMessage(`noDebug was not set to true when resolving debug config, despite being passed`);
	}
}

However in 1.45.1 and earlier, the value was correctly passed through. This results in a lot of commands/CodeLens links that are supposed to run without debugging, now running with debugging.
I've created a fork of MockDebug with the code from above to repro:
https://github.com/DanTup/vscode-repro-nodebug-lost
Run the extension and run the MockDebug: Run without debugging command.

@isidorn I don't know if this is related to #99743, but it appears to have changed in the most recent version and has broken a lot of functionality in Dart (there are many places we programatically spawn sessions without debugging - in some cases it's because debugging is not supported for those cases).

Hi @DanTup sorry about the breakage. We have fixed this in vscode insiders. Can you please try to reproduce with vscode insiders?
Also there will be a vscode recovery build soon which should contain the fix.

@isidorn thanks for the quick response - though unfortunately it still repros using the example project above with this mornings Insiders:
Version: 1.47.0-insider
Commit: 84f52fe1c0124307046ac0f5443493cda946e60f
Date: 2020-06-17T06:56:23.406Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.4.0

@DanTup thanks for trying with vscode insiders. Investigating...

@DanTup thanks for reporting. This was caused by a bad change I did and an even worse fix that I pushed. We will push this to the recovery release.

Reopening to track for recovery

@isidorn great, thanks! I'll check this in the next insiders build when it's available.

@dantup can I ask you to please try out this version of VS Code. The issue should be fixed with it, we would just like that you verify so we are 100% sure. Thanks!
Here's the link for the build
mac https://az764295.vo.msecnd.net/stable/78ea4488eb6e195cb0736182fe9e5a0d68eb1c39/VSCode-darwin-stable.zip
win
https://az764295.vo.msecnd.net/stable/78ea4488eb6e195cb0736182fe9e5a0d68eb1c39/VSCodeSetup-x64-1.46.1.exe
linux
https://az764295.vo.msecnd.net/stable/78ea4488eb6e195cb0736182fe9e5a0d68eb1c39/code-stable-1592408577.tar.gz

The fix works for me: adding a "noDebug": true to a node.js launch config makes the target program run without debugging.

Yep, it works for me too - on Stable when I click "Run" in my CodeLens, I still hit breakpoints. With the version above I do not. And when I use the Dart: Run All Tests command I can see it connecting debuggers in stable, but not in the version above.
Thanks!

Thank you DanTup for letting us know.


deprecate/remove github releases

eg https://github.com/LabVIEW-DCAF/TagEditorCore/releases
the last one is from 2014 so it could be confusing to go in there and download a version thats several years out of date :)

Deprecate / Delete old releases. Github release will only be done on DCAF Core repository.

Fixed.


WebView overrides horizontal scrolling

Is there a way to navigate to the next page when the user is still scrolling left or right but there's nothing more to scroll inside a webview ?
Thanks

this.state.index = 1
<Swiper index=`this.state.index`

// set state to change index?
setState({
  index: 2
})


Can you explain how to install?

I'm sorry but I couldn't install locally to test, I have stable diffusion (A1111 and comfyui) but I couldn't install this, I looked for tutorials on YouTube from this repository but I didn't find anything, do you have anything?

sorry , @matiasstornini not video yet, I can work on this later, but right now you have to clone
git clone https://github.com/radames/Real-Time-Latent-Consistency-Model
cd Real-Time-Latent-Consistency-Model
python -m venv venv
source venv/bin/activate
pip3 install -r server/requirements.txt
cd frontend && npm install && npm run build && cd ..
python server/main.py --reload --pipeline img2imgSDTurbo

Is there any way to make it work on Windows? I've followed through up untill
pip3 install -r server/requirements.txt
Then errors that wheel is not supported on this platform :(
No way to install such depedencies

please try commenting on theses lines https://github.com/radames/Real-Time-Latent-Consistency-Model/blob/9f0c5bb89637f054678cbaad017dbf7c3650e1dc/server/requirements.txt#L15-L17 and try the install steps again.
are you using WSL on windos?

I did that.
That did not work either. I was trying to install it "native" without WSL. I'm gonna try installing it with WSL or on PopOS/Manjaro.
Windows is always sketchy -.-


Question Re AST - Not Issue

Hi,
Thanks for this helpful library.  If you have the time/interest, can you help me understand or point me in the right direction of understanding the right way to get a "tree" model of the MD (ast?) using your library?
I'm trying to find a parser that will give me all the text under a header, and link the headers hierarchically in some for out outline or tree structure.
Thanks again. Dave G.

Oops.  Nevermind.


Add metrics to price estimation

It would be nice to instrument our price estimators in the Orderbook API. This way we can measure:

Success rate of the ParaSwap price estimator
Round trip time of the ParaSwap price estimator

To get a sense of how it is performing.

Implemented with #1639, #1591, #1282


Realtime torrent import

Hi, I found myself thinking, it would be possible to take the request to the tracker in real time and the tracker make the request on another tracker, so webtorrent can stream with udp trackers, for example large public trackers udp as desync, coppersurfer?
Sorry for my English.

That would only work for node clients. And even so, those clients can add any trackers they want; such as udp trackers. So I don't think there's any need for that feature.

I understood this as a proxy/relay that allows tracking using other trackers.
I also don't think there's a need for this feature.

@darkwolf66 Thanks for the suggestion, but this wouldn't really work because trackers aren't used for sending actual torrent data.
They just help peers to connect directly to each other. And there's no way to get a browser to directly connect to a TCP/uTP based desktop torrent client.

I think he's getting at making a ws:// tracker available for the web that is a proxy for udp:// on the server side. I'm also wondering how to do this.

@chovy It makes no sense to proxy udp:// to wss://, WebSocket trackers are for WebRTC peers, which can't connect to TCP/UDP.

I had not thought like a proxy but thinking it would be a proxy, I would have to implement the protocol used in the udp and tcp tracker to convert to wss protocol


Add Yelan aim cancels

.

@kurt22i do you have the vid link for this PR?

@kurt22i do you have the vid link for this PR?

I took it from Bowtae's sheet here: https://docs.google.com/spreadsheets/d/187T-SngEZUUordjY_K_tF_DdvHjQju9CoBJdp2eJOis/edit#gid=0
This is also how all the other aim cancels are currently done, we don't have footage for specific Aim->X interactions atm


Check for dependencies in Makefile

For example: before running make dev ensure that cargo-watch and sqlx-cli are installed. If not, install them.
Checkout the README to know what are all the dependencies required.

I will work on this.

Dobara PR banaunga, abhi urgent PR ki jaroorat thi.. makefiles ke paap mitane ke liye. Sorry. Thanks.


active design phase not highlighted in any way

When I visit http://qa.opendesignkit.org/phases/discover.html it isn't clear to me that "discover" is actively being filtered. Maybe some kind of active state would be nice on the button?

What if we included a 4px shadow (no blur, only on y axis) in a slightly brighter shade - @susanjrobertson

Sure @iamjessklein, can you give me the hex or the rgba for the shadow color for each of these? Then I'll that in for the individual phase page only.

Sure @susanjrobertson:
discover: #FFCF81
define: #9BECCE
design: #EF9ED0
develop: #82B7F5

This is on QA @iamjessklein, let me know if you want any changes or tweaks.

👍


Audio sync

If you'd add a method / property which returns current frame / time, it can be extended to sync with audio in the background.

canvid will not sync with audios, but a getter and setter for the frames is a good idea.

Yes, I need just a getter ;) setter can be called "seekTo", e.g.
Will create sync separately (it shouldn't be difficult though).

I added the functions getCurrentFrame and setCurrentFrame.


Vite 5 & laravel-vite-plugin v1 is exploding on build server

Vite Plugin Version
1.0.0
Laravel Version
10.37.3
Node Version
20.10.0
NPM Version
10.2.5
Operating System
Linux
OS Version
Ubuntu 22.04.1 LTS
Web browser and version
Irrelevant for this issue
Running in Sail?
No
Description
I've just deployed my upgraded app to the build server, newly with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and am hitting the following:
✘ [ERROR] "laravel-vite-plugin" resolved to an ESM file. ESM file cannot be loaded by `require`. See https://vitejs.dev/guide/troubleshooting.html#this-package-is-esm-only for more details. [plugin externalize-deps]

Steps To Reproduce
Note this also happens locally (M1 Macbook Pro, Sonoma 14.1, node 20.8.1 and npm 10.1.0). So I'm not sure really sure how to reproduce.
All I did was upgrade Vite to the latest version along with its one main dependent, laravel-vite-plugin

In my case, renaming the Vit config file fixed it
- vite.config.js
+ vite.config.mjs

Hi @simonhamp,
Did you follow the steps outlined in the Upgrade Guide?
Specifically:

Ensure your package.json contains "type": "module".
Run the following command in your project's root directory or anywhere you have your package.json files:

npm pkg set type=module

You may also need to rename any *.js configuration files that contain CJS, which is the older-style Node-flavored var plugin = require('plugin') syntax, to filename.cjs after making this change.

Yep I tried just adding "type": "module" but bumped into some issue with PostCSS still using require() somewhere
Haven't debugged further but will. It's surely not a laravel-vite-plugin issue.
Felt it was worth recording though in case anyone else came across the issue and went hunting.

For sure. The whole migration from CJS to MJS in the JS ecosystem is a super painful.
Easy fix is to rename any files that use the require syntax to {filename}.cjs.
But I'd be pushing to just move everything over to JS import / export where you can and be done with it all (hopefully 🤞)

Totally. That's where I'm heading, just need to hunt that down.


Added 2019-07-07 Blobs Swagger

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python


Object.assign does not work as expected in classes

Flow version: 0.97.0
Expected behavior
The following code:
class Test {
  constructor( param1, param2 ) {
    Object.assign( this, { param1, param2 })
  }
}

let T = new Test( 'A', 'B' )

console.log( 'Params:', T.param1, T.param2 )

should pass.
Actual behavior
Flow produces 4 errors saying properties param1 and param2 are missing in Test.
Well, they were indeed missing, until I explicitly assigned them... :)

https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVBjGBDAzrsAFQFNcAXMAb1TDAzgDtyAnAVwzLmYAowAHbM2wBbAIwAafoJEAmMAEoqNWmADyAIwBWxDgDo8uAJYBzBrzIALQ7kmUpQsZIEO5AX3nLXqL6hjEKhGAAvGAMxEgk5LwA5ACC0ZLRAELRCuj0THB+uvDGMQAK0sK4AFwJRLrOIhIVVcJy8kA

https://flow.org/try/#0PTAEAEDMBsHsHcBQiDG0CGBnToAqBTTAF1AG9FRQAHdAJ3QFsBGALlGNoEsA7AcwG4K1OowBMbDjwFCUsbhwCuKIrFoAKGvWYAaYVtEBKMkMpEAFp0wA6TYyagAvHrv9QIUJB74Toc5ZsiDKKOzkGu7p7c3pSUAPIARgBW+MpWWJicvNxqfpi6pKFMurZBoAC+BuFg6NCYsB5eQmWIzYjQ+CS4IVHweIREagBEAIKDuoMAQoOVyLLysO1WcLxDAAqBmCxjeAFaRTslhoJAA

Ok, I see. I've gotten used to Flow automatically detecting types using class property syntax, so I wasn't thinking about the need to define fields before the constructor in this case. Thanks for clearing that up.

@wchargin any chance we could reduce some boilerplate by inferring types in the following code
export class Test {
  x: number
  y: number
  z: number

  constructor(
    x: number,
    y: number,
    z: number
  ) {
    Object.assign( this, { x, y, z })
  }

so that it can be shortened to this
export class Test {
  x: number
  y: number
  z: number

  constructor( x, y, z ) {
    Object.assign( this, { x, y, z })
  }

since it would only make sense that objects with those keys being assigned to this would have to be numbers?

Dchhfjfchift

@soulofmischief: Flow does infer such types:
// @flow
class C {
  x: number;
  y: number;
  constructor(x, y) {
    this.x = x; // fine
    Object.assign(this, { y }); // also fine
  }
}

But the class in your example is exported, which means that its
constructor is also exported, and exported symbols must always be
explicitly typed. This is valuable for documentation purposes: I don’t
want to have to read the implementation of your constructor and
cross-reference it against the field definitions—maybe in superclasses,
maybe in other modules!—just to figure out what the parameter types are
supposed to be. It also makes typechecking significantly more efficient,
because each module can be typechecked independently.

(Independent of types or Flow, I’d hesitate to use Object.assign to
initialize fields at all. If I want to see where this.x is assigned
(which is something that I frequently want), I start by grepping for
“.x = ”; using “tricks” to save a few keystrokes now hampers your
readability and searchability later.)


Inward facing cylinder wall has normals pointing the wrong way

I'm using a GVRCylinderSceneObject with FacingOut set to false to use as a circular room. Inside the cylinder I've placed a GVRPointLight to light the walls. I find if I set the light to mainly diffuse then the walls are very poorly lit.
If I run this function to reverse the normals then walls are lit up properly.
    public static void mirrorNormals(GVRSceneObject sceneObject) {
        GVRMesh mesh = sceneObject.getRenderData().getMesh();
        float[] norms = mesh.getNormals();
        for(int index = 0; index < norms.length; index ++) {
            norms[index] = -norms[index];
        }
        mesh.setNormals(norms);
    }

Which constructor are you using? The one with signature
public GVRCylinderSceneObject(GVRContext gvrContext, boolean facingOut,
        ArrayList<GVRTexture> textureList)

is not assigning its facingOut parameter to anything

Add
params.FacingOut = facingOut;
to after the line
CylinderParams params = new CylinderParams();
to the definition of this constructor should fix

I'm using this signature:
public GVRCylinderSceneObject(GVRContext gvrContext, GVRCylinderSceneObject.CylinderParams params)
The FacingOut field is working okay with this function except for the normals. It looks like what you've found is a different bug.

ok. In
private void createBody(CylinderParams params)
the normals are actually not conditionally generated. We should add something like
if (params.FacingOut) {
nx0 = -nx0;
nx1 = -nx1;
...
...
//so on and so forth before copying to the normal buffer
}

I ran a similar test using X3D which calls the same Cylinder object and Cylinder Params.
It looks like the Normals inside the Cylinder are not flipping, except on the top and bottom of the Cylinder.
The left Cylinder has a texture map (same texture applied to a plane in the background) and a blue Cylinder on the right.
I attached  screen shot as well as the X3D file plus texture map.
mitch
Mitch Williams
Samsung GearVR X3D development
310-809-4836 (outside line)
From: Bo Huang<EMAIL_ADDRESS>Sent: Friday, February 9, 2018 11:59 AM
To: Samsung/GearVRf<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [Samsung/GearVRf] Inward facing cylinder wall has normals pointing the wrong way (#1734)
ok. In
private void createBody(CylinderParams params)
the normals are actually not conditionally generated. We should add something like
if (params.FacingOut) {
nx0 = -nx0;
nx1 = -nx1;
...
...
//so on and so forth before copying to the normal buffer
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Samsung/GearVRf/issues/1734#issuecomment-364546752, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ARSfvmx656z6MytDcjGk_LyVW3OEuoZlks5tTKN3gaJpZM4SAQa1.

Just another screen shot.
I rotated both cylinders to show the texture mapping on the inner top of Cylinder, but not on the sides.
Mitch Williams
Samsung GearVR X3D development
310-809-4836 (outside line)
From: Bo Huang<EMAIL_ADDRESS>Sent: Friday, February 9, 2018 11:59 AM
To: Samsung/GearVRf<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [Samsung/GearVRf] Inward facing cylinder wall has normals pointing the wrong way (#1734)
ok. In
private void createBody(CylinderParams params)
the normals are actually not conditionally generated. We should add something like
if (params.FacingOut) {
nx0 = -nx0;
nx1 = -nx1;
...
...
//so on and so forth before copying to the normal buffer
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Samsung/GearVRf/issues/1734#issuecomment-364546752, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ARSfvmx656z6MytDcjGk_LyVW3OEuoZlks5tTKN3gaJpZM4SAQa1.

PR #1736 should fix this issue for you.


Module compiled with Swift 5.0.1 cannot be imported by the Swift 5.1 compiler

I updated my Xcode to version 11 (to support iOS 13), and I wasn't able to run the library. I receive the message in the title:

Module compiled with Swift 5.0.1 cannot be imported by the Swift 5.1 compiler

I updated my pod to the latest version, and it seems the latest version in the pod supports 5.0 compiler. Could you please support 5.1 compiler?

@zengxinzhy @bingh0616 Any update on this please ?

+1

+1 xCode 11 gm is released, we look forward the update of tiny crayon. +1

+1

+1

+1

+1

+1

+1

+1

I am also waiting for the new release. but I have a tinycrayon-like repo. https://github.com/alexdecor/grabcut , let's implement ourselves while waiting for the release.

Hello, apple announced that all SDKs must run on iOS 13 in April 2020, this question can't be solved by finding a lot of methods. I don't know if I can ask for your help, thank you.
Xcode has been updated to version 11.4 beta 2
ITMS-90725: SDK Version Issue - This app was built with the iOS 12.2 SDK. Starting April 2020, all iOS apps submitted to the App Store must be built with the iOS 13 SDK or later, included in Xcode 11 or later.
Ref: https://developer.apple.com/ios/submit/

+1 on this

+1 on this

Hi
If you have the TinyCrayon Library available with you, Can you please share with us ?


Adsk Contrib - Ability to customize the default logging mechanism.

Signed-off-by: Patrick Hodoul<EMAIL_ADDRESS>As the library could be integrated in various applications the default logging mechanism must be customizable. The common use case would be to use a DCC logging mechanism if any. By default, the library uses the std::cerr.
The pull request adds a public mechanism to register a custom logging method.
Refer to include/OpenColorIO/OpenColorTypes.h at line 231 to have the callback details, and to include/OpenColorIO/OpenColorIO.h at line 138-141 to have the public method declarations.

Friendly reminder that this PR qualifies for single approver rule so it could now be merged this week.


fix(web-components): added margin left to mobile app container

Summary of the changes
added margin left to app title container on mobile to fit focus state
Related issue
#540
Checklist

[x] I have added relevant unit and visual regression tests.
[] I have manually accessibility tested any changes, if relevant.
[] I have ensured any changes match the Figma component library.

Slight update for this ticket. We have noticed a negative margin-left which should be removed instead of the additional styling added as part of the ticket: https://github.com/mi6/ic-ui-kit/blob/develop/packages/web-components/src/components/ic-top-navigation/ic-top-navigation.css#L24


Updated registry_landscape.md

Simplified and tweaked registry landscape table.
/cc @pauldul @clintkitson

LGTM

Coverage increased (+0.05%) to 64.56% when pulling 88941810aefaa2e659bbd29385cdfac432161413 on update-registry-landscape into fcae81a03410982e5c3ab1bfb1c68df71eaf94e5 on master.

@reasonerjt can you please give a :+1:?