{2015/11/07 15:08:01} Finished boxing /var/www/html/media/vi_0753_20151107_150755.mp4 from Box Queue at pos 30
{2015/11/07 15:08:03} send smd 1
[2015/11/07 15:08:03] Start capture requested from Pipe
[2015/11/07 15:08:03] Send ca 1
{2015/11/07 15:08:03} Capturing started
{2015/11/07 15:08:17} send smd 0
[2015/11/07 15:08:17] Stop capture requested
[2015/11/07 15:08:17] Send ca 0
{2015/11/07 15:08:17} Capturing stopped
{2015/11/07 15:08:17} Add /var/www/html/media/vi_0754_20151107_150803.mp4 to Box Queue at pos 31
{2015/11/07 15:08:17} Start boxing /var/www/html/media/vi_0754_20151107_150803.mp4.h264 to /var/www/html/media/vi_0754_20151107_150803.mp4 Queue pos 31
{2015/11/07 15:08:20} Finished boxing /var/www/html/media/vi_0754_20151107_150803.mp4 from Box Queue at pos 31
{2015/11/07 15:08:55} send smd 1
[2015/11/07 15:08:55] Start capture requested from Pipe
[2015/11/07 15:08:55] Send ca 1
{2015/11/07 15:08:55} Capturing started
{2015/11/07 15:09:03} send smd 0
[2015/11/07 15:09:03] Stop capture requested
[2015/11/07 15:09:03] Send ca 0
{2015/11/07 15:09:03} Capturing stopped
{2015/11/07 15:09:03} Add /var/www/html/media/vi_0755_20151107_150855.mp4 to Box Queue at pos 0
{2015/11/07 15:09:04} Start boxing /var/www/html/media/vi_0755_20151107_150855.mp4.h264 to /var/www/html/media/vi_0755_20151107_150855.mp4 Queue pos 0
{2015/11/07 15:09:05} Finished boxing /var/www/html/media/vi_0755_20151107_150855.mp4 from Box Queue at pos 0
{2015/11/07 15:09:12} send smd 1
[2015/11/07 15:09:12] Start capture requested from Pipe
[2015/11/07 15:09:12] Send ca 1
{2015/11/07 15:09:12} Capturing started
{2015/11/07 15:09:18} send smd 0
[2015/11/07 15:09:18] Stop capture requested
[2015/11/07 15:09:18] Send ca 0
{2015/11/07 15:09:18} Capturing stopped
{2015/11/07 15:09:18} Add /var/www/html/media/vi_0756_20151107_150912.mp4 to Box Queue at pos 1
{2015/11/07 15:09:18} Start boxing /var/www/html/media/vi_0756_20151107_150912.mp4.h264 to /var/www/html/media/vi_0756_20151107_150912.mp4 Queue pos 1
{2015/11/07 15:09:19} Finished boxing /var/www/html/media/vi_0756_20151107_150912.mp4 from Box Queue at pos 1
{2015/11/07 15:09:19} send smd 1
[2015/11/07 15:09:20] Start capture requested from Pipe
[2015/11/07 15:09:20] Send ca 1
{2015/11/07 15:09:20} Capturing started
{2015/11/07 15:09:24} send smd 0
[2015/11/07 15:09:24] Stop capture requested
[2015/11/07 15:09:24] Send ca 0
{2015/11/07 15:09:24} Capturing stopped
{2015/11/07 15:09:24} Add /var/www/html/media/vi_0757_20151107_150920.mp4 to Box Queue at pos 2
{2015/11/07 15:09:25} Start boxing /var/www/html/media/vi_0757_20151107_150920.mp4.h264 to /var/www/html/media/vi_0757_20151107_150920.mp4 Queue pos 2
{2015/11/07 15:09:26} Finished boxing /var/www/html/media/vi_0757_20151107_150920.mp4 from Box Queue at pos 2
{2015/11/07 15:09:26} send smd 1
[2015/11/07 15:09:26] Start capture requested from Pipe
[2015/11/07 15:09:26] Send ca 1
{2015/11/07 15:09:27} Capturing started
{2015/11/07 15:09:31} send smd 0
[2015/11/07 15:09:31] Stop capture requested
[2015/11/07 15:09:31] Send ca 0
{2015/11/07 15:09:31} Capturing stopped
{2015/11/07 15:09:31} Add /var/www/html/media/vi_0758_20151107_150927.mp4 to Box Queue at pos 3
{2015/11/07 15:09:31} Start boxing /var/www/html/media/vi_0758_20151107_150927.mp4.h264 to /var/www/html/media/vi_0758_20151107_150927.mp4 Queue pos 3
{2015/11/07 15:09:31} send smd 1
{2015/11/07 15:09:32} Finished boxing /var/www/html/media/vi_0758_20151107_150927.mp4 from Box Queue at pos 3
[2015/11/07 15:09:33] Start capture requested from Pipe
[2015/11/07 15:09:33] Send ca 1
{2015/11/07 15:09:33} Capturing started
{2015/11/07 15:09:37} send smd 0
[2015/11/07 15:09:37] Stop capture requested
[2015/11/07 15:09:37] Send ca 0
{2015/11/07 15:09:37} Capturing stopped
{2015/11/07 15:09:37} Add /var/www/html/media/vi_0759_20151107_150933.mp4 to Box Queue at pos 4
{2015/11/07 15:09:37} Start boxing /var/www/html/media/vi_0759_20151107_150933.mp4.h264 to /var/www/html/media/vi_0759_20151107_150933.mp4 Queue pos 4
{2015/11/07 15:09:38} Finished boxing /var/www/html/media/vi_0759_20151107_150933.mp4 from Box Queue at pos 4
[2015/11/07 15:12:24] Scheduled management tasks. Next at<PHONE_NUMBER>
{2015/11/07 15:15:41} send smd 1
[2015/11/07 15:15:41] Start capture requested from Pipe
[2015/11/07 15:15:41] Send ca 1
{2015/11/07 15:15:41} Capturing started
{2015/11/07 15:15:45} send smd 0
[2015/11/07 15:15:45] Stop capture requested
[2015/11/07 15:15:45] Send ca 0
{2015/11/07 15:15:45} Capturing stopped
{2015/11/07 15:15:45} Add /var/www/html/media/vi_0760_20151107_151541.mp4 to Box Queue at pos 5
{2015/11/07 15:15:45} Start boxing /var/www/html/media/vi_0760_20151107_151541.mp4.h264 to /var/www/html/media/vi_0760_20151107_151541.mp4 Queue pos 5
{2015/11/07 15:15:46} Finished boxing /var/www/html/media/vi_0760_20151107_151541.mp4 from Box Queue at pos 5
{2015/11/07 15:18:43} send smd 1
[2015/11/07 15:18:43] Start capture requested from Pipe
[2015/11/07 15:18:43] Send ca 1
{2015/11/07 15:18:44} Capturing started
{2015/11/07 15:18:47} send smd 0
[2015/11/07 15:18:47] Stop capture requested
[2015/11/07 15:18:47] Send ca 0
{2015/11/07 15:18:47} Capturing stopped
{2015/11/07 15:18:47} Add /var/www/html/media/vi_0761_20151107_151844.mp4 to Box Queue at pos 6
{2015/11/07 15:18:48} Start boxing /var/www/html/media/vi_0761_20151107_151844.mp4.h264 to /var/www/html/media/vi_0761_20151107_151844.mp4 Queue pos 6
{2015/11/07 15:18:49} Finished boxing /var/www/html/media/vi_0761_20151107_151844.mp4 from Box Queue at pos 6
{2015/11/07 15:21:10} send smd 1
[2015/11/07 15:21:10] Start capture requested from Pipe
[2015/11/07 15:21:10] Send ca 1
{2015/11/07 15:21:10} Capturing started
{2015/11/07 15:21:15} send smd 0
[2015/11/07 15:21:15] Stop capture requested
[2015/11/07 15:21:15] Send ca 0
{2015/11/07 15:21:16} Capturing stopped
{2015/11/07 15:21:16} Add /var/www/html/media/vi_0762_20151107_152110.mp4 to Box Queue at pos 7
{2015/11/07 15:21:16} Start boxing /var/www/html/media/vi_0762_20151107_152110.mp4.h264 to /var/www/html/media/vi_0762_20151107_152110.mp4 Queue pos 7
{2015/11/07 15:21:17} Finished boxing /var/www/html/media/vi_0762_20151107_152110.mp4 from Box Queue at pos 7
{2015/11/07 15:21:46} send smd 1
[2015/11/07 15:21:46] Start capture requested from Pipe
[2015/11/07 15:21:46] Send ca 1
{2015/11/07 15:21:46} Capturing started
{2015/11/07 15:21:51} send smd 0
[2015/11/07 15:21:51] Stop capture requested
[2015/11/07 15:21:51] Send ca 0
{2015/11/07 15:21:51} Capturing stopped
{2015/11/07 15:21:51} Add /var/www/html/media/vi_0763_20151107_152146.mp4 to Box Queue at pos 8
{2015/11/07 15:21:51} Start boxing /var/www/html/media/vi_0763_20151107_152146.mp4.h264 to /var/www/html/media/vi_0763_20151107_152146.mp4 Queue pos 8
{2015/11/07 15:21:52} send smd 1
{2015/11/07 15:21:52} Finished boxing /var/www/html/media/vi_0763_20151107_152146.mp4 from Box Queue at pos 8
[2015/11/07 15:21:53] Start capture requested from Pipe
[2015/11/07 15:21:53] Send ca 1
{2015/11/07 15:21:53} Capturing started
{2015/11/07 15:22:04} send smd 0
[2015/11/07 15:22:04] Stop capture requested
[2015/11/07 15:22:04] Send ca 0
{2015/11/07 15:22:04} Capturing stopped
{2015/11/07 15:22:04} Add /var/www/html/media/vi_0764_20151107_152153.mp4 to Box Queue at pos 9
{2015/11/07 15:22:04} Start boxing /var/www/html/media/vi_0764_20151107_152153.mp4.h264 to /var/www/html/media/vi_0764_20151107_152153.mp4 Queue pos 9
{2015/11/07 15:22:07} Finished boxing /var/www/html/media/vi_0764_20151107_152153.mp4 from Box Queue at pos 9
{2015/11/07 15:22:15} send smd 1
[2015/11/07 15:22:15] Start capture requested from Pipe
[2015/11/07 15:22:15] Send ca 1
{2015/11/07 15:22:15} Capturing started
{2015/11/07 15:22:25} send smd 0
[2015/11/07 15:22:25] Stop capture requested
[2015/11/07 15:22:25] Send ca 0
{2015/11/07 15:22:25} Capturing stopped
{2015/11/07 15:22:25} Add /var/www/html/media/vi_0765_20151107_152215.mp4 to Box Queue at pos 10
{2015/11/07 15:22:26} Start boxing /var/www/html/media/vi_0765_20151107_152215.mp4.h264 to /var/www/html/media/vi_0765_20151107_152215.mp4 Queue pos 10
{2015/11/07 15:22:28} Finished boxing /var/www/html/media/vi_0765_20151107_152215.mp4 from Box Queue at pos 10
{2015/11/07 15:26:38} send smd 1
[2015/11/07 15:26:38] Start capture requested from Pipe
[2015/11/07 15:26:38] Send ca 1
{2015/11/07 15:26:39} Capturing started
{2015/11/07 15:26:42} send smd 0
[2015/11/07 15:26:42] Stop capture requested
[2015/11/07 15:26:42] Send ca 0
{2015/11/07 15:26:42} Capturing stopped
{2015/11/07 15:26:42} Add /var/www/html/media/vi_0766_20151107_152639.mp4 to Box Queue at pos 11
{2015/11/07 15:26:43} Start boxing /var/www/html/media/vi_0766_20151107_152639.mp4.h264 to /var/www/html/media/vi_0766_20151107_152639.mp4 Queue pos 11
{2015/11/07 15:26:44} Finished boxing /var/www/html/media/vi_0766_20151107_152639.mp4 from Box Queue at pos 11
[2015/11/07 15:32:25] Scheduled management tasks. Next at<PHONE_NUMBER>
{2015/11/07 15:36:39} send smd 1
[2015/11/07 15:36:39] Start capture requested from Pipe
[2015/11/07 15:36:39] Send ca 1
{2015/11/07 15:36:39} Capturing started
{2015/11/07 15:36:47} send smd 0
[2015/11/07 15:36:47] Stop capture requested
[2015/11/07 15:36:47] Send ca 0
{2015/11/07 15:36:47} Capturing stopped
{2015/11/07 15:36:47} Add /var/www/html/media/vi_0767_20151107_153639.mp4 to Box Queue at pos 12
{2015/11/07 15:36:47} Start boxing /var/www/html/media/vi_0767_20151107_153639.mp4.h264 to /var/www/html/media/vi_0767_20151107_153639.mp4 Queue pos 12
{2015/11/07 15:36:48} Finished boxing /var/www/html/media/vi_0767_20151107_153639.mp4 from Box Queue at pos 12
{2015/11/07 15:37:07} send smd 1
[2015/11/07 15:37:07] Start capture requested from Pipe
[2015/11/07 15:37:07] Send ca 1
{2015/11/07 15:37:07} Capturing started
{2015/11/07 15:37:15} send smd 0
[2015/11/07 15:37:15] Stop capture requested
[2015/11/07 15:37:15] Send ca 0
{2015/11/07 15:37:16} Capturing stopped
{2015/11/07 15:37:16} Add /var/www/html/media/vi_0768_20151107_153707.mp4 to Box Queue at pos 13
{2015/11/07 15:37:16} Start boxing /var/www/html/media/vi_0768_20151107_153707.mp4.h264 to /var/www/html/media/vi_0768_20151107_153707.mp4 Queue pos 13
{2015/11/07 15:37:17} Finished boxing /var/www/html/media/vi_0768_20151107_153707.mp4 from Box Queue at pos 13
{2015/11/07 15:44:24} send smd 1
[2015/11/07 15:44:24] Start capture requested from Pipe
[2015/11/07 15:44:24] Send ca 1
{2015/11/07 15:44:24} Capturing started
{2015/11/07 15:44:27} send smd 0
[2015/11/07 15:44:27] Stop capture requested
[2015/11/07 15:44:27] Send ca 0
{2015/11/07 15:44:27} Capturing stopped
{2015/11/07 15:44:27} Add /var/www/html/media/vi_0769_20151107_154424.mp4 to Box Queue at pos 14
{2015/11/07 15:44:28} Start boxing /var/www/html/media/vi_0769_20151107_154424.mp4.h264 to /var/www/html/media/vi_0769_20151107_154424.mp4 Queue pos 14
{2015/11/07 15:44:29} send smd 1
[2015/11/07 15:44:29] Start capture requested from Pipe
[2015/11/07 15:44:29] Send ca 1
{2015/11/07 15:44:29} Capturing started
{2015/11/07 15:44:29} Finished boxing /var/www/html/media/vi_0769_20151107_154424.mp4 from Box Queue at pos 14
{2015/11/07 15:44:33} send smd 0
[2015/11/07 15:44:33] Stop capture requested
[2015/11/07 15:44:33] Send ca 0
{2015/11/07 15:44:33} Capturing stopped
{2015/11/07 15:44:33} Add /var/www/html/media/vi_0770_20151107_154429.mp4 to Box Queue at pos 15
{2015/11/07 15:44:33} Start boxing /var/www/html/media/vi_0770_20151107_154429.mp4.h264 to /var/www/html/media/vi_0770_20151107_154429.mp4 Queue pos 15
{2015/11/07 15:44:34} Finished boxing /var/www/html/media/vi_0770_20151107_154429.mp4 from Box Queue at pos 15
{2015/11/07 15:44:56} send smd 1
[2015/11/07 15:44:56] Start capture requested from Pipe
[2015/11/07 15:44:56] Send ca 1
{2015/11/07 15:44:56} Capturing started
{2015/11/07 15:45:00} send smd 0
[2015/11/07 15:45:00] Stop capture requested
[2015/11/07 15:45:00] Send ca 0
{2015/11/07 15:45:00} Capturing stopped
{2015/11/07 15:45:00} Add /var/www/html/media/vi_0771_20151107_154456.mp4 to Box Queue at pos 16
{2015/11/07 15:45:01} Start boxing /var/www/html/media/vi_0771_20151107_154456.mp4.h264 to /var/www/html/media/vi_0771_20151107_154456.mp4 Queue pos 16
{2015/11/07 15:45:02} Finished boxing /var/www/html/media/vi_0771_20151107_154456.mp4 from Box Queue at pos 16
{2015/11/07 15:45:04} send smd 1
[2015/11/07 15:45:04] Start capture requested from Pipe
[2015/11/07 15:45:04] Send ca 1
{2015/11/07 15:45:04} Capturing started
{2015/11/07 15:45:12} send smd 0
[2015/11/07 15:45:12] Stop capture requested
[2015/11/07 15:45:12] Send ca 0
{2015/11/07 15:45:13} Capturing stopped
{2015/11/07 15:45:13} Add /var/www/html/media/vi_0772_20151107_154504.mp4 to Box Queue at pos 17
{2015/11/07 15:45:13} Start boxing /var/www/html/media/vi_0772_20151107_154504.mp4.h264 to /var/www/html/media/vi_0772_20151107_154504.mp4 Queue pos 17
{2015/11/07 15:45:15} Finished boxing /var/www/html/media/vi_0772_20151107_154504.mp4 from Box Queue at pos 17
{2015/11/07 15:45:26} send smd 1
[2015/11/07 15:45:26] Start capture requested from Pipe
[2015/11/07 15:45:26] Send ca 1
{2015/11/07 15:45:27} Capturing started
{2015/11/07 15:45:32} send smd 0
[2015/11/07 15:45:32] Stop capture requested
[2015/11/07 15:45:32] Send ca 0
{2015/11/07 15:45:32} Capturing stopped
{2015/11/07 15:45:32} Add /var/www/html/media/vi_0773_20151107_154527.mp4 to Box Queue at pos 18
{2015/11/07 15:45:33} Start boxing /var/www/html/media/vi_0773_20151107_154527.mp4.h264 to /var/www/html/media/vi_0773_20151107_154527.mp4 Queue pos 18
{2015/11/07 15:45:34} Finished boxing /var/www/html/media/vi_0773_20151107_154527.mp4 from Box Queue at pos 18
{2015/11/07 15:45:36} send smd 1
[2015/11/07 15:45:36] Start capture requested from Pipe
[2015/11/07 15:45:36] Send ca 1
{2015/11/07 15:45:36} Capturing started
{2015/11/07 15:45:42} send smd 0
[2015/11/07 15:45:42] Stop capture requested
[2015/11/07 15:45:42] Send ca 0
{2015/11/07 15:45:43} Capturing stopped
{2015/11/07 15:45:43} Add /var/www/html/media/vi_0774_20151107_154536.mp4 to Box Queue at pos 19
{2015/11/07 15:45:43} Start boxing /var/www/html/media/vi_0774_20151107_154536.mp4.h264 to /var/www/html/media/vi_0774_20151107_154536.mp4 Queue pos 19
{2015/11/07 15:45:43} send smd 1
[2015/11/07 15:45:45] Start capture requested from Pipe
[2015/11/07 15:45:45] Send ca 1
{2015/11/07 15:45:45} Capturing started
{2015/11/07 15:45:45} Finished boxing /var/www/html/media/vi_0774_20151107_154536.mp4 from Box Queue at pos 19
{2015/11/07 15:45:48} send smd 0
[2015/11/07 15:45:48] Stop capture requested
[2015/11/07 15:45:48] Send ca 0
{2015/11/07 15:45:48} Capturing stopped
{2015/11/07 15:45:48} Add /var/www/html/media/vi_0775_20151107_154545.mp4 to Box Queue at pos 20
{2015/11/07 15:45:49} Start boxing /var/www/html/media/vi_0775_20151107_154545.mp4.h264 to /var/www/html/media/vi_0775_20151107_154545.mp4 Queue pos 20
{2015/11/07 15:45:50} send smd 1
[2015/11/07 15:45:50] Start capture requested from Pipe
[2015/11/07 15:45:50] Send ca 1
{2015/11/07 15:45:50} Capturing started
{2015/11/07 15:45:50} Finished boxing /var/www/html/media/vi_0775_20151107_154545.mp4 from Box Queue at pos 20
{2015/11/07 15:45:56} send smd 0
[2015/11/07 15:45:56] Stop capture requested
[2015/11/07 15:45:56] Send ca 0
{2015/11/07 15:45:56} Capturing stopped
{2015/11/07 15:45:56} Add /var/www/html/media/vi_0776_20151107_154550.mp4 to Box Queue at pos 21
{2015/11/07 15:45:56} Start boxing /var/www/html/media/vi_0776_20151107_154550.mp4.h264 to /var/www/html/media/vi_0776_20151107_154550.mp4 Queue pos 21
{2015/11/07 15:45:57} Finished boxing /var/www/html/media/vi_0776_20151107_154550.mp4 from Box Queue at pos 21
{2015/11/07 15:45:59} send smd 1
[2015/11/07 15:45:59] Start capture requested from Pipe
[2015/11/07 15:45:59] Send ca 1
{2015/11/07 15:45:59} Capturing started
{2015/11/07 15:46:05} send smd 0
[2015/11/07 15:46:05] Stop capture requested
[2015/11/07 15:46:05] Send ca 0
{2015/11/07 15:46:05} Capturing stopped
{2015/11/07 15:46:05} Add /var/www/html/media/vi_0777_20151107_154559.mp4 to Box Queue at pos 22
{2015/11/07 15:46:06} Start boxing /var/www/html/media/vi_0777_20151107_154559.mp4.h264 to /var/www/html/media/vi_0777_20151107_154559.mp4 Queue pos 22
{2015/11/07 15:46:08} Finished boxing /var/www/html/media/vi_0777_20151107_154559.mp4 from Box Queue at pos 22
{2015/11/07 15:46:09} send smd 1
[2015/11/07 15:46:09] Start capture requested from Pipe
[2015/11/07 15:46:09] Send ca 1
{2015/11/07 15:46:09} Capturing started
{2015/11/07 15:46:14} send smd 0
[2015/11/07 15:46:14] Stop capture requested
[2015/11/07 15:46:14] Send ca 0
{2015/11/07 15:46:15} Capturing stopped
{2015/11/07 15:46:15} Add /var/www/html/media/vi_0778_20151107_154609.mp4 to Box Queue at pos 23
{2015/11/07 15:46:15} Start boxing /var/www/html/media/vi_0778_20151107_154609.mp4.h264 to /var/www/html/media/vi_0778_20151107_154609.mp4 Queue pos 23
{2015/11/07 15:46:16} Finished boxing /var/www/html/media/vi_0778_20151107_154609.mp4 from Box Queue at pos 23
{2015/11/07 15:46:19} send smd 1
[2015/11/07 15:46:19] Start capture requested from Pipe
[2015/11/07 15:46:19] Send ca 1
{2015/11/07 15:46:19} Capturing started
{2015/11/07 15:46:28} send smd 0
[2015/11/07 15:46:28] Stop capture requested
[2015/11/07 15:46:28] Send ca 0
{2015/11/07 15:46:28} Capturing stopped
{2015/11/07 15:46:28} Add /var/www/html/media/vi_0779_20151107_154619.mp4 to Box Queue at pos 24
{2015/11/07 15:46:29} Start boxing /var/www/html/media/vi_0779_20151107_154619.mp4.h264 to /var/www/html/media/vi_0779_20151107_154619.mp4 Queue pos 24
{2015/11/07 15:46:31} Finished boxing /var/www/html/media/vi_0779_20151107_154619.mp4 from Box Queue at pos 24
{2015/11/07 15:46:34} send smd 1
[2015/11/07 15:46:34] Start capture requested from Pipe
[2015/11/07 15:46:34] Send ca 1
{2015/11/07 15:46:34} Capturing started
{2015/11/07 15:46:38} send smd 0
[2015/11/07 15:46:38] Stop capture requested
[2015/11/07 15:46:38] Send ca 0
{2015/11/07 15:46:39} Capturing stopped
{2015/11/07 15:46:39} Add /var/www/html/media/vi_0780_20151107_154634.mp4 to Box Queue at pos 25
{2015/11/07 15:46:39} Start boxing /var/www/html/media/vi_0780_20151107_154634.mp4.h264 to /var/www/html/media/vi_0780_20151107_154634.mp4 Queue pos 25
{2015/11/07 15:46:40} send smd 1
{2015/11/07 15:46:40} Finished boxing /var/www/html/media/vi_0780_20151107_154634.mp4 from Box Queue at pos 25
[2015/11/07 15:46:41] Start capture requested from Pipe
[2015/11/07 15:46:41] Send ca 1
{2015/11/07 15:46:41} Capturing started
{2015/11/07 15:46:45} send smd 0
[2015/11/07 15:46:45] Stop capture requested
[2015/11/07 15:46:45] Send ca 0
{2015/11/07 15:46:45} Capturing stopped
{2015/11/07 15:46:45} Add /var/www/html/media/vi_0781_20151107_154641.mp4 to Box Queue at pos 26
{2015/11/07 15:46:45} send smd 1
{2015/11/07 15:46:46} Start boxing /var/www/html/media/vi_0781_20151107_154641.mp4.h264 to /var/www/html/media/vi_0781_20151107_154641.mp4 Queue pos 26
[2015/11/07 15:46:47] Start capture requested from Pipe
[2015/11/07 15:46:47] Send ca 1
{2015/11/07 15:46:47} Capturing started
{2015/11/07 15:46:47} Finished boxing /var/www/html/media/vi_0781_20151107_154641.mp4 from Box Queue at pos 26
{2015/11/07 15:46:51} send smd 0
[2015/11/07 15:46:51] Stop capture requested
[2015/11/07 15:46:51] Send ca 0
{2015/11/07 15:46:51} Error: Could not send buffers to port, h264 callback
{2015/11/07 15:46:51} Executing macro /var/www/html/macros/error_hard.sh "Could not send buffers to port, h264 callback"
[2015/11/07 15:52:27] Scheduled management tasks. Next at<PHONE_NUMBER>
[2015/11/07 16:12:28] Scheduled management tasks. Next at<PHONE_NUMBER>
[2015/11/07 16:32:37] Scheduled management tasks. Next at<PHONE_NUMBER>
[2015/11/07 16:32:41] Purged 49 Files
[2015/11/07 16:52:31] Scheduled management tasks. Next at<PHONE_NUMBER>
{2015/11/07 16:56:27} RaspiMJPEG Version 5.2.11
{2015/11/07 16:56:28} recommended video buffers 1
{2015/11/07 16:56:28} h264 buffers set to recommended 1
{2015/11/07 16:56:28} Set up internal detect width=121 height=68
{2015/11/07 16:56:28} MJPEG streaming, ready to receive commands
{2015/11/07 16:56:28} send smd 9
[2015/11/07 16:56:29] RaspiCam support started
[2015/11/07 16:56:29] Capture Pipe already exists /var/www/html/FIFO1
[2015/11/07 16:56:29] Scheduler loop is started
[2015/11/07 16:56:29] Reload parameters command requested
[2015/11/07 16:56:29] Scheduler loop is started
[2015/11/07 16:56:41] New period detected 0
[2015/11/07 16:56:41] Scheduled management tasks. Next at<PHONE_NUMBER>
{2015/11/07 16:56:41} Internal motion detection started
{2015/11/07 16:56:41} recommended video buffers 1
{2015/11/07 16:56:41} h264 buffers set to recommended 1
{2015/11/07 16:56:41} send smd 1
[2015/11/07 16:56:41] Start capture requested from Pipe
[2015/11/07 16:56:41] Send ca 1
{2015/11/07 16:56:41} Set up internal detect width=121 height=68
{2015/11/07 16:56:41} send smd 1
{2015/11/07 16:56:41} Capturing started
[2015/11/07 16:56:43] Start capture requested from Pipe
[2015/11/07 16:56:43] Send ca 1
{2015/11/07 16:56:43} Already capturing. Ignore
[2015/11/07 17:16:42] Scheduled management tasks. Next at<PHONE_NUMBER>
{2015/11/07 17:31:19} send smd 0
[2015/11/07 17:31:19] Stop capture requested
[2015/11/07 17:31:19] Send ca 0
{2015/11/07 17:31:19} Capturing stopped
{2015/11/07 17:31:19} Add /var/www/html/media/vi_0783_20151107_165641.mp4 to Box Queue at pos 0
{2015/11/07 17:31:20} Start boxing /var/www/html/media/vi_0783_20151107_165641.mp4.h264 to /var/www/html/media/vi_0783_20151107_165641.mp4 Queue pos 0
{2015/11/07 17:31:57} send smd 1
[2015/11/07 17:31:57] Start capture requested from Pipe
[2015/11/07 17:31:57] Send ca 1
{2015/11/07 17:31:57} Capturing started
{2015/11/07 17:32:00} send smd 0
[2015/11/07 17:32:01] Stop capture requested
[2015/11/07 17:32:01] Send ca 0
{2015/11/07 17:32:01} Capturing stopped
{2015/11/07 17:32:01} Add /var/www/html/media/vi_0784_20151107_173157.mp4 to Box Queue at pos 1
{2015/11/07 17:32:02} send smd 1
[2015/11/07 17:32:03] Start capture requested from Pipe
[2015/11/07 17:32:03] Send ca 1
{2015/11/07 17:32:03} Capturing started
{2015/11/07 17:32:20} send smd 0
[2015/11/07 17:32:20] Stop capture requested
[2015/11/07 17:32:20] Send ca 0
{2015/11/07 17:32:20} Capturing stopped
{2015/11/07 17:32:23} Add /var/www/html/media/vi_0785_20151107_173203.mp4 to Box Queue at pos 2
{2015/11/07 17:33:09} send smd 1
[2015/11/07 17:33:09] Start capture requested from Pipe
[2015/11/07 17:33:09] Send ca 1
{2015/11/07 17:33:17} Capturing started
{2015/11/07 17:33:21} send smd 0
[2015/11/07 17:33:21] Stop capture requested
[2015/11/07 17:33:21] Send ca 0
{2015/11/07 17:33:21} Capturing stopped
{2015/11/07 17:33:21} Add /var/www/html/media/vi_0786_20151107_173309.mp4 to Box Queue at pos 3
{2015/11/07 17:33:54} send smd 1
[2015/11/07 17:33:54] Start capture requested from Pipe
[2015/11/07 17:33:54] Send ca 1
{2015/11/07 17:33:54} Capturing started
{2015/11/07 17:33:57} send smd 0
[2015/11/07 17:33:57] Stop capture requested
[2015/11/07 17:33:57] Send ca 0
{2015/11/07 17:33:57} Capturing stopped
{2015/11/07 17:33:57} Add /var/www/html/media/vi_0787_20151107_173354.mp4 to Box Queue at pos 4
{2015/11/07 17:36:21} send smd 1
[2015/11/07 17:36:27] Start capture requested from Pipe
[2015/11/07 17:36:27] Send ca 1
{2015/11/07 17:36:28} Capturing started
{2015/11/07 17:36:32} send smd 0
[2015/11/07 17:36:32] Stop capture requested
[2015/11/07 17:36:32] Send ca 0
{2015/11/07 17:36:32} Capturing stopped
{2015/11/07 17:36:32} Add /var/www/html/media/vi_0788_20151107_173628.mp4 to Box Queue at pos 5
{2015/11/07 17:36:40} send smd 1
[2015/11/07 17:36:40] Start capture requested from Pipe
[2015/11/07 17:36:40] Send ca 1
{2015/11/07 17:36:42} Capturing started
[2015/11/07 17:36:43] Scheduled management tasks. Next at<PHONE_NUMBER>
{2015/11/07 17:36:46} send smd 0
[2015/11/07 17:36:46] Stop capture requested
[2015/11/07 17:36:46] Send ca 0
{2015/11/07 17:36:46} Capturing stopped
{2015/11/07 17:36:46} Add /var/www/html/media/vi_0789_20151107_173640.mp4 to Box Queue at pos 6
{2015/11/07 17:36:48} send smd 1
[2015/11/07 17:36:48] Start capture requested from Pipe
[2015/11/07 17:36:48] Send ca 1
{2015/11/07 17:36:49} Capturing started
{2015/11/07 17:36:59} send smd 0
[2015/11/07 17:36:59] Stop capture requested
[2015/11/07 17:36:59] Send ca 0
{2015/11/07 17:36:59} Capturing stopped
{2015/11/07 17:36:59} Add /var/www/html/media/vi_0790_20151107_173648.mp4 to Box Queue at pos 7
{2015/11/07 17:37:07} send smd 1
[2015/11/07 17:37:07] Start capture requested from Pipe
[2015/11/07 17:37:07] Send ca 1
{2015/11/07 17:37:07} Capturing started
{2015/11/07 17:37:10} send smd 0
[2015/11/07 17:37:10] Stop capture requested
[2015/11/07 17:37:10] Send ca 0
{2015/11/07 17:37:12} Capturing stopped
{2015/11/07 17:37:12} Add /var/www/html/media/vi_0791_20151107_173707.mp4 to Box Queue at pos 8
{2015/11/07 17:39:15} send smd 1
[2015/11/07 17:39:15] Start capture requested from Pipe
[2015/11/07 17:39:15] Send ca 1
{2015/11/07 17:39:15} Capturing started
{2015/11/07 17:39:19} send smd 0
[2015/11/07 17:39:19] Stop capture requested
[2015/11/07 17:39:19] Send ca 0
{2015/11/07 17:39:19} Capturing stopped
{2015/11/07 17:39:19} Add /var/www/html/media/vi_0792_20151107_173915.mp4 to Box Queue at pos 9
{2015/11/07 17:39:21} send smd 1
[2015/11/07 17:39:21] Start capture requested from Pipe
[2015/11/07 17:39:21] Send ca 1
{2015/11/07 17:39:21} Capturing started
{2015/11/07 17:39:28} send smd 0
[2015/11/07 17:39:28] Stop capture requested
[2015/11/07 17:39:28] Send ca 0
{2015/11/07 17:39:28} Capturing stopped
{2015/11/07 17:39:28} Add /var/www/html/media/vi_0793_20151107_173921.mp4 to Box Queue at pos 10
{2015/11/07 17:39:32} send smd 1
[2015/11/07 17:39:32] Start capture requested from Pipe
[2015/11/07 17:39:32] Send ca 1
{2015/11/07 17:39:35} Capturing started
{2015/11/07 17:39:40} send smd 0
[2015/11/07 17:39:40] Stop capture requested
[2015/11/07 17:39:40] Send ca 0
{2015/11/07 17:39:40} Capturing stopped
{2015/11/07 17:39:40} Add /var/www/html/media/vi_0794_20151107_173932.mp4 to Box Queue at pos 11
{2015/11/07 17:40:52} send smd 1
[2015/11/07 17:40:52] Start capture requested from Pipe
[2015/11/07 17:40:52] Send ca 1
{2015/11/07 17:40:52} Capturing started
{2015/11/07 17:41:00} send smd 0
[2015/11/07 17:41:00] Stop capture requested
[2015/11/07 17:41:01] Send ca 0
{2015/11/07 17:41:01} Capturing stopped
{2015/11/07 17:41:01} Add /var/www/html/media/vi_0795_20151107_174052.mp4 to Box Queue at pos 12
{2015/11/07 17:41:16} send smd 1
[2015/11/07 17:41:16] Start capture requested from Pipe
[2015/11/07 17:41:16] Send ca 1
{2015/11/07 17:41:16} Capturing started
{2015/11/07 17:43:15} Watchdog detected problem. Stopping{2015/11/07 17:43:15} SIGINT/SIGTERM received, stopping
{2015/11/07 17:43:22} RaspiMJPEG Version 5.2.11
{2015/11/07 17:43:22} recommended video buffers 1
{2015/11/07 17:43:22} h264 buffers set to recommended 1
{2015/11/07 17:43:22} Set up internal detect width=121 height=68
{2015/11/07 17:43:22} MJPEG streaming, ready to receive commands
{2015/11/07 17:43:22} send smd 9
[2015/11/07 17:43:22] Reload parameters command requested
[2015/11/07 17:43:33] Scheduler loop is started
[2015/11/07 17:43:34] Scheduled management tasks. Next at<PHONE_NUMBER>
[2015/11/07 18:03:35] Scheduled management tasks. Next at<PHONE_NUMBER>
[2015/11/07 18:23:36] Scheduled management tasks. Next at<PHONE_NUMBER>
[2015/11/07 18:43:37] Scheduled management tasks. Next at<PHONE_NUMBER>
[2015/11/07 19:03:38] Scheduled management tasks. Next at<PHONE_NUMBER>
{2015/11/07 19:18:23} Internal motion detection started
{2015/11/07 19:18:23} recommended video buffers 1
{2015/11/07 19:18:23} h264 buffers set to recommended 1
{2015/11/07 19:18:23} send smd 1
[2015/11/07 19:18:23] Start capture requested from Pipe
[2015/11/07 19:18:23] Send ca 1
{2015/11/07 19:18:23} Set up internal detect width=121 height=68
{2015/11/07 19:18:23} Capturing started
{2015/11/07 19:18:24} send smd 1
[2015/11/07 19:18:25] Start capture requested from Pipe
[2015/11/07 19:18:25] Send ca 1
{2015/11/07 19:18:25} Already capturing. Ignore
[2015/11/07 19:23:39] Scheduled management tasks. Next at<PHONE_NUMBER>
[2015/11/07 19:43:40] Scheduled management tasks. Next at<PHONE_NUMBER>
{2015/11/07 19:44:37} send smd 0
[2015/11/07 19:44:37] Stop capture requested
[2015/11/07 19:44:37] Send ca 0
{2015/11/07 19:44:37} Capturing stopped
{2015/11/07 19:44:37} Add /var/www/html/media/vi_0797_20151107_191823.mp4 to Box Queue at pos 0
{2015/11/07 19:44:38} Start boxing /var/www/html/media/vi_0797_20151107_191823.mp4.h264 to /var/www/html/media/vi_0797_20151107_191823.mp4 Queue pos 0
{2015/11/07 19:44:42} send smd 1
[2015/11/07 19:44:42] Start capture requested from Pipe
[2015/11/07 19:44:42] Send ca 1
{2015/11/07 19:44:42} Capturing started
{2015/11/07 19:45:13} send smd 0
[2015/11/07 19:45:13] Stop capture requested
[2015/11/07 19:45:13] Send ca 0
{2015/11/07 19:45:13} Capturing stopped
{2015/11/07 19:45:13} Add /var/www/html/media/vi_0798_20151107_194442.mp4 to Box Queue at pos 1
{2015/11/07 19:45:15} send smd 1
[2015/11/07 19:45:15] Start capture requested from Pipe
[2015/11/07 19:45:15] Send ca 1
{2015/11/07 19:45:15} Capturing started
{2015/11/07 19:45:25} send smd 0
[2015/11/07 19:45:26] Stop capture requested
[2015/11/07 19:45:26] Send ca 0
{2015/11/07 19:45:26} Capturing stopped
{2015/11/07 19:45:26} Add /var/www/html/media/vi_0799_20151107_194515.mp4 to Box Queue at pos 2
{2015/11/07 19:45:32} send smd 1
[2015/11/07 19:45:33] Start capture requested from Pipe
[2015/11/07 19:45:33] Send ca 1
{2015/11/07 19:45:36} Capturing started
{2015/11/07 19:45:47} send smd 0
[2015/11/07 19:45:47] Stop capture requested
[2015/11/07 19:45:47] Send ca 0
{2015/11/07 19:45:47} Capturing stopped
{2015/11/07 19:45:54} Add /var/www/html/media/vi_0800_20151107_194533.mp4 to Box Queue at pos 3
{2015/11/07 19:45:49} send smd 1
[2015/11/07 19:45:54] Start capture requested from Pipe
[2015/11/07 19:45:54] Send ca 1
{2015/11/07 19:45:55} Capturing started
{2015/11/07 19:46:00} send smd 0
[2015/11/07 19:46:00] Stop capture requested
[2015/11/07 19:46:00] Send ca 0
{2015/11/07 19:46:00} Capturing stopped
{2015/11/07 19:46:00} Add /var/www/html/media/vi_0801_20151107_194555.mp4 to Box Queue at pos 4
{2015/11/07 19:46:08} send smd 1
[2015/11/07 19:46:14] Start capture requested from Pipe
[2015/11/07 19:46:14] Send ca 1
{2015/11/07 19:46:14} Capturing started
{2015/11/07 19:46:18} send smd 0
[2015/11/07 19:46:18] Stop capture requested
[2015/11/07 19:46:18] Send ca 0
{2015/11/07 19:46:19} Capturing stopped
{2015/11/07 19:46:19} Add /var/www/html/media/vi_0802_20151107_194614.mp4 to Box Queue at pos 5
{2015/11/07 19:46:20} send smd 1
[2015/11/07 19:46:22] Start capture requested from Pipe
[2015/11/07 19:46:22] Send ca 1
{2015/11/07 19:46:22} Capturing started
{2015/11/07 19:46:33} send smd 0
[2015/11/07 19:46:33] Stop capture requested
[2015/11/07 19:46:33] Send ca 0
{2015/11/07 19:46:33} Capturing stopped
{2015/11/07 19:46:33} Add /var/www/html/media/vi_0803_20151107_194622.mp4 to Box Queue at pos 6
{2015/11/07 19:46:46} send smd 1
[2015/11/07 19:46:46] Start capture requested from Pipe
[2015/11/07 19:46:46] Send ca 1
{2015/11/07 19:46:46} Capturing started
{2015/11/07 19:46:49} send smd 0
[2015/11/07 19:46:49] Stop capture requested
[2015/11/07 19:46:49] Send ca 0
{2015/11/07 19:46:50} Capturing stopped
{2015/11/07 19:46:50} Add /var/www/html/media/vi_0804_20151107_194646.mp4 to Box Queue at pos 7
{2015/11/07 19:48:23} send smd 1
[2015/11/07 19:48:24] Start capture requested from Pipe
[2015/11/07 19:48:24] Send ca 1
{2015/11/07 19:48:32} Capturing started
{2015/11/07 19:48:39} send smd 0
[2015/11/07 19:48:39] Stop capture requested
[2015/11/07 19:48:39] Send ca 0
{2015/11/07 19:48:39} Capturing stopped
{2015/11/07 19:48:39} Add /var/www/html/media/vi_0805_20151107_194824.mp4 to Box Queue at pos 8
{2015/11/07 19:48:40} send smd 1
[2015/11/07 19:48:41] Start capture requested from Pipe
[2015/11/07 19:48:41] Send ca 1
{2015/11/07 19:48:43} Capturing started
{2015/11/07 19:48:58} send smd 0
[2015/11/07 19:48:58] Stop capture requested
[2015/11/07 19:48:58] Send ca 0
{2015/11/07 19:48:58} Capturing stopped
{2015/11/07 19:48:58} Add /var/www/html/media/vi_0806_20151107_194841.mp4 to Box Queue at pos 9
{2015/11/07 19:48:59} send smd 1
[2015/11/07 19:49:00] Start capture requested from Pipe
[2015/11/07 19:49:00] Send ca 1
{2015/11/07 19:49:02} Capturing started
{2015/11/07 19:49:09} send smd 0
[2015/11/07 19:49:09] Stop capture requested
[2015/11/07 19:49:09] Send ca 0
{2015/11/07 19:49:09} Capturing stopped
{2015/11/07 19:49:09} Add /var/www/html/media/vi_0807_20151107_194900.mp4 to Box Queue at pos 10
{2015/11/07 19:49:15} send smd 1
[2015/11/07 19:49:15] Start capture requested from Pipe
[2015/11/07 19:49:15] Send ca 1
{2015/11/07 19:49:15} Capturing started
{2015/11/07 19:49:19} send smd 0
[2015/11/07 19:49:19] Stop capture requested
[2015/11/07 19:49:19] Send ca 0
{2015/11/07 19:49:19} Capturing stopped
{2015/11/07 19:49:19} Add /var/www/html/media/vi_0808_20151107_194915.mp4 to Box Queue at pos 11
{2015/11/07 19:49:29} send smd 1
[2015/11/07 19:49:30] Start capture requested from Pipe
[2015/11/07 19:49:30] Send ca 1
{2015/11/07 19:49:30} Capturing started
{2015/11/07 19:49:34} send smd 0
[2015/11/07 19:49:34] Stop capture requested
[2015/11/07 19:49:34] Send ca 0
{2015/11/07 19:49:34} Capturing stopped
{2015/11/07 19:49:34} Add /var/www/html/media/vi_0809_20151107_194930.mp4 to Box Queue at pos 12
{2015/11/07 19:49:52} send smd 1
[2015/11/07 19:49:52] Start capture requested from Pipe
[2015/11/07 19:49:52] Send ca 1
{2015/11/07 19:49:52} Capturing started
{2015/11/07 19:50:02} send smd 0
[2015/11/07 19:50:02] Stop capture requested
[2015/11/07 19:50:02] Send ca 0
{2015/11/07 19:50:02} Capturing stopped
{2015/11/07 19:50:02} Add /var/www/html/media/vi_0810_20151107_194952.mp4 to Box Queue at pos 13
{2015/11/07 19:50:03} send smd 1
[2015/11/07 19:50:04] Start capture requested from Pipe
[2015/11/07 19:50:04] Send ca 1
{2015/11/07 19:50:04} Capturing started
{2015/11/07 19:50:13} send smd 0
[2015/11/07 19:50:13] Stop capture requested
[2015/11/07 19:50:13] Send ca 0
{2015/11/07 19:50:13} Capturing stopped
{2015/11/07 19:50:13} Add /var/www/html/media/vi_0811_20151107_195004.mp4 to Box Queue at pos 14
{2015/11/07 19:50:17} send smd 1
[2015/11/07 19:50:17] Start capture requested from Pipe
[2015/11/07 19:50:17] Send ca 1
{2015/11/07 19:50:18} Capturing started
{2015/11/07 19:50:21} send smd 0
[2015/11/07 19:50:21] Stop capture requested
[2015/11/07 19:50:21] Send ca 0
{2015/11/07 19:50:21} Capturing stopped
{2015/11/07 19:50:21} Add /var/www/html/media/vi_0812_20151107_195017.mp4 to Box Queue at pos 15
{2015/11/07 19:50:25} send smd 1
[2015/11/07 19:50:27] Start capture requested from Pipe
[2015/11/07 19:50:27] Send ca 1
{2015/11/07 19:50:27} Capturing started
{2015/11/07 19:50:30} send smd 0
[2015/11/07 19:50:30] Stop capture requested
[2015/11/07 19:50:30] Send ca 0
{2015/11/07 19:50:31} Capturing stopped
{2015/11/07 19:50:31} Add /var/www/html/media/vi_0813_20151107_195027.mp4 to Box Queue at pos 16
{2015/11/07 19:50:51} send smd 1
[2015/11/07 19:50:51] Start capture requested from Pipe
[2015/11/07 19:50:51] Send ca 1
{2015/11/07 19:50:56} Capturing started
{2015/11/07 19:51:04} send smd 0
[2015/11/07 19:51:04] Stop capture requested
[2015/11/07 19:51:04] Send ca 0
{2015/11/07 19:51:04} Capturing stopped
{2015/11/07 19:51:04} Add /var/www/html/media/vi_0814_20151107_195051.mp4 to Box Queue at pos 17
{2015/11/07 19:51:05} send smd 1
[2015/11/07 19:51:06] Start capture requested from Pipe
[2015/11/07 19:51:06] Send ca 1
{2015/11/07 19:51:07} Capturing started
{2015/11/07 19:51:11} send smd 0
[2015/11/07 19:51:11] Stop capture requested
[2015/11/07 19:51:11] Send ca 0
{2015/11/07 19:51:11} Capturing stopped
{2015/11/07 19:51:11} Add /var/www/html/media/vi_0815_20151107_195106.mp4 to Box Queue at pos 18
{2015/11/07 19:51:14} send smd 1
[2015/11/07 19:51:21] Start capture requested from Pipe
[2015/11/07 19:51:21] Send ca 1
{2015/11/07 19:51:21} Error: Could not send buffers to port, h264 callback
{2015/11/07 19:51:21} Executing macro /var/www/html/macros/error_hard.sh "Could not send buffers to port, h264 callback"


GSE114727 Single-Cell Map of Diverse Immune Phenotypes in the Breast Tumor Microenvironment

Project short name:
GSE114727_BreastTumorMicroenvironment
Primary Wrangler:
Ray
Secondary Wrangler:
Enrique

Associated files

Google Drive: https://drive.google.com/drive/folders/1WJ4dHUWMOXfskU4HU47UZwHKehufAF-o

Published study links

Paper: Azizi E, Carr AJ, Plitas G, et al. Single-Cell Map of Diverse Immune Phenotypes in the Breast Tumor Microenvironment. Cell. 2018 Aug;174(5):1293-1308.e36. DOI: 10.1016/j.cell.2018.05.060
PMID: 29961579

Accessioned data: GSE114727:	This SuperSeries is composed of the SubSeries listed below.

GSE114724	Single-cell Map of Diverse Immune Phenotypes in the Breast Tumor Microenvironment - 5' RNA sequencing and TCR sequencing
GSE114725	Single-cell Map of Diverse Immune Phenotypes in the Breast Tumor Microenvironment 3' RNA Sequencing

Key Events

[x] Convert published metadata to HCA spreadsheet
[x] Manually curate dataset to meet HCA metadata standard
[x] Collect any matrix and cell-type annotation files
[x] Upload sheet to validate metadata
[x] Check linking using ingest graph validator
[x] Transfer raw files to ingest to validate data files
[x] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[x] Submit dataset to Production
[ ] Convert project data to SCEA format following the SCEA conversion SOP if appropriate

I have uploaded the metadata spreadsheet to the google drive folder of the project. It is ready for secondary review.
The project level metadata can be found in Ingest, not in the metadata spreadsheet.

@rays22 I have reviewed the dataset and overall LGTM! I just have a couple of comments for some specimens:
Specimen from organism

Changed some organs labelled with “immune organ” to “immune system” ontology
Changed organ part from blood specimens from “peripheral blood mononuclear cell” to “venous blood” (Feels more right as an organ part, and the collection protocol does not specify any enrichment on mononuclear cells, but happy to discuss about this)

I have uploaded a reviewed spreadsheet into the folder, same name but with a ES_review appended. Let me know if you need any help checking other things or you disagree with the changes I did!

Thank you @ESapenaVentura for the quick review. I will implement your suggestions and then export the project.

I have exported the project to the DCP and filled in the data import form.

This dataset is not eligible for SCEA because there are no available raw data files. Moving this to finished.


feat(trading): market page snags

Related issues 🔗
Closes #6316
Description ℹ

[x] increase row height
[x] fix sorting to use percentage / notional values
[x] adjust market state icons' background
[x] remove grid store
[x] adjust font size

Demo 📺

Technical 👨🔧
Details of technical implementation that reviewers may need to be aware of, if applicable.

@MadalinaRaicu Open interest is still cut off for 13inch mac 100% zoom:
I don't think this has been done:

I think the font of the "primary" info in the table (market code, price etc) could be bigger to distinguish it more from the "secondary" grey info

This also hasn't been done:

It seems like the spark line graph doesn't fill the entire height of the row? The chart starts from maybe a third of the way up? But then it goes to the very top?

i previously enabled autosize on all the tables but it also saves the column widths if you dragged them.
i think the open interest column width was saved previously on your computer so resetting console would make it work...but .now I have removed storing column preferences based on Matt's comment

the font was slightly larger on market names, i don't think it looks very well on numerical fields. i have pushed now a change to make it slightly larger.

the sparkline doesn't start from the third height of the row but from the middle and it is aligned with the 24h change  values. i sort of left the sparkline changes out of this PR


When clicking on the finish button, a player gets navigated to the intermediate leaderboard screen if not all of the rounds have been played yet and to the final leaderboard screen if all rounds have been played.

Also, these commits: https://github.com/sopra-fs24-group-20/sopra-fs24-group-20-client/commit/76e4e045d1174442e3b093833823b554ffe98640, https://github.com/sopra-fs24-group-20/sopra-fs24-group-20-client/commit/f303a7a7323d0cd7fb0b7d1b23007cb663e3d7f2, https://github.com/sopra-fs24-group-20/sopra-fs24-group-20-client/commit/d5794cbbab9d787f80c1b4275a9eb8e8d9b59776, https://github.com/sopra-fs24-group-20/sopra-fs24-group-20-client/commit/70bba81084d021f6920d0d399bef426a0ecde5a8, https://github.com/sopra-fs24-group-20/sopra-fs24-group-20-client/commit/6f91bdaf259147bb90c92019207a29334e6971e4


NOISSUE: better goroutines control

- What I did
- How I did it
- How to verify it
- Description for the changelog

Codecov Report

Merging #165 into master will decrease coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #165      +/-   ##
==========================================
- Coverage   72.80%   72.71%   -0.10%
==========================================
  Files          55       55
  Lines        3854     3852       -2
==========================================
- Hits         2806     2801       -5
- Misses        894      896       +2
- Partials      154      155       +1

Impacted Files
Coverage Δ

etl/controller/pulsemaintainer.go
86.06% <100.00%> (-2.65%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7755995...618d780. Read the comment docs.


Wrong variables type generated for array fields

Describe the bug

Wrong type generated
To Reproduce
Steps to reproduce the behavior:
https://codesandbox.io/s/misty-forest-h519g?file=/types.ts

My GraphQL schema:

type Query {
    search(queries: [String!]!): [User!]!
}

type User {
    id: ID!
    username: String!
    email: String!
}

My GraphQL operations:

query search($queries: [String!]!) {
    search(queries: $queries) {
        id
    }
}

My codegen.yml config file:

schema: schema.graphql
documents: document.graphql
generates:
  types.ts:
    plugins:
      - typescript
      - typescript-operations

outputs:
export type SearchQueryVariables = Exact<{
  queries: Array<Scalars['String']> | Scalars['String'];
}>;

Expected behavior

the queries field for SearchQueryVariables should be Array<Scalars['String']> instead of Array<Scalars['String']> | Scalars['String']
Environment:

OS:
@graphql-codegen/typescript: 1.20.0

@graphql-codegen/typescript-operations: 1.17.13

@graphql-codegen/cli: 1.20.0

NodeJS: v10.23.0

Additional context

Same here with the following deps:
    "@graphql-codegen/add": "2.0.2",
    "@graphql-codegen/cli": "1.20.0",
    "@graphql-codegen/fragment-matcher": "2.0.1",
    "@graphql-codegen/typescript": "1.20.0",
    "@graphql-codegen/typescript-compatibility": "2.0.1",
    "@graphql-codegen/typescript-operations": "1.17.13",

It seems that all Input types which have a list field are being typed as Array<T> | T rather than the correct Array<T>. Example diff:
export type AddCustomersToGroupMutationVariables = Exact<{
  groupId: Scalars['ID'];
-  customerIds: Array<Scalars['ID']>;
+  customerIds: Array<Scalars['ID']> | Scalars['ID'];
}>;

export type CreateFacetValuesMutationVariables = Exact<{
- input: Array<CreateFacetValueInput>;
+ input: Array<CreateFacetValueInput> | CreateFacetValueInput;
}>;

Same here with the following deps:
    "@graphql-codegen/add": "2.0.2",
    "@graphql-codegen/cli": "1.20.0",
    "@graphql-codegen/fragment-matcher": "2.0.1",
    "@graphql-codegen/typescript": "1.20.0",
    "@graphql-codegen/typescript-compatibility": "2.0.1",
    "@graphql-codegen/typescript-operations": "1.17.13",

It seems that all Input types which have a list field are being typed as Array<T> | T rather than the correct Array<T>. Example diff:
export type AddCustomersToGroupMutationVariables = Exact<{
  groupId: Scalars['ID'];
-  customerIds: Array<Scalars['ID']>;
+  customerIds: Array<Scalars['ID']> | Scalars['ID'];
}>;

export type CreateFacetValuesMutationVariables = Exact<{
- input: Array<CreateFacetValueInput>;
+ input: Array<CreateFacetValueInput> | CreateFacetValueInput;
}>;

This issue seems to imply the Array<T> | T is actually the valid spec
https://github.com/dotansimha/graphql-code-generator/issues/4888

This issue seems to imply the Array<T> | T is actually the valid spec
https://github.com/dotansimha/graphql-code-generator/issues/4888

This issue seems to imply the Array<T> | T is actually the valid spec
#4888

@jlismore Thanks for your comments.
Seems this is really a feature than a bug 🤣 . But I think may be providing an option like arrayCoercion to disable it before we update the whole code base to be compatible with this improvement would be better.

This issue seems to imply the Array<T> | T is actually the valid spec
#4888

@jlismore Thanks for your comments.
Seems this is really a feature than a bug 🤣 . But I think may be providing an option like arrayCoercion to disable it before we update the whole code base to be compatible with this improvement would be better.

For anyone interested, we use this type utility to work around this:
/**
 * Removes [input list coercion][1] from GraphQL query variable types.
 *
 * Example:
 *
 * ```ts
 * // Original codegen'd type:
 * type ProductsQueryVariables = {
 *   productId: string;
 *   filters?: Maybe<Array<FilterInput> | FilterInput>;
 *   ratings?: Maybe<Array<RatingInput> | RatingInput>;
 * }
 *
 * // Result of `RemoveListCoercion<ProductsQueryVariables>`:
 * type Result = {
 *   productId: string;
 *   filters?: Maybe<Array<FilterInput>>;
 *   ratings?: Maybe<Array<RatingInput>>;
 * }
 * ```
 *
 * [1]: https://spec.graphql.org/draft/#sel-FAHjBJFCAACE_Gh7d
 */
export type RemoveGraphqlInputListCoercion<T> = {
  // Source & explanation: https://stackoverflow.com/q/66105845/21728
  [K in keyof T]: T[K] extends Maybe<infer V>
    ? Extract<V, Array<any>>[number] extends infer R
      ? T[K] extends Maybe<Array<R> | R>
        ? Maybe<Array<R>>
        : T[K]
      : T[K]
    : T[K];
};

I think that graphql-codegen is doing the right thing when it now generates a union of T[] | T for query variable types but it was certainly quite challenging to solve this in our codebase. I don't know if an option like arrayCoercion should be added or not (suggested above) but it would probably make our life a bit easier 😄.

An option to disable this would be very useful. Basically this update broke our builds since we're using the generated input types for typing a form as well. Having Array<...> | ... defined there completely breaks this.

I agree that according to the GraphQL spec this is the way to go. Whether or not we agree with the spec is irrelevant here.
However, since the generated code was previously incorrect and now is correct, this should have been treated as a breaking change and documented accordinlgy.
Thankfully for us the migration wasn't too difficult but it very well could have been so I second the petition to add an option to disable this behaviour. In fact I think that the correct way forward is:

Release a patch version reverting to the old/incorrect behaviour.
Release a minor version adding an option to opt into (not out of) the correct behaviour.
Release a major version making the correct behaviour the default and deprecate the option.
Remove the option at some point in the future.

I agree that according to the GraphQL spec this is the way to go. Whether or not we agree with the spec is irrelevant here.
However, since the generated code was previously incorrect and now is correct, this should have been treated as a breaking change and documented accordinlgy.
Thankfully for us the migration wasn't too difficult but it very well could have been so I second the petition to add an option to disable this behaviour. In fact I think that the correct way forward is:

Release a patch version reverting to the old/incorrect behaviour.
Release a minor version adding an option to opt into (not out of) the correct behaviour.
Release a major version making the correct behaviour the default, deprecate the option, and document the breaking change.
Remove the option at some point in the future.

We do follow semver, and we treat releases very seriously. I think the community here knows that. All releases in this repo contain a very detailed list of changes and their source.
I guess our main conflict here is whether this was a breaking change or not. Our goal in the base plugins is to follow the GraphQL spec. We missed part of it, and that's a bug from my point of view. We might have need to communicate it better, but I don't think we should have released a major in this case.

If you had T before, and it was changed to T | T[], all previously written TS code should work just the same.

It was the other way around – it was T[] before and it became T[] | T. That broke some of our code consuming it.
Don't get me wrong, you're doing great job with releases, proper changelogs etc. – graphql-codegen is an awesome project! But this was a breaking change and the workflow suggested by @MeLlamoPablo sounds reasonable for a smoother rollout.

Got it, totally makes sense. Anyway - we'll definitely try to avoid these in the future!

In my view this is both a bug fix and a breaking change; those are not mutually exclusive.
I apologize for my tone though, I probably have come across as a bit of a dick :smile: I meant no disrespect whatsoever and I also appreciate a lot the work you're putting in this project.

I think there should be an option to disable this.

While it's obviously a change to adhere to the spec, it's still something that is not ideal for a lot of people. @dotansimha would you accept a PR adding an option to disable this? I would try to allocate some time for it in that case.


[How to migrate language studio project along with blob content from one environment (DEV/QA) to another(QA/PROD)]

Library name and version
azure.ai.textanalytics.5.2.0-beta.2
Query/Question
We have created a "Custom Named Entity Recognition ( Custom NER)" project in Language Studio. We are using the Text Analytics SDK version (azure.ai.textanalytics.5.2.0-beta.2). We are trying to migrate the language studio project from one environment(DEV/QA) to another(QA/PROD) along with its blob contents.
Is there any way available to migrate the projects from one environment (DEV/QA) to another(QA/PROD) along with its blob contents ?
Note : - we are using the below mentioned block of codes to analyze the text from the document.
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/textanalytics/Azure.AI.TextAnalytics/tests/samples//Sample9_RecognizeCustomEntitiesAsync.cs
Environment
We are hosting our application in Azure and using dot net 5 version to build our application along with Azure AI form recognizer 3.1.1 and Azure AI Text Analytics 5.2 beta 2.

Hi @bibhutimoharana.   Thank you for reaching out and we regret that you're experiencing difficulties.   Apologies, but I'm not sure that I understand your scenario.  When you say "migrate from one environment to another" - are you talking about exporting the project and then importing from another Azure subscription?
Can you talk a bit more about the details of what you'd like to do so that I can better understand?

Hi @bibhutimoharana. Thank you for reaching out and we regret that you're experiencing difficulties. Apologies, but I'm not sure that I understand your scenario. When you say "migrate from one environment to another" - are you talking about exporting the project and then importing from another Azure subscription?
Can you talk a bit more about the details of what you'd like to do so that I can better understand?

Hi jsquire,
Thanks for your quick response.
In our project we are using the Azure AI Text Analytics SDK to extract the SKU codes embeded in descriptions of the user's PO files.
Before this we are following these below mentioned steps.
Step 1-> Creating storage account for different environment.
Step 2->Creating container inside the storage account.
Step 3->uploading the text files having different SKU codes inside the container.
Step 4->Creating a language studio and pointing to the created container.
Step 5->Creating a new project inside the language studio.
Step 6->Mapping SKU codes present inside the text files within the container.
After these steps only our application will be able to recognize those mapped and similar type SKU codes.
While deploying our application in different environment (QA and PROD), we need to migrate those above mentioned (Step1-Step6) in QA and PROD. This migration should get automated so that there will not be any manual task.
Is there any way available that we can migrate those steps (Step1-Step6) in QA and PROD ?
Is there any way to do this migration using the Devops Pipeline Powershell script ?
Please guide us on this.

@jsquire, do we know whether the MSFT product teams has plans for GA to include either a export/import option or a "migrate" from one Text Analytics resource to another (as with Form Recognizer) option? This seems an obvious "must" for it to be productionalized.

@vhhughes - I do not have that insight, unfortunately.   I can only speak to the SDK.  As mentioned above, your best path to an answer to that would be opening a support request so that the folks best positioned to answer roadmap questions for Language Studio and the service can assist.


Bug 2060720: rbd: return unimplemented error for block-mode reclaimspace req

blkdiscard cmd discards all data on the block device which
is not desired. Hence, return unimplemented code if the
volume access mode is block.


GUI Microscope Settings - Load / Save Filetype mismatch

Similar to the issue we had with Protocol files. Load wants .json, Save wants .tsv.

fixed.


ci: add workflow to create oci artifact

Signed-off-by: Tyler Witlin<EMAIL_ADDRESS>
Description of the change
This PR add a workflow to create and push charts to GHCR as an OCI artifact.
Benefits
Flux users can now use this repository using the new OCI artifacts.
Possible drawbacks
N/A
Applicable issues

N/A
Additional information

Checklist

[x] Title of the PR conforms to the Conventional Commits standard.
[x] Scope of the of the PR title contains the chart name.
[ ] Chart version in Chart.yaml has been bumped according to Semantic Versioning.
[ ] Chart artifacthub.io/changes changelog annotation has been updated in Chart.yaml. See Artifact Hub documentation for more info.
[ ] Variables have been documented in the values.yaml file.

I'd also love to use this with flux, is there something that we can contribute with to get this merged?

I'd also love to use this with flux, is there something that we can contribute with to get this merged?

I think it just needs to be tested

TBH I didn't think many folks would want this... I'll see if I can get it implemented somewhere in the coming week 👍

This would be very useful, as it's easier to cache an OCI chart with Harbor's pull-through cache, than a standard helm chart :)

I've merged it as-is and will try and tweak in the development branch. Thanks for the PR @coolguy1771!

https://github.com/bjw-s/helm-charts/pkgs/container/app-template
app-template is being published to GHCR as an OCI artifact now :)


Multiplex override logic should live in back-end

The logic currently lives here, in the client.  This results in inconsistencies where the client reports (here, based on the remote config setting) that the tlsmasq connection is not mutliplexed.
Moving this to the back-end would (a) resolve such inconsistencies and (b) allow us to control this setting remotely.

This isn't technically tlsmasq-specific, but tlsmasq is the only protocol we currently use which does this.


glfw in ebiten on Win32 is not self contained

If I build a win32 (GOOS=windows, GOARCH=386) binary with ebiten, it does not run on a fresh Windows system as it complains that libgcc_s_dw2-1.dll is missing.
Note that with GOARCH=amd64, it works.
Suspecting that the glfwDLLCompressed for Win32 requires this extra DLL, while the Win64 one does not.
And indeed:
[rpolzer@co2 drive_c]$ objdump -x './users/rpolzer/Local Settings/Application Data/ebiten/757fe85fcdb46e92da9256bffb1c0838472821e069c26b743c07a801df38504c.dll'|grep 'DLL Name:'
	DLL Name: GDI32.dll
	DLL Name: KERNEL32.dll
	DLL Name: msvcrt.dll
	DLL Name: SHELL32.dll
	DLL Name: USER32.dll
	DLL Name: libgcc_s_dw2-1.dll
[rpolzer@co2 drive_c]$ objdump -x './users/rpolzer/Local Settings/Application Data/ebiten/de55a18e5ffe69870a244951d2aca066d891af7c89c321865c701e82b015c9f5.dll' | grep 'DLL Name:'
	DLL Name: GDI32.dll
	DLL Name: KERNEL32.dll
	DLL Name: msvcrt.dll
	DLL Name: SHELL32.dll
	DLL Name: USER32.dll

For some reason the 64bit version only requires things that come with Windows, while the 32bit version requires this additional DLL.
Can this be fixed? From what I read on the web, maybe all it takes is passing -static-libgcc when linking the DLL.

The only symbols imported from that DLL seem to be:
        49114      40  __divdi3
        49120     119  __udivdi3
        4912c     121  __umoddi3

Which commit have you tried? Probably the latest commit works.

#1758 might be related.

The latest commit should work since this doesn't depend on libgcc:
$ objdump -x e6422fe98c4089e2a7f8ddc41f94ecb156dfda774974326280946db1770543ba.dll | grep 'DLL'
    DLL Name: GDI32.dll
    DLL Name: KERNEL32.dll
    DLL Name: msvcrt.dll
    DLL Name: SHELL32.dll
    DLL Name: USER32.dll
 DLL name: glfw_windows_386.dll

Statical linking to libgcc might affect the license (the library part is under LGPL), so this might not be a good solution unfortunately.

The only symbols imported from that DLL seem to be:

Just out of curiosity, how did you list the symbols?

objdump -x e6422fe98c4089e2a7f8ddc41f94ecb156dfda774974326280946db1770543ba.dll shows the symbol names too close to the dll name.
And thanks for the recent changes! Can't switch to main yet as there's another issue, but I'll file that separately.

OK let me close this.


Document custom stream application guidelines

As a user, I'd like to refer to docs when developing custom source, processor, or sink applications, so I can develop by following the best practices.
Acceptance:

reference guide include guidelines for each application type
unit-testing section is included
troubleshooting techniques listed
sample applications available for reference

This could possibly evolve from this document.

We could borrow some fragments from Josh's blog: https://spring.io/blog/2016/04/05/1-stream-2-applications-and-3-dependencies-for-spring-cloud-data-flow.


before/after done callback support

Hi @PanayotCankov,
Thanks for the project, it really helps.
are done callback supported on before/after methods?
i tried:
@suite('some suite')
export class SomeTest {
  before(done) {
    // done is undefined here
  }
}

@interisti #6 adresses this, please check if it is ok for you. I am closing this issue.

@PanayotCankov  Perfect.
Thanks @Haringat


Push or replace route with query params

Can I use pushRoute or replaceRoute and specify query parameters via json object?

I've come across this issue too

You can specify query parameters by passing an object in pushRoute or replaceRouter
let params = {a: '1', b: '2', c: '3'}
Router.pushRoute('routeName', params)
In pushRoute the first paramter will be the name of the route defined in your router file

Hi @haotangio.
I think that this is the point

https://github.com/fridays/next-routes/blob/master/src/index.js#L172

Nested Objects needs to stringified by qs

@theshaune When route is resolved by URL, there's no params argument.
Authors answer on issue: https://github.com/fridays/next-routes/issues/75#issuecomment-314796343


Add covid reference notebook

This is a copy of the notebook from here https://github.com/NUPulmonary/scarches-covid-reference
just to put them in one place, as suggested by @M0hammadL
Please, do not merge yet, as I need to rerun it, because we changed the annotations on GEO.
This is the basic structure, with the 2 additional files with utility functions. Please let me know if the structure is ok, or if I need to modify anything.
Thank you

Hi Nik, thanks a lot. Unfirtatenly we have updated the whole repo with the new version. We now use PyTorch instead of Tensorflow. I guess you can rerun the whole analysis with scANVI mode. You can use create a reference atlas and then project and classify it without using any knn.

Hi Nik, thanks a lot. Unfirtatenly we have updated the whole repo with the new version. We now use PyTorch instead of Tensorflow. I guess you can rerun the whole analysis with scANVI mode. You can use create a reference atlas and then project and classify it without using any knn.

Hey. That's good news! Could you please tell me what changes practically for the package and for this pull request?
Do I get it right that this is the relevant notebook now? https://github.com/theislab/scarches/blob/master/notebooks/scanvi_surgery_pipeline.ipynb
I can adapt this covid notebook to that one, but it'll take some time. Please let me know what's the best next step?

Hey. That's good news! Could you please tell me what changes practically for the package and for this pull request?
Do I get it right that this is the relevant notebook now? https://github.com/theislab/scarches/blob/master/notebooks/scanvi_surgery_pipeline.ipynb
I can adapt this covid notebook to that one, but it'll take some time. Please let me know what's the best next step?

Yes, that is the writing notebook:
I would perform this analysis:
1- train scANVI reference model with  your reference data
2- treat your query data as unlabeled (see notebook)
3- transfer cell type labels from reference to query (you don't need any knn claassifier the model does it for you)

Yes, that is the writing notebook:
I would perform this analysis:
1- train scANVI reference model with  your reference data
2- treat your query data as unlabeled (see notebook)
3- transfer cell type labels from reference to query (you don't need any knn claassifier the model does it for you)

Hey. That's good news! Could you please tell me what changes practically for the package and for this pull request?

The package now uses PyTorch library instead of TensorFlow therefore you need to install the newest version first. Since the library and the implementations have changed you need to rerun your analysis using the new version.

Do I get it right that this is the relevant notebook now? https://github.com/theislab/scarches/blob/master/notebooks/scanvi_surgery_pipeline.ipynb

Yes, that is the right notebook:
I would perform this analysis:
1- train scANVI reference model with your reference data
2- treat your query data as unlabeled (see notebook)
3- transfer cell type labels from reference to query (you don't need any knn classifier the model does it for you)

I can adapt this covid notebook to that one, but it'll take some time. Please let me know what's the best next step?

If you manage to rerun the same analysis with the new version you can ask for another pull request.
Please let me know if you need any other help.
Mo

Hey. That's good news! Could you please tell me what changes practically for the package and for this pull request?

The package now uses PyTorch library instead of TensorFlow therefore you need to install the newest version first. Since the library and the implementations have changed you need to rerun your analysis using the new version.

Do I get it right that this is the relevant notebook now? https://github.com/theislab/scarches/blob/master/notebooks/scanvi_surgery_pipeline.ipynb

Yes, that is the right notebook:
I would perform this analysis:
1- train scANVI reference model with your reference data
2- treat your query data as unlabeled (see notebook)
3- transfer cell type labels from reference to query (you don't need any knn classifier the model does it for you)

I can adapt this covid notebook to that one, but it'll take some time. Please let me know what's the best next step?

If you manage to rerun the same analysis with the new version you can ask for another pull request.
Please let me know if you need any other help.
Mo

Thank you very much for the explanations. Ok, I'll close this for now and will open the new one when I have a new version

Thank you very much for the explanations. Ok, I'll close this for now and will open the new one when I have a new version


Update WebUntisRequestManager.java

Removed two / from DEFAULT_ENDPOINT and anonymousLogin that made the resulting URL end up with two / and result in an error

Nice Library btw, the only one for WebUntis in Java. Idk why it's not more popular

Thank you :)
That's why I made the lib but I could have written it better.
Unfortunately I don't have access to a WebUntis account anymore and can't really test it.
But I tried to recreate the error with another URL. I just put a second / inside the URL but everything worked just fine.
Can you show me the error?
It probably depends on the server URL whether you have two / or one.
WebUntisRequestManager.java:
26		final URL url = new URL(session.getServer() + getEndPoint(endPoint) + "?school=" + school);
So it would probably better to check in the getEndPoint() for a leading / and check that getServer() (or when setting the URL only once) returns a string with a trailing /.
I have also seen that the new URL(str) constructor is deprecated in Java 20. Would you mind to replace them with new URI(str).toURL();? Maybe this could fix the error. But I can do that too if I got them time.

So the error i got was this:
Server returned HTTP response code: 500 for URL: https://nessa.webuntis.com//WebUntis/jsonrpc_intern.do?school=school (removed school for privacy)
I actually didn't really look into why this was happening a few days ago but i had to remove two / because i am using anonymous login. So the first error happens because the anonymous logins EndPoint has a leading / and the second because all other requests are using DEFAULT_ENDPOINT which also has a leading /.
Using URI(str).toURL(); sadly didn't fix it.
Alright so i'll remove all leading / from all EndPoints i find and replace the URL constructor and then commit.
Also don't tell yourself your lib is bad :D, i mean it works (almost) perfectly while my stuff didn't D: and it's the only one in Java.

If you open the URL inside the browser you see the whole error message.
`Type Exception Report
Message The request was rejected because the URL contained a potentially malicious String "//"
Description The server encountered an unexpected condition that prevented it from fulfilling the request.
Exception
org.springframework.security.web.firewall.RequestRejectedException: The request was rejected because the URL contained a potentially malicious String "//"
org.springframework.security.web.firewall.StrictHttpFirewall.rejectedBlacklistedUrls(StrictHttpFirewall.java:369)
org.springframework.security.web.firewall.StrictHttpFirewall.getFirewalledRequest(StrictHttpFirewall.java:336)
org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:194)
org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:178)
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:354)
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:267)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51)
com.grupet.web.filter.Log4j2PropertiesPostFilter.doFilter(Log4j2PropertiesPostFilter.java:39)
com.grupet.web.core.SessionFilter.doFilter(SessionFilter.java:100)
com.grupet.web.filter.HttpMethodPreFilter.doFilter(HttpMethodPreFilter.java:46)
com.grupet.web.filter.Log4j2PropertiesPreFilter.doFilter(Log4j2PropertiesPreFilter.java:81)
org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:71)
Note The full stack trace of the root cause is available in the server logs.`
Thank you again ;)


Implemented StripControls for channel messages and notices

Implemented StripControls for channel messages and notices. Either network wide or for selected channels.
This Fixes #387

What about queries?

@DarthGandalf I'm unsure how the setting for queries should look like.. Reuse the network wide setting or a dedicated setting for (all) queries?

@DarthGandalf Added extra setting to strip controls from private messages network wide. A blacklist for nicks would be overkill imho.

Do we necessarily need a separate setting for channels and queries? Or could the same network level StripControls setting be used for both queries and as a default for channels, and then individual channels can override if desired.

Thats what i asked here: https://github.com/znc/znc/pull/850#issuecomment-73301956
I'm really unsure about it... I can imagine users which would like to allow colors in queries but disallow them in channels. In that case a separate setting comes in handy. On the other hand disabling stripcolors for all channels manually is still possible without a separate setting ...
I'm open for both ways, choose which one you prefer and i'll update the PR accordingly

There's always someone who thinks that this and that additional setting is useful for some corner case. Personally I'm in favor of keeping settings to the minimum. The less settings the better. :) Optimize for the convenience of the most common use. Controlpanel supports wildcards, so it's pretty easy to change the setting for all channels.

@jpnurmi Agreed. :) Done.

07.02.2015 21:20, J-P Nurmi пишет:

Personally I'm in favor of keeping settings to the minimum
+1

Also: Is this failing travis build (https://travis-ci.org/znc/znc/jobs/49888849) my fault?

I think it's OOM-killer. Modpython's source is already 4.3 MB of generated C++ code, and address sanitizer adds to it.
You're adding 6 more functions to be wrapped, and this is enough to go over the threshold.

The memory limit is 3gb of ram :\

Hi, sorry for the delay. I've been a bit busy with stuff. If you want to make the submission perfect, you could fix the coding style in IRCSock.cpp. ZNC uses a space after if, before the opening parenthesis. It's not entirely consistent across the code base, just me being pedantic. :) Furthermore, the body of the for-loop in CIRCNetwork::SetStripControls() has a double indentation.
That was just nitpick, but I have also one real finding; I believe we should also strip controls for both channel and private CTCP ACTIONs. Otherwise looks all good. :)

I'll fix the issues at weekend

@jpnurmi Everything should've been fixed now.

@jpnurmi Well, you are totally right. Pushed the wrong branch, sorry. Fixed it :>

Merged to master. Thanks! :)

Would this not be better suited as a module instead of bloating the core? I can't see that there would be a huge demand for this.

Good point, I didn't even think about it. :/ Oh well, we can still change it...

The module could be something as simple as https://github.com/jpnurmi/znc/commit/cdc4de9248db9013b3ded4b9821911c9990a5c1b. It could be loaded either on network or user level. The trade-off is that there wouldn't be control over individual channels. Would you guys see that as a big problem?

Settings of it could have list of channels...
Or, if #125 is fixed, channel could have a setting for this module without
having a setting in core.
2015-02-24 12:57 GMT-08:00 J-P Nurmi<EMAIL_ADDRESS>
The module could be something as simple as jpnurmi@cdc4de9
https://github.com/jpnurmi/znc/commit/cdc4de9248db9013b3ded4b9821911c9990a5c1b.
It could be loaded either on network or user level. The trade-off is that
there wouldn't be control over individual channels. Would you guys see that
as a big problem?
—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/pull/850#issuecomment-75844331.

The new settings system proposed in #125 sounds great. Did you just
volunteer? :)
On Wed, Feb 25, 2015, 07:23 Alexey Sokolov<EMAIL_ADDRESS>wrote:

Settings of it could have list of channels...
Or, if #125 is fixed, channel could have a setting for this module without
having a setting in core.
2015-02-24 12:57 GMT-08:00 J-P Nurmi<EMAIL_ADDRESS>
The module could be something as simple as jpnurmi@cdc4de9
<
https://github.com/jpnurmi/znc/commit/cdc4de9248db9013b3ded4b9821911c9990a5c1b
.
It could be loaded either on network or user level. The trade-off is that
there wouldn't be control over individual channels. Would you guys see
that
as a big problem?
—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/pull/850#issuecomment-75844331.

—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/pull/850#issuecomment-75911776.

I didn't volunteer, I don't have enough time.
But I'd prefer a module instead of a new setting in core regardless.

https://github.com/znc/znc/pull/917
On Wed, Mar 4, 2015, 08:44 Alexey Sokolov<EMAIL_ADDRESS>wrote:

I didn't volunteer, I don't have enough time.
But I'd prefer a module instead of a new setting in core regardless.
—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/pull/850#issuecomment-77110108.


Update MyDeque.java

Added more functions/methods using linked list to MyDeque

@Anuj-Kumar-Sharma merge it with the master branch. I've added almost functions of Deque : )

thanks bhaiya :-)
On Wed, Jun 24, 2020, 12:11 AM Anuj Kumar Sharma<EMAIL_ADDRESS>wrote:

Merged #26 https://github.com/Anuj-Kumar-Sharma/DS-Algo/pull/26 into
master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Anuj-Kumar-Sharma/DS-Algo/pull/26#event-3474306855,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APPKGOAOEH7UG5VJOTZBFPDRYDZPDANCNFSM4N3EQTHQ
.


rocksdb_6_23, rocksdb_7_10: fix build on newer compilers

Description of changes
There is a code that triggers "unused-but-set-variable" warning (in versions 7.x and 6.x) which is promoted to error.
There is another code that triggers "deprecated-copy" warning (in versions 6.x).
This change prevents this promotion, so older versions of rocksdb build successfully again.
I also had to check the rec to finalAttrs, otherwise the comparison for versionOlder was not using the overriden version, but the original one.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

@GrahamcOfBorg build rocksdb rocksdb_6_23 rocksdb_7_10


Mappm segmentation faults

mappm has been crashing with segmentation faults on some synthetic data tests as part of #313.
I can work on a MCVE, but I suspect it occurs if delp is negative.

Might be fairly easy to fix by wrapping mappm with a check for negative delp and/or nans.

I was not able to reproduce this with nans, negative pressures, nor non-monotonic pressures. Any ideas?

Started working on this and adding tests in this PR.

Closed as not reproducible.


hash(SomeEnum.SOME_VALUE) reports unhashable

I can hash Java enum values in 0.7.1 but not in 0.7.2 or tip of master (24e716e).
0.7.1 Output
$ python -c "import jpype; jpype.startJVM(convertStrings=False); print(hash(jpype.java.util.Formatter.BigDecimalLayoutForm.DECIMAL_FLOAT))"
1175962212

0.7.2 Output
$ python -c "import jpype; jpype.startJVM(convertStrings=False); print(hash(jpype.java.util.Formatter.BigDecimalLayoutForm.DECIMAL_FLOAT))"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: unhashable type: 'java.util.Formatter.BigDecimalLayoutForm'

Thank you for the bug report.  Seems like a glitch in the Python type system.  Checking the __mro__ we see the following.
q=java.util.Formatter.BigDecimalLayoutForm.DECIMAL_FLOAT
for i in type(q).__mro__:
    print(i, i.__hash__)

Somehow we have None get into the table as __hash__
<java class 'java.util.Formatter.BigDecimalLayoutForm'> None
<java class 'java.lang.Enum'> None
<java class 'java.lang.Comparable'> None
<java class 'java.io.Serializable'> <slot wrapper '__hash__' of '_jpype._JObject' objects>
<java class 'java.lang.Object'> <slot wrapper '__hash__' of '_jpype._JObject' objects>
<java class '_jpype._JObject'> <slot wrapper '__hash__' of '_jpype._JObject' objects>
<class 'object'> <slot wrapper '__hash__' of 'object' objects>

It appears that the customizer that applies equals is somehow removing hash.  Likely some magic behavior of Python.  I am sure there is some documentation that __eq__ and __hash__ work together, but it is odd that it would cover up the base version with None.  Googling around gives us
https://help.semmle.com/wiki/display/PYTHON/Inconsistent+equality+and+hashing

In Python 3, if you define a class-level equality method and omit a hash method then the class is automatically marked as unhashable.

Seems like a pretty dangerous behavior.... oh well.
Here is the work around...
# Add this anywhere before the jvm is started (or before the first use of the type)
@jpype.JImplementationFor('java.lang.Comparable')
class _JComparableHash(object):
    def __hash__(self):
        return self.hashCode()

# Then it will work.
print(hash(java.util.Formatter.BigDecimalLayoutForm.DECIMAL_FLOAT))

I will add a test to testbench for this case and verify that it is fixed in the next release.


feat(mocktail): Generic Fallbacks

Status
READY
Breaking Changes
NO
Description

The general idea is to use List<Never>, Map<Never, Never> and Set<Never> as a fallback for any list/map/set.
This patch adds fallback values as a List, where the first value that is the type we want will be chosen from as the fallback. I still left the original mechanism in and added matchExactType parameter to the registerFallbackValue function to distinguish between the mechanisms. Thoughts? Not sure if this API is the best.
Type of Change

[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

I now also added a fallback for callbacks. The type signature of the fallback looks like this:

Do you think it is useful to keep the distinction of matchExactType? I can't think of a situation where one would want to have more granular control of which fallback value is used exactly. Should I completely remove _fallbackValues?

Do you think it is useful to keep the distinction of matchExactType? I can't think of a situation where one would want to have more granular control of which fallback value is used exactly. Should I completely remove _fallbackValues?

Yeah I don’t think we need it either 👍

Done!


Remove Events class in src/lobby/Home.js

Remove Events class in src/lobby/Home.js whose getTargetPoint is duplicated with src/utils/Events.js.
The getTargetPoint function in Events of Home.js is exactly the same with that in src/utils/Events.js.

/cc @chrisgarrity @thisandagain


Show notifications for failed backend project submission

Currently when a backend project submission fails, the users are only notified by a brief warning message saying that the server is not being updated and the user is navigated to the next challenge. as illustrated here https://github.com/freeCodeCamp/freeCodeCamp/issues/37381#issuecomment-544185610
to reproduce:
to make the backend projects submission fail, please add
  componentDidUpdate() {
     this.props.updateSolutionForm({});
  }

below the following block https://github.com/freeCodeCamp/freeCodeCamp/blob/d01ce3bbc11fb0736ed3ad81e8565c6d23c342b9/client/src/templates/Challenges/projects/SolutionForm.js#L30
Additionally this #37494 handles the api side of the message on submission failure, so a JSON should be send to the client upon failure.
expected behavior:
the user should see the message that was sent from the api-server and not be navigated to the next challenge.

hi, i want to tackle this one. feel free to assign me the task

Please go ahead with a pull request. no assignment is necessary.

@Ahmad-Faizan I've just followed the instructions, but failed to reproduce the bug. Has this bug been already fixed?

@Twaha-Rahman I think you tagged the wrong ahmad for the bug.

@Ahmad-Faizan Sorry, my bad! 😅😓

@ahmadabdolsaheb  I've just followed the instructions, but failed to reproduce the bug. Has this bug been already fixed?

@Twaha-Rahman, thanks for looking into this. Some of the files have been changed since the issue was created.
I have updated the description. Now you should be able to reproduce the issue.

to reproduce:
to make the backend projects submission fail, please add
  componentDidUpdate() {
    this.props.updateProjectForm({});
  }

This does not work. I had replace updateProjectForm with updateSolutionForm to re-create the bug.

@Twaha-Rahman, that makes sense. I updated the issue accordingly.

@ahmadabdolsaheb I would be happy to help on this. Should I update on of my PRs touching this, or open a new PR for it?

@ahmadabdolsaheb I would be happy to help on this. Should I update on of my PRs touching this, or open a new PR for it?

@ShaunSHamilton, thanks for your interest. And additional PR would be better.

@ShaunSHamilton, thanks for your interest. And additional PR would be better.

Just to let you know my thoughts on resolving this:

There appears to be some ground-work expected to solve this: https://github.com/freeCodeCamp/freeCodeCamp/blob/4f4622dd212f32c8118413dede1a9199099ff9a0/client/src/redux/index.js#L139-L140

The actions have not been added to the reducer, but are defined, and are called here:
https://github.com/freeCodeCamp/freeCodeCamp/blob/4f4622dd212f32c8118413dede1a9199099ff9a0/client/src/templates/Challenges/redux/completion-epic.js#L33-L49
Am I missing something, or can I just continue implementing updateComplete and updateFailed?

Just to let you know my thoughts on resolving this:

There appears to be some ground-work expected to solve this: https://github.com/freeCodeCamp/freeCodeCamp/blob/4f4622dd212f32c8118413dede1a9199099ff9a0/client/src/redux/index.js#L139-L140

The actions have not been added to the reducer, but are defined, and are called here:
https://github.com/freeCodeCamp/freeCodeCamp/blob/4f4622dd212f32c8118413dede1a9199099ff9a0/client/src/templates/Challenges/redux/completion-epic.js#L33-L49
Am I missing something, or can I just continue implementing updateComplete and updateFailed?

I think you are in the right track. We just need to make sure that when something fails in the backend, the info is communicated with the client and the client displays errors properly.
There is some groundwork, and it seems like the client is notified about the error, but the user is navigated to the next challenge. (that should not happen)

I think you are in the right track. We just need to make sure that when something fails in the backend, the info is communicated with the client and the client displays errors properly.
There is some groundwork, and it seems like the client is notified about the error, but the user is navigated to the next challenge. (that should not happen)

hi
tried to mimic server error at 'save challenge' api
i cannot see the redirection to next challenge (as it says at the issue description), also not see any error message...

if I remember correctly, this issue only happens on backend project submissions.

If issue exist obly at backend challenges, may be it can  be good to add this at issue description

so, after reading, and understanding more about this issue,
i will try to summarize  things i found out so far:
the bug happens when there is some problem with api server (error at request), and user trying to submit back-end challenge.
the bug is - that user present with "success" modal
the desired behavior is - user should not see any modal, but only a warning message about server failure

I am closing this issue and opening a new one, to make the new goal of adding feedback to user clearer.


DynamicTrees won't work with Forge

Every time I try to install and transfer this mod into Minecraft, Forge says that it's not made for the current forge.

“Not made for Forge”... It’s made using Forge... What version of Forge are you using and how are you installing it?


Anyone has tried XLA to accelerate Tacotron2

Before using XLA, the Tacotron 2 runs about 0.5s, however, after using XLA, it increases to about 0.7s which is much slower.
config = tf.ConfigProto()
config.graph_options.optimizer_options.global_jit_level = tf.OptimizerOptions.ON_1
self.session = tf.Session(config=config)

I use XLA like above. Any thoughts would be appreciated. Thanks.

Hi,  when did you use XLA ? train or inference phrase?

Just for inference.


[GAL-322] Open images in new tab from NFT Detail Page

This opens images in a new tab when clicked from an NFT detail page.

Audio: Does not open in new tab, because I think these are usually two separate components (one for audio, one for video)
Video: Clicking pauses/plays videos
GIFs: Open in new tab
SVGs: Open in new tab
Images: Open in new tab

There may be a simpler way to do this, but right now we pass the inDetailPage prop down to the primary image component (ImageWithLoading). (I can't access the image url src from the NftDetailAssetcomponent, so we can't pass it towindow.open()`)

There may be a simpler way to do this, but right now we pass the inDetailPage prop down to the primary image component (ImageWithLoading). (I can't access the image url src from the NftDetailAssetcomponent, so we can't pass it towindow.open()`)

thanks @connorrothschild! i just pushed up a commit that switches to using onClick, which leverages the image URL available for the nft detail page. easiest way to see the change is just by browsing the diff: https://github.com/gallery-so/gallery/pull/922/files
will go ahead and merge this!


Netlify Dev: Add support for .env files

- Summary
Allows users to use .env files for their site generators and Netlify functions written in JS, when using netlify dev.
Fixes: https://github.com/netlify/cli/issues/457
Fixes: https://github.com/netlify/cli/issues/444
Fixes: https://github.com/netlify/cli/issues/474
Fixes: https://github.com/netlify/cli/issues/405

- Test plan

Add .env file to your function directory with SOMETHING=true and see if it is accessible in function using process.env while running through netlify dev
Add a similar .env file to the root of your project and see if it is available to your site framework (etc. React etc.) when running through netlify dev

- Description for the changelog

Use dotenv package to parse .env file if exists and set the env variables to newly spawned site server process.
Do the same for Netlify functions builder when running through netlify dev
Use lambda-local to serve JS functions and pass path to function local .env file as parameter when executing

- A picture of a cute animal (not mandatory but encouraged)
🙈

looks good but needs docs and tests. got to start having a habit of adding these alongside features or it just never gets done

So this seems to work for new variables in .env, but if I have an existing variable in netlify.com the "remote" variable overrides my local .env. This seems backwards to me. The whole point of a .env file is to use "dev" api key for local development and a production key in actual production. Am I missing something?

@unclejustin I can confirm this behavior for Netlify Function. The cause for this is that dotenv doesn't override env variables that are already set. Please hold on while we figure this out.

Being discussed here: https://github.com/netlify/cli/issues/734
cc @unclejustin @jrunestone

@RaeesBhatti
No matter what I do - I cannot access any variables from my .env file in my functions.
It doesn't matter if the .env file is in my root folder, inside the functions folder, inside a function folder.
netlify dev do report: Overriding the following env variables with .env file: BISNODE_API_KEY,BISNODE_API_SECRET
Though process.env do not contain it.
On a side note, this is the third bothersome quirk with netlify dev I've experienced with your functions offering. I'd really like to use your product, and it saddens that I'm having such a hard time with these seemingly basic things

@oles Can you please share an example project with this problem!

@RaeesBhatti Sure - I'll get to it tomorrow 👍

@RaeesBhatti Here you go: https://github.com/oles/netlify-functions-env-example
Just run netlify dev in it, verify that it reports Overriding the following env variables with .env file: API_KEY,API_SECRET.
Then open http://localhost:8888/.netlify/functions/example, and see that it is blank, and that it logs out two undefineds in the console.
They should be the values from the .env file, as accessed in the function with const {API_KEY, API_SECRET} = process.env

Thanks for reporting this @oles. This was caused by a silly mistake, we've added tests to make sure that doesn't happen again: https://github.com/netlify/cli/pull/748

🍻 Cheers for the transparency @RaeesBhatti !

@RaeesBhatti Perfect! Thank you!

A fix for this has been released in<EMAIL_ADDRESS>

This only listens for for variables in .env and ignores alternatives like .env.production and .env.development

Yeah this is confusing as Gatsby uses the above env files, not just.env

Yeah this is confusing as Gatsby uses the above env files, not just.env

yes, I was also confused by that so I created https://github.com/netlify/cli/pull/924 hope that helps


Move to Redux hooks

Fixes #2345.
Changelog Entry
(TBD)
Description
<EMAIL_ADDRESS>finally support partitioned Redux hooks in their #1309! 🎉 It was just released the day before yesterday!
Thanks for @corinagum on the BIG push of moving from class components to functional components. So we can make this push today. 💪🏻
We are also moving away from HOC and use hooks intensively. This will reduce code complexity and highly improve readability.
Now it is super easy to build a new UI component without too much reading into Web Chat code, thanks to the React hooks pattern.
For example, if you want to build a button that would open microphone.
import { useStartDictate } from 'botframework-webchat-component';

const StartRecordingButton = () => {
  const startDictate = useStartDictate();

  return <button onClick={startDictate}>Turn on microphone</button;
}

And put this <StartRecordingButton> inside any part of Web Chat, it will automatically wired up.
Also, the propTypes on the component is very clean now. No more unnecessary-but-required-by-ESLint props from the context or store.
Specific Changes

Added hook for every functionality

Every use* hook is small and we are able to shuffle the physical location of the actual function if we want to, without breaking the user

We currently have things not located accurately, they are in React context and Redux store. Some appears on both of them (e.g. language).

Redux hooks requires us to make smaller hook and composite them into a bigger one

Update all components that use connectToWebChat() into useSelector(WebChatReduxContext) and useContext(WebChatContext)
Add deprecation notes to all connect* HOC functions

[ ] Revisit every component and hook to make sure the exposed surface as lean-and-mean as possible
[x] Update samples (at least one of them) to show off the ability to use hooks

[x] samples/09.customization-reaction-buttons
[x] samples/10.b.customization-password-input
[x] samples/21.customization-plain-ui

[ ] Document some fundamental differences between connect* and use*

For useComponent (e.g. useMicrophoneButton), we no longer expose language

[x] Consider a dedicated namespace inside our package for the hooks

For example, import { useActivities } from 'botframework-webchat-component/lib/hooks, and not exposing it at the root level

[ ] Test under IE11
[ ] (Optional) Might be a good idea to understand more about the performance gain
[ ] (Optional) Experiment on how to add a new UI component to Web Chat in the new world
[ ] Testing Added

ping!

We need more samples. 21.customization-plain-ui is a great way to show off the simplicity of React Hooks!

Spent a lot of time revisiting every single hook. There were stupidity but all are fixed now.
Should write down my rationale and thoughts on what to hook and how, in HOOKS.md.

Couldn't believe I refactored 150 files in a single commit and I only have 2 build-time errors. No runtime errors. 💪🏻

Finally, a well-defined (and hopefully well-thought) Web Chat API. 💪🏻
For starter, please read HOOKS.md first. All hooks defined are in some ways used by Web Chat UI. 1P = 3P.


Building container image based on registry.redhat.io image failing

I'm unable to build a image using the buildah-build action, when my containerfile is based on image from registry.redhat.io
STEP 1: FROM registry.redhat.io/ubi8/ubi:latest
error creating build container: Error initializing source docker://registry.redhat.io/ubi8/ubi:latest: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
level=error msg="exit status 125"
Error: Error: buildah exited with code 125
error creating build container: Error initializing source docker://registry.redhat.io/ubi8/ubi:latest: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
level=error msg="exit status 125"

You have to log in to use registry.redhat.io. Without logging in, you have to use registry.access.redhat.com.
https://access.redhat.com/RegistryAuthentication

I know that I have to login. But how can I do this?
I didn't found any information on buildah-action.

ah, ok. This action doesn't have a login feature - You can run docker login in a step just before running this action.

Thanks, that helped. closing this issue.

I will add a note in the readme.


kubeconfig file for user<EMAIL_ADDRESS>not working

Do we have a stale config?  If so, how can we test and fix?

Stale configs fixed


Abstract aggregator for simple aggregation development

Hi, I just added two classes, one is an abstract aggregator for simple aggregator development, I took Tibco Streambase approach of calculate everything at the end, even the whole group is not considered in Streambase , but that´s something to discuss about :)

Miguel-
Thanks for the patch! Good point about the group data in the aggregator. You had me thinking about the design a little bit. This is probably something that the Aggregation bolt could do underneath. I definitely think it's worth creating a ticket for.
Would be nice to:

Get some automated testing in place for each of the aggregators and
Get the other aggregators moved over to using your abstract class.

I think the tests can be done as a separate ticket considering none of the aggregators are tested on their own yet.

Hi!
Good! I will create an issue with the description of a "light aggregator", maybe just another abstract one?

of course, I was waiting for your merge hehehe
consider it done, I will keep creating simple ones too

Best Regards!