Errors relating to system-image-upgrade-controller by ProjectController seen for clusters.

Rancher server version - Build from master
Steps to reproduce the problem:
Create a DO cluster.
Deployed few workloads in default namespace.
Errors relating to system-image-upgrade-controller by ProjectController seen for clusters at regular intervals.
2018/09/14 23:28:04 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:05 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:05 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:05 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:05 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:05 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:07 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:09 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:15 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:17 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:32 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:28:33 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:29:04 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:29:05 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:30:08 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:30:09 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:18 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:18 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:18 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:18 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:18 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:19 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:20 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:23 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:24 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:31 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:32 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:47 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:31:49 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:32:16 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:32:18 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:32:20 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:32:21 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:33:24 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:33:25 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:35:32 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:35:33 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:36:32 [ERROR] ProjectController c-jltkg/p-7h4sx [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:36:34 [ERROR] ProjectController c-jltkg/p-8dk8g [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:39:48 [ERROR] ProjectController c-nz664/p-7bfl8 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:39:49 [ERROR] ProjectController c-nz664/p-56cv4 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:31 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:31 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:31 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:31 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:32 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:32 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:34 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:34 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:38 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:38 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:46 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:51:46 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:52:02 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:52:02 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:52:34 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:52:34 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:53:38 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:53:39 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:55:47 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/14 23:55:47 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:00:03 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:00:03 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:08:35 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:08:35 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:25:15 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:25:15 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:41:55 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:41:55 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:58:35 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 00:58:35 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 01:15:15 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 01:15:16 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 01:31:55 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 01:31:56 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 01:48:36 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 01:48:36 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 01:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 01:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 02:05:16 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 02:05:16 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 02:21:56 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 02:21:56 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 02:38:36 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 02:38:36 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 02:55:16 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 02:55:17 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 03:11:56 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 03:11:57 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 03:28:36 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 03:28:37 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 03:45:17 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 03:45:17 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 03:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 03:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 04:01:57 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 04:01:57 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 04:18:37 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 04:18:37 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 04:35:17 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 04:35:17 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 04:51:57 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 04:51:57 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:08:37 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:08:37 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:25:17 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:25:17 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:41:57 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:41:58 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:58:38 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 05:58:38 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 06:15:18 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 06:15:18 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 06:31:58 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 06:31:58 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 06:48:38 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 06:48:38 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:05:18 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:05:18 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:21:58 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:21:58 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:38:38 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:38:39 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:55:19 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 07:55:19 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 08:11:59 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 08:11:59 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 08:28:39 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 08:28:39 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 08:45:19 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 08:45:19 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:01:59 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:01:59 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:18:39 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:18:39 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:35:19 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:35:20 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:52:00 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 09:52:00 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 10:08:40 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 10:08:40 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 10:25:20 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 10:25:20 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 10:42:00 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 10:42:00 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 10:58:40 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 10:58:40 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 11:15:20 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 11:15:20 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 11:32:01 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 11:32:01 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 11:48:42 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 11:48:42 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 11:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 11:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 12:05:22 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 12:05:22 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 12:22:02 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 12:22:02 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 12:38:42 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 12:38:42 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 12:55:22 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 12:55:23 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 13:12:02 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 13:12:03 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 13:28:43 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 13:28:43 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 13:45:23 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 13:45:23 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 13:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 13:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 14:02:03 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 14:02:03 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 14:18:43 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 14:18:43 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 14:35:23 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 14:35:23 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 14:52:03 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 14:52:04 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:08:44 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:08:44 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:25:24 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:25:24 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:42:04 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:42:04 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:58:44 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 15:58:44 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 16:15:24 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 16:15:24 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 16:32:04 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 16:32:04 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 16:48:44 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 16:48:44 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:05:24 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:05:25 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:22:04 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:22:05 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:38:45 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:38:45 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:55:25 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 17:55:25 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 18:12:05 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 18:12:05 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 18:28:46 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 18:28:46 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 18:45:27 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 18:45:27 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:02:07 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:02:07 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:18:47 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:18:47 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:35:27 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:35:27 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:52:07 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 19:52:07 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 20:08:47 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 20:08:47 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 20:25:27 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 20:25:27 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 20:42:08 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 20:42:08 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 20:58:48 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 20:58:48 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 21:15:28 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 21:15:28 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 21:32:08 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 21:32:08 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 21:48:48 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 21:48:48 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 21:51:30 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 21:51:30 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 22:05:28 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 22:05:28 [ERROR] ProjectController c-tm24x/p-645m9 [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided
2018/09/15 22:22:08 [ERROR] ProjectController c-tm24x/p-fhr6m [system-image-upgrade-controller] failed with : an empty namespace may not be set when a resource name is provided

Tested with latest build from master.
Create a DO cluster.
Deployed few workloads in default namespace.
Errors relating to system-image-upgrade-controller not seen in logs anymore.


[py] GRPC routing metadata is incorrectly computed for update calls

As an example:
https://github.com/googleapis/google-cloud-python/blob/de73e45a7183a638113153d0faec105cfc437f0e/kms/google/cloud/kms_v1/gapic/key_management_service_client.py#L1569
When the crypto_key argument to UpdateCryptoKey is a dict, the attempt to resolve crypto_key.name results in an AttributeError ("'dict' object has no attribute 'name'").  The error is caught and ignored, so this fails silently.
Reported by a customer at https://stackoverflow.com/questions/59617920/cant-update-cryptokey-in-us-central1

The bug also happens with UpdateCryptoKeyVersion

@software-dov ,  can you clarify this issue happens in the micro-generator or is this something that we should fix in the current monolithic?


Work with Spring Boot 3.2

The release of Spring Boot 3.2.0 is scheduled for November 23rd. In it, the class LocalVariableTableParameterNameDiscoverer will be removed. To ensure functionality, it is necessary to update the MethodInfo class, replacing LocalVariableTableParameterNameDiscoverer with StandardReflectionParameterNameDiscoverer. Additionally, to ensure successful operation, it is necessary to update the pom.xml file:
<plugin>           <groupId>org.apache.maven.plugins</groupId>           <artifactId>maven-compiler-plugin</artifactId>           <version>3.11.0</version>           <configuration>           <source>${java.version}</source>           <target>${java.version}</target>             <compilerArgs>               <arg>-parameters</arg>             </compilerArgs>           </configuration> </plugin>
The task is not a big one, I could have done it myself. However, it seems that some permissions are needed to push the branch, I am currently getting a 403 error.

Can you create a Pull Request instead @BalikhinLB ?

I feel very embarrassed, I haven't contributed to open source yet. To make a pull request here, do I need to execute a fork? I don't have the option to pull the branch directly into the current repository?

No worries - the first time is always the most exciting one :-)
Yes - you need to fork the repo and do the changes in your fork (there you have all permissions). Then you have the option to create a PR from there. Typically you create a branch for each PR - but I don't think GitHub forces you to.
See also https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

Ok, thx. I did it: PR


[Feature]: Restore Access to Utility Functions in "jest-snapshot/utils" for Continued Tooling Support

🚀 Feature Proposal
Please consider re-exposing the following functions and corresponding types in jest-snapshot/utils.ts to enable tools like vscode-jest and jest-editor-support to retrieve snapshot content by test names effectively:

getSnapshotData
testNameToKey

In jest-snapshot version 27.x, these utilities were fully accessible at jest-snapshot/utils, facilitating robust tool integration. However, versions 28.x and 29.x have restricted access to these functions/types, significantly impacting tool functionality and integration.
Motivation
The primary motivation for this request is to maintain backward compatibility with existing features in community tools, such as the "view snapshot" feature in vscode-jest. This functionality, along with others, enables users to view, update, run, and debug snapshots for individual tests, is crucial for enhancing the user experience in VSCode's Jest integration.
Example
For instance, the jest-editor-support library uses functions like getSnapshotData and testNameToKey from jest-snapshot/utils to retrieve snapshot content. Here's how it's implemented in getSnapshotContent and getMetadata
Pitch
I understand the concerns about exposing unnecessary functions. However, considering their existing use within the tooling community, unless there is a better alternative, could we consider re-exposing these utility functions/types? If you agree with this proposal, I could submit a PR shortly.

@SimenB do you object we re-expose these functions/types?

Perhaps the utils could simply be published as separate @jest/snapshot-utils package?

Separate util package makes sense to me 👍 Happy to take a PR to that effect 🙂

@SimenB, a few follow-up questions regarding splitting the utils into its own package @jest/snapshot-utils:
Circular Reference
Is it correct to assume that you would prefer the @jest/snapshot-utils package not to depend on the @jest/snapshot package due to circular reference? If that is the case, we have the following dependency issues to resolve:
In utils.ts:
import {getSerializers} from './plugins';
import type {SnapshotData} from './types';

The ./plugins module is not used anywhere except in utils.ts. Should we move it to @jest/snapshot-utils as well?
The type SnapshotData from ./types is simply a Record<string, string>. Do we want to create a new package @jest/snapshot-types for a single line type definition? Or maybe the whole ./types file?

Re-evaluation
Given these issues, do we still favor splitting utils.ts into new packages (@jest/snapshot-utils, @jest/snapshot-types) over exposing it within @jest/snapshot?

In TypeScript repo they have public and internal utilities. Perhaps similar strategy could be adopted? I mean, the new package could exposing only getSnapshotData(), testNameToKey() and other actually useful utilities not all what utils.ts contains.
By the way, I think SnapshotData can be replaced with Record<string, string>. That looks fine, because TypeScript does not have nominal types. SnapshotData is not very useful type, for example, the return type of getSnapshotData() currently is {data: Record<string, string>; dirty: boolean}.

Moving SnapshotData to the new package should be fine, yeah

sorry for the delay, I am back to this issue now. One more question, given the jest-snapshot doesn't use the "@jest" scope (not sure what the naming rule is), do we want the new package to be @jest/snapshot-utils or jest-snapshot-utils?

The old ones don't as they predate our ownership of the jest org on NPM. All new packages should use the namescaped one, but we don't wanna migrate old ones (just to avoid dependents getting left behind).

https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.5


Reporting Sample of Northwind object does not support this method. executeReport.

I was running the Northwind sample Reporting where there are two samples CustomerGross and Sales By Cat  and I receive the following error when clicking the excel icon: - of course there also looks to be no data in the popped up grids.
The code breaks in
ReportDialog.ts
getToolBarButtons{ onClick: () => this.executeReport('_blank', 'xlsx', true) }
Unhandled exception at line 7200, column 48 in http://localhost:...../Site/Tutorials.Web.js
0x800a01b6 - JavaScript runtime error: Object doesn't support property or method 'executeReport'

It works in serenity.is, so i'm pretty sure you miss some file.

@stixoffire , check to see that all of the northwind .cshtml pages are being included in the publish.

Also try taking latest ReportDialog.ts, your project might have an out of date version.

@volkanceylan - I downloaded vsix <IP_ADDRESS> from vs gallery yesterday (as I wanted to try out the other samples and see the examples ) - I also have a separate project I Nugetted up to 2.6.10 these both exhibit the same issue.
I have an older test project <IP_ADDRESS> and it works just as expected.

@volkanceylan after running the other build that worked it seems I am able to run these in <IP_ADDRESS>  must be something was cached that should not have been. Sorry for the trouble. Thought for sure with 2 projects doing the same thing and one earlier version working - that something broke.


Number classes for COCO is 81, but it is 90 in the config?

Hello. Thanks for your implementation.
I read through the config.py and see the number class =90, therefore the weight of cls_net.predict.conv_pw is [810x fpn_feature x1x1], where the number of anchor =9. (90x9=810)
This is different with I expect, since COCO has 80 foreground classes, it should be 80x9=720 instead.

That's the way the Google researchers set up their model, I'd remap the classes down to 81 but they left the gaps. Since I ported their weights I left that. I'll likely add an 81 class mode for weights I train in the future


Custom video data support #1722 & #1721

📝 Description

Provide a clear summary of the changes and the issue that has been addressed.
Add support to use custom data to create datamodules of video-based data.
Support for masks as .npy / .pt / or an image type.
Support for train/test videos as .avi/.mp4 or as a collection of images in a folder.
🛠 Fixes #1722 & #1721

✨ Changes
Select what type of change your PR is:

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🔨 Refactor (non-breaking change which refactors the code base)
[X] 🚀 New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] 📚 Documentation update
[ ] 🔒 Security update

✅ Checklist
Before you submit your pull request, please make sure you have completed the following steps:

[ ] 📋 I have summarized my changes in the CHANGELOG and followed the guidelines for my type of change (skip for minor changes, documentation updates, and test enhancements).
[ ] 📚 I have made the necessary updates to the documentation (if applicable).
[X] 🧪 I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).

For more information about code review checklists, see the Code Review Checklist.

Hello good day, I will start making the Documentation as another PR.

Has anomalib support the "test_split_mode.SYNTHETIC" feature for Video datasets?
To add it in the docs or not.
And should I make the arguments, even more 1:1 with the folder class?
@samet-akcay @ashwinvaidya17 @djdameln

And I would like to add a micro toy dataset ( 6mb ) that combines the other 3 datasets but in its minimum configuration.


Feature/documentation

Description
Issues and Pull requests should only be made for changes to the application code, not Tech Challenge Assessments.

Completed documentation

Fixes: https://github.com/servian/TechChallengeApp/issues/{issue number}
Checklist

[x] Code compiles correctly
[x] Created tests which fail without the change (if possible)
[x] All tests passing
[x] Extended the README / documentation, if necessary
[ ] Added issue number to Fixes line above

As stated in the issue template:
Issues and Pull requests should only be made for changes to the application code, not Tech Challenge Assessments.
I'll also refer you to the Tech Challenge Instructions.


Calibration on Arduino nano: Load_cell output val: nan

Hi again, my phone weight only 50 grams so I need calibration, probably the sketch for calibrate is made for working only under ESP8266, when I decide to write to eeprom I have this:
Load_cell output val: nan (it fills my terminal without stopping)
Can you please help me fix it?

I forgot to change pin 4 and 5 with the default 2 and 3, sorry bu tusually all sketch are based on them. Works fine! Thanks

My best congratulation for this library, simply fantastic. Calibration is wonderful, I've tested it with a profesional kitchen scale and the difference was about 1g for heavy and light things

Many thanks, glad you like it :)

I am facing the same issue, I am getting "Load_cell output val: NAN " my connections are perfectly fine. Can someone help me with this.


docs: Worker example of Web Share Target API

Hi,
after a bit of struggling, I finally managed to have a working PWA with Web Share Target API (so you can choose a picture in your gallery, click "share" and send them to my PWA :tada: )
It uses the (default) generateWS mode and the following config:
        manifest: {
          //...
          share_target: {
            action: "/share",
            method: "POST",
            enctype: "multipart/form-data",
            params: {
              files: [
                {
                  name: "images",
                  accept: ["image/*"],
                },
              ],
            },
          },
        },
        workbox: {
          importScripts: ["sw-next-message.js"],
          runtimeCaching: [
            {
              handler: ({ event }) => {
                const dataPromise = event.request.formData();
                event.waitUntil(
                  (async function () {
                    // defined in sw-next-message.js
                    await nextMessage("share-ready");
                    const client = await self.clients.get(
                      event.resultingClientId
                    );

                    const formData = await dataPromise;
                    client.postMessage({
                      images: formData.getAll("images") || [],
                      uri: "/share",
                    });
                  })()
                );
                return Response.redirect("/share");
              },
              urlPattern: "/share",
              method: "POST",
            },
          ],
        }

Do you think that it would be worth integrating such an example in the documentation?
If yes, where ? (Maybe a new category Examples > Workbox > Web Share Target API)
I can try to craft a working minimal example in vue.

@oliverpool But what is the flow? I mean, if you share a photo, the pwa , what will do with that photo (open share api)? Maybe you should create a minimal example repo and explain it a bit more...

My PWA is like a social network and I want to let the people share their own pictures easily.
There is this "Web Share Target API" to let the browser/smartphone know that my PWA wants to be included in the possibilities to share a picture. For this API to work, the files reception must be handled by the worker:

a POST request is made to the worker on the specified URL of the share_target
the data can be received by the worker using:

                const formData = await event.request.formData();
                const files = formData.getAll("images")
                // do whatever you want with the files

if you want to send this files to the frontend (for the user to add a message to it for instance), you must post a message from the worker to the frontend (which requires some synchronization between them)
once in the frontend, you can do whatever you want with the files

Before I take the time to make a working minimal example using this library, I wanted to know if this would be a good example to include in this repo (to show the worker customization possibilities allowed by your great library).
Shall I take your comment as a "yes, please show us a working example, just make a PR with an example under vite-plugin-pwa/examples/vue-web-share-target"? :angel:

@oliverpool closing this since there are a few resources from Google and Microsoft about pwa stuff, including your example:

https://web.dev/progressive-web-apps/
https://microsoft.github.io/win-student-devs/#/30DaysOfPWA/kickoff


Updated and Linked professional footer UI designing

Hii @Susmita-Dey !
✔Added some interesting footer design UI with hover effect and added animations. Hope you like it :) Thank you!
✔And added footer's logo css to the top for improving UI
✔Also linked your socials :)

@fykaa
But this issue was not assigned to you. I am working on this issue.

Hello, @Vanshiii203  I contributed for the Hacktoberfest; ig it does not necessarily imply issues; I just performed the PR that I believed needed to be improved; that is what the Hacktoberfest was intended for. You may still make your desired modifications because this is an enhancement PR and not a bug repair.

@Susmita-Dey Updated changes to the Design as such -

Also Added Flip Animation :)

@fykaa Don't make PRs directly like this. Issue needs to be made and then after i assign you, you can make a PR.


fix(state): Stop reading redundant blocks for every FindHashes and FindHeaders request

Motivation
Zebra reads 160-500 redundant blocks for each FindHashes or FindHeaders request.
The FindHeaders requests regularly take 5-10 seconds to answer.
This is a security issue because remote nodes can send these requests.
Solution

Find a range of heights, rather than a list of hashes
Stop reading redundant blocks and calculating redundant hashes
Remove redundant state queries
Allow some inconsistencies that can happen during concurrent writes, but don't do concurrent queries yet
Simplify some of the code

This PR contains a regression - the header queries used to be partially concurrent, now they block the rest of the state.
The next PR will implement full concurrency.
Review
This is an urgent PR to fix Zebra sync performance.
Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Thanks for the review!
All the tests passed except for lightwalletd, which is fixed by PR #4828.
So I'm going to admin-merge this.


[wallet] Update the respondWithAlternative transaction to work with the new contracts

As per #23 but for respondWithAlternative. Note that checkpoint is the method that replaces respondWithAlternative.

This has been done.


VirtualService traffic shifting not respected by traffic originating from ServiceEntry

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
I have a k8s cluster with the following setup:
Traffic originating from app A, heading towards a hostname (service-B-alias.local) defined in a ServiceEntry configured as such:
apiVersion: networking.istio.io/v1beta1
kind: ServiceEntry
spec:
  endpoints:
    - address: serviceB.namespace-B.svc.cluster.local
  hosts:
    - service-B-alias.local
  location: MESH_INTERNAL
  ports:
    - name: http
      number: 80
      protocol: TCP
  resolution: DNS

Traffic does in fact make it from app A to app B, (DNS resolution works fine in the sidecar proxy), however when trying to apply a virtualservice (See below) for traffic shifting behavior, the .local hostname is not being matched and the traffic is split round-robin 50/50.
apiVersion: networking.istio.io/v1beta1
kind: VirtualService
spec:
  hosts:
    - service-B-alias.local
  http:
    - match:
        - uri:
            prefix: /
      name: primary
      route:
        - destination:
            host: serviceB.namespace-B.svc.cluster.local
            subset: stable
          weight: 99
        - destination:
            host: serviceB.namespace-B.svc.cluster.local
            subset: canary
          weight: 1

I'm not sure where this is going wrong, any debugging help would be greatly appreciated. Thanks!
Version
client version: 1.17.2
control plane version: 1.16.4
data plane version: 1.16.4 (245 proxies)

Client Version: v1.25.4
Kustomize Version: v4.5.7
Server Version: v1.23.17-eks-0a21954

v3.12.0+gc9f554d

Additional Information
No response
Affected product area

[ ] Ambient
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

Do you have a DestinationRule created for host service-B-alias.local which defines the stable and canary subsets?

+1  @roee-landesman do you have resolve this? I have the same quesiton.

Hi all, we can go ahead and close this issue.
The solution for us was to use a Service of type ExternalName, placed in the local namespaces, such that internal services can use that internal hostname as an alias FQDN.


fix: MD033/no-inline-html

Ignore tags needed for inside markdown tables (br/ol/ul/li)
Replace iframe with !VIDEO
Escape
Escape  but this may be an artifact
Disable inline for HTML pages
Replace  with escaped characters
Replace img tags with markdown
Remove empty paragraphs

We are reviewing this PR for impact.

@gewarren - can you take a look at this? thanks.

@gewarren : Thanks for your contribution! The author, @gewarren, has been notified to review your proposed change.


Multiple Newsletter

Hi!
Is it possible to finally have multiple newsletters? Or is it going to be difficult?
Thanks for your work.

Update: I've internally started working on this. No ETAs though.

GREAT! 😍🙌

Update: The linked branch i.e. multiple-newsletters contains this feature request.

Update: The linked branch i.e. multiple-newsletters contains this feature request.

Great!!! is there any way to install this branch in second instance without damaging the main app installed by ghosler cli? I have the service running and I don't want to mess it up.
Thanks!

@viriatusX You can install ghosler from the mentioned branch in a different directory.
However it will require a manual setup as ghosler-cli doesn't currently support managing multiple instances.
Here's a basic flow to test the branch -

Git clone the branch to a directory.
Run npm ci --omit-dev && pm2 start app.js --name ghosler-dev in the directory.

I'll be verifying this branch too before merging the linked PR but no timeline on it as I'm travelling for a while.
Thanks!

@ItzNotABug It's work perfectly! I just test it!
It would be nice to have an option to send the article to ALL newsletters.
Thanks for all!

@viriatusX Thanks for testing!
About the suggestion, I don't think we should allow sending to 'all' newsletter or 'multiple newsletters'.
The reason being, a user may be subscribed to multiple newsletters & hence would receive multiple emails for the same blog post.
However, we could add an option to send the email to 'all' subscribed users, irrespective of a newsletter which makes sure that every user receives only one email.

@viriatusX Here's what I meant - https://github.com/ItzNotABug/ghosler/pull/32#issuecomment-1936959053.

Perfect 🙌👏


Docker Image with Python>3.6 for building jax

I am looking to build jax inside the docker image, but current jax requires python>3.6.  Just checked out rocm/tensorflow:latest and noticed it is using Ubuntu Bionic python 3.6.  Is there a 20.04 docker image, since it would have python 3.8?

Apologies, I just found the "beta" docker image for jax.


net: l2: ieee802154: Automatically select CONFIG_NET_6LO

802.15.4 IP-based networking requires 6LoWPAN layer and won't work
correctly without it. So, if NET_L2_IEEE802154 is select,
automatically select NET_6LO. This is similar to what BLE L2
does (NET_L2_BT causes selection of NET_6LO).
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

@dleach02 , @priyankaNXP: FYI.


⚠ Bofrost.lu has degraded performance

In 5ec2db3, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1259 ms

Resolved: Bofrost.lu performance has improved in 0eb10ec after 16 minutes.


Add metric type COSINE

/kind feature

/kind improvement

/hold

would this be backport to Milvus 2.2.X?

would this be backport to Milvus 2.2.X?

In current plan, we will just support it after Milvus 2.3. Plz let us know if it is necessary to have it in Milvus 2.2.x.

/lgtm

/approve

/unhold


Clean up Realm README.md section

Format notes
Add details about subclassing

I think with the changes introduced in 1.5.0 we'll probably want to update this PR. I believe all those extra initializers won't be necessary anymore

Closing this as StaticMappable has changed the implementation approach. @robbiet480 feel free to create a new PR with more up to date instructions! Thx


[Question] Can the demo run on the Kirin chip

❓ General Questions

I compiled a demo based on the document and found that it crashes directly on a Huawei Kirin chip phone, while it runs normally on other chip phones. Is this a persistent issue? Or what configuration needs to be modified to run?

We only tested on the Android App on Qualcomm 8gen2 and 8gen3, but we do not have use any specific API for Qualcomm Soc, so it should work on any android devices.
It would be great if you could locate the problem or send a PR to fix it :)

Gonna close this issue due to inactivity. You are welcome to reopen it or open a new one if there are further questions.


For OPTIONS request Route::any() not work like Route::match(['OPTIONS'],...)

Found this issue when trying implement CORS response to AJAX fetch.
Route::any() does not handle OPTIONS request as expected, but Route::match(['OPTIONS']) was.

Hello @barryvdh :)
Do you have any reason why Route::any() shouldn't match an OPTIONS verb?

Yes, any() doesn't register the Options route: https://github.com/laravel/framework/blob/c7de016c568c0b1555914487b0944b7298105fbe/src/Illuminate/Routing/Router.php#L208-L213
public function any($uri, $action = null)
    {
        $verbs = ['GET', 'HEAD', 'POST', 'PUT', 'PATCH', 'DELETE'];
        return $this->addRoute($verbs, $uri, $action);
    }

In my cors package, I intercept the CORS request in my ServiceProvider:
https://github.com/barryvdh/laravel-cors/blob/7236b8ca722fb404c5f83444eca195ec4ca46d55/src/ServiceProvider.php#L42-L44
And use the Router to detect if it can match the Router for the requested verb (so not OPTIONS, but e.g POST). If so, return a response from the middleware directly:
https://github.com/barryvdh/laravel-cors/blob/master/src/HandlePreflight.php

So do you believe that we should keep it that way and not match OPTIONs?

https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS

The Cross-Origin Resource Sharing standard works by adding new HTTP headers that allow servers to describe the set of origins that are permitted to read that information using a web browser.  Additionally, for HTTP request methods that can cause side-effects on user data (in particular, for HTTP methods other than GET, or for POST usage with certain MIME types), the specification mandates that browsers "preflight" the request, soliciting supported methods from the server with an HTTP OPTIONS request method, and then, upon "approval" from the server, sending the actual request with the actual HTTP request method.  Servers can also notify clients whether "credentials" (including Cookies and HTTP Authentication data) should be sent with requests.

Matching OPTIONS with any would have a side effect of executing the request/action already, so I don't think that is expected behavior.

Oh, that makes sense.
Thank you so much for your help :)
@Denys-Bushulyak please check above.


Memory-based bookkeeping for Terraform operations

Description of your changes
Not tested, not wired up to controller. This is the initial draft PR to get early feedback on the design at a high level since it had to touch many things.
Fixes https://github.com/crossplane-contrib/terrajet/issues/74
I have:

[ ] Read and followed Crossplane's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

@ulucinar @turkenh  As we talked yesterday, terrajet client now has sync and async variant of both Destroy and Apply  operations for different type of resources, i.e. VPCs would be completely sync where as cluster, database etc. whose creation/deletion is long would use async functions. I'm wondering how we do the separation especially in regards to @turkenh 's work around getting input from user:

We can have a bool in controller like IsAsync and add if to Create and Delete functions to toggle between sync and async calls.
We can have two different ExternalClient implementations and user would supply which one to use as config.
We can have two different Adapters that act as the backend of the same ExternalClient and user would choose which backend to use, which is similar to current implementation, though most ExternalClient calls become just a call to the adapter interface (the pushed change just moved the same logic to controller directly)

I am leaning towards the first option where we can return early in async cases with a simple if so the code wouldn't look complex to read. Between 2 and 3, I'm sort of on the side of 2 where we have two distinct controllers and it'd be a single place to make changes if needed for both cases instead of having to go through another layer. What are your thoughts?

@ulucinar @turkenh As we talked yesterday, terrajet client now has sync and async variant of both Destroy and Apply operations for different type of resources, i.e. VPCs would be completely sync where as cluster, database etc. whose creation/deletion is long would use async functions. I'm wondering how we do the separation especially in regards to @turkenh 's work around getting input from user:

We can have a bool in controller like IsAsync and add if to Create and Delete functions to toggle between sync and async calls.
We can have two different ExternalClient implementations and user would supply which one to use as config.
We can have two different Adapters that act as the backend of the same ExternalClient and user would choose which backend to use, which is similar to current implementation, though most ExternalClient calls become just a call to the adapter interface (the pushed change just moved the same logic to controller directly)

I am leaning towards the first option where we can return early in async cases with a simple if so the code wouldn't look complex to read. Between 2 and 3, I'm sort of on the side of 2 where we have two distinct controllers and it'd be a single place to make changes if needed for both cases instead of having to go through another layer. What are your thoughts?

@muvaf the first option sounds good to me. We can infer a sensible default per resource using schema.ResourceTimeout (e.g. if Create/Update Timeout > 5mins use async) and still allow provider developers to override the default behavior. We can generate setup.go based on the final value and pass this as an option to the controller.
For example, AWS RDS cluster has a default of 120 mins and we could choose async mode by default.

We can infer a sensible default per resource using schema.ResourceTimeout (e.g. if Create/Update Timeout > 5mins use async) and still allow provider developers to override the default behavior. We can generate setup.go based on the final value and pass this as an option to the controller.

@turkenh I think that's a great idea and we can use that information to default to sync mode if the timeout is 0. But I'd prefer implementing this in another PR since this one is already very big. Could you open an issue with the links you discovered?

We can infer a sensible default per resource using schema.ResourceTimeout (e.g. if Create/Update Timeout > 5mins use async) and still allow provider developers to override the default behavior. We can generate setup.go based on the final value and pass this as an option to the controller.

@turkenh I think that's a great idea and we can use that information to default to sync mode if the timeout is 0. But I'd prefer implementing this in another PR since this one is already very big. Could you open an issue with the links you discovered?

Sounds good, he it is: https://github.com/crossplane-contrib/terrajet/issues/78

@turkenh @ulucinar I rebased this and integrated the latest changes with the controller, specifically late initializer. Please take another look. @turkenh I will do another pass of manual tests now to see if we can implement your suggestions about printing errors and returning diff.

The missing tests are the tests of Workspace and WorkspaceStore objects which depend on exec functionality. I'm thinking of bootstrapping a small tool to mock the exec interface, something similar to afero that we use for filesystem operations. But that's for another PR.


[Anime-pictures] Low quality images downloaded.

Bug description
Grabber downloads low-quality images instead of the original images of better quality.
Steps to reproduce

Go to Grabber and download an image from Anime-pictures using whatever tags.
Download the same image but use the actual website (download manually).
See the difference in quality. The image downloaded from the website is way better quality than the image grabbed.

Expected behaviour
It should download the original file instead of the lower-quality image.
Context
Log and Settings.zip
Screenshots
Grabber knows that the image is 6MB for this file:

But, when I right-click and save, it downloads this:

System information

OS: Windows 10
Grabber version: 7.9.0

From what I can see in your settings, you have image resizing enabled at 1000x1000 (in "Settings > Save > Image size").

I turned that option off, but it still doesn't work. I also increased the size and it still doesn't download the highest quality image.

I think the problem is that the batch download function is downloading the preview images instead of the actual full size image.
I'm running into this issue as well. It's downloading the preview jpg's instead of the full resolution PNG's like it should be.


add column_comment to Field help_text when in inspectdb with mysql

add column_comment to Field help_text when in inspectdb with mysql

Thanks for the proposal but I don't think it's a good idea. help_text is user facing while database comments are not. Similar ideas were discussed in https://code.djangoproject.com/ticket/13867. Of course, you can have your own management command and introspection if this mapping makes sense for your use case.

when use inspectdb make model from db.
the db column is created by dba, not developer .
db  column comments set to models Field is helpful for developer.
it not necessary set to help_text.
like
    field = models.IntegerField(blank=True, null=True, db_comments='comments in db')
or
    field = models.IntegerField(blank=True, null=True) #comments in db


TableView cell color

Hey,
Is there a way to change the color of certain cells in a table view based on their value? Is there any other customization possible othen than through the RepresentationGetter?
Thanks,
Marcel

At the moment you can only change the text that is displayed (and text alignment) and it can only occupy a single console row.  The reason for this design is to allow rapid scrolling around large tables (e.g. 100,000 rows / 50 columns) without having to calculate the full table representation of every cell.
The rendering process will instead start at the scrolled to part of the DataTable and use the RepresentationGetter to measure and draw that bit of the table until it runs out of space in the console.  It also measures the representations returned to avoid showing half a cell where possible (e.g. where content spills off the right hand side do to many/large columns).
We could definetly add colored cell support though! The current draw code that would need updated is:
https://github.com/migueldeicaza/gui.cs/blob/7f27d78cc732c3155995ada06096a0748687605b/Terminal.Gui/Views/TableView.cs#L394-L433
We would need a corresponding member in ColumnStyle.  Something like:
/// <summary>
/// Defines a delegate for returning custom color values for cells in the table.
/// </summary>
public Func<object, ColorScheme?> ColorGetter;


flit install should install dependencies

The requires field should be a valid requirements.txt file, so we can shell out to pip to install these.
Suggestion from @minrk

Annoyingly, as @jhamrick pointed out, requirements.txt is not the same format as the requires-dist metadata.
# requirements.txt
someproject>=3.0

# requires-dist
someproject (>=3.0)

So I guess I'll need to parse them to some extent.

Booooooo

@takluyver do you copy the requires field in flit.ini directly to to the wheel, or let it do the normal transforms that it does when coming from setup.py (i.e. converting from pkg > 1 to pkg (>1))? I would expect to specify pkg > 1 in flit.ini.

#42 adds install, but doesn't handle the requires-dist != requirements issue yet, because it seems like the requires field in flit.ini should expect the requirements.txt format, not the Requires-Dist format.

It does directly copy the requirements to the wheel metadata. One of my side goals here is to remove some of the unnecessary padding around Python packaging so that you're interacting with certain things more directly. I don't think the requirements.txt format is a clear improvement over the real metadata format, so I'd rather remove the intermediary and write in the metadata format directly.

i.e. I think flit.ini should use the metadata format and translate to the pip format when needed, rather than vice versa. I'm open to arguments in favour of doing it the other way round, but that's my current preference.


chore: update readme, add open-webui

After testing most of these suggested frontends, "Open WebUI", formerly "ollama-webui", looks like the best open option for amateurs looking to self-host a frontend similar to OpenAI's ChatGPT interface.

Open WebUI is already in the list.


fastapi oauth guide

Hi there.
I'm using fastapi, it's pretty good, and I can easily manage the role based auth using Depends method from fastapi.
In the casdoor-python-vue-sdk-example, it's flask using sessions as a way for auth. Didn't find any useful info for fastapi devs.
I'm not a pro programmer, so I'm learning and coding, can't find any guides for fastapi and cardoor sdk examples yet, any guidance so I can use fastapi oauth as easy as this demo: https://fastapi.tiangolo.com/tutorial/security/oauth2-jwt/
much appreciated.

Update:
I found this issue from fastapi very promissing: https://github.com/tiangolo/fastapi/issues/12, may be of some help.


Need help for using my datas in real-time

Hello,
I modified the code to use it in real time in an ROS environment.
I need to know where do you modify your inputs in the model.
I have actually a '720, 1280, 3' image from cv2.
Your model need '64, 3, 7, 7'.
Can you have some times to explain me ?

@lucastabelini

have you resized to 360*640 ?

I tried, but i don't know what do do next.

The model does not need a 64x3x7x7 input. The input is an image resized do 512x288, as described in the paper.

Yes, but you use the Dataloader to import it. And the dataloader changed all the dimensions of the input using batch size, etc.
I would try to delete the Dataloader, is it possible ?

No.


Sync notifications not shown

On Pixel 4, photo and data sync status notifications not appearing. Reproduced using debug build.
This will likely being resolved when implementing #1125.

We've removed notifications, closing as obsolete.


Post Modify

Time required: 7 hours.

Add an article
Remove an article
Modify an article
Import an image

Time spent : 6hours


Remove smoothScroll from example

It gives an error in the console when trying to execute the example: example1.items.push({ message: 'Baz' })
This might confuse new people.
Perhaps it is better not to have it in the code at all, since it does nothing because of it being undefined.

Agreed. This seems to be some leftover.


Add pause and resume to EmitterController

This would support low bandwidth situations when emitting events should be paused.

The Emitter already has a pause and resume functions that are called from the Tracker when it is paused or resumed. However, they only pause the timer which regularly calls the flush function to send waiting events. The addPayloadToBuffer function can still trigger the flush and send events even if the emitter is paused.
I can see 2 options:

Adapt the current pause and resume functions to be used by the EmitterController. We would change them a bit to also disable sending events from addPayloadToBuffer. The Tracker will continue using these calls.
We add a new pause2 and resume2 functions (will need to figure out a different naming to distinguish them). These will call the old pause and resume but also disable addPayloadToBuffer. The tracker will keep using the current calls.

The same goes for the Android tracker, but there is a different naming being used (shutdown and flush).
This is an edge case, but I'm not sure what should happen in this case:

user pauses emitter
user pauses tracker
user resumes tracker

Should the emitter be resumed at this point?

Thanks @matus-tomlein for looking into this.
I would tend to option 1. The Emitter is an internal component now and the option 1 seems a cleaner change.
About the edge case it's a very minor thing but it would be a nice touch to avoid confusion on this.
In my opinion the Emitter shouldn't be resumed. The emitter would be stopped when we want to track but we don't want to emit the events (saving battery or network). The decision to pause the tracking could be completely independent from the decision to pause the emitter.
We can probably fix this keeping memory of who/what requested to pause the Emitter (whether the tracker pause or the user from EmitterController).
Unless, we want to distinguish the two again. TrackerController just pauses tracking (letting the emitter to flush the events) and EmitterController just pauses emission (letting the tracker to track the events for a later emission). More I think to this and more it seems the correct behaviour.

Thanks Alex! I agree that they should be different actions:

pausing the emitter should disable the flush function
pausing the tracker should disable the timer that periodically calls the flush


Fix swap_dims() index names (issue #3748)

[x] Closes #3748
[x] Tests added
[x] Passes isort -rc . && black . && mypy . && flake8
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API

I added a simple test, but not sure it is correctly set up. I wasn't sure about how pytest fixtures worked, so I didn't know if I needed/how to set up a new fixture to test the bugfix.

The 4 pytest failures per check are taking place in tests/test_plot.py. I suspect that these failures are unrelated to the pull request.

We have different test failures than last time. They appear to be happening in tests with time indexes this time. I suspect these failures are again unrelated to the pull request.

test failure is unrelated. Thanks @jaicher

Thanks a lot @jaicher
Thanks for all the recent reviews @dcherian ; I'll attempt to contribute a bit more...


Update README.md

Update the link on the samples README.md for the (formerly) ASP.NET 5 sample to link to the ASP.NET Core sample.

Hi @Lutando, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

Hi @Lutando, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

thanks!


Server Side Import

I am trying to import this on the serverside and am getting the following error.
import { Html } from "@react-email/html";
         ^^^^
SyntaxError: The requested module '@react-email/html' does not provide an export named 'Html'
    at ModuleJob._instantiate (internal/modules/esm/module_job.js:92:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:107:20)
    at async Loader.import (internal/modules/esm/loader.js:179:24)

Can you a repo/codesandbox to reproduce this?

Closing due to inactivity.

The issue here is trying to use this module in a Native ESM context. In a Native ESM application, you'd have to import the file in the dist directory (including the file extension). The solution is to use the package.json exports config. Radix had a similar problem recently and solved it that way: https://github.com/radix-ui/primitives/blob/main/packages/react/checkbox/package.json#L5

There is a repository that has a repro at: https://github.com/dawnmist/react-email-issue-513
This was created from Kent's Epic Stack, then modified to add react-email and a single email template.
Steps to see the error:

clone the repository
npm install
npm run build
npm run start

The dev server (npm run dev) hangs at the point where it is supposed to be compiling the application - the compile error isn't being shown but the compile doesn't succeed and the server continues waiting for it. When running with mocks (npm run start:mocks) the error is also not shown but the server itself doesn't function. When running the server on its own the import error is surfaced to the user, finally explaining why the dev server and server with mocks were hanging.

I can confirm that adding:
"exports": {
   ".": {
     "import": {
       "default": "./dist/index.mjs",
       "types": "./dist/index.d.ts"
     },
     "require": {
       "default": "./dist/index.js",
       "types": "./dist/index.d.ts"
     }
   }
 },

to the package.json file for the @react-email/components package allows me to successfully import components using native esm imports.
Given that the various component packages can be individually used rather than always through the @react-email/components package, each of them would also need to have the equivalent update in their package.json file so that they can still to be used individually when using native esm imports.

Note: I discovered later that the exports in the package.json file had broken the email dev server, giving the error message "Module not found: Default condition should be last one" pointing to the line where components were being imported from @react-email/components.
What caused it was that I had the "types" and "default" conditions in the json snippet above the wrong way around.
I've fixed the snippet above so that the default value being specified for the import and require sections is the last condition so if anyone else comes across the thread they don't copy/paste the wrong information, and the email dev server is working again - but I wanted to highlight that it's important that default lines come last in their sections otherwise the nextjs server will be unable to load the email templates.


Track global pose of points on map

What is the best way to track a global pose of a locations on map?
Assuming that due to global optimizations the global pose of these locations changes over time.

I do not have an answer, but I am facing a similar situation. My idea is as follows: first thing to do is to publish the cartographer's global pose, and somehow pair it with the current trajectory, store pairs (pose,traj). Then, whenever we need to map the stored poses we request the current local to global transform and use it to map the stored positions to the current location. I need to research more into this as at this point I do not know if the transforms are cumulative or not. Any thoughts on this?

I do not have an answer, but I am facing a similar situation. My idea is as follows: first thing to do is to extract the cartographer's local pose, and somehow pair it with the current trajectory, store pairs (pose,traj). Then, whenever we need to map the stored poses we request the current local to global transform and use it to map the stored positions to the current location. I need to research more into this as at this point I do not know if the transforms are cumulative or not. Any thoughts on this?

@blablebli-robots
After some research I found out the way that they track global pose of landmarks.
They are doing it by saving the time of the observation and then interpolating between the two closest(in time) trajectory nodes, the only problem I have is that due to trimming the observation become older then the first trajectory node and it stopped tracking the landmark global pose.
Please view this related issue I posted:
https://github.com/googlecartographer/cartographer_ros/issues/1425

Great, I see. So it should be possible then to maintain a parallel list of, in your case landmarks in mine a sub-trajectory, that it is not trimmed at any point, transforming only poses overtime using the new transforms. As if embedding the list/traj in the current landmarks/trajectory.

Great, I see. So it should be possible then to maintain a parallel list of, in your case landmarks in mine a sub-trajectory, that it is not trimmed at any point, transforming only poses overtime using the new transforms. As if embedding the list/traj in the current landmarks/trajectory. Of course, making sure it does not participate in any optimization at all.

I have a lot of global points which I need to track, avoid trimming them will cause high memory that I'm trying to avoid with the trimmer

I hear you, my case seems to be simpler then, but somehow related to yours. I need to track sub-trajectories over time, but need to make sure that all my selected points survive over time. So I will start by creating a "shadow" of trajectory_nodes_ in pose_graph.* to store my sub-trajectory. I will then transform this sub-trajectory in RunOptimization() after the Solve call, before the LandMark transforms. I still need to figure out how lots of other stuff, but I think this is where all happens as far as trajectory/landmark transforms over time.
What do you think?

Great, I see. So it should be possible then to maintain a parallel list of, in your case landmarks in mine a sub-trajectory, that it is not trimmed at any point, transforming only poses overtime using the new transforms. As if embedding the list/traj in the current landmarks/trajectory. Of course, making sure it does not participate in any optimization at all.

By sub-trajectory you mean multiple trajectory nodes?

I'd like to store robot's poses while moving from point A to point B during mapping and track poses from point A to point B over time, specially after optimizations and loop closures. So by sub-trajectory I mean the segment of the global trajectory corresponding to poses between A and B inclusive. I hope I have explained myself this time.
Cheers!

I'd like to store robot's poses while moving from point A to point B during mapping and track poses from point A to point B over time, specially after optimizations and loop closures. So by sub-trajectory I mean the segment of the global trajectory corresponding to poses between A and B inclusive. I hope I have explained myself this time.
Cheers!

 From now on you can track the trajectory nodes id's between nodeA and nodeB. If you don't have trimming involved I think it's no problem.

Yes you got it right. The main issue I am facing is precisely trimming, making it hard to even interpolate poses. I tried doing it externally but there is no way to deal with trimming as the metric properties from point A to point B change over time, specially in areas where mapping is trickiest. I am now trying to do it internally by discovering how the process works.


add run method to Pausable

Sonarqube has way too many bad recommendations. The violated rule isn't applicable to abstract classes, but that doesn't stop it from false positives


feat: assert last event

Changes made to the pop-api crate for the assert_last_event! macro in pop-drink

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 51.60%. Comparing base (4a7a320) to head (1e4b58a).

@@                       Coverage Diff                        @@
##           chungquantin/feat-psp22_example     #370   +/-   ##
================================================================
  Coverage                            51.60%   51.60%
================================================================
  Files                                   48       48
  Lines                                 4910     4910
  Branches                              4910     4910
================================================================
  Hits                                  2534     2534
  Misses                                2327     2327
  Partials                                49       49


getting file path

Hello, i have an input of type file, i want to get the path from the input to my python script, for example electron provides an additional input.files[0].path field that allows for this to happen, since the default web browser path would look like this c:/fakepath/filename.

I don't think it's possible. The workaround I personally picked is to use the tkinter to do that (https://pythonspot.com/tk-file-dialogs/) . As this is in the standard library, this is not a problematic dependency to manage.

I did the same as @brumar. It's not possible unless you actually do use Electron as the browser

For security reasons it is not possible to get the file path through the browser. Using the Tkinter library, you can easily do it as shown in the example below.
app.py
@eel.expose
def btn_ResimyoluClick():
	root = Tk()
	root.withdraw()
	root.wm_attributes('-topmost', 1)
	folder = filedialog.askdirectory()
	kamera_takip_arayuz.resimyolu = folder
	return folder

main.html


ReorientTetMesh and NC meshes

There is some problem with shared face orientation that is not resolved by ParMesh::ReorientTetMesh if the mesh is an NC mesh.
How to reproduce: in ex3p.cpp, add mesh->EnsureNCMesh(true) right after the serial mesh is loaded. Then run
mpirun -n 2 ./ex3p -m ../data/inline-tet.mesh -o 2

Output:
MFEM abort: triangle face orientation 1 is not supported! Use Mesh::ReorientTetMesh to fix it.
 ... in function: virtual const int* mfem::ND_FECollection::DofOrderForOrientation(mfem::Geometry::Type, int) const
 ... in file: fem/fe_coll.cpp:2649

This should be resolved by the work in https://github.com/mfem/mfem/pull/1046
cc: @mlstowell

Now that #1046 is merged, can we check if this is still an issue, @jakubcerveny ?

I can no longer reproduce the orientation error, so I think this issue can be closed.
However I do observe a problem on the processor boundary if the mesh is an NC tet mesh. The solution is wrong and takes a long time to "converge". I will continue looking into this in #2492.