make release:gen-payload command only mirror images with payload images.

[dev@62111d54b562 doozer]$ ./doozer  --group openshift-4.5 release:gen-payload --is-name 4.5-art-latest --organization openshift-release-dev --repository ocp-v4.0-art-dev
2020-08-03 14:45:43,902 INFO Initial execution (cwd) directory: /workspaces/doozer
2020-08-03 14:45:43,903 INFO Data clone directory already exists, checking commit sha
2020-08-03 14:45:43,968 INFO $0: ['git', 'status', '-sb'] - [cwd=/workspaces/doozer-working-dir/ocp-build-data]: Executing:cmd_gather
2020-08-03 14:45:43,982 INFO Time elapsed (hh:mm:ss.ms) 0:00:00.013735 in /workspaces/doozer/doozerlib/exectools.py:158 from /workspaces/doozer/doozerlib/gitdata.py:102:rc, out, err = exectools.cmd_gather("git status -sb") : $0: ['git', 'status', '-sb'] - [cwd=/workspaces/doozer-working-dir/ocp-build-data]: Executed:cmd_gather
2020-08-03 14:45:43,984 INFO $1: ['git', 'rev-parse', '--abbrev-ref', 'HEAD'] - [cwd=/workspaces/doozer-working-dir/ocp-build-data]: Executing:cmd_gather
2020-08-03 14:45:43,992 INFO Time elapsed (hh:mm:ss.ms) 0:00:00.007188 in /workspaces/doozer/doozerlib/exectools.py:158 from /workspaces/doozer/doozerlib/gitdata.py:111:rc, out, err = exectools.cmd_gather("git rev-parse --abbrev-ref HEAD") : $1: ['git', 'rev-parse', '--abbrev-ref', 'HEAD'] - [cwd=/workspaces/doozer-working-dir/ocp-build-data]: Executed:cmd_gather
2020-08-03 14:45:44,003 INFO Cloning config data from https://github.com/openshift/ocp-build-data.git
2020-08-03 14:45:44,009 INFO $2: ['git', 'clone', '--no-single-branch', '-b', 'openshift-4.5', '--depth', '1', 'https://github.com/openshift/ocp-build-data.git', '/workspaces/doozer-working-dir/ocp-build-data'] - [cwd=/workspaces/doozer] [env={'GIT_SSH_COMMAND': 'ssh -oBatchMode=yes', 'GIT_TERMINAL_PROMPT': '0'}]: Executing:cmd_gather
2020-08-03 14:48:00,602 INFO Time elapsed (hh:mm:ss.ms) 0:02:16.593120 in /workspaces/doozer/doozerlib/exectools.py:158 from /workspaces/doozer/doozerlib/gitdata.py:146:rc, out, err = exectools.cmd_gather(cmd, set_env=constants.GIT_NO_PROMPTS) : $2: ['git', 'clone', '--no-single-branch', '-b', 'openshift-4.5', '--depth', '1', 'https://github.com/openshift/ocp-build-data.git', '/workspaces/doozer-working-dir/ocp-build-data'] - [cwd=/workspaces/doozer] [env={'GIT_SSH_COMMAND': 'ssh -oBatchMode=yes', 'GIT_TERMINAL_PROMPT': '0'}]: Executed:cmd_gather
2020-08-03 14:48:00,740 INFO Using branch from group.yml: rhaos-4.5-rhel-7
2020-08-03 14:48:01,810 INFO Fetching latest image builds from Brew...
2020-08-03 14:48:17,041 INFO Fetching image archives...
2020-08-03 14:48:31,863 INFO Filtering out shipped builds...
2020-08-03 14:48:31,863 INFO Getting tags for 108 builds...
2020-08-03 14:48:37,287 INFO Fetching rpms in 310 images...
...
2020-08-03 14:50:03,099 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-ironic-ipa-downloader@sha256:57a3e5d48e7e658d3d9d6307785ac9022ac2ed4be9c6c951f4ebcf71dd1a652e to the public mirroring list with imagestream tag ironic-ipa-downloader...
2020-08-03 14:50:03,099 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-ironic-ipa-downloader@sha256:57a3e5d48e7e658d3d9d6307785ac9022ac2ed4be9c6c951f4ebcf71dd1a652e to the private mirroring list with imagestream tag ironic-ipa-downloader...
2020-08-03 14:50:03,100 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-ironic-ipa-downloader@sha256:37e96c0d9c70e5c04f441e92b69280bff84e44f4543003d437e451d7f8902d37 to the public mirroring list with imagestream tag ironic-ipa-downloader...
2020-08-03 14:50:03,100 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-ironic-ipa-downloader@sha256:37e96c0d9c70e5c04f441e92b69280bff84e44f4543003d437e451d7f8902d37 to the private mirroring list with imagestream tag ironic-ipa-downloader...
2020-08-03 14:50:03,100 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-node-tuned@sha256:7dfe664413f311f5de08e99852c74d08cb101f0062546f56176c0d864020ef53 to the public mirroring list with imagestream tag cluster-node-tuned...
2020-08-03 14:50:03,100 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-node-tuned@sha256:7dfe664413f311f5de08e99852c74d08cb101f0062546f56176c0d864020ef53 to the private mirroring list with imagestream tag cluster-node-tuned...
2020-08-03 14:50:03,100 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-node-tuned@sha256:559693a425e8bcbd8dde3e2fbed4d2e792c1bcf2e08fdf3892c3d3cad5c72d88 to the public mirroring list with imagestream tag cluster-node-tuned...
2020-08-03 14:50:03,101 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-node-tuned@sha256:559693a425e8bcbd8dde3e2fbed4d2e792c1bcf2e08fdf3892c3d3cad5c72d88 to the private mirroring list with imagestream tag cluster-node-tuned...
2020-08-03 14:50:03,101 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-node-tuned@sha256:a627e36d589e3480fb19d3815ebf3b0b841a01fe69f3500a5062cbec24b8de5d to the public mirroring list with imagestream tag cluster-node-tuned...
2020-08-03 14:50:03,101 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-node-tuned@sha256:a627e36d589e3480fb19d3815ebf3b0b841a01fe69f3500a5062cbec24b8de5d to the private mirroring list with imagestream tag cluster-node-tuned...
2020-08-03 14:50:03,101 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-csi-snapshot-controller@sha256:a0c5db58f724489fd757b39280d0c849ff86fb185b2b28e4a89e86a31c4bd8b8 to the public mirroring list with imagestream tag csi-snapshot-controller...
2020-08-03 14:50:03,101 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-csi-snapshot-controller@sha256:a0c5db58f724489fd757b39280d0c849ff86fb185b2b28e4a89e86a31c4bd8b8 to the private mirroring list with imagestream tag csi-snapshot-controller...
2020-08-03 14:50:03,101 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-csi-snapshot-controller@sha256:8ac0b42a9b832c9a9b63555f4ef0ca3497e570f2a97ba07e667b09250b57f3cc to the public mirroring list with imagestream tag csi-snapshot-controller...
2020-08-03 14:50:03,101 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-csi-snapshot-controller@sha256:8ac0b42a9b832c9a9b63555f4ef0ca3497e570f2a97ba07e667b09250b57f3cc to the private mirroring list with imagestream tag csi-snapshot-controller...
2020-08-03 14:50:03,101 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-csi-snapshot-controller@sha256:5a725a9d03a85e583f62d6a86e91193d25ab7429881bffd04513eb8f32ac30cb to the public mirroring list with imagestream tag csi-snapshot-controller...
2020-08-03 14:50:03,101 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-csi-snapshot-controller@sha256:5a725a9d03a85e583f62d6a86e91193d25ab7429881bffd04513eb8f32ac30cb to the private mirroring list with imagestream tag csi-snapshot-controller...
2020-08-03 14:50:03,101 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-aws-machine-controllers@sha256:b568c3a122debc597137c91ad2a730c90745dcb8d4c3cfbff190429e28a8b595 to the public mirroring list with imagestream tag aws-machine-controllers...
2020-08-03 14:50:03,101 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-aws-machine-controllers@sha256:b568c3a122debc597137c91ad2a730c90745dcb8d4c3cfbff190429e28a8b595 to the private mirroring list with imagestream tag aws-machine-controllers...
2020-08-03 14:50:03,102 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-docker-registry@sha256:6e32cdf6187638f9000620a1b0be7e8c8eecfdac096a3a042694b96f4a5313a2 to the public mirroring list with imagestream tag docker-registry...
2020-08-03 14:50:03,102 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-docker-registry@sha256:6e32cdf6187638f9000620a1b0be7e8c8eecfdac096a3a042694b96f4a5313a2 to the private mirroring list with imagestream tag docker-registry...
2020-08-03 14:50:03,102 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-docker-registry@sha256:01181d31f7fee136b00314d63220d22fc11c38ffb805a6dbb76e36243e858d66 to the public mirroring list with imagestream tag docker-registry...
2020-08-03 14:50:03,102 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-docker-registry@sha256:01181d31f7fee136b00314d63220d22fc11c38ffb805a6dbb76e36243e858d66 to the private mirroring list with imagestream tag docker-registry...
2020-08-03 14:50:03,102 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-docker-registry@sha256:a97254c6c35acaba16f0db20e7c000b62a15bb301a6ddde3ff2bb3552296daec to the public mirroring list with imagestream tag docker-registry...
2020-08-03 14:50:03,102 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-docker-registry@sha256:a97254c6c35acaba16f0db20e7c000b62a15bb301a6ddde3ff2bb3552296daec to the private mirroring list with imagestream tag docker-registry...
2020-08-03 14:50:03,102 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-telemeter@sha256:7995bd95abc4a2e1b92f573cfaf8bc2ecfdda1bf1858a94c098da32b83a4f72a to the public mirroring list with imagestream tag telemeter...
2020-08-03 14:50:03,102 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-telemeter@sha256:7995bd95abc4a2e1b92f573cfaf8bc2ecfdda1bf1858a94c098da32b83a4f72a to the private mirroring list with imagestream tag telemeter...
2020-08-03 14:50:03,102 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-telemeter@sha256:2acbf4cf6a66a1ea5e9c2ed0e2a8b290f967191173f38846d956fe49f37e5857 to the public mirroring list with imagestream tag telemeter...
2020-08-03 14:50:03,102 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-telemeter@sha256:2acbf4cf6a66a1ea5e9c2ed0e2a8b290f967191173f38846d956fe49f37e5857 to the private mirroring list with imagestream tag telemeter...
2020-08-03 14:50:03,102 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-telemeter@sha256:786a5b680940aab3350d2d17381b2a2b40de5c682d5662ab6d96159b495bba65 to the public mirroring list with imagestream tag telemeter...
2020-08-03 14:50:03,103 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-telemeter@sha256:786a5b680940aab3350d2d17381b2a2b40de5c682d5662ab6d96159b495bba65 to the private mirroring list with imagestream tag telemeter...
2020-08-03 14:50:03,103 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-ironic-static-ip-manager@sha256:304c0dc99812c8fa76a5671f3b8bf922b618a20680509a664011b0efda74ac50 to the public mirroring list with imagestream tag ironic-static-ip-manager...
2020-08-03 14:50:03,103 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-ironic-static-ip-manager@sha256:304c0dc99812c8fa76a5671f3b8bf922b618a20680509a664011b0efda74ac50 to the private mirroring list with imagestream tag ironic-static-ip-manager...
2020-08-03 14:50:03,104 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-ironic-static-ip-manager@sha256:8dc32d4ca2942abd784d4488d074219661353e64402aa1f6e193a5cdbaf50e36 to the public mirroring list with imagestream tag ironic-static-ip-manager...
2020-08-03 14:50:03,104 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-ironic-static-ip-manager@sha256:8dc32d4ca2942abd784d4488d074219661353e64402aa1f6e193a5cdbaf50e36 to the private mirroring list with imagestream tag ironic-static-ip-manager...
2020-08-03 14:50:03,104 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-openshift-apiserver@sha256:4d6169c31a91911e95268a3a82fc265be434dda2dd99bae887fb61e5ddcfc029 to the public mirroring list with imagestream tag openshift-apiserver...
2020-08-03 14:50:03,104 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-openshift-apiserver@sha256:4d6169c31a91911e95268a3a82fc265be434dda2dd99bae887fb61e5ddcfc029 to the private mirroring list with imagestream tag openshift-apiserver...
2020-08-03 14:50:03,105 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-openshift-apiserver@sha256:b03bc5b87eabfb710b0a71a284903a2135176e82af6490497755cfa0ee0eef71 to the public mirroring list with imagestream tag openshift-apiserver...
2020-08-03 14:50:03,105 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-openshift-apiserver@sha256:b03bc5b87eabfb710b0a71a284903a2135176e82af6490497755cfa0ee0eef71 to the private mirroring list with imagestream tag openshift-apiserver...
2020-08-03 14:50:03,105 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-openshift-apiserver@sha256:53f19248381c04b15c69502ed195699ec4ddc31a2f45c60ace87bf1ccb2a0a5f to the public mirroring list with imagestream tag openshift-apiserver...
2020-08-03 14:50:03,105 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-openshift-apiserver@sha256:53f19248381c04b15c69502ed195699ec4ddc31a2f45c60ace87bf1ccb2a0a5f to the private mirroring list with imagestream tag openshift-apiserver...
2020-08-03 14:50:03,105 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-prometheus-node-exporter@sha256:3105d1b8302758868b69cc3f8a790613f0e0c14688e6c432754c269a93d5d5e8 to the public mirroring list with imagestream tag prometheus-node-exporter...
2020-08-03 14:50:03,105 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-prometheus-node-exporter@sha256:3105d1b8302758868b69cc3f8a790613f0e0c14688e6c432754c269a93d5d5e8 to the private mirroring list with imagestream tag prometheus-node-exporter...
2020-08-03 14:50:03,105 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-prometheus-node-exporter@sha256:d8f8864a8579a0d7578278fc9cb5aa74092d5da3a42b1264e81a3814507d32a3 to the public mirroring list with imagestream tag prometheus-node-exporter...
2020-08-03 14:50:03,105 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-prometheus-node-exporter@sha256:d8f8864a8579a0d7578278fc9cb5aa74092d5da3a42b1264e81a3814507d32a3 to the private mirroring list with imagestream tag prometheus-node-exporter...
2020-08-03 14:50:03,105 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-prometheus-node-exporter@sha256:d2341196cfe11dfb420331adead871e26fbbbc6982183a212b2cb2d6176af183 to the public mirroring list with imagestream tag prometheus-node-exporter...
2020-08-03 14:50:03,105 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-prometheus-node-exporter@sha256:d2341196cfe11dfb420331adead871e26fbbbc6982183a212b2cb2d6176af183 to the private mirroring list with imagestream tag prometheus-node-exporter...
2020-08-03 14:50:03,105 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-kube-rbac-proxy@sha256:519ea4e1e8b8de8ad09c8b38941274e5e70af2d178b5754144b37a403b23cd2d to the public mirroring list with imagestream tag kube-rbac-proxy...
2020-08-03 14:50:03,106 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-kube-rbac-proxy@sha256:519ea4e1e8b8de8ad09c8b38941274e5e70af2d178b5754144b37a403b23cd2d to the private mirroring list with imagestream tag kube-rbac-proxy...
2020-08-03 14:50:03,106 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-kube-rbac-proxy@sha256:f24d19b9b881e54d652e7d4d36e7355f849a80ce085db8f8077d5f71d06da3c1 to the public mirroring list with imagestream tag kube-rbac-proxy...
2020-08-03 14:50:03,106 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-kube-rbac-proxy@sha256:f24d19b9b881e54d652e7d4d36e7355f849a80ce085db8f8077d5f71d06da3c1 to the private mirroring list with imagestream tag kube-rbac-proxy...
2020-08-03 14:50:03,106 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-kube-rbac-proxy@sha256:20f28e8d02298040c61546f3af59a15d0d9329906f0685edcd73a8576085632b to the public mirroring list with imagestream tag kube-rbac-proxy...
2020-08-03 14:50:03,106 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-kube-rbac-proxy@sha256:20f28e8d02298040c61546f3af59a15d0d9329906f0685edcd73a8576085632b to the private mirroring list with imagestream tag kube-rbac-proxy...
2020-08-03 14:50:03,106 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-machine-api-operator@sha256:48de721d2bf64514a7732493857d4566d542ed07a02622fde833987ad270c7d2 to the public mirroring list with imagestream tag machine-api-operator...
2020-08-03 14:50:03,106 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-machine-api-operator@sha256:48de721d2bf64514a7732493857d4566d542ed07a02622fde833987ad270c7d2 to the private mirroring list with imagestream tag machine-api-operator...
2020-08-03 14:50:03,106 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-machine-api-operator@sha256:eb1fc5afed7f1536a1645ac91bb33fc72989a8ebc66ddd418f1ba203103cd779 to the public mirroring list with imagestream tag machine-api-operator...
2020-08-03 14:50:03,106 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-machine-api-operator@sha256:eb1fc5afed7f1536a1645ac91bb33fc72989a8ebc66ddd418f1ba203103cd779 to the private mirroring list with imagestream tag machine-api-operator...
2020-08-03 14:50:03,106 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-machine-api-operator@sha256:cdb6197e6a55c9be317cdd057fd8ec7df469967421b6338b6ddac23b942a5a71 to the public mirroring list with imagestream tag machine-api-operator...
2020-08-03 14:50:03,106 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-machine-api-operator@sha256:cdb6197e6a55c9be317cdd057fd8ec7df469967421b6338b6ddac23b942a5a71 to the private mirroring list with imagestream tag machine-api-operator...
2020-08-03 14:50:03,106 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-kube-scheduler-operator@sha256:87bd226f209458b84ead56dcdde77f8a1e65b803b0e6f0d8b1fe4642b7061997 to the public mirroring list with imagestream tag cluster-kube-scheduler-operator...
2020-08-03 14:50:03,107 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-kube-scheduler-operator@sha256:87bd226f209458b84ead56dcdde77f8a1e65b803b0e6f0d8b1fe4642b7061997 to the private mirroring list with imagestream tag cluster-kube-scheduler-operator...
2020-08-03 14:50:03,107 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-kube-scheduler-operator@sha256:5f5337d44384491b0ac2507074c0f466b80f8cb97ad579d37297e4fa4e5ec058 to the public mirroring list with imagestream tag cluster-kube-scheduler-operator...
2020-08-03 14:50:03,107 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-kube-scheduler-operator@sha256:5f5337d44384491b0ac2507074c0f466b80f8cb97ad579d37297e4fa4e5ec058 to the private mirroring list with imagestream tag cluster-kube-scheduler-operator...
2020-08-03 14:50:03,107 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-kube-scheduler-operator@sha256:010253167b1e4afaca1411d71d40613ed2deea524dfaa89371650f314d9e8806 to the public mirroring list with imagestream tag cluster-kube-scheduler-operator...
2020-08-03 14:50:03,107 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-kube-scheduler-operator@sha256:010253167b1e4afaca1411d71d40613ed2deea524dfaa89371650f314d9e8806 to the private mirroring list with imagestream tag cluster-kube-scheduler-operator...
2020-08-03 14:50:03,107 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry@sha256:a44d196f28210286d7102f89a4cd82dd9bdb3a954e613964930dee9d5961d7ce to the public mirroring list with imagestream tag operator-registry...
2020-08-03 14:50:03,107 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry@sha256:a44d196f28210286d7102f89a4cd82dd9bdb3a954e613964930dee9d5961d7ce to the private mirroring list with imagestream tag operator-registry...
2020-08-03 14:50:03,107 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry@sha256:9cfaa8f6c3c8bc128500eeb5e44dfc31bd6e387bb1793daddd9f7f0cdcc1626c to the public mirroring list with imagestream tag operator-registry...
2020-08-03 14:50:03,107 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry@sha256:9cfaa8f6c3c8bc128500eeb5e44dfc31bd6e387bb1793daddd9f7f0cdcc1626c to the private mirroring list with imagestream tag operator-registry...
2020-08-03 14:50:03,108 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry@sha256:c0fed2fa9bd38b15f5962e4fac1e2972ffefa36bd206646bb29863517393b806 to the public mirroring list with imagestream tag operator-registry...
2020-08-03 14:50:03,108 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-operator-registry@sha256:c0fed2fa9bd38b15f5962e4fac1e2972ffefa36bd206646bb29863517393b806 to the private mirroring list with imagestream tag operator-registry...
2020-08-03 14:50:03,108 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-openshift-apiserver-operator@sha256:fd42755aa0a45e7e8c9bbe4b849b73b6e4bf009ee309c62acfdb3a5bf113f975 to the public mirroring list with imagestream tag cluster-openshift-apiserver-operator...
2020-08-03 14:50:03,108 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-openshift-apiserver-operator@sha256:fd42755aa0a45e7e8c9bbe4b849b73b6e4bf009ee309c62acfdb3a5bf113f975 to the private mirroring list with imagestream tag cluster-openshift-apiserver-operator...
2020-08-03 14:50:03,108 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-openshift-apiserver-operator@sha256:b3bffe0b34c237dc5fa9697fbe53553ec6727277181f094ed821ee8e32e04933 to the public mirroring list with imagestream tag cluster-openshift-apiserver-operator...
2020-08-03 14:50:03,108 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-openshift-apiserver-operator@sha256:b3bffe0b34c237dc5fa9697fbe53553ec6727277181f094ed821ee8e32e04933 to the private mirroring list with imagestream tag cluster-openshift-apiserver-operator...
2020-08-03 14:50:03,109 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-openshift-apiserver-operator@sha256:785fd3bc3e9892abbef29d65c0ba36bb6241d4cefecb993dd0bd014d5b3df84d to the public mirroring list with imagestream tag cluster-openshift-apiserver-operator...
2020-08-03 14:50:03,109 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-cluster-openshift-apiserver-operator@sha256:785fd3bc3e9892abbef29d65c0ba36bb6241d4cefecb993dd0bd014d5b3df84d to the private mirroring list with imagestream tag cluster-openshift-apiserver-operator...
2020-08-03 14:50:03,109 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-service-ca-operator@sha256:e4d1e194ed36bcd2cf76498e107bac3d3de14a598d276df845311c02b196548c to the public mirroring list with imagestream tag service-ca-operator...
2020-08-03 14:50:03,109 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-service-ca-operator@sha256:e4d1e194ed36bcd2cf76498e107bac3d3de14a598d276df845311c02b196548c to the private mirroring list with imagestream tag service-ca-operator...
2020-08-03 14:50:03,109 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-service-ca-operator@sha256:20a1318672d423d8045365e348ee5432694c88de328fcf378262b30a6d41c8cb to the public mirroring list with imagestream tag service-ca-operator...
2020-08-03 14:50:03,109 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-service-ca-operator@sha256:20a1318672d423d8045365e348ee5432694c88de328fcf378262b30a6d41c8cb to the private mirroring list with imagestream tag service-ca-operator...
2020-08-03 14:50:03,110 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-service-ca-operator@sha256:d908715bc7102d256dc4c00bb99db860d57c85a2c6a61928ded208b2fb63a00b to the public mirroring list with imagestream tag service-ca-operator...
2020-08-03 14:50:03,110 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-service-ca-operator@sha256:d908715bc7102d256dc4c00bb99db860d57c85a2c6a61928ded208b2fb63a00b to the private mirroring list with imagestream tag service-ca-operator...
2020-08-03 14:50:03,110 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-oauth-server@sha256:92e7da82c2a8122e7e23bf51f8fea2336c6f3f1a17fa7d2b0630b56a259e10ae to the public mirroring list with imagestream tag oauth-server...
2020-08-03 14:50:03,110 INFO Adding ppc64le image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-oauth-server@sha256:92e7da82c2a8122e7e23bf51f8fea2336c6f3f1a17fa7d2b0630b56a259e10ae to the private mirroring list with imagestream tag oauth-server...
2020-08-03 14:50:03,110 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-oauth-server@sha256:fe9bf0cd53c5c42b9375c40070b7ddfed5f2f5d6ff88647ffd981c5c1876826f to the public mirroring list with imagestream tag oauth-server...
2020-08-03 14:50:03,110 INFO Adding s390x image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-oauth-server@sha256:fe9bf0cd53c5c42b9375c40070b7ddfed5f2f5d6ff88647ffd981c5c1876826f to the private mirroring list with imagestream tag oauth-server...
2020-08-03 14:50:03,110 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-oauth-server@sha256:20a46944325a5c294283bd6e04830323949d3a65affff7fcd6a74cfe016d9bef to the public mirroring list with imagestream tag oauth-server...
2020-08-03 14:50:03,110 INFO Adding x86_64 image registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-oauth-server@sha256:20a46944325a5c294283bd6e04830323949d3a65affff7fcd6a74cfe016d9bef to the private mirroring list with imagestream tag oauth-server...
Unable to find tag azure-machine-controllers for arch ppc64le ; substituting cli image
Unable to find tag aws-machine-controllers for arch ppc64le ; substituting cli image
Unable to find tag azure-machine-controllers for arch ppc64le ; substituting cli image
Unable to find tag aws-machine-controllers for arch ppc64le ; substituting cli image
Unable to find tag ironic-ipa-downloader for arch s390x ; substituting cli image
Unable to find tag ironic-inspector for arch s390x ; substituting cli image
Unable to find tag kuryr-controller for arch s390x ; substituting cli image
Unable to find tag kuryr-cni for arch s390x ; substituting cli image
Unable to find tag azure-machine-controllers for arch s390x ; substituting cli image
Unable to find tag ironic-static-ip-manager for arch s390x ; substituting cli image
Unable to find tag ironic-machine-os-downloader for arch s390x ; substituting cli image
Unable to find tag ironic for arch s390x ; substituting cli image
Unable to find tag aws-machine-controllers for arch s390x ; substituting cli image
Unable to find tag keepalived-ipfailover for arch s390x ; substituting cli image
Unable to find tag ironic-hardware-inventory-recorder for arch s390x ; substituting cli image
Unable to find tag gcp-machine-controllers for arch s390x ; substituting cli image
Unable to find tag ironic-ipa-downloader for arch s390x ; substituting cli image
Unable to find tag ironic-inspector for arch s390x ; substituting cli image
Unable to find tag kuryr-controller for arch s390x ; substituting cli image
Unable to find tag kuryr-cni for arch s390x ; substituting cli image
Unable to find tag azure-machine-controllers for arch s390x ; substituting cli image
Unable to find tag ironic-static-ip-manager for arch s390x ; substituting cli image
Unable to find tag ironic-machine-os-downloader for arch s390x ; substituting cli image
Unable to find tag ironic for arch s390x ; substituting cli image
Unable to find tag aws-machine-controllers for arch s390x ; substituting cli image
Unable to find tag keepalived-ipfailover for arch s390x ; substituting cli image
Unable to find tag ironic-hardware-inventory-recorder for arch s390x ; substituting cli image
Unable to find tag gcp-machine-controllers for arch s390x ; substituting cli image

Codecov Report

Merging #256 into master will increase coverage by 0.00%.
The diff coverage is 9.09%.

@@           Coverage Diff           @@
##           master     #256   +/-   ##
=======================================
  Coverage   27.69%   27.69%
=======================================
  Files          30       30
  Lines        6236     6239    +3
  Branches     1243     1244    +1
=======================================
+ Hits         1727     1728    +1
- Misses       4449     4451    +2
  Partials       60       60

Impacted Files
Coverage Δ

doozerlib/cli/release_gen_payload.py
0.00% <0.00%> (ø)

doozerlib/image.py
13.79% <50.00%> (+0.17%)
:arrow_up:

Continue to review full report at Codecov.

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

alright @shiywang openshift-4.6-rhel-8 branch is finally merged, can you add payload image indicators in 4.6 now?

@sosiouxme  here is the PR: https://github.com/openshift/ocp-build-data/pull/661

/hold cancel


add support for $main and $aux built-ins

Currently, we have the built-in $rand which allows accessing a random value by index, e.g. $rand[0].
It would be convenient to do the same thing with the main and auxiliary execution traces and allow columns to be accessed by index rather than exclusively by their column identifier.
This requires:

[x] add lexing/parsing for $main[n], $aux[n], $main[n]', and $aux[n]' where n is a number. This should only be allowed in transition constraint expressions. The AST needs to be updated to allow the new column representation as well.
[x] update the IR to process and validate columns accessed this way when building the transition constraints graph

closed by #112


multi gpus for full finetune

I want to run the full.py on multi gpus, but only one GPU was used.
Using bfloat16 Automatic Mixed Precision (AMP)
Initializing distributed: GLOBAL_RANK: 0, MEMBER: 1/1
----------------------------------------------------------------------------------------------------
distributed_backend=nccl
All distributed processes registered. Starting with 1 processes
----------------------------------------------------------------------------------------------------

[rank: 0] Global seed set to 1337

Can you help me to solve this?

I don't have a good explanation, but maybe you accidentally set devices = 1 here?

No. All the settings are right. Btw, I use slurm to run the code. Is this the problem?

There might be SLURM (not Lit-GPT-specific) problem with requesting the GPUs. You could add the following PyTorch code at the top to see if the machine indeed has multiple GPUs that are usable in PyTorch:
import torch

num_gpus = torch.cuda.device_count()
print("Number of GPUs available:", num_gpus)


Plugin not working when running Umbraco:CMS:Hosting:Debug="false"

Hi!
We just upgraded the plugin to version 4..0.0 on a Umbraco 10.2.0 solution.
The overlay is not triggered when clicking the "Add" button while configuring the data-type, but we are just redirected to "/umbraco".
In the console we get this error:
Error: [$controller:ctrlreg] http://errors.angularjs.org/1.8.3/$controller/ctrlreg?p0=Our.Iconic.Prevalues.Packages     at umbraco-backoffice-js.js.v638016869865565329:25:168     at umbraco-backoffice-js.js.v638016869865565329:117:19     at ea (umbraco-backoffice-js.js.v638016869865565329:99:20)     at p (umbraco-backoffice-js.js.v638016869865565329:90:355)     at g (umbraco-backoffice-js.js.v638016869865565329:84:186)     at umbraco-backoffice-js.js.v638016869865565329:83:311     at Object.link (umbraco-backoffice-js.js.v638016869865565329:321:432)     at umbraco-backoffice-js.js.v638016869865565329:35:134     at Ca (umbraco-backoffice-js.js.v638016869865565329:108:361)     at p (umbraco-backoffice-js.js.v638016869865565329:92:340) '<div ng-include="propertyEditorView">'
We found out, that if we set Umbraco:CMS:Hosting:Debug="true", then it suddenly works...
Is it related to modification maybe?

@christianknu did you try the latest version? Is this still an issue?


When replacing nginx with higress, do you only need to modify the ingressClassName in ingress, or do you need to configure other content? The current configuration is 404 after higress.

There is no error log in the container  ,What else needs to be configured?

It has been resolved after consultation in the community group

DNS configurations need to be updated as well.


UI Designing

UI PAGES

[ ] Login Screen
[x] Role Selection Screen
[x] Teacher Wizard
[x] Student Wizard
[ ] Dashboard Teacher
[ ] Dashboard Student
[ ] Assignments Teacher
[ ] Assignments Student
[ ] Students Management
[ ] Course Management

UI Components

[ ] Navbar
[ ] Splash Screen
[ ] Logo
[ ] Buttons
[ ] Dropdown
[ ] Text areas
[ ] File input

Other

[x] Color Palette
[x] Font

UI Link (Requires free download)
https://lun-us.icons8.com/d/QS8VsoQN3UCJ7BY7iDmEKQ?page=tMHnVAOTykizxsXWzjEwVA&vp=486,751,1690,1368

Color Palette
Advice would be to set up global color variables.

I added color variables to the tailWing config file.

For the font, going to use Poppins.

Role selection screen:

Primary Button Component.

Normal
Hover
Disabled

Teacher Wizard
Darft.js is what will be replacing the description. Not sure if that can be styled to look like the concept.

I have designed NavBar component and login page as per my understanding. Let me know if I need to make any changes.

Next, I will go with student and teacher dashboards. From what I understand:
For student,

It will show the all classroom they have currently enrolled in. [List of cards I am thinking]
they will also have completed classrooms for the previous year or semester.[List of grayed cards I am thinking]
Join classroom button.

For Teachers (similar to students),

It will show the all classroom they have currently created and the number of students enrolled.
they will also have completed classrooms for the previous year or semester.
Create classroom button.

Let me know if I am missing something.

Are you looking for any help with these issues?


reprojecting nuts2

Hi all,
I'm trying to reproject a NUTS2 dataset and am getting the following error:
$ fio cat nuts2_2008.shp --dst_crs EPSG:4326 | fio load --format Shapefile --dst_crs EPSG:4326 output.shp
ERROR:fio:Exception caught during processing
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/fiona/fio/cat.py", line 586, in load
    first = next(source)
  File "build/bdist.linux-x86_64/egg/fiona/fio/cat.py", line 577, in feature_gen
    for feat in json.loads(text)['features']:
  File "/usr/lib/python2.7/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 369, in decode
    raise ValueError(errmsg("Extra data", s, end, len(s)))
ValueError: Extra data: line 2 column 1 - line 311 column 1 (char 775 - 550587)
Aborted!

It is the load command that is failing here, FWIW. Any suggestions would be welcome.

@gidden Looks like you probably need $ fio load --sequence.  $ fio cat produces GeoJSON features, one per line, and $ fio load expects a full FeatureCollectionby default.

Hi @geowurster, that worked beautifully. I'll close the issue.


libxgboost4j.so introduces dependency for libhdfs.so, failed to load in some environment.

latest xgboost master branch libxgboost4j.so introduces libhdfs.so dependency.
and it leads failure to load xgboost4j library because the libhdfs.so can't be found even its in the library path.
according to NativeLibLoader.java logic.

it tries to add nativePath=../../lib to java.library.path
2  load xgboost library from java.library.path
if 2 fails, load libxgboost4j.so from the fat jar's lib path.
however when libxgboost4j.so has new dependency libhdfs.so.0.0.0, using
below code System.load($LIB_FILE), it seems not to be able to load dependency libhdfs.so.0.0.0  even it is in java.library.path

  private static void loadLibraryFromJar(String path) throws IOException, IllegalArgumentException{
    String temp = createTempFileFromResource(path);
    // Finally, load the library
    System.load(temp);
  }

why nativePath defaults to ../../lib?
private static final String nativePath = "../../lib/";
when I run xgboost using spark over yarn,
the directory ../../ in each container is the application's root directory
ie: $YARN_APPCACHE/application_1529012605927_0680
but it does not contains a  lib sub-directory..
should I put both libxgboost4j.so and libhdfs.so on java.library.path?

the reason I hit that error because libhdf.so.0.0.0 is not in the standard lib path and I have to explicitly tell spark executor where to find it.
I worked around this by adding this config to pyspark/spark-shell
--conf "spark.executorEnv.LD_LIBRARY_PATH=$YOUR_DIR_HOLD_LIBHDFS_SO"
adding "--conf "spark.executor.extraJavaOptions=-Djava.library.path=$YOUR_DIR_HOLD_LIBHDFS_SO" does not work because
If a library is not explcitely loaded from java, i.e. a dependent library has to be used, then LD_LIBRARY_PATH has to be used to have that library available in the jvm.

why do we introduce libhdfs.so dependency in xgboost4j library?

can you show me the steps you prove it's introduced by xgboost4j?

ldd libxgboost4j.so
linux-vdso.so.1 =>  (0x00007fffb63b8000)
libjvm.so => /home/mine/installers/jdk1.8.0_92/jre/lib/amd64/server/libjvm.so (0x00007fcc7701d000)
libhdfs.so.0.0.0 => /opt/HADOOP_HOME/lib/native/libhdfs.so.0.0.0 (0x00007fcc76e0c000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fcc76af4000)
libm.so.6 => /lib64/libm.so.6 (0x00007fcc767f2000)
libgomp.so.1 => /lib64/libgomp.so.1 (0x00007fcc765cb000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fcc763b5000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fcc76199000)
libc.so.6 => /lib64/libc.so.6 (0x00007fcc75dd5000)
/lib64/ld-linux-x86-64.so.2 (0x00007fcc78503000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fcc75bd1000)

when I run xgboost directly over yarn, libhdfs.so.0.0.0 is required because xgboost directly read files from hdfs, when I run xgboost through spark over yarn, why do we need libhdfs.so.0.0.0?  without it, the container will throw libhdfs.so.0.0.0 shared library couldn't be found when it tries to load libxgboost4j.so explicitly from uber jar(jar-with-dependency)

how you built it? did you turn on https://github.com/dmlc/xgboost/blob/e939192978a0c152ad7b49b744630e99d54cffa8/jvm-packages/create_jni.py#L18 by any chance?
nanzhu@xxxxx:~$ ldd libxgboost4j.so
linux-vdso.so.1 (0x00007ffe1252e000)
libjvm.so => not found
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f320f394000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f320f092000)
libgomp.so.1 => /usr/lib/x86_64-linux-gnu/libgomp.so.1 (0x00007f320ee7c000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f320ec66000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f320ea48000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f320e69d000)
/lib64/ld-linux-x86-64.so.2 (0x0000560422b73000)

ah, yes, i turned hdfs on...

if you want xgboost to access HDFS data directly, you need to turn it on


Update confluence.go

replace url path
https://docs.atlassian.com/ConfluenceServer/rest/7.12.0/

Hi @glvnian
Thank you so much for this PR!!, but the Test Cases and the Coverage are failing 😞


Problems in pop/jazz music samples

Both McFerrin_Don't_worry.mei and Parker-Gillespie_ShawNuff.mei have problems with the rhythmic notation above the staff. The problems I see:

They need to be in a separate layer (sometimes they are, sometimes not)
I don't think @pname and @oct attributes are appropriate.  Maybe @loc?
Frequently, they're lacking @dur

Additionally, I see some issues with text in Parker-Gillespie_ShawNuff.mei.

Things that don't belong together shouldn't be combined in one <dir>, only separated by a line break (<lb>). As an example: MI(MAT) (trp.<lb/>alto) in measure 5 - where "MI(MAT)" should actually be "MI(MA7)" and part of something like <harm>BbMI(MA7)</harm>. However, I'm not sure how to write the chords, that's a little underspecified in MEI.
N.C. actually means "no chords" - should we put it in a <harm> as well?  It's structurally the same thing as a chord symbol - in the PDF, it typographically uses the font/size combination that is unique to chord symbols.

These problems (I think) originated with the initial conversion from MusicXML to MEI.  But, without access to the original, it's difficult to fix them all.
I fixed the dir/harm confusion for "N.C." and the <lb/> issue. But exact placement of the results may still be "off".


ISS overhead 🚀🛰👀

https://github.com/CCOSTAN/Home-AssistantConfig/blob/master/config/packages/space.yaml


Unideal results

Hello,
I have been trying to implement your code as a learning material recently.
However, I haven't achieved the same good results as shown in Figure 3 of your paper.
Could you please help me identify possible issues?
I have attached all 72 different angle images as follows, "Optimizing G only" and "Optimizing both G and z", respectively.
I believe the results corresponding to the given x-ray (same angle) are quite good (the top-left image), while there seems to be a noticeable discrepancy with the remaining 71 images.

I haven't adjusted any parameters and I applied the same knee dataset. I also used "01_xray0000" to generate images of other angles (the "model_best.pt" I used is exactly the 100,000th iteration).
Thank you very much for your help and time. I believe any insights from you would be greatly helpful, and I truly appreciate it!

Hi there,
Overall, the generated images for camera poses similar to those found in the training data look somewhat similar to what we obtained from the "optimizing G only" file. You can continue optimizing by increasing the PSNR threshold and you should get better results.
On the other hand, this blurriness is a common outcome in generative models, especially when they have limited capacity or training data. In our case, the dataset we used for training was relatively small compared to other datasets, which can contribute to this uncertainty.
I've included links to our models' weights in the readme. I hope this helps clarify the results you're observing.

Thank you so much for your response and assistance!
I used your model's weights to generate other angles images, and they look really great.
My results are obtained by setting the PSNR threshold to 50 and after 5000 iterations.
Could you please give me some advice on how to tune these parameters?
On the other hand, in your understanding, how should I improve the results obtained from "Optimizing both G and z"?
Seems like the model's still trying to figure out the 3D consistency due to the lack of latent structures.
Thank you again for your help, I greatly appreciate it!

Hi,
I used your chest model's weights to render other images through the "optimizing G only" file, yet I came across some difficulties that I wanted to discuss with you.
During the initial iterations of my experiment, the results unexpectedly look like knee samples rather than chest images.
I wonder if there might have been a mix-up with the weights, perhaps uploading another knee model.
Could you please take a moment to verify the uploaded weights, ensuring that they correspond to the chest model as intended?
Thank you very much for your time and attention to this matter!

Hello, I would like to ask how many pictures we need to render other parts when rendering the process render_xray_G.py

Hi, I used your chest model's weights to render other images through the "optimizing G only" file, yet I came across some difficulties that I wanted to discuss with you. During the initial iterations of my experiment, the results unexpectedly look like knee samples rather than chest images. I wonder if there might have been a mix-up with the weights, perhaps uploading another knee model. Could you please take a moment to verify the uploaded weights, ensuring that they correspond to the chest model as intended? Thank you very much for your time and attention to this matter!

I think that both of the links have the same model's weights - the knee model. I loaded both models and they have the same  load_dict['fid_best']=75.32657579762895.

嗨，我使用您的胸部模型的权重通过“仅优化 G”文件渲染其他图像，但我遇到了一些我想与您讨论的困难。在我实验的初始迭代中，结果出乎意料地看起来像膝盖样本而不是胸部图像。我想知道是否可能与重量混淆，也许上传了另一个膝盖模型。您能否花点时间验证上传的重量，确保它们与预期的胸部模型相对应？非常感谢您抽出宝贵时间关注此事！

我认为这两个链接具有相同模型的重量 - 膝盖模型。我加载了两个模型，它们具有相同的load_dict['fid_best']=75.32657579762895。
How do you get load_dict['fid_best']=75.32657579762895? I don't know how to get it, I hope you can teach me, thank you

嗨，我使用您的胸部模型的权重通过“仅优化 G”文件渲染其他图像，但我遇到了一些我想与您讨论的困难。在我实验的初始迭代中，结果出乎意料地看起来像膝盖样本而不是胸部图像。我想知道是否可能与重量混淆，也许上传了另一个膝盖模型。您能否花点时间验证上传的重量，确保它们与预期的胸部模型相对应？非常感谢您抽出宝贵时间关注此事！

我认为这两个链接具有相同模型的重量 - 膝盖模型。我加载了两个模型，它们具有相同的load_dict['fid_best']=75.32657579762895。
How do you get load_dict['fid_best']=75.32657579762895? I don't know how to get it, I hope you can teach me, thank you

For example from generate_G.py you need to load the checkpoint
    # Load checkpoint
    model_file = args.model
    print('load %s' % os.path.join(checkpoint_dir, model_file))
    load_dict = checkpoint_io.load(model_file)

and then you just print this parameter print(load_dict['fid_best'])

嗨，我使用您的胸部模型的权重通过"仅优化 G"文件渲染其他图像，但我遇到了一些我想与您讨论的困难。在我实验的初始迭代中，结果出乎意料地看起来像膝盖样本而不是胸部图像。我想知道是否可能与重量混淆，也许上传了另一个膝盖模型。您能否花点时间验证上传的重量，确保它们与预期的胸部模型相对应？非常感谢您抽出宝贵时间关注此事！

我认为这两个链接具有相同模型的重量 - 膝盖模型。我加载了两个模型，它们具有相同的load_dict['fid_best']=75.32657579762895。你如何得到 load_dict['fid_best']=75.32657579762895？我不知道怎么得到它，我希望你能教我，谢谢

例如，您需要从render_xray_G.py加载检查点
    # Load checkpoint
    model_file = args.model
    print('load %s' % os.path.join(checkpoint_dir, model_file))
    load_dict = checkpoint_io.load(model_file)

然后你只需打印这个参数 print（load_dict['fid_best']）

Thank you very much for your answer. I also have a problem, in my training with mednerf and graf, the kid_best I get is always mednerf is better than graf. I want to know if you have tried training the code provided by the author. If you have tried it and got good results, can you teach me

嗨，我使用您的胸部模型的权重通过"仅优化 G"文件渲染其他图像，但我遇到了一些我想与您讨论的困难。在我实验的初始迭代中，结果出乎意料地看起来像膝盖样本而不是胸部图像。我想知道是否可能与重量混淆，也许上传了另一个膝盖模型。您能否花点时间验证上传的重量，确保它们与预期的胸部模型相对应？非常感谢您抽出宝贵时间关注此事！

我认为这两个链接具有相同模型的重量 - 膝盖模型。我加载了两个模型，它们具有相同的load_dict['fid_best']=75.32657579762895。你如何得到 load_dict['fid_best']=75.32657579762895？我不知道怎么得到它，我希望你能教我，谢谢

例如，您需要从render_xray_G.py加载检查点
    # Load checkpoint
    model_file = args.model
    print('load %s' % os.path.join(checkpoint_dir, model_file))
    load_dict = checkpoint_io.load(model_file)

然后你只需打印这个参数 print（load_dict['fid_best']）

Thank you very much for your answer. I also have a problem, in my training with mednerf and graf, the kid_best I get is always mednerf is better than graf. I want to know if you have tried training the code provided by the author. If you have tried it and got good results, can you teach me

I tried the code, but just with fid_best mode. And I am not sure why you want graf to be better than mednerf... That is the purpose of the paper that mednerf is supposed to be better than graf?

Hi, I have updated the weights to the models. Indeed mistakenly weights were from the same model, but that's corrected now

嗨，我已经更新了模型的权重。确实错误地砝码来自同一模型，但现在已经纠正了

Thank you for sharing. I still have some questions. When we train a knee model, for example, do we input 5 sets of data with a total of 360 pictures? I tried it out, trained 10,000 rounds, and trained with 4090D, which took over a dozen hours. However, the minimum value of fid during training is 94.69, and the minimum value of kid is 0.0757. I would like to know how you trained to achieve the lower fid in the paper. I used default.yaml directly. Maybe there's something wrong with my training. I hope you can guide me

Hi, you'll need to train it for longer. We trained both chest and knee models for 100,000 iterations

嗨，你需要训练更长的时间。我们训练了胸部和膝盖模型进行 100,000 次迭代

Thank you for your answer. Could you share the original data set of DRR images generated from CT scan? I didn't find it in the paper link

嗨，你需要训练更长的时间。我们训练了胸部和膝盖模型进行 100,000 次迭代

Sorry, actually I used 100,000 iterations, I was wrong in the above answer, but the fid_best in the iteration process is only 94.69, which seems to be much higher than what you mentioned in your paper. I want to know if your yaml during training is default.yaml


Shell Command Uninstall 'code' from PATH nukes shell PATH

Does this issue occur when all extensions are disabled?: Don't know

VS Code Version: 1.83.0
OS Version: Apple M1 Pro Ventura Version 13.5.2

Steps to Reproduce:

Run Shell Command: Install 'code' from PATH
Run Shell Command: Uninstall 'code' from PATH

This nuked my PATH completely. I had nothing but builtin commands to recover my shell. The request for elevated permission should have been a red flag to abort.
I'm happy to take a look at this repo and find out how/if it happened via vscode if someone can helped me get started. I searched this repo and couldn't find anything related to that command. I don't even know what files vscode manipulated to edit the PATH in the first place.

I figured this out. Copied and pasted these instructions into my zshrc and didn't see the forward slash. PEBCAK.


gqq on multiline comment results in infinite loop

Hey 👋 ,
Sample test.ts:
 /*
 * arstarstarstarstarstarstarstarstarstarstarstarsienoeinoeinoneoarstarstarstarstarstarstarstarstarstarstarstarsienoeinoeinoneoarstarstarstarstarstarstarstarstarstarstarstarsienoeinoeinoneoarstarstarstarstarstarstarstarstarstarstarstarsienoeinoeinoneo
 */

Issuing gqq on the middle (long) line run an infinite loop (CPU core maxed out, "gqq" flashing in the cmd line).
Somewhat related to https://github.com/HerringtonDarkholme/yats.vim/issues/209 I guess.
I suspect this is a bug in the Fixedgq function.
Side note: It seems that the Fixedgq function actively dismisses formatting multiline comments. But that's precisely why I use gqq for; my code formatting needs are handled by prettier. I would prefer it for my syntax files to not mess with that.
Thanks!

I'm also seeing this, after taking a peek at #216 I'm curious if #212 may have introduced this as well?
If anyone else is using this via vim-polyglot using 05e21a9e252b283b2d71568ad3b671d7f28fe0bc gets things rollin' again!

At least for me this is caused by using the neovim-treesitter highlighting. When this is active you can no longer query the current syntax group using synId, which yats#IsInMultilineComment depends on to work.
There is some discussion around this in https://github.com/nvim-treesitter/nvim-treesitter/issues/1228, it seems we'd need do something custom for treesitter to make this work. In the meantime adding an option to disable the custom formatter as suggested in #247 could be a good workaround.


Add client and server timeouts to rpc

This is an implementation of the suggested feature mentioned here: https://www.notion.so/Full-support-for-RPC-timeouts-592cd7903cc84a049be11abfe778d5ce
There are still some additional tests missing but the basic concept would be to add to arguments to all rpc clients (standalone and dependency provider):

timeout: will raise a timeout if when the total roundtrip time is exceeded (raised in at the callers machine)
delivery_timeout: Uses rabbitmqs "expiration" to remove undelivered messages from the server.

I built in logic to try and prevent race conditions (message removed from server and client is still waiting forever for an answer).
As always there are a few open questions I'd like to discuss with the maintainers (@mattbennett ?):
The current implementation no longer uses the socket timeout on the standalone rpc client (as suggested in the roadmap).  However, it now relies on the timeout being raised by the rpc client.  Previously (as far as I can tell) the standalone client did not rely on eventlet at all, but now the rpc client uses this to implement timing out after waiting for a reply for a while.  The question is whether this is ok, or if this was a conscious decision to allow non-monkeypatched clients to still use the standalone rpc client.

For now though people rely on it working without a monkey patch. Can you implement a native-thread based timeout mechanism?

I used the builtin "timeout" argument in the consumer and added a test test_timeout_with_multiple_calls for the scenario mentioned in https://www.notion.so/Full-support-for-RPC-timeouts-592cd7903cc84a049be11abfe778d5ce (regarding the standalone rpc proxy implementation).
If this is not enough I can try to implement a threading based approach (I tried that first but had problems as there's no easy way to kill native threads in python which caused problems for me trying to implement a threading based timeout ... I'm admittedly the opposite of proficient when it comes to using native threads in python though).

any update on this PR. I think timeout on RPC seems to be a good idea

@chewfred we're waiting for the nameko 3 release (sorry I can't find the thread where we decided this).  After 3.0 get's out of rc we'll complete this.

Hi folks!
Will timeouts be supported in 3.0?
Thx.


app.src.script ignored

Yaws won't compile with rebar3 but works fine with rebar. The reason is that YAWS has a yaws.app.src.script that must run before {pre_hooks, [{compile, "./scripts/rebar-pre-script"}]}. I think what is happening is because yaws.app.src already exists the yaws.app.src.script does not run. So the behavior is different between rebar and rebar3.

So I had a look at the code and it looks like its not being ignored its just not being run before the pre_hook and will only get called once the a call to compile the .app.src to make is too late. So not sure what to do here. YAWS seems to rely heavily (both via Autotools and rebar) on the app.src.script being evaluated before anything else

This may require changes to yaws... It doesn't make sense to me to move it just for yaws. I'll look at how yaws uses it though.

Sure. If you have time have a look and let me know what you think. Else you can close this issue

Actually this works for me, are you using https://github.com/klacke/yaws ?

Oh, partially lied, I had to remove {sub_dirs, ["rel"]}. and {src_dirs, ["src", "examples/src"]}

Also I just made https://github.com/rebar/rebar3/pull/654 which has fixes for .app.src.script uses.

Should we consider this resolved?

I think so. Was waiting for @josephDunne to reply.

Sorry wasnt aware I was to reply. So you had to make changes to yaws to work with rebar3..so I should open an issue on the Yaws repo?

Yes, thanks this can be resolved. the master branch of rebar3 works with yaws. Thank you <3


Grep for temporary failures and retry.

Following a suggestion from @TheLortex this PR introduces a naive way of retrying on temporary failures. The point is to introduce a small change and see if the retry mechanism addresses #103 - if it does, we can proceed towards a solution that is more robust.

Thanks for this PR. My main comment is about extracting the retry loop in a recursive function, so that we can retry 3 or 4 times instead of once.

@novemberkilo
Looking at existing failures in docs CI, I also see (for example in https://docs.ci.ocaml.org/job/2023-04-10/161235-voodoo-prep-11de8a) Disconnected: Switch turned off.
I don't know where it's coming from but won't be handled by the current scheme as it doesn't appear in the logs.
One thing I suspect is the let** _ = Current_ocluster.Connection.run_job ... in body won't execute if run_job returns an error. In that case the error should also be considered as temporary and go in the retry loop.

@TheLortex I have updated the PR along the lines of your feedback. I am now trying to figure out how best to test this and I'm wondering how to mock the various things that go into Prep.build ... or whether refactoring the function so that I can avoid (most of) the mocking is the way to go. I'd appreciate any thoughts you may have on the matter. Thank you :)


Removing bad images

updated notebook added in new PR https://github.com/scikit-beam/scikit-beam-examples/pull/52
closing this due to merge conflicts


Fix issues by testing with latest Choreo Console

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

@shaniR It seems there are more correctness and consistency issues in the first part of the page too. Please check them as well.


[Bug]  REST API  GET /batches/{batchId} return inconsistent

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the bug
Deployed two kyuubi servers, provide a unified external rest api through load balancing.
I submitted a batch task and got the task status through /api/v1/batches/{batchId} polling.
From the log below, all requests are sent to a kyuubi server with same ip:
2023-02-24 16:14:23.726 status=200, the normal request, jobState is running
2023-02-24 16:15:01.045 Invalid batchId
2023-02-24 16:15:01.046 status=404, the abnormal request
2023-02-24 16:18:14.848 status=200, the normal request, jobState is finished
Repeated testing found that this phenomenon occurs at the end of the job.
2023-02-24 16:14:23.726 INFO org.apache.kyuubi.server.http.authentication.AuthenticationAuditLogger: user=401(auth:BASIC)	ip=xxx.xxx.7.74	proxyIp=null	method=GET	uri=/api/v1/batches/7c1a4b85-f396-4f79-a2b8-e63348d9c4d7	params=null	protocol=HTTP/1.1	status=200
2023-02-24 16:15:01.045 ERROR org.apache.kyuubi.server.api.v1.BatchesResource: Invalid batchId: 7c1a4b85-f396-4f79-a2b8-e63348d9c4d7
2023-02-24 16:15:01.046 INFO org.apache.kyuubi.server.http.authentication.AuthenticationAuditLogger: user=401(auth:BASIC)	ip=xxx.xxx.7.74	proxyIp=null	method=GET	uri=/api/v1/batches/7c1a4b85-f396-4f79-a2b8-e63348d9c4d7	params=null	protocol=HTTP/1.1	status=404
2023-02-24 16:15:12.498 INFO org.apache.kyuubi.operation.BatchJobSubmission: Monitoring submitted SPARK batch[7c1a4b85-f396-4f79-a2b8-e63348d9c4d7] job: spark-080f7446308347ab84c1fb81f1713e33
2023-02-24 16:18:14.848 INFO org.apache.kyuubi.server.http.authentication.AuthenticationAuditLogger: user=401(auth:BASIC)	ip=xxx.xxx.7.74	proxyIp=null	method=GET	uri=/api/v1/batches/7c1a4b85-f396-4f79-a2b8-e63348d9c4d7	params=null	protocol=HTTP/1.1	status=200

Affects Version(s)
branch-1.7
Kyuubi Server Log Output
No response
Kyuubi Engine Log Output
No response
Kyuubi Server Configurations
No response
Kyuubi Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
[ ] No. I cannot submit a PR at this time.

Please provide your kyuubi-defauls.conf

You need an RDBMS, e.g. MySQL to store the batch job metadata, so all Kyuubi instances can know all batch jobs.

@pan3793  You mean kyuubi server needs an RDBMS as metadata storage? How to configure, I did not find relevant information in the document.

But from the log, all requests are sent to one kyuubi server, and no request is made to another.

It's called metadata, the name is borrowed from Livy
https://kyuubi.readthedocs.io/en/master/deployment/settings.html#metadata

also cc @turboFei


Add Azure Blob Storage Delete operation doc

Please follow this checklist before submitting:

[x] Read the contribution guide
[x] Commands include options for Linux, MacOS, and Windows within codetabs
[x] New file and folder names are globally unique
[x] Page references use shortcodes instead of markdown or URL links
[x] Images use HTML style and have alternative text
[x] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
Adds documentation for the delete operation of the Azure Blob binding.
Issue reference
#1277

Since this functionality won't be released until Dapr v1.2, please retarget PR to the v1.2 branch

Unfortunately it slipped through creating the necessary docs PR.
The functionality should already be available in version 1.1.0.
https://github.com/dapr/dapr/releases/tag/v1.1.0
https://github.com/dapr/components-contrib/issues/681

Since this functionality won't be released until Dapr v1.2, please retarget PR to the v1.2 branch

Unfortunately it slipped through creating the necessary docs PR.
The functionality should already be available in version 1.1.0.
https://github.com/dapr/dapr/releases/tag/v1.1.0
dapr/components-contrib#681

Sounds good, thanks for the clarification!


We recommend that you add an LP permission group

I don't see the permissions for 'custommap' when configuring permissions for LP permission groups, so please add support for LP permission groups

Thanks for your message, the plugin is now updated and has a permission custommaps.custommap to use /custommap command. You can also enable and disable this in config.yml if you want.


[WIP] use ipython.parallel to bootstrap dask.distributed

Currently running the test with a > 2 engines gives a zmq TypeError: context must be specified. I'm stuck on this at the moment.

Need to add ipython to travis.ci and skip the test appropriately if library is not found.  I wouldn't add this to requirements.

Fixes #119 cc @phrrngtn

I made cowlicks/dask#1 with small changes that allow the provided test to pass.

It works! https://travis-ci.org/ContinuumIO/dask/jobs/62754132#L894

We are going to wait to merge this until after the next dask release. And after we have abstracted what serializer we are using. Hopefully cloudpickle will solve our problems.

Okay ipcluster setup/teardown is now managed in test_ipython_utils.py I ended up just parsing stdout/stderr from the process since there was a nose dependency buried in the ipyparallel setup/teardown.

OK, this looks good to me.  Merging.


build: Remove IonIcons

:tada: This PR is included in version 5.3.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Build started failing recently

I think this might be due to a regression in a dependency. Not sure though.

fixed by https://github.com/nolanlawson/relational-pouch/pull/38


RPC crashes on simulate_transaction

Running v1.14.17-jito, the RPC periodically crashes with:
ERROR solana_metrics::metrics] datapoint: panic program="validator" thread="solRpcEl" one=1i message="panicked at 'simulation bank must be frozen', runtime/src/bank.rs:4077:9" location="runtime/src/bank.rs:4077:9" version="\"1.14.17 (src:devbuild; feat:3488713414)

todo:

run 1.14.16-jito and v1.14.17 vanilla client to determine if issue is upstream

I wonder if that's simply calling too early and there is a missing protection in the solana validator. I can repro this by sending a transaction early on a solana-test-validator with a finalized commitment.


this library is a long time coming in android world.

Thank You for this library.
how can I adjust duration of slide on screen?

Slide duration is controlled by the playlists.

got it thank you!


[10.x] Eloquent & Query Builder last() methods

Now it is in the right branch, I expect! 😄
This pull request adds last() method to Eloquent & Query Builder.
People were using latest()->first() and I think it could be helpful.
Also, the use of latest()->first() is actually a bad practice when you want the last record of a given table, because it could return unexpected results on records created at same timestamp (literally returning the first of the last).
This PR also solves this, adding an optional parameter to latest() method called primaryKey. When it is set to true, Eloquent will getKeyName() instead of use created_at, while default Query Builder will always use defaultKeyName().
It also works for model relationships, of course.
Examples:

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Add Page For Configuring Options Set On Signup

Please add a template for configuring options that are set on the signup page. You can add fields to the signup page, but there doesn't appear to be any way to modify them after creation except by making your own page.
An option should be added to access a similar page as a second step after OAuth so that users can specify needed fields, such as birthday or location.

Do you mean something like a user profile page?
...if this is the case, I'm not sure we could be general enough to be good for everyone.
Why don't you create your profile page with aldeed:autoform or similar?
I think Telescope is doing it like that...


Remove dropdown from #177 (New documentation experience).

While the big button looks nice, hiding documentation in submenus make some documentation impossible to discover without clicking everywhere.
just form the top of your head if you are a new contributor:

Where is the doc for Jupyter_core ?  Architecture  or deployment ?
What's the difference between jupyterHub and Deployment ?
Why is Lab not in Interfaces it's only an interface AFAICT.

My take on that is to expand the dropdown by default So that user can easily find the project they are looking for instead of having to click 9 categories.

Let's look at these categories with Brian next week. There's a few things that we should swap around from submenus. There were some design elements from Matlab and Apple docs that this was targeting. We should make the new contributor comfortable from the start.
@cameronoelsen @charnpreetsingh Let's think about a block which will support access to all projects by name (A to Z) or context search. @Carreau I'm going to assign myself for now so it doesn't fall off my radar.

Even if we fix categories, I think that having submenus hidden by default is the wrong choice.
Or at least there should be :

Either more indication that there are submenues
Or More top level direct access to some categories.

@willingc Will you be around next week or will you be at the dev meeting?

Hi @charnpreetsingh, I'll be at the dev meeting but we can try to have a call with Brian. Would you and @cameronoelsen brainstorm some options for a visual indicator for a submenu (perhaps in the lower right corner of each category box). Thanks!

@willingc Sounds good, I will work with him on some ideas.

The idea for these dropdowns came from the Mathematica Documentation, which is the best large scale technical language documentation I have ever seen:
http://reference.wolfram.com/language/
Some of the important points:

Within 2-3 clicks you can end up looking at exactly what you want - it is really spectacular in this respect and I encourage you to play with it.
The documentation is organized around what the user is trying to do, rather than how Mathematica is written and organized as a code base.
They spent a significant effort/time working on how to organize their content into a clean hierarchy.
You can't pull that off without significant user testing of the information architecture.

Our intent with the documentation landing page and the Sphinx theme redesign is to set the visual design. But for everything to work, we will have to follow up with a very significant information/content reorganization (hence the hiring of the technical writer). I have started to gather resources and approaches for organizing large scale content to help us approach that in a systematic manner. One of the main pushes I would like to make in that reorganization is to begin organizing our documentation not around repos (which users don't care/know about) to a set of cleanly organize hierarchical topics. A great example would be a general area like this:

Working with Notebook Documents

Converting notebooks to other formats
The Notebook document format
Notebook metadata

A user wouldn't know or care that these three topics span many different repos (nbformat, nbconvert, notebook, jupyterlab).
I agree that the current organization of the cards and submenus is confusing. I basically told @cameronoelsen "make something up for now" and for that level of treatment I think he did a great job. But I fully agree with all the points you made about particular things being in add places though.
The original thinking for hiding content behind dropdowns came from two sources:

The efficacy of the Mathematica docs.
The idea that too many choices at a given level makes it difficult for a user to find content.

However, a quick search for research in this area shows that 2) might not be justified:
This study found evidence that a flat approach works quite well, but that other hierarchy shapes also work well:
http://www.surl.org/examining-the-effects-of-hypertext-shape-on-user-performance/
This book looks to be highly regarded, but a longer read:
http://www.uis.edu/webservices/wp-content/uploads/sites/8/2013/02/Designing_for_Scent.pdf

But, wolfram have 10 if not more categories per box. Seeing the amount of categories we have I'm going to say that 2 to 3 click is 1 to 2 click too many in most cases. I'm fine with some things being hidden or under a submenu. But let's look at 1 of the wolfram categories:

One of this panel could host and link to all the current links we currently have without having to click through N submenus.
Collapsing is useful when you have too much on screen. but we don't have too much yet so collapsing is adding extra burden on the user.
Most of the studies you link to point to at least testing with 64 elements. Most of the case made are for contents that are more than twice the number of links we have.

Yep, we may not have enough links that the nested approach is needed. However, that isn't completely obvious to me that we won't end up with 50-100 secondary level topics. I think we should proceed with the information architecture design (what our appropriate top-level, secondary, tertiary topics) and let that determine what type of UI is appropriate. If the number of secondary topics is reasonable I am fine removing the dropdowns. Also fine with doing some redesign in the meantime to expand this content.

Yep, we may not have enough links that the nested approach is needed. However, that isn't completely obvious to me that we won't end up with 50-100 secondary level topics. I think we should proceed with the information architecture design (what our appropriate top-level, secondary, tertiary topics) and let that determine what type of UI is appropriate. If the number of secondary topics is reasonable I am fine removing the dropdowns. Also fine with doing some redesign in the meantime to expand this content.

That seem like a good plan. I agree that if number of links increase menus are necessary. But if possible promoting things to top level would be great !
Thanks !

@ellisonbg @Carreau Let's discuss at the team meeting. I wonder if we could combine the Education block with JupyterHub since right now only nbgrader is under education. That would free up a block to use as A to Z projects where all the projects could be accessed if the block is clicked.

Since this ticket has been inactive for three years, I'm going to close as stale. If you'd like to continue the discussion, feel free to chime in.


Added myself as a Mentor

Provide your information
Name: Anirudh Panda
LinkedIn: Anirudh Panda
Twitter: Anirudh Panda
About: I am an aspiring full-stack web developer and an Open Source Geek
Why do you want to become a mentor (optional)
I would love to help beginners to start their Open Source journey. My community Opentek is exclusively made for that

@AnirudhPanda hey, if you have any projects please send the pr or dm me i will add it.

@AnirudhPanda hey, if you have any projects please send the pr or dm me i will add it.

Hey I have added my project Opentek in the Readme


watchNamespace only processes one namespace when multiple are specified

Describe the bug
Deploying an AGIC to watch multiple namespaces only processes one namespace. Testing each namespace independently does work.
To Reproduce
Create WAF V2 Application Gateway with 2 replicas
Configure aaPodIdentity with Reader and Contributor roles in IAM for AG
Create an AGIC with aaPodIdentity, rbac enabled: true, and watchNamespace: test1,test2
Ingress Controller details
Tried with AGIC version 0.8.0 & 0.9.0
Azure controller logs show it's recognizing the configuration with this:
'Ingress Controller will observe the following namespaces:test1,test2'
Setting APPGW_VERBOSITY_LEVEL to 5 doesn't mention the other namespace after outputting the observation line above. It continues processing only one namespace and completes successfully.
I'm able to configure the AG with each of the namespaces independently, but not at the same time with multiple namespace. I reviewed the ingress resources and configured them with different domains to rule out conflicts.

**Update
I tried again with AGIC 0.10.0 and I'm still unable to get multiple namespace support working. Here's the example and test ingress resources used along with the helm config. Our use case is a staging and production namespaces with the same applications.
example-ing.txt
test-ing.txt
helm-config-debug-redacted.txt
installed with:

helm install --name debug-azure-ingress --version 0.10.0 -f helm-config-debug.yaml application-gateway-kubernetes-ingress/ingress-azure

AGIC version

0.10.0
AG with WAF V2

Aks cluster version

1.14.6

helm version

v2.15.2

@draychev
Setting "KUBERNETES_WATCHNAMESPACE": "" in the AGIC config map successfully watches and process all ingress resources in all namespaces, but setting it to test,example only watches the test namespace.
Is there a known bug for this and is there anything I can use in addition to "APPGW_VERBOSITY_LEVEL" to get to the bottom of this?

@abenck Thanks for helping troubleshoot this.
I'm working on this - will have a version for you to test with soon.

@draychev Great, thank you! If you need any additional info please let me know.

Hi @abenck,
Thanks for your patience with this issue.
We released version 0.10.1-rc1 of AGIC, which we believe addresses the issue you ran into:  https://github.com/Azure/application-gateway-kubernetes-ingress/releases/tag/0.10.1-rc1
Would you be so kind to upgrade to this release candidate: 0.10.1-rc1
helm repo update
helm search -l application-gateway-kubernetes-ingress
helm list
helm upgrade <XYZ> \
    --version 0.10.1-rc1 \
    application-gateway-kubernetes-ingress/ingress-azure \
    --debug

Would you be so kind to test the new version and let us know whether it was able to observe the listed namespaces?

Hey @draychev, thank you for handling this! I'll deploy a testing environment to try this out later today and get back to you.

Looks like the Application Gateway is configured for both namespaces, thanks for fixing this!


Feedback for “Radial Menu”

Would it be possible to enable a key plus a mouse button for the radial menu shortcuts. Alias had a very elegant solution that used the ctrl + shift key and one of the three mouse buttons to bring up radial menus.  This was incredibly fast as your left pinky is always hovering over the ctrl or shift key. Hold down ctrl shift, plus mouse button one, two or three and swipe in the direction of the command then release the mouse button.   Three menus ( or more depending on how many mouse buttons you have ) always directly accessible without changing your hand positions at all.
Thanks
Chris

Thank you for the feedback. The idea of invoking the radial menu with modifier keys and mouse buttons is good. I'll pass it on to the development team.

Thanks, I was a 3D modeler at Disney for 8 Years, and we used Alias for a lot of creature modeling at the time. All the modelers there used the crtl + Shift and 3 mouse buttons for their radial shortcuts. It allowed us to have an uncluttered viewport and instant access to all our most used functions. You can fit just about everything you need in 3 radial menus.
Thanks
Chris

From: Shinji esk. @.>
Sent: Sunday, October 15, 2023 10:22 PM
To: shinjiesk/plasticity-unofficial-document @.>
Cc: ckc1010 @.>; Author @.>
Subject: Re: [shinjiesk/plasticity-unofficial-document] Feedback for “Radial Menu” (Issue #12)
Thank you for the feedback. The idea of invoking the radial menu with modifier keys and mouse buttons is good. I'll pass it on to the development team.
—
Reply to this email directly, view it on GitHubhttps://github.com/shinjiesk/plasticity-unofficial-document/issues/12#issuecomment-1763745455, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADGEH7XDUETHI6RFEZAS7XDX7TADHAVCNFSM6AAAAAA543TLO2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRTG42DKNBVGU.
You are receiving this because you authored the thread.Message ID: @.***>


Add Libya processing epidemology setup in pipelines/

Following the steps here:
https://github.com/open-covid-19/data/blob/master/src/pipelines/epidemiology/README.md

Looks good so far! I just added unit tests last week to make sure that all data sources output some data so we won't be able to merge this until you fill in the parse method.
To pass the unit tests, you'll probably also need to add this to the YAML config:
fetch:
    - url: ...
test:
    metadata_query: "key.str.match('LY*')"

I ended up parsing the Libya data entirely in this PR (initially i had plans to return dummy data here and add a new PR for parsing logic, but while working with the unit tests I was able to add the simple parsing logic here itself :) )
PTAL. All tests seem to be passing now.

Thanks @pranalipy, the code looks good. Can you confirm that we are parsing the regions being output by the CSV file? Looking at the logs, it looks like we still have a lot of mismatches although they appear not to be proper subregions, for example:
/home/runner/work/data/data/src/lib/error_logger.py:30: UserWarning: [2020-07-09T16:18:50.9859][LibyaHumdataDataSource] No key match found for:
subregion1_name    Al-Qarah Bulley
total_confirmed                  3
total_recovered                  0
total_deceased                   0
date                    2020-07-08
country_code                    LY
_vec               Al-Qarah Bulley

From the regions in metadata, it looks like only Benghazi is being properly ingested by this data source. Is that expected?

Yes great catch!! I should be reading the locality as match_string instead of subregion1_name. Just getting a hang of things :)
It's parsing 111 rows now, and not just Bengazi. Can you PTAL? I think in this period, the Libya govt has added more regions which I'll next add to metadata.csv.

Looks great! I'm seeing the following records being added:
+LY_BA 2020-05-01
+LY_BA 2020-05-03
+LY_BA 2020-05-05
+LY_BA 2020-05-06
+LY_BA 2020-05-07
+LY_BA 2020-05-12
+LY_BA 2020-05-19
+LY_BA 2020-05-26
+LY_BA 2020-05-27
+LY_BA 2020-05-28
+LY_BA 2020-06-01
+LY_BA 2020-06-02
+LY_BA 2020-06-04
+LY_BA 2020-06-05
+LY_BA 2020-06-08
+LY_BA 2020-06-09
+LY_BA 2020-06-11
+LY_BA 2020-06-15
+LY_BA 2020-06-16
+LY_BA 2020-06-21
+LY_BA 2020-07-01
+LY_BA 2020-07-06
+LY_BA 2020-07-07
+LY_BA 2020-07-08
+LY_JI 2020-06-09
+LY_JI 2020-06-11
+LY_JI 2020-06-15
+LY_JI 2020-06-16
+LY_JI 2020-06-21
+LY_JI 2020-07-01
+LY_JI 2020-07-06
+LY_JI 2020-07-07
+LY_SB 2020-05-26
+LY_SB 2020-05-27
+LY_SB 2020-05-28
+LY_SB 2020-06-01
+LY_SB 2020-06-02
+LY_SB 2020-06-04
+LY_SB 2020-06-05
+LY_SB 2020-06-08
+LY_SB 2020-06-09
+LY_SB 2020-06-11
+LY_SB 2020-06-15
+LY_SB 2020-06-16
+LY_SB 2020-06-21
+LY_SB 2020-07-01
+LY_SB 2020-07-06
+LY_SB 2020-07-07
+LY_SB 2020-07-08
+LY_ST 2020-05-28
+LY_ST 2020-06-01
+LY_ST 2020-06-02
+LY_ST 2020-06-04
+LY_ST 2020-06-05
+LY_ST 2020-06-08
+LY_ST 2020-06-09
+LY_ST 2020-06-11
+LY_ST 2020-06-15
+LY_ST 2020-06-16
+LY_ST 2020-06-21
+LY_ST 2020-07-01
+LY_ST 2020-07-06
+LY_ST 2020-07-07
+LY_ST 2020-07-08
+LY_TB 2020-05-01
+LY_TB 2020-05-03
+LY_TB 2020-05-05
+LY_TB 2020-05-06
+LY_TB 2020-05-07
+LY_TB 2020-05-12
+LY_TB 2020-05-19
+LY_TB 2020-05-26
+LY_TB 2020-05-27
+LY_TB 2020-05-28
+LY_TB 2020-06-01
+LY_TB 2020-06-02
+LY_TB 2020-06-04
+LY_TB 2020-06-05
+LY_TB 2020-06-08
+LY_TB 2020-06-09
+LY_TB 2020-06-11
+LY_TB 2020-06-15
+LY_TB 2020-06-16
+LY_TB 2020-06-21
+LY_TB 2020-07-01
+LY_TB 2020-07-06
+LY_TB 2020-07-07
+LY_TB 2020-07-08
+LY_WS 2020-06-16
+LY_WS 2020-06-21
+LY_WS 2020-07-01
+LY_WS 2020-07-06
+LY_WS 2020-07-07
+LY_WS 2020-07-08
+LY_ZL 2020-05-26
+LY_ZL 2020-05-27
+LY_ZL 2020-05-28
+LY_ZL 2020-06-01
+LY_ZL 2020-06-02
+LY_ZL 2020-06-04
+LY_ZL 2020-06-05
+LY_ZL 2020-06-08
+LY_ZL 2020-06-09
+LY_ZL 2020-06-11
+LY_ZL 2020-06-15
+LY_ZL 2020-06-16
+LY_ZL 2020-06-21
+LY_ZL 2020-07-01
+LY_ZL 2020-07-06
+LY_ZL 2020-07-07
+LY_ZL 2020-07-08

You have write access to the repo, so feel free to submit at your earliest convenience :-)


Error when using with react-quill 2.0 - moduleClass is not a constructor

Hello,
I'm trying to use the plugin with latest react-quill in TS but getting error in this simple sample. Am I missing any import?
https://stackblitz.com/edit/react-ts-wxeqnr?file=Editor.tsx

Any luck with this @hasangursoy ?

No luck with it. I've solved my issue with using the latest branch from here https://github.com/zenoamaro/react-quill/pull/973#issuecomment-2100320953 (I've cloned and created my own NPM package)

No luck with it. I've solved my issue with using the latest branch from here zenoamaro/react-quill#973 (I've cloned and created my own NPM package)

Ahh ohk Thanks. I'm currently trying to use v4.1.0 with the latest version of react-quill. If that doesn't work out, I'll resort to using your npm fork.

No luck with it. I've solved my issue with using the latest branch from here zenoamaro/react-quill#973 (I've cloned and created my own NPM package)

Ahh ohk Thanks. I'm currently trying to use v4.1.0 with the latest version of react-quill. If that doesn't work out, I'll resort to using your npm fork.

Btw @hasangursoy I was able to get quill-mentions working with the latest version of react-quill by downgrading it to v4.1.0

@batflarrow What ver of react-quill did you get this working with? I'm trying with react-quill-new and still not having any luck..

@batflarrow What ver of react-quill did you get this working with? I'm trying with react-quill-new and still not having any luck..

Currently I'm using the packages on the following versions and it's working as expected.
"quill-mention": "^6.0.1",
"react-quill-new": "^3.3.0",

Some code snippets that we are using
import 'quill-mention/dist/quill.mention.css';
      Promise.all([import('quill'), import('quill-mention')]).then(([quill, quillMention]) => {
        quill.default.register({
          'blots/mention': quillMention.MentionBlot,
          'modules/mention': quillMention.Mention,
        });
const Quill = dynamic(() => import('react-quill-new'), {
  ssr: false,
  loading: () => <Spin />,
});

@batflarrow What ver of react-quill did you get this working with? I'm trying with react-quill-new and still not having any luck..

@mcamack I face the same issue when using<EMAIL_ADDRESS>with<EMAIL_ADDRESS> After investing a couple of hours, I finally able to figure out the root cause of the problem.
Root cause of the problem:
quill-mention and react-quill-new both have separate quill package under their node_modules. That's why they uses different Quill instances. [ I notice this when I was debugging and console logging after this line and found that insertEmbed function returns empty delta. ]

If we run npm ls quill command, we can see the same thing.

Solution
You, somehow, need to tell quill-mention and react-quill-new to use the same quill package reference. You can achieve that in several ways.
Using npm package manager

Add<EMAIL_ADDRESS>to the dependency list of your package.json file. [ You might get error doing this. Probably, other package (like quill-blot-formatter) uses another version of quill. ]
If first one is not possible, you can add the following option in you package.json file.

"overrides": {
    "quill": "^2.0.2"
}

Make sure that, both quill-mention and react-quill-new use the same quill package. You can verify that by running npm ls quill command. It will now show deduped.

Finally, run npm install command aging and now the mention functionality in the editor should work properly.

Using pnpm packager manager

You need not do anything. I have also tested with pnpm. Probably, pnpm package manager de-duplicate packages by default.

Please let me know if you can be able to solve the issue after following these steps.


Clicking the hyperlink in Temporary-Sign-Up-Tool

Script folder: https://github.com/avinashkranjan/Amazing-Python-Scripts/tree/master/Temporary-Sign-Up-Tool
Describe the bug
Clicking the 10minutemail hyperlink in the webpage does not open the correct webpage
To Reproduce
Steps to reproduce the behavior:

Run the script
Click on '10minutemail.net' hyperlink
See error

Expected behavior
It should open the 10minutemail.net website.

@chaitanyabisht you are a participant of GGSOC or doing this contribution casually?

@chaitanyabisht you are a participant of GGSOC or doing this contribution casually?

I am a participant of GSSOC


[Azure.Core] Add Public Model Serialization

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

https://github.com/Azure/azure-sdk-for-net/issues/35665

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Core

Would it be possible to add a section to the description talking about how these types will be used? For example, will all generated models in our libraries implement these interfaces? Will we move Azure.Core types like ETag to implement them? How will it work with IUtf8JsonSerializable? What other types/components will take IJsonSerializable that the interface should work well with? Will there be a reason for customers to implement the interface? What are key usage scenarios?
Do we have a description of the feature set we're looking to support with this feature? For example, are we concerned with backward compatibility and versioning? E.g. if a service API follows the Azure API guidelines, does this interface guarantee it can always be deserialized from any library? If so, should these methods take api-version?
Do we have plans to support serialization of non-JSON formats, e.g. XML, or other? Should the interfaces support that, or would we add separate interfaces for those formats?

I believe I addressed that this interface will be on all of our models and then implementation using the internal IUtf8JsonSerializable will not change in v1, but can change after that since we are already looking at using Utf8JsonReader for perf reasons.
In the Bring-Your-Own-Model scenario customers can implement this same interface.
We decided to not take on a serialization option called version for the first iteration and any backwards compatibility concerns and handled via the HandleAddtionalProperties option.  In order to add this capability our underlying serialization implementation needs to be updated to know how to deal with this which if we go down this route will happen in a later update.
No plans to support non-json format.  If we did this it would be the same as the version option we would need to update our serialization writers in the generator first then introduce the capability in the public layer.


Catch every invalid signature

Malformed or incorrect JWT's are not catched. It's helpful to always return a signature_error.

Coverage remained the same at 88.757% when pulling 2eef923422a05919ad664933242aca3e41293090 on davidvanleeuwen:fix/invalid-signature into 4a91b06069af51862e65f90ff1b9611831f6c602 on bryanjos:master.

Thanks! I've noticed it but hadn't had the time to look into.
It will be included on our next rc. Just curious: are you using Joken 2 already in production or simply assessing it for now? What do you think of the new API?

Well, particularly I am not much into JavaScript but a quick browse over the API surface seems a little bit too opinionated (like which claims a token will have).
If you use default_claims/1 to configure your token you get exp generation (2hs by default) and validation. But I'll take another pass on the docs to see if we've implied otherwise.
Thanks once again!


Need help adding formatter for object type in dictionary<int, object> serialization

I have a class that has a dictionary of type Dictionary<int, object>. It is used to store some data of various types. Now I want to deserialize the stored data, but I get the error message:
MemoryPackSerializationException: System.Object is not registered in this provider.
MemoryPack.MemoryPackSerializationException.ThrowNotRegisteredInProvider (System.Type type) (at Assets/Packages/MemoryPack/Runtime/MemoryPack.Core/MemoryPackSerializationException.cs:84)

I have looked up similar issue and found out that object is not supported by default and I need to add a formatter for it. But I'm not quite sure how I should add a formatter for the object type. Should I add a formatter for Dictionary<int, object> or is there a more complete example to refer to?
Here is my minimal code in Unity 2021.3 Environment:
using MemoryPack;
using System.Collections.Generic;
using System.IO;
using UnityEditor;
using UnityEngine;

[MemoryPackable]
public partial class MemoryClass {
    public Dictionary<int, object> dictionary;
}

public class TestMemory {

    [MenuItem("Tools/Test MemoryPack")]
    public static void Save() {
        using (FileStream stream = new FileStream(Path.Combine(Application.persistentDataPath, "Memory.bin"), FileMode.Create)) {
            stream.Write(MemoryPackSerializer.Serialize(new MemoryClass() {
                dictionary = new Dictionary<int, object>() { { 1, "2" }, { 2, true }, {3, new int[]{1,2,3,4,5}} }
            }));
        }
    }
}

I've been researching for a few days and wrote the following code:
public class ObjectFormatter : MemoryPackFormatter<object> {
    public override void Serialize(ref MemoryPackWriter writer, ref object value) {
        if (value == null) {
            writer.WriteNullObjectHeader();
            return;
        }
        if (value is int i) {
            writer.WriteVarInt(i);
            return;
        }
        if (value is int[] ints) {
            writer.WriteArray(ints);
            return;
        }

        if (value is string str) {
            writer.WriteString(str);
            return;
        }
        if (value is string[] strs) {
            writer.WriteArray(strs);
            return;
        }

        // CustomType with [MemoryPackable] Attribute
        if (value is CustomClass custom) {
            writer.WritePackable(custom);
            return;
        }

        // How to WriteBool or WriteDictionary ?

    }
    public override void Deserialize(ref MemoryPackReader reader, ref object value) {
        if (reader.PeekIsNull()) {
            reader.Advance(1);
            value = null;
            return;
        }

        value = reader.ReadVarIntInt32();
        // reader.ReadValue(ref value);
        // Use ReadValue(ref value) will throw a StackOverflowException: The requested operation caused a stack overflow.

        // How to make the reader determine the type and assign a value?
    }
}

This code can only serialize/deserialize objects with the actual type of int. I don't know how to write the corresponding serialization for types like bool or Dictionary, etc. Also, during deserialization, I'm not sure how to determine what type the reader should currently read. I hope to receive some guidance.

I have the same problem, can anyone offer some help?

Same issue here: https://github.com/Cysharp/MemoryPack/issues/225

MemoryPack's binary specification does not allow retrieval of data structures without a C# type definition.
So it seems difficult to support this.
( By the way, this is a similar restriction to binary specifications such as protobuf.
If you want to dump binary data dynamically, it seems to me that MessagePack or JSON is probably the way to go .
Also, if you know the type variations in advance, please try Union.


Suggestions

Hi Micah,
Since the current "official" Yellow Paper is out of date, have you included the more recent EIPs from Byzantium into your specification? I see you've added the opcodes for REVERT and STATICCALL, but there is no description of these, so that needs to be done.
It also has CALL_BLACKBOX which I don't think is actually a part of the EVM. Sources:

https://www.reddit.com/r/ethdev/comments/6i05w2/when_is_the_call_blackbox_opcode_going_to_be/
https://www.reddit.com/r/ethereum/comments/5256ht/ethereum_20_mauve_paper/d7i9dvv/
searching for CALL_BLACKBOX in the EIPs repo yields no results.

There is no result when I search for precompiles.
While I understand that the blanched almond paper is concise, I think it is helpful to have a full formal specification, which it isn't, e.g. compared to the Yellow Paper it doesn't formally specify the opcodes. We could also improve on my version of the Yellow Paper for people who wish to have an in-depth understanding. For example one formal specification that I didn't see is of the difficulty, which is best represented by maths (or maths in code) rather than pseudocode.
Also have you outlined the development roadmap? E.g., implement sharding which will then enable more rapid development of other projects, e.g. EWASM, parallelizability, etc.
Finally it'd obviously be good to have this info on a website, e.g. one made by https://readthedocs.org/.
I haven't read through your repo yet but these are my initial thoughts on how the yellow paper needs to be improved, in addition to your ideas.
Additionally I think it would be good to have the formal math operations, but then you can also have pseudocode or explanations in plain English. You can also refer to Wikipedia's List of Mathematical symbols and make sure the symbol is listed there (add it if it isn't).
Links for the high level languages would be good.

Thanks for this feedback! I'm going to incorporate your suggestions into the paper.
Is there anything else you wanted to add before I close this issue?

You're welcome Micah! Haha, I think I gave a lot of feedback, nothing further comes to mine at this stage.

I just want to emphasise that "the current EVM will eventually be replaced and we don’t want you to spend your labor [editing] something that will later be discarded". http://notes.eth.sg/s/rksCgM0Mz#on-verifying-compilers-to-evm

@jamesray1 That's an interesting fact that the current EVM will be replaced. What are the implications of that, in your opinion?

Yes, it will probably be replaced with EWASM, which will execute much more efficiently and provide more scalability for Ethereum.
https://github.com/ewasm/design


Revert "Make GCP OAuth scopes configurable via pipeline options."

Reverts apache/beam#23644

Run Python 3.7 PostCommit

Run Python 3.9 PostCommit

Run Python 3.8 PostCommit

Note that I filed https://github.com/apache/beam/issues/23676 for the failure

I believe I have a forward fix in https://github.com/apache/beam/pull/23677, waiting on postcommit to ensure that it passes.

https://github.com/apache/beam/pull/23677 resolved the problem


Project directory structure and path mappings

As a mineral-ui developer, I would like to make some internal directory structure changes, to make development easier and quicker to grok for new contributors.
AC:

Change layout of src directory, e.g.

src

library
website

Use directory alias for imports to avoid ../../../../

e.g. import Button from ‘library/Button’;
e.g. import App from ‘website/App’

Other Considerations:

Team should discuss directory aliases prior to implementing.

Are the directory aliases a good idea or just churn?
Would all paths get updated or would we still use ‘./Foo’ in some cases?

Going to close this for now.  The main thing that I wanted to accomplish was the directory restructure and this was done in #631.  The directory aliasing may have value and we may do it in the future, but there are much higher priorities at this time.


minimap2 no dependency not documented

Hello,
you may want to update the doc to say that system minimap2 or user provided minimpa2 can be used when running make with MINIMPA2=noinstall exactly as eigen, htslib and hdf5
NB tarball compiles fine with the following provided via module environement and noinstall for all components
gcc/9.2.0
hdf5/1.10.6
htslib/1.10
eigen/3.3.7
fast5/0.6.5
minimap2/2.17
regards
Eric

Good catch, sorry for missing this. Fixed now and thanks for testing the noinstall build.