Support simple ping mesh in agent.

We need to implement a simple ping-mesh monitoring tool to get nodes connectivity latency.
Design doc(TODO): https://docs.google.com/document/d/1EdKJ8iQ3KwVBQAHaPisqHP7cgpq4RW8mD9KPWtYETbE
Issue: #5514

Antrea agent running logs.
I0319 07:57:46.104868       1 log_file.go:93] Set log file max size to 104857600
I0319 07:57:46.105703       1 agent.go:110] "Starting Antrea agent" version="v2.0.0-dev-f22b92bd.dirty"
I0319 07:57:46.105713       1 client.go:89] No kubeconfig file was specified. Falling back to in-cluster config
I0319 07:57:46.105974       1 prometheus.go:189] Initializing prometheus metrics
I0319 07:57:46.106018       1 agent.go:144] "Node IPs" NodeCount=0
I0319 07:57:46.106035       1 ovs_client.go:71] Connecting to OVSDB at address /var/run/openvswitch/db.sock
I0319 07:57:47.106956       1 ovs_client.go:90] Not connected yet, will try again in 2s
I0319 07:57:47.107595       1 agent.go:412] Setting up node network
I0319 07:57:47.107721       1 discoverer.go:82] Starting ServiceCIDRDiscoverer
I0319 07:57:47.126357       1 agent.go:1023] "Got Interface MTU" MTU=1450
I0319 07:57:47.127492       1 ovs_client.go:122] Created bridge: d139c498-6d32-44ff-8384-ea8265617754
I0319 07:57:47.137270       1 agent.go:881] "Allocated OpenFlow port for tunnel interface" port="antrea-tun0" ofPort=1
I0319 07:57:47.142829       1 agent.go:702] "Allocated OpenFlow port for gateway interface" port="antrea-gw0" ofPort=2
I0319 07:57:47.158629       1 route_linux.go:192] Initializing iptables
I0319 07:57:47.158784       1 agent.go:1170] No round number found in OVSDB, using 1
I0319 07:57:47.158793       1 agent.go:1182] Using round number 1
I0319 07:57:47.158927       1 ofctrl.go:218] Initialize connection or re-connect to /var/run/openvswitch/br-int.mgmt.
I0319 07:57:47.184359       1 route_linux.go:204] Initialized iptables
I0319 07:57:48.159516       1 ofctrl.go:233] Connected to socket /var/run/openvswitch/br-int.mgmt
I0319 07:57:48.159696       1 ofctrl.go:295] New connection..
 Falling back to in-cluster config
I0319 07:57:48.200075       1 client.go:108] Didn't get CA certificate, skip updating Antrea Client
I0319 07:57:48.200094       1 channel.go:83] "Starting SubscribableChannel" name="PodUpdate"
I0319 07:57:48.200097       1 log_file.go:121] Starting log file monitoring. Maximum log file number is 4
I0319 07:57:48.200109       1 route_linux.go:244] "Starting iptables, ipset and route sync" interval="1m0s"
I0319 07:57:48.200118       1 configmap_cafile_content.go:202] "Starting controller" name="antrea-ca::kube-system::antrea-ca::ca.crt"
I0319 07:57:48.200128       1 shared_informer.go:270] Waiting for caches to sync for antrea-ca::kube-system::antrea-ca::ca.crt
I0319 07:57:48.200128       1 cluster.go:335] "Starting" controllerName="MemberListCluster"
I0319 07:57:48.200136       1 shared_informer.go:270] Waiting for caches to sync for MemberListCluster
I0319 07:57:48.200141       1 server.go:655] "Starting CNI server"
I0319 07:57:48.200153       1 controller.go:168] Starting ExternalIPPoolController
I0319 07:57:48.200152       1 config.go:423] "Starting node config controller"
I0319 07:57:48.200156       1 shared_informer.go:270] Waiting for caches to sync for ExternalIPPoolController
I0319 07:57:48.200159       1 shared_informer.go:270] Waiting for caches to sync for node config
I0319 07:57:48.200159       1 config.go:314] Starting endpoint slice config controller
I0319 07:57:48.200165       1 shared_informer.go:270] Waiting for caches to sync for endpoint slice config
I0319 07:57:48.200167       1 networkpolicy_controller.go:599] Waiting for Antrea client to be ready
I0319 07:57:48.200169       1 traceflow_controller.go:173] Starting AntreaAgentTraceflowController
I0319 07:57:48.200175       1 egress_controller.go:491] Starting AntreaAgentEgressController
I0319 07:57:48.200177       1 shared_informer.go:270] Waiting for caches to sync for AntreaAgentTraceflowController
I0319 07:57:48.200180       1 server.go:665] "CNI server is listening ..."
I0319 07:57:48.200149       1 config.go:223] Starting service config controller
I0319 07:57:48.200185       1 node_route_controller.go:334] Starting AntreaAgentNodeRouteController
I0319 07:57:48.200188       1 shared_informer.go:270] Waiting for caches to sync for service config
I0319 07:57:48.200192       1 shared_informer.go:270] Waiting for caches to sync for AntreaAgentNodeRouteController
I0319 07:57:48.200208       1 shared_informer.go:270] Waiting for caches to sync for AntreaAgentEgressController
I0319 07:57:48.200217       1 ip_scheduler.go:219] "Starting Egress IP scheduler"
I0319 07:57:48.200223       1 local_ip_detector_linux.go:59] Starting localIPDetector
I0319 07:57:48.200284       1 collector.go:86] Start collecting metrics
E0319 07:57:48.201843       1 cluster.go:224] "Processing Node CREATE event error, join cluster failed" err=<
	1 error occurred:
		* Failed to join <IP_ADDRESS>:10351: dial tcp <IP_ADDRESS>:10351: connect: connection refused

 > member="<IP_ADDRESS>"
I0319 07:57:48.207886       1 discoverer.go:207] "Service IPv4 CIDR was updated" ServiceCIDR="<IP_ADDRESS>/16"
I0319 07:57:48.300615       1 shared_informer.go:277] Caches are synced for AntreaAgentTraceflowController
I0319 07:57:48.300632       1 shared_informer.go:277] Caches are synced for antrea-ca::kube-system::antrea-ca::ca.crt
I0319 07:57:48.300642       1 shared_informer.go:277] Caches are synced for AntreaAgentNodeRouteController
I0319 07:57:48.300646       1 node_route_controller.go:287] Reconciliation for AntreaAgentNodeRouteController
I0319 07:57:48.300676       1 shared_informer.go:277] Caches are synced for AntreaAgentEgressController
I0319 07:57:48.300719       1 client.go:105] No antrea kubeconfig file was specified. Falling back to in-cluster config
I0319 07:57:48.300743       1 shared_informer.go:277] Caches are synced for ExternalIPPoolController
I0319 07:57:48.300761       1 shared_informer.go:277] Caches are synced for MemberListCluster
I0319 07:57:48.300764       1 route_linux.go:1171] "Restoring IP routes and rules for Egress"
I0319 07:57:48.300798       1 client.go:130] Updating Antrea client with the new CA bundle
I0319 07:57:48.300817       1 shared_informer.go:277] Caches are synced for node config
I0319 07:57:48.300823       1 shared_informer.go:277] Caches are synced for service config
I0319 07:57:48.300828       1 shared_informer.go:277] Caches are synced for endpoint slice config
I0319 07:57:48.300852       1 egress_controller.go:1208] Starting watch for EgressGroup
I0319 07:57:48.300853       1 cluster.go:531] "Processed Node event" eventType="Join" nodeName="kind-worker2" affectedExternalIPPoolNum=1
I0319 07:57:48.300865       1 cluster.go:531] "Processed Node event" eventType="Join" nodeName="kind-control-plane" affectedExternalIPPoolNum=1
W0319 07:57:48.301052       1 egress_controller.go:1219] Failed to start watch for EgressGroup: Get "https://<IP_ADDRESS>:443/apis/controlplane.antrea.io/v1beta2/egressgroups?fieldSelector=nodeName%3Dkind-worker2&watch=true": dial tcp <IP_ADDRESS>:443: connect: connection refused
I0319 07:57:48.306830       1 serving.go:348] Generated self-signed cert in-memory
I0319 07:57:48.400402       1 networkpolicy_controller.go:610] Antrea client is ready
I0319 07:57:48.400416       1 networkpolicy_controller.go:625] Waiting for all watchers to complete full sync
I0319 07:57:48.400434       1 networkpolicy_controller.go:959] Starting watch for AppliedToGroup
I0319 07:57:48.400471       1 networkpolicy_controller.go:959] Starting watch for AddressGroup
I0319 07:57:48.400514       1 networkpolicy_controller.go:959] Starting watch for NetworkPolicy
W0319 07:57:48.400606       1 networkpolicy_controller.go:962] Failed to start watch for AppliedToGroup: Get "https://<IP_ADDRESS>:443/apis/controlplane.antrea.io/v1beta2/appliedtogroups?fieldSelector=nodeName%3Dkind-worker2&watch=true": dial tcp <IP_ADDRESS>:443: connect: connection refused
W0319 07:57:48.400607       1 networkpolicy_controller.go:962] Failed to start watch for AddressGroup: Get "https://<IP_ADDRESS>:443/apis/controlplane.antrea.io/v1beta2/addressgroups?fieldSelector=nodeName%3Dkind-worker2&watch=true": dial tcp <IP_ADDRESS>:443: connect: connection refused
I0319 07:57:48.400622       1 networkpolicy_controller.go:937] "Getting init events for %s from fallback" AppliedToGroup="(MISSING)"
I0319 07:57:48.400623       1 networkpolicy_controller.go:937] "Getting init events for %s from fallback" AddressGroup="(MISSING)"
W0319 07:57:48.400708       1 networkpolicy_controller.go:962] Failed to start watch for NetworkPolicy: Get "https://<IP_ADDRESS>:443/apis/controlplane.antrea.io/v1beta2/networkpolicies?fieldSelector=nodeName%3Dkind-worker2&watch=true": dial tcp <IP_ADDRESS>:443: connect: connection refused
I0319 07:57:48.400719       1 networkpolicy_controller.go:937] "Getting init events for %s from fallback" NetworkPolicy="(MISSING)"
I0319 07:57:48.400756       1 networkpolicy_controller.go:627] All watchers have completed full sync, installing flows for init events
I0319 07:57:48.401053       1 networkpolicy_controller.go:632] Starting NetworkPolicy workers now
I0319 07:57:48.401058       1 networkpolicy_controller.go:638] Starting IDAllocator worker to maintain the async rule cache
I0319 07:57:48.401063       1 status_controller.go:210] Starting NetworkPolicy StatusController
I0319 07:57:48.413988       1 monitor.go:122] "Start to ping all nodes"
I0319 07:57:48.413991       1 agent.go:53] Starting Antrea Agent Monitor
W0319 07:57:48.414001       1 shared_informer.go:416] The sharedIndexInformer has started, run more than once is not allowed
I0319 07:57:48.414001       1 pipeline.go:492] Start collecting OVS meter stats
I0319 07:57:48.413993       1 monitor.go:157] "Finish to ping all nodes"
I0319 07:57:48.414988       1 configmap_cafile_content.go:202] "Starting controller" name="client-ca::kube-system::extension-apiserver-authentication::client-ca-file"
I0319 07:57:48.414991       1 shared_informer.go:270] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0319 07:57:48.414991       1 requestheader_controller.go:169] Starting RequestHeaderAuthRequestController
I0319 07:57:48.414995       1 shared_informer.go:270] Waiting for caches to sync for RequestHeaderAuthRequestController
I0319 07:57:48.414997       1 configmap_cafile_content.go:202] "Starting controller" name="client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file"
I0319 07:57:48.415005       1 shared_informer.go:270] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file
I0319 07:57:48.415203       1 secure_serving.go:210] Serving securely on [::]:10350
I0319 07:57:48.415216       1 tlsconfig.go:240] "Starting DynamicServingCertificateController"
I0319 07:57:48.433803       1 node_route_controller.go:499] "Adding routes and flows to Node" Node="kind-control-plane" podCIDRs=["<IP_ADDRESS>/24"] addresses=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-control-plane"}]
I0319 07:57:48.433817       1 node_route_controller.go:542] "Adding route and flow to Node" Node="kind-control-plane" podCIDR="<IP_ADDRESS>/24" peerNodeIP="<IP_ADDRESS>"
I0319 07:57:48.433875       1 node_route_controller.go:499] "Adding routes and flows to Node" Node="kind-worker" podCIDRs=["<IP_ADDRESS>/24"] addresses=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-worker"}]
I0319 07:57:48.433887       1 node_route_controller.go:542] "Adding route and flow to Node" Node="kind-worker" podCIDR="<IP_ADDRESS>/24" peerNodeIP="<IP_ADDRESS>"
I0319 07:57:48.515514       1 shared_informer.go:277] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0319 07:57:48.515583       1 shared_informer.go:277] Caches are synced for RequestHeaderAuthRequestController
I0319 07:57:48.515648       1 shared_informer.go:277] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file
I0319 07:57:48.786250       1 cluster.go:531] "Processed Node event" eventType="Join" nodeName="kind-worker" affectedExternalIPPoolNum=1
I0319 07:57:53.301671       1 egress_controller.go:1208] Starting watch for EgressGroup
W0319 07:57:53.302486       1 egress_controller.go:1219] Failed to start watch for EgressGroup: Get "https://<IP_ADDRESS>:443/apis/controlplane.antrea.io/v1beta2/egressgroups?fieldSelector=nodeName%3Dkind-worker2&watch=true": dial tcp <IP_ADDRESS>:443: connect: connection refused
I0319 07:57:53.401282       1 networkpolicy_controller.go:959] Starting watch for NetworkPolicy
I0319 07:57:53.401337       1 networkpolicy_controller.go:959] Starting watch for AppliedToGroup
I0319 07:57:53.401357       1 networkpolicy_controller.go:959] Starting watch for AddressGroup
W0319 07:57:53.401795       1 networkpolicy_controller.go:962] Failed to start watch for AppliedToGroup: Get "https://<IP_ADDRESS>:443/apis/controlplane.antrea.io/v1beta2/appliedtogroups?fieldSelector=nodeName%3Dkind-worker2&watch=true": dial tcp <IP_ADDRESS>:443: connect: connection refused
W0319 07:57:53.401807       1 networkpolicy_controller.go:962] Failed to start watch for NetworkPolicy: Get "https://<IP_ADDRESS>:443/apis/controlplane.antrea.io/v1beta2/networkpolicies?fieldSelector=nodeName%3Dkind-worker2&watch=true": dial tcp <IP_ADDRESS>:443: connect: connection refused
W0319 07:57:53.401809       1 networkpolicy_controller.go:962] Failed to start watch for AddressGroup: Get "https://<IP_ADDRESS>:443/apis/controlplane.antrea.io/v1beta2/addressgroups?fieldSelector=nodeName%3Dkind-worker2&watch=true": dial tcp <IP_ADDRESS>:443: connect: connection refused
I0319 07:57:56.107009       1 agent.go:144] "Node IPs" NodeCount=3
I0319 07:57:56.107534       1 agent.go:146] "Node IP" Node="kind-control-plane" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-control-plane"}]
I0319 07:57:56.107569       1 agent.go:146] "Node IP" Node="kind-worker" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-worker"}]
I0319 07:57:56.107591       1 agent.go:146] "Node IP" Node="kind-worker2" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-worker2"}]
I0319 07:57:58.195490       1 agent.go:574] Deleting stale flows from previous round if any
I0319 07:57:58.195529       1 agent.go:512] Persisting round number 1 to OVSDB
I0319 07:57:58.196954       1 agent.go:517] Round number 1 was persisted to OVSDB
I0319 07:57:58.302755       1 egress_controller.go:1208] Starting watch for EgressGroup
I0319 07:57:58.320987       1 egress_controller.go:1229] Started watch for EgressGroup
I0319 07:57:58.321487       1 egress_controller.go:1257] Received 0 init events for EgressGroup
I0319 07:57:58.401517       1 networkpolicy_controller.go:959] Starting watch for NetworkPolicy
I0319 07:57:58.401650       1 networkpolicy_controller.go:959] Starting watch for AddressGroup
I0319 07:57:58.401688       1 networkpolicy_controller.go:959] Starting watch for AppliedToGroup
I0319 07:57:58.408003       1 networkpolicy_controller.go:974] Started watch for AppliedToGroup
I0319 07:57:58.408170       1 networkpolicy_controller.go:1004] Received 0 init events for AppliedToGroup
I0319 07:57:58.408249       1 networkpolicy_controller.go:974] Started watch for NetworkPolicy
I0319 07:57:58.408249       1 networkpolicy_controller.go:974] Started watch for AddressGroup
I0319 07:57:58.408386       1 networkpolicy_controller.go:1004] Received 0 init events for NetworkPolicy
I0319 07:57:58.408418       1 networkpolicy_controller.go:1004] Received 0 init events for AddressGroup
I0319 07:57:58.415061       1 monitor.go:122] "Start to ping all nodes"
I0319 07:58:03.416423       1 monitor.go:185] "Ping statistics" Statistics={"PacketsRecv":5,"PacketsSent":6,"PacketsRecvDuplicates":0,"PacketLoss":16.666666666666664,"IPAddr":{"IP":"<IP_ADDRESS>","Zone":""},"Addr":"<IP_ADDRESS>","Rtts":[246782,144857,172223,160353,224077],"MinRtt":144857,"MaxRtt":246782,"AvgRtt":189659,"StdDevRtt":39032}
I0319 07:58:03.440882       1 monitor.go:185] "Ping statistics" Statistics={"PacketsRecv":5,"PacketsSent":5,"PacketsRecvDuplicates":0,"PacketLoss":0,"IPAddr":{"IP":"<IP_ADDRESS>","Zone":""},"Addr":"<IP_ADDRESS>","Rtts":[276265,97715,113798,147698,130275],"MinRtt":97715,"MaxRtt":276265,"AvgRtt":153151,"StdDevRtt":63768}
I0319 07:58:03.487302       1 monitor.go:185] "Ping statistics" Statistics={"PacketsRecv":5,"PacketsSent":5,"PacketsRecvDuplicates":0,"PacketLoss":0,"IPAddr":{"IP":"<IP_ADDRESS>","Zone":""},"Addr":"<IP_ADDRESS>","Rtts":[416554,211148,156739,155181,222316],"MinRtt":155181,"MaxRtt":416554,"AvgRtt":232388,"StdDevRtt":96076}
I0319 07:58:03.487357       1 monitor.go:157] "Finish to ping all nodes"
I0319 07:58:03.487530       1 monitor.go:160] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":153151,"Status":true,"LastUpdated":"2024-03-19T07:58:03.440896041Z","CreatedAt":"2024-03-19T07:58:03.440896041Z"}
I0319 07:58:03.487563       1 monitor.go:160] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":232388,"Status":true,"LastUpdated":"2024-03-19T07:58:03.48733016Z","CreatedAt":"2024-03-19T07:58:03.48733016Z"}
I0319 07:58:03.487585       1 monitor.go:160] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":189659,"Status":true,"LastUpdated":"2024-03-19T07:58:03.416438747Z","CreatedAt":"2024-03-19T07:58:03.416438747Z"}
I0319 07:58:06.108728       1 agent.go:144] "Node IPs" NodeCount=3
I0319 07:58:06.108791       1 agent.go:146] "Node IP" Node="kind-worker" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-worker"}]
I0319 07:58:06.108814       1 agent.go:146] "Node IP" Node="kind-worker2" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-worker2"}]
I0319 07:58:06.108835       1 agent.go:146] "Node IP" Node="kind-control-plane" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-control-plane"}]
I0319 07:58:13.487835       1 monitor.go:122] "Start to ping all nodes"
I0319 07:58:16.109431       1 agent.go:144] "Node IPs" NodeCount=3
I0319 07:58:16.118958       1 agent.go:146] "Node IP" Node="kind-control-plane" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-control-plane"}]
I0319 07:58:16.118979       1 agent.go:146] "Node IP" Node="kind-worker" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-worker"}]
I0319 07:58:16.118989       1 agent.go:146] "Node IP" Node="kind-worker2" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-worker2"}]
I0319 07:58:18.488600       1 monitor.go:185] "Ping statistics" Statistics={"PacketsRecv":5,"PacketsSent":6,"PacketsRecvDuplicates":0,"PacketLoss":16.666666666666664,"IPAddr":{"IP":"<IP_ADDRESS>","Zone":""},"Addr":"<IP_ADDRESS>","Rtts":[142627,38384,171111,105800,74946],"MinRtt":38384,"MaxRtt":171111,"AvgRtt":106574,"StdDevRtt":47150}
I0319 07:58:18.488620       1 monitor.go:185] "Ping statistics" Statistics={"PacketsRecv":5,"PacketsSent":6,"PacketsRecvDuplicates":0,"PacketLoss":16.666666666666664,"IPAddr":{"IP":"<IP_ADDRESS>","Zone":""},"Addr":"<IP_ADDRESS>","Rtts":[204288,32270,235729,196501,50838],"MinRtt":32270,"MaxRtt":235729,"AvgRtt":143926,"StdDevRtt":84815}
I0319 07:58:18.488619       1 monitor.go:185] "Ping statistics" Statistics={"PacketsRecv":5,"PacketsSent":6,"PacketsRecvDuplicates":0,"PacketLoss":16.666666666666664,"IPAddr":{"IP":"<IP_ADDRESS>","Zone":""},"Addr":"<IP_ADDRESS>","Rtts":[259245,56934,195897,165001,69710],"MinRtt":56934,"MaxRtt":259245,"AvgRtt":149358,"StdDevRtt":76644}
I0319 07:58:18.488658       1 monitor.go:157] "Finish to ping all nodes"
I0319 07:58:18.488702       1 monitor.go:160] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":143926,"Status":true,"LastUpdated":"2024-03-19T07:58:18.488639295Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0319 07:58:18.488714       1 monitor.go:160] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":106574,"Status":true,"LastUpdated":"2024-03-19T07:58:18.488623178Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0319 07:58:18.488723       1 monitor.go:160] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":149358,"Status":true,"LastUpdated":"2024-03-19T07:58:18.48864284Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0319 07:58:26.119562       1 agent.go:144] "Node IPs" NodeCount=3
I0319 07:58:26.119623       1 agent.go:146] "Node IP" Node="kind-worker2" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-worker2"}]
I0319 07:58:26.119638       1 agent.go:146] "Node IP" Node="kind-control-plane" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-control-plane"}]
I0319 07:58:26.119651       1 agent.go:146] "Node IP" Node="kind-worker" IP=[{"type":"InternalIP","address":"<IP_ADDRESS>"},{"type":"Hostname","address":"kind-worker"}]
I0319 07:58:28.489383       1 monitor.go:122] "Start to ping all nodes"
I0319 07:58:33.490175       1 monitor.go:185] "Ping statistics" Statistics={"PacketsRecv":5,"PacketsSent":6,"PacketsRecvDuplicates":0,"PacketLoss":16.666666666666664,"IPAddr":{"IP":"<IP_ADDRESS>","Zone":""},"Addr":"<IP_ADDRESS>","Rtts":[198436,29758,12446,42406,134468],"MinRtt":12446,"MaxRtt":198436,"AvgRtt":83503,"StdDevRtt":71321}
I0319 07:58:33.490205       1 monitor.go:185] "Ping statistics" Statistics={"PacketsRecv":5,"PacketsSent":6,"PacketsRecvDuplicates":0,"PacketLoss":16.666666666666664,"IPAddr":{"IP":"<IP_ADDRESS>","Zone":""},"Addr":"<IP_ADDRESS>","Rtts":[205458,110971,39595,47471,91606],"MinRtt":39595,"MaxRtt":205458,"AvgRtt":99021,"StdDevRtt":59524}
I0319 07:58:33.490218       1 monitor.go:185] "Ping statistics" Statistics={"PacketsRecv":5,"PacketsSent":6,"PacketsRecvDuplicates":0,"PacketLoss":16.666666666666664,"IPAddr":{"IP":"<IP_ADDRESS>","Zone":""},"Addr":"<IP_ADDRESS>","Rtts":[207491,102489,36650,39972,172961],"MinRtt":36650,"MaxRtt":207491,"AvgRtt":111913,"StdDevRtt":68979}
I0319 07:58:33.490268       1 monitor.go:157] "Finish to ping all nodes"
I0319 07:58:33.490295       1 monitor.go:160] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":99021,"Status":true,"LastUpdated":"2024-03-19T07:58:33.490234228Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0319 07:58:33.490312       1 monitor.go:160] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":111913,"Status":true,"LastUpdated":"2024-03-19T07:58:33.490245162Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0319 07:58:33.490323       1 monitor.go:160] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":83503,"Status":true,"LastUpdated":"2024-03-19T07:58:33.490198988Z","CreatedAt":"0001-01-01T00:00:00Z"}

This is the log after introducing crd, try to create/update/delete this CRD.
apiVersion: crd.antrea.io/v1alpha2
kind: NodeLatencyMonitor
metadata:
  name: default
spec:
  pingInterval: "10s"
  pingTimeout: "5s"
  pingConcurrentLimit: 2

I0407 09:19:22.093637       1 networkpolicy_controller.go:1004] Received 0 init events for NetworkPolicy
W0407 09:19:53.457015       1 reflector.go:347] pkg/mod/k8s.io/client-go@v0.26.4/tools/cache/reflector.go:169: watch of *v1alpha2.NodeLatencyMonitor ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"NodeLatencyMonitor\" is registered for version \"crd.antrea.io/v1alpha2\" in scheme \"pkg/runtime/scheme.go:100\"") has prevented the request from succeeding
I0407 09:19:55.015313       1 monitor.go:109] "NodeLatencyMonitor added" NodeLatencyMonitor="default"
I0407 09:19:55.015372       1 monitor.go:196] "Start to ping all nodes"
W0407 09:19:55.015408       1 shared_informer.go:416] The sharedIndexInformer has started, run more than once is not allowed
I0407 09:19:55.015659       1 monitor.go:345] "Received ICMP reply"
I0407 09:19:58.016282       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:01.016606       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:01.016667       1 monitor.go:235] "Finish to ping all nodes"
I0407 09:20:01.016833       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":160011,"Status":true,"LastUpdated":"2024-04-07T09:19:55.015684256Z","CreatedAt":"2024-04-07T09:19:55.015684256Z"}
I0407 09:20:01.016863       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":153080,"Status":true,"LastUpdated":"2024-04-07T09:19:58.016319004Z","CreatedAt":"2024-04-07T09:19:58.016319004Z"}
I0407 09:20:01.016878       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":102191,"Status":true,"LastUpdated":"2024-04-07T09:20:01.016646456Z","CreatedAt":"2024-04-07T09:20:01.016646456Z"}
I0407 09:20:11.017137       1 monitor.go:196] "Start to ping all nodes"
I0407 09:20:11.017298       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:14.018301       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:17.018377       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:17.018479       1 monitor.go:235] "Finish to ping all nodes"
I0407 09:20:17.018556       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":66115,"Status":true,"LastUpdated":"2024-04-07T09:20:11.017314926Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:20:17.018587       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":195725,"Status":true,"LastUpdated":"2024-04-07T09:20:14.018368368Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:20:17.018615       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":124521,"Status":true,"LastUpdated":"2024-04-07T09:20:17.01844394Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:20:27.019169       1 monitor.go:196] "Start to ping all nodes"
I0407 09:20:27.019442       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:30.020296       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:33.019708       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:33.019733       1 monitor.go:235] "Finish to ping all nodes"
I0407 09:20:33.019751       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":127651,"Status":true,"LastUpdated":"2024-04-07T09:20:27.019467918Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:20:33.019757       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":109659,"Status":true,"LastUpdated":"2024-04-07T09:20:30.020335289Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:20:33.019761       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":35410,"Status":true,"LastUpdated":"2024-04-07T09:20:33.019723569Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:20:43.020605       1 monitor.go:196] "Start to ping all nodes"
I0407 09:20:43.020852       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:46.021782       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:49.021595       1 monitor.go:345] "Received ICMP reply"
I0407 09:20:49.021661       1 monitor.go:235] "Finish to ping all nodes"
I0407 09:20:49.021705       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":109389,"Status":true,"LastUpdated":"2024-04-07T09:20:43.020877473Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:20:49.021720       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":135532,"Status":true,"LastUpdated":"2024-04-07T09:20:46.021832113Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:20:49.021732       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":108687,"Status":true,"LastUpdated":"2024-04-07T09:20:49.02163948Z","CreatedAt":"0001-01-01T00:00:00Z"}
W0407 09:20:55.136460       1 reflector.go:347] pkg/mod/k8s.io/client-go@v0.26.4/tools/cache/reflector.go:169: watch of *v1alpha2.NodeLatencyMonitor ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"NodeLatencyMonitor\" is registered for version \"crd.antrea.io/v1alpha2\" in scheme \"pkg/runtime/scheme.go:100\"") has prevented the request from succeeding
I0407 09:20:57.407212       1 monitor.go:139] "NodeLatencyMonitor updated" NodeLatencyMonitor="default"
W0407 09:20:57.783930       1 reflector.go:347] pkg/mod/k8s.io/client-go@v0.26.4/tools/cache/reflector.go:169: watch of *v1alpha2.NodeLatencyMonitor ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"NodeLatencyMonitor\" is registered for version \"crd.antrea.io/v1alpha2\" in scheme \"pkg/runtime/scheme.go:100\"") has prevented the request from succeeding
I0407 09:20:59.022201       1 monitor.go:196] "Start to ping all nodes"
I0407 09:20:59.022492       1 monitor.go:345] "Received ICMP reply"
I0407 09:21:00.988498       1 monitor.go:139] "NodeLatencyMonitor updated" NodeLatencyMonitor="default"
I0407 09:21:00.988564       1 monitor.go:196] "Start to ping all nodes"
W0407 09:21:00.988638       1 shared_informer.go:416] The sharedIndexInformer has started, run more than once is not allowed
I0407 09:21:00.988784       1 monitor.go:345] "Received ICMP reply"
E0407 09:21:00.988881       1 monitor.go:334] "Received ICMP message from unexpected peer"
I0407 09:21:02.023288       1 monitor.go:345] "Received ICMP reply"
I0407 09:21:03.989596       1 monitor.go:345] "Received ICMP reply"
I0407 09:21:03.989655       1 monitor.go:235] "Finish to ping all nodes"
I0407 09:21:03.989728       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":107152,"Status":true,"LastUpdated":"2024-04-07T09:21:03.98963555Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:21:03.989744       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":78448,"Status":true,"LastUpdated":"2024-04-07T09:21:02.023312183Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:21:03.989756       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":89430,"Status":true,"LastUpdated":"2024-04-07T09:21:00.988816972Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:21:05.022773       1 monitor.go:345] "Received ICMP reply"
I0407 09:21:05.022831       1 monitor.go:235] "Finish to ping all nodes"
I0407 09:21:05.022872       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":107152,"Status":true,"LastUpdated":"2024-04-07T09:21:03.98963555Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:21:05.022891       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":78448,"Status":true,"LastUpdated":"2024-04-07T09:21:02.023312183Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:21:05.022902       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":108258,"Status":true,"LastUpdated":"2024-04-07T09:21:05.022809966Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:21:13.990694       1 monitor.go:196] "Start to ping all nodes"
I0407 09:21:13.990993       1 monitor.go:345] "Received ICMP reply"
I0407 09:21:13.991262       1 monitor.go:345] "Received ICMP reply"
W0407 09:21:15.995477       1 reflector.go:347] pkg/mod/k8s.io/client-go@v0.26.4/tools/cache/reflector.go:169: watch of *v1alpha2.NodeLatencyMonitor ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"NodeLatencyMonitor\" is registered for version \"crd.antrea.io/v1alpha2\" in scheme \"pkg/runtime/scheme.go:100\"") has prevented the request from succeeding
I0407 09:21:16.990963       1 monitor.go:345] "Received ICMP reply"
I0407 09:21:16.991030       1 monitor.go:235] "Finish to ping all nodes"
I0407 09:21:16.991107       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":175302,"Status":true,"LastUpdated":"2024-04-07T09:21:13.991328459Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:21:16.991124       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":126433,"Status":true,"LastUpdated":"2024-04-07T09:21:13.991026861Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:21:16.991136       1 monitor.go:238] "Connection status" Connection={"FromIP":"","ToIP":"<IP_ADDRESS>","Latency":72389,"Status":true,"LastUpdated":"2024-04-07T09:21:16.991006624Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0407 09:21:26.643509       1 monitor.go:171] "NodeLatencyMonitor deleted" NodeLatencyMonitor="(MISSING)"
W0407 09:21:53.220041       1 reflector.go:347] pkg/mod/k8s.io/client-go@v0.26.4/tools/cache/reflector.go:169: watch of *v1alpha2.NodeLatencyMonitor ended with: an error on the server ("unable to decode an event from the watch stream: unable to decode watch event: no kind \"NodeLatencyMonitor\" is registered for version \"crd.antrea.io/v1alpha2\" in scheme \"pkg/runtime/scheme.go:100\"") has prevented the request from succeeding
I0407 09:22:16.720088       1 monitor.go:109] "NodeLatencyMonitor added" NodeLatencyMonitor="default"
I0407 09:22:16.720189       1 monitor.go:196] "Start to ping all nodes"
W0407 09:22:16.720193       1 shared_informer.go:416] The sharedIndexInformer has started, run more than once is not allowed
I0407 09:22:16.720790       1 monitor.go:345] "Received ICMP reply"
I0407 09:22:16.721322       1 monitor.go:345] "Received ICMP reply"
I0407 09:22:19.721500       1 monitor.go:345] "Received ICMP reply"
I0407 09:22:19.721591       1 monitor.go:235] "Finish to ping all nodes"

/test-conformance

support to get gw0/podCIDR from node spec.
support singleton CRD in nodelatencymonitor.

Maybe I need to consider about the NetworkPolicyOnly mode by using Transport Address, now only support get IP from first CIDR IP.

I0408 19:16:11.801016       1 monitor.go:249] "Connection status" Connection={"FromIP":"<IP_ADDRESS>","ToIP":"<IP_ADDRESS>","Latency":0,"Status":false,"LastUpdated":"2024-04-08T19:16:11.800804713Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0408 19:16:11.801040       1 monitor.go:249] "Connection status" Connection={"FromIP":"<IP_ADDRESS>","ToIP":"<IP_ADDRESS>","Latency":97881,"Status":true,"LastUpdated":"2024-04-08T19:16:11.80070513Z","CreatedAt":"0001-01-01T00:00:00Z"}
I0408 19:16:11.801057       1 monitor.go:249] "Connection status" Connection={"FromIP":"<IP_ADDRESS>","ToIP":"<IP_ADDRESS>","Latency":0,"Status":false,"LastUpdated":"2024-04-08T19:16:11.800928351Z","CreatedAt":"0001-01-01T00:00:00Z"}

I will update my code later.

Latest log:
I0422 18:01:41.173972       1 monitor.go:315] "Recv ICMP message" IP="<IP_ADDRESS>" SeqID=6 echo={"ID":1,"Seq":6,"Data":"MjAyNC0wNC0yMlQxODowMTo0MS4xNzM4MDI0MTZa"}
I0422 18:01:41.174009       1 monitor.go:366] "NodeIPLatency status" Key="<IP_ADDRESS>" Entry={"SeqID":6,"LastSendTime":"2024-04-22T18:01:41.173802416Z","LastRecvTime":"2024-04-22T18:01:26.173511212Z","LastMeasuredRTT":451565}
I0422 18:01:41.174042       1 monitor.go:366] "NodeIPLatency status" Key="<IP_ADDRESS>" Entry={"SeqID":4,"LastSendTime":"2024-04-22T18:01:41.173511596Z","LastRecvTime":"2024-04-22T18:01:26.177130478Z","LastMeasuredRTT":3727957}
I0422 18:01:41.174064       1 monitor.go:366] "NodeIPLatency status" Key="<IP_ADDRESS>" Entry={"SeqID":5,"LastSendTime":"2024-04-22T18:01:41.17371097Z","LastRecvTime":"2024-04-22T18:01:26.177815251Z","LastMeasuredRTT":4256801}

Hi @antoninbas , do you know why the codecov bot is not running for this PR? @IRONICBo was asking about the codecov requirements for merging a PR

I don't think there has been a successful CI run yet?
For example currently, even unit tests are failing.

/test-all

I have fixed the unit test error in my local machine.
antrea/pkg/agent/monitortool# go test -race ./...
ok      antrea.io/antrea/pkg/agent/monitortool  1.243s

@antoninbas Hi mentor, please review my latest commits :)

I think we are getting there. As Antonin suggested, we will have more confidence in the monitor code if we could at least have UT for the ticker mechanism, which may need its own PR

Yes, there was already a unit test for monitor in the previous PR, as suggested by antonin, this unit test file has been removed and a new PR will be opened to redo it.

Thanks for your careful review, and I will subsequently open follow-ups subsequent PRs for monitor tool.


[BUG] 403 for URL: https://artifacts.opensearch.org/releases/plugins/repository-s3/1.0.0/repository-s3-1.0.0.zip.asc

Describe the bug
403 for URL: https://artifacts.opensearch.org/releases/plugins/repository-s3/1.0.0/repository-s3-1.0.0.zip.asc
To Reproduce
Steps to reproduce the behavior:

/usr/share/opensearch/bin/opensearch-plugin install --batch repository-s3
view error

Expected behavior
plugin to install
Plugins
That's the point the plugin did not install.
Here's the full output from an example dockerfile:
docker build . -t test:opensearch
Sending build context to Docker daemon  5.632kB
Step 1/3 : FROM opensearchproject/opensearch:1.0.0
 ---> 88b67cc9e81f
Step 2/3 : RUN /usr/share/opensearch/bin/opensearch-plugin install --batch repository-s3
 ---> Running in b2785c4c2ef8
-> Installing repository-s3
-> Downloading repository-s3 from opensearch
-> Failed installing repository-s3
-> Rolling back repository-s3
-> Rolled back repository-s3
Exception in thread "main" java.io.IOException: Server returned HTTP response code: 403 for URL: https://artifacts.opensearch.org/releases/plugins/repository-s3/1.0.0/repository-s3-1.0.0.zip.asc
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1932)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1528)
	at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:224)
	at java.base/java.net.URL.openStream(URL.java:1167)
	at org.opensearch.plugins.InstallPluginCommand.urlOpenStream(InstallPluginCommand.java:482)
	at org.opensearch.plugins.InstallPluginCommand.verifySignature(InstallPluginCommand.java:622)
	at org.opensearch.plugins.InstallPluginCommand.downloadAndValidate(InstallPluginCommand.java:600)
	at org.opensearch.plugins.InstallPluginCommand.download(InstallPluginCommand.java:306)
	at org.opensearch.plugins.InstallPluginCommand.execute(InstallPluginCommand.java:260)
	at org.opensearch.plugins.InstallPluginCommand.execute(InstallPluginCommand.java:237)
	at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:99)
	at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:140)
	at org.opensearch.cli.MultiCommand.execute(MultiCommand.java:104)
	at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:140)
	at org.opensearch.cli.Command.main(Command.java:103)
	at org.opensearch.plugins.PluginCli.main(PluginCli.java:60)
The command '/bin/sh -c /usr/share/opensearch/bin/opensearch-plugin install --batch repository-s3' returned a non-zero code: 1

Host/Environment (please complete the following information):

OS: bionic beaver

Additional context
Example Dockerfile to reproduce error:
FROM opensearchproject/opensearch:1.0.0
RUN /usr/share/opensearch/bin/opensearch-plugin install --batch repository-s3

Following these pages:
https://opensearch.org/docs/opensearch/install/docker#customize-the-docker-image
https://opensearch.org/docs/opensearch/snapshot-restore/#amazon-s3

No sure where the .asc is coming in the URL. But I am able to download with this URL
wget https://artifacts.opensearch.org/releases/plugins/repository-s3/1.0.0/repository-s3-1.0.0.zip

I realized repository-s3-1.0.0.zip.asc is actually the PGP signature file to verify integrity of download plugin artifact. Need to check with infra team that maintains artifact distribution.
@peterzhuamazon @bbarani

perhaps relates to:
https://github.com/opensearch-project/opensearch-build/issues/86

https://github.com/opensearch-project/OpenSearch/issues/996
We are still in discussion here will close this issue as it is duplicated.
Thanks.


[Proposal] Add alias StateValues for Values

IMO it would be nice to have another variable name for state values such as .StateValues as alias of .Values. In my usage, I have a lot of raw content which content .Values which is helm variable, having both helmfile .Values and helm .Values in the same file is sometimes confusing.

@itscaro what is your usecase?
I am not able to see how helmfile state values and helm values can land in the same templated yaml manifest...

I use gotmpl and inside helmfile value are used, for example, to template ingress dns. In the same file I have a list of K8S manifest like volumes which will be rendered by helm later. These configmap cannot be rendered by helmfile because helmfile .Values does not contain the values which it is generating for helm.
# .Values is helmfile's one
image:
  tag: {{.Values.app_1.version}}

ingress:
  enabled: true
  hostname: {{.Values.stack.prefix}}-{{.Environment.Name}}.{{.Values.dnsBase}}

# .Values is helm's one
# Raw content: helm will do the render
{{`
extraVolumeMounts: |
  {{- if .Values.metrics.enabled }}
  - name: metrics
    mountPath: /metrics
  {{- end }}
`}}

Other solutions to avoid having .Values of two nature:

declare locally a new variable {{ $StateValues := .Values }}, this is ok for me but having a native alias is way better ;-)
separate into multiple files, but this solution generates too many files to handle and not fits best for me.

@itscaro Hey! I looked your example but still curious how it could work.
Even if you named StateValues as .StateValues, any reference to {{ .Values }} would break your deployment as either (1)your helmfile template would fail due to missing values(because helmfile looks for state values rather than helm chart values) or (2)helm doesn't seen any {{ .Values | whatever }} expressions as helmfile has already rendered and replaced all of them.
Maybe I'm missing something? Could you share an example project that doesn't work before but starts working after #1744?

@mumoshu In the above example you can see there is usage of two .Values which do not mean the same thing. The .Values out of raw content are values coming from environment context of helmfile, and in raw part the .Values is helm's one which is values generated from helmfile.

@itscaro Ah sorry I somehow missed the beginning and the end of the template comment in the last half of your example. All good!


Plugin is building framework only for arm64 and X64

Hello,
I am trying to provide Cocoapod repository for our iOS team. I expected that the plugin will built the pod for all the architectures (x64, armv7, armv7s and arm64).
However, when we check the supported architectures via this command: lipo -info [nameOfFramework] it shows this message:
Architectures in the fat file: [nameOfFramework] are: x86_64 arm64
Did I miss some way how to config the plugin? My goal is to be able to deliver framework which run on all iPhone devices and simulator.
Thank you.

Hi,
the plugin automatically detects all the defined source sets. But, if you are using the ios target shortcut, only 64-bit arch are used.
To build also 32-bit arch, you need to manually define the sourcsets:
kotlin {
    android()

    iosArm32 {
        binaries.framework("LibraryName")
    }
    iosArm64 {
        binaries.framework("LibraryName")
    }
    iosX64 {
        binaries.framework("LibraryName")
    }

    sourceSets {
        val commonMain by getting
        val commonTest by getting {
            dependencies {
                implementation(kotlin("test-common"))
                implementation(kotlin("test-annotations-common"))
            }
        }

       ...

        val iosArm64Main by getting
        val iosArm64Test by getting
        val iosArm32Main by getting
        val iosArm32Test by getting
        val iosX64Main by getting
        val iosX64Test by getting

    }
}

And just to avoid duplicating code into different source sets, you can use a symlink


can we find Calufa's missing scrape?

The archive.org copy has been taken down: https://archive.org/details/2011-05-calufa-twitter-sql

About the data:

- DB Size: 543 million rows

- Data Size: 173GB (uncompressed)

- Stored in mysql

- 200+ Million tweets from 13+ Million users

Several mentions on HackerNews: https://news.ycombinator.com/item?id=2633384
another dead link: http://burnbit.com/torrent/170493/twitter_sql_bz2

added it to my PR https://github.com/philshem/awesome-twitter-data/tree/patch-1


[FLINK-8228][cleanup] Code cleanup - pointless bitwise expressions

Brief change log
Remove pointless bitwise expressions, Such expressions include anding with zero, oring by zero, and shifting by zero.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

I think these zeros are there to make the formatting more similar and to also highlight, that this is the case were we don't shift. So I would like to keep this as is. What do you think?

If this change does not improve performance, I agree with you keep origin formatting. :)


Add Onduis Analytics

Onduis Analytics is privacy-focused simple web analytics. Track your visitors in real time, without compromising their privacy.

Hi, could you make the PR again on the main branch?
Thank you.


OrchardCoreContrib.Html not released as nuget package

Could you release OrchardCoreContrib.Html module as nuget package?

It's just a preview version, we need to get a feedback from the users, if all goes well we will bump the version to 1.0.0. Your feedback is welcome

It's just a preview version, we need to get a feedback from the users, if all goes well we will bump the version to 1.0.0. Your feedback is welcome
OK, I'll give my feedback when try the module.

@DotCat1985 did you try the HTML module, I'm glad to hear any feedback from you, before releasing 1.0.0

@DotCat1985 did you try the HTML module, I'm glad to hear any feedback from you, before releasing 1.0.0

OK. I'll provide some feedback to you as soon as I complete my test.

I give a feedback about my test now.
GrapeJS editor is cropped by scrollbar (see the attached screenshot).

The editor seems to work well.
How can I write Liquid code using GrapeJS editor?
I know any HTML field can include Liquid code.

I filed two issues #63 #64 for tracking, the first one might needs increase the width, @kudryavtsevda did you try Liquid in GrapesJS editor before?


Generate and upload API documentation

@seroukhov completed

It is not quite completed yet. We need to completely reimplement the mocks. After that all API docs shall be updated


Fix Time#getlocal signature

Motivation
Fix signature of Time#getlocal so it can also take a String offset, not just Integer.
Test plan
None, docs above already state that it can be called with a String.

Stripe build: http://go/builds/bui_H9Z2odu1OIio3S


MAVSDK timeout tuning

It seems to me that the timeout used in MAVSDK is a bit low for bad links (I'm thinking about a slow connection to a cloud simulator), resulting in a lot of timeouts (which makes it difficult to e.g. upload a reasonably-sized mission).
@julianoes: is there a global timeout that can be tuned, and what would it imply if we increased it? Like do we want to have an option to set the timeout (or choose the link speed), or would it be fine to just increase the timeout for everybody?
From my tests uploading a big mission to a cloud simulator, each waypoint took an average 0.4s to upload... I have heard of issues when uploading from a device emulator (iOS/Android), so I wonder if that maybe went above 0.5s, triggering the timeouts?

I added this a while ago, give it a try:
https://github.com/mavlink/MAVSDK/blob/f7e96f3579c4d199e8a28197568409cfbd65bfb4/src/core/mavsdk.h#L271-L279

Hi,
First post here so I hope this is the right location...
I would like to get this working too and I am willing to put effort in this to achieve this. I am currently trying to upload a mission via a serial connection (holybro telemetry radio v3) to a pixhawk 4 and keep getting the timeout. I am using mavsdk v0.40.0
Can you give my some guidance?
Thanks,
Raymond

@reedev doesn't the set_timeout_s function above do what you want? Haven't used it yet, but I think it's exactly what I want

no, I put the line
mavsdk.set_timeout_s(5.0);
right after the allocation of mavsdk and within the 5 seconds I get the message 'Mission upload failed (Timeout), exiting'

@reedev this would mean something with the other side or the communication goes wrong. Please create a new issue and describe how to reproduce the problem.

Sure, that's why I opened the other issue, so that I can chip in myself
and find details.
On 7-6-2021 08:20, Julian Oes wrote:

@reedev https://github.com/reedev this would mean something with the
other side or the communication goes wrong. Please create a new issue
and describe how to reproduce the problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mavlink/MAVSDK/issues/1441#issuecomment-855620373,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASINJBTWEHELYWAMRMOQH3TRRQMNANCNFSM45L3LEZQ.

--
--
Deze e-mail is gecontroleerd op virussen door AVG.
http://www.avg.com

Sure, that's why I opened the other issue, so that I can chip in myself and find details. I will get back on this.

That's interesting: I went back in time and I could upload the mission via the fly_mission.cpp from v0.22.0 Although with some timeouts 28 mission items were uploaded. Double checked with QGC and I see the mission near the Milchbuck-Tunnel
I will proceed... (when time allows)

(intermediate update) this is rather interesting: v0.24.0 works as expected while v0.25.0 does not anymore. The interface has changed between these versions too so it seems a rather large change. Still going on...

We have an integration test for lossy mission transfers: https://github.com/mavlink/MAVSDK/blob/main/src/integration_tests/mission_transfer_lossy.cpp
So best would be if you could change that so you can reproduce your issue.

From v0.24.0 to v0.25.0 I completely rewrote the mission upload, so it's possible I got something wrong.

So best would be if you could change that so you can reproduce your issue.

I second that! It would be very interesting if you had an integration test that fails for you, so we could try to reproduce on our side!

Sure! I will do my best and need to dive into this first to get familiar with the integration tests.

This should be enough:
cmake --build build/default -j8 && build/default/src/integration_tests/integration_tests_runner --gtest_filter="SitlTest.MissionTransferLossy"

@julianoes I use MAVSDK-Java in my project and I had the timeout issues with upload and download over high latency radio link. I compiled a new version of MAVSDK by setting the default timeout as below in mavsdk.h
static constexpr double DEFAULT_TIMEOUT_S = 5;
I can confirm that the upload mission timeout is fixed but this doesn't work for download mission api. Is there a different timeout setting for download mission?
Please suggest.

I am using the recently released MAVSDK Python 0.19.0, and similar to what is described above I increased the set_mavlink_timeout(timeout_s) function to 5 and 10 secs, It doesn't work with more than 1 waypoint. Uploading a mission via a serial connection (holybro telemetry radio v3) to a pixhawk 4 unfortunately results in a timeout.

5 or 10 seconds seems way too high, it likely won't work because PX4 on the other side still assumes a timeout much lower, around 0.5 seconds. What is the ping/latency between MAVSDK and PX4 for your setup?

I might be wrong but I assumed the timeout  function told PX4 what timeout to expect? From your answer, I gather I would have better results if put the timeout at 1 or 2 secs?
I haven’t checked the latency between MAVSDK and PX4 but since I’m using radios to communicate, it shouldn’t be too high.

Quick update from my side. I noticed the recent timeout related changes and tried out fly_mission and the result is still the same, could not upload a mission. I will check out the integration test asap...

v0.42.0
I tested with a Herelink / Pixhawk4 / PX4 setup with a different result: the autopilot is not found.
I also tested with sitl with Gazebo and that's working as expected.

I might be wrong but I assumed the timeout function told PX4 what timeout to expect?

No, it's really on the MAVSDK side: it tells MAVSDK which timeout to use. You are right that it would make sense to synchronize that value with PX4, but MAVLink does not provide that, and I don't know what it would imply on the PX4 side (and how one would handle the case where PX4 does not support it).

Let's close that, it's been inactive for a long time. Feel free to reopen if necessary, or create a new issue if the timeout has a bug.


Update GitHub project description to mention Oracle

Is it time to update the project description to mention Oracle? Currently it just says "A query builder for PostgreSQL, MySQL and SQLite3".

@tgriesser or someone else, who has enough control to change project settings is needed for this. Maybe @rhys-vdw has enough rights?

@tgriesser Can this be done? MSSQL is also missing.


Streaming sink for Spark Structured Streaming

Develop a streaming sink for splice machine. In other words, it should be possible to run a streaming query with the following:
dataframe.writeStream.format("splice")

Proved to be working fine in 4d200effa6b19ca6880cbd3a57408ac02422f22b


Update README.md

update readme for better understanding where the testing support library is located

I signet it!

Cheers thanks!


Can't find documentation for MongoDB integration

In the user docs it is mentioned that invenio can be integrated with mongodb: but I can't find any documentation to do that.

This seems to be much older Invenio v2 documentation. Keep in mind that v2 is not suitable for production systems and isn't actively developed. If you are building something new you should start with the latest documentation on v3.
Invenio v3 does not officially support MongoDB, though this doesn't prevent anyone from using MongoDB to develop features or other Invenio modules.


New package: NeuronBuilder v0.1.0

Registering package: NeuronBuilder
Repository: https://github.com/Dhruva2/NeuronBuilder
Created by: @AndreaRamirezH
Version: v0.1.0
Commit: 84f86c3b78daea3fb41659ed39f5716726b04254
Reviewed by: @AndreaRamirezH
Reference: https://github.com/Dhruva2/NeuronBuilder/commit/84f86c3b78daea3fb41659ed39f5716726b04254#commitcomment-69431912
Description: Builds conductance based neural networks iteratively, from ion channels and synapses

@AndreaRamirezH
please see the message above.  Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.  Also, why does your package depend on Revise at all?  That's a development tool, packages shouldn't normally depend on it, users will use it locally.
[noblock]

Hi @giordano
Yeah, you're right, I was using Revise for development but now I've removed it from the dependencies.
The two issues are fixed :) and I re-did the registration in the last commit yesterday. Just waiting for the pull request to be updated.

Just waiting for the pull request to be updated.

To be clear, you have to update the pull request by triggering registration again without changing the version number
[noblock]

Yes, I believe I already did
https://github.com/Dhruva2/NeuronBuilder.jl/commit/3a18ddab9a87d2b1698874c6b930b41268ffd404#commitcomment-69459255
Isn't this re-triggering the registration?
[noblock]

Clearly not, since the bot didn't reply to you and this pull request wasn't changed 🙂  You may want to try again.  Maybe yesterday your message didn't go through because of the github outage: https://www.githubstatus.com/incidents/y5hdmv0p49x3
[noblock]

@giordano ah! I was wondering why it took so long to get a reply! Ok that was very useful thanks!
This time it seems to be working  :)


Fastlane updating causes an error

Step version 2.2.0, no Gemfile in work_dir, so the system installed fastlane is used. "Should update fastlane gem before run?" is true.
Logs:
+------------------------------------------------------------------------------+
| (7) fastlane testflight                                                      |
+------------------------------------------------------------------------------+
| id: fastlane                                                                 |
| version: 2.2.0                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2016-12-18T18:41:59-08:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
$ cd /Users/vagrant/git/ios

 (i) No Gemfile found - using system installed fastlane ...
 (i) Updating fastlane ...
$ gem install fastlane --no-document
ERROR:  Error installing fastlane:
	fastlane requires xcode-install (~> 2.0.0)
Successfully installed xcpretty-0.2.4
Successfully installed gh_inspector-1.0.2
Successfully installed word_wrap-1.0.0
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | fastlane testflight (exit code: 1)                            | 4.92 sec |
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-io/steps-fastlane/issues           |
| Source: https://github.com/bitrise-io/steps-fastlane                         |
+---+---------------------------------------------------------------+----------+

Currently the system installed version is 1.84.0, so disabling the festlane update is not a good idea. Of course, we can put Gemfile into work_dir, but still the system version updating remains broken.

Please report this on fastlane's issue tracker, all this step does is gem install fastlane - the issue comes from the dependency definitions of fastlane


Basic fonts

Are there any basic fonts like Arial or Times Roman the exist across all platforms?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fe0572c4-91be-fc86-d130-242db2bf470b
Version Independent ID: 1238fdd7-c378-6d0d-654e-55656a70d386
Content: Fonts in Xamarin.Forms - Xamarin
Content Source: docs/xamarin-forms/user-interface/text/fonts.md
Product: xamarin
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Xamarin.Forms runs on a lot of platforms, I'm not aware of any font that's guaranteed to be on all of them. I'd recommend not specifying the FontFamily (which means your app will use the default) or specify a specific font for each platform that you have tested and know works.


README

README
User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily dins and read the information
Acceptance Criteria
GIVEN the prework project repository
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

Completed


State setter feature

Coverage decreased (-4.4%) to 94.175% when pulling 94cb9946b810a7d6e4e4cacc8ec88c3d6c631110 on state-setter-feature into 8e28e0c539dc7b4cae2f893b97eb4dd9ef3388e1 on master.


Tweaks on user switching

@keybase/react-hackers

@jakob223 I can't manage to see the mobile version for this feature. Is it behind a feature flag on mobile?

Will this show a badge on users with currently unread notifications?

@junderw The first version of it won't have badges but it's on our roadmap.

@keybase/react-hackers Bump ^

@jakob223 I can't manage to see the mobile version for this feature. Is it behind a feature flag on mobile?

I think I answered this in chat, but in case I didn't: yes, it's behind a feature flag for now until we can polish it when IMP TOFU is finished.


Rimworld of Magic: Gateway spell hangs the game

Describe the bug
Arcane mage's spell "Gateway" stopping game completely
Steps to reproduce the behavior (VERY IMPORTANT)

start new game
get arcane mage somehow (spawn and use arcane gem + arcane tome: power)
spawn and learn gateway spell scroll
use spell on any location
game not responding

Error Log
Player.log https://gist.github.com/disarmer/3bdae54dc458ca82f3ee237a873f5efc
Mod list (Preferably a RimPy compatible list.)

brrainz.harmony
ludeon.rimworld (core)
unlimitedhugs.hugslib
jecrell.jecstools
torann.arimworldofmagic
majorhoff.rimthreaded

Can confirm.
Test Save:
https://drive.google.com/file/d/16NuekJg0YmffEDWf6Ol7MyEJQFdCYRYG/view?usp=sharing
Go into the save and cast Arcane Gateway. The freeze only happens after you place the spell on your colony tile. There is no error produced in the player log, even after about 10 minutes of waiting. I guess it freezes before it can write error to file.


Further cleanup on Application::Client and Solo and deprecate solo_legacy_mode UX

🚧
closes #8366
fixes #6375
fixes #8138

#8361 broke executing single recipes since dropping privs also does a chdir and the work done to error if the recipes don't exist happen after the chdir now and fail.  that probably needs to get addressed somehow.

@lamont-granquist is this on the todo list for chef 17?


Created hole trigger for scoring

When the trigger is touched by the player the game will change its state to end.

@kristiana11

this looks good


descale: Add descaled_height prop

It'd be nice if there was a way to check what resolution the clip was descaled to when given two or more native resolutions. I think a frameprop is the least intrusive way to do so.

It already does that

https://github.com/Irrational-Encoding-Wizardry/vs-scale/blob/master/vsscale/descale.py#L286
https://github.com/Irrational-Encoding-Wizardry/vs-scale/blob/master/vsscale/types.py#L105


[SPARK-12155] [SPARK-12253] Fix executor OOM in unified memory management

Problem. In unified memory management, acquiring execution memory may lead to eviction of storage memory. However, the space freed from evicting cached blocks is distributed among all active tasks. Thus, an incorrect upper bound on the execution memory per task can cause the acquisition to fail, leading to OOM's and premature spills.
Example. Suppose total memory is 1000B, cached blocks occupy 900B, spark.memory.storageFraction is 0.4, and there are two active tasks. In this case, the cap on task execution memory is 100B / 2 = 50B. If task A tries to acquire 200B, it will evict 100B of storage but can only acquire 50B because of the incorrect cap. For another example, see this regression test that I stole from @JoshRosen.
Solution. Fix the cap on task execution memory. It should take into account the space that could have been freed by storage in addition to the current amount of memory available to execution. In the example above, the correct cap would have been 600B / 2 = 300B.
This patch also guards against the race condition (SPARK-12253):
(1) Existing tasks collectively occupy all execution memory
(2) New task comes in and blocks while existing tasks spill
(3) After tasks finish spilling, another task jumps in and puts in a large block, stealing the freed memory
(4) New task still cannot acquire memory and goes back to sleep

@JoshRosen @davies

Test build #47474 has started for PR 10240 at commit cd0c680.

Test build #47474 has finished for PR 10240 at commit cd0c680.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  *         logInfo(s\"HBase class not found $e\")\n  *         logDebug(\"HBase class not found\", e)\n

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47474/
Test FAILed.

Test build #47491 has started for PR 10240 at commit d8be669.

Test build #47491 has finished for PR 10240 at commit d8be669.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47491/
Test PASSed.

Test build #2195 has started for PR 10240 at commit d8be669.

Test build #2195 has finished for PR 10240 at commit d8be669.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

ok, retest this please

Last commit actually passed tests last night.

Test build #47528 has started for PR 10240 at commit d8be669.

Test build #47528 has finished for PR 10240 at commit d8be669.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47528/
Test PASSed.

Merged build finished. Test PASSed.

retest this please

@davies please look at the final changes.

Test build #47539 has started for PR 10240 at commit 2929640.

Test build #2197 has started for PR 10240 at commit d8be669.

Test build #2196 has started for PR 10240 at commit d8be669.

Test build #2198 has started for PR 10240 at commit d8be669.

LGTM

Test build #2198 has finished for PR 10240 at commit d8be669.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  *         logInfo(s\"HBase class not found $e\")\n  *         logDebug(\"HBase class not found\", e)\n

Test build #47539 has finished for PR 10240 at commit 2929640.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47539/
Test PASSed.

Merged build finished. Test PASSed.

Test build #2197 has finished for PR 10240 at commit d8be669.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #2196 has finished for PR 10240 at commit d8be669.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Thanks, merging into master 1.6.


How is multishell data split in multiple files handled?

Hello !
I have a similar question as #320. I have multi-shell data which was acquired with slightly different parameters (see screenshot below), and are split by b-values: one file for b=1000, one for b=2000.
Here's what it looks like after putting in BIDS format:
.
├── dataset_description.json
├── sub-1
│   ├── anat
│   │   ├── sub-1_run-1_T1w.json
│   │   ├── sub-1_run-1_T1w.nii.gz
│   │   ├── sub-1_run-1_T2w.json
│   │   └── sub-1_run-1_T2w.nii.gz
│   └── dwi
│       ├── sub-1_acq-d30b1000_run-1_dwi.bval
│       ├── sub-1_acq-d30b1000_run-1_dwi.bvec
│       ├── sub-1_acq-d30b1000_run-1_dwi.json
│       ├── sub-1_acq-d30b1000_run-1_dwi.nii.gz
│       ├── sub-1_acq-d55b2000_run-1_dwi.bval
│       ├── sub-1_acq-d55b2000_run-1_dwi.bvec
│       ├── sub-1_acq-d55b2000_run-1_dwi.json
│       └── sub-1_acq-d55b2000_run-1_dwi.nii.gz
...

I'm not quite sure how qsiprep will handle that: should I concatenate the files myself before running it, is there a special argument to use? I saw on BIDS docs there is a multipart-split-dwi-schemes, but not sure if this the right way to go about that either.

Any help would be appreciated, thank you!

Given the difference in TE between the acquisitions, I would expect the measurements to differ between the two scans in ways that are not predictable only by the b-values. For example, I'd expect the b=0 measurements to systematically differ. One approach to correcting for this would be to pre-process each of the scans separately and then add a post-processing step where each volume (including b=0 volumes) is normalized to its average b=0 measurement before proceeding with any of the reconstruction steps (e.g., modeling). I'd be curious to hear other folks' thoughts on this, and whether qsiprep already supports this kind of use-case.

Is it not common to collect multiple b>0 values in GE DWI scans? @arokem I had typed something almost identical, and agree that processing these separately is likely the safest way to go. You can do this with the --separate-all-dwis flag, which will process each independently. Without this flag, qsiprep will concatenate these scans and your downstream analyses may not work as intended.
I wonder if this is similar to what used to happen for some siemens sequences where big delta and little delta would get secretly adjusted under the hood depending on the maximum b-value in the sequence. Based on the different TE, this might be happening in these scans. If that is the case you'll need to be extra careful when using something like MAPMRI (you won't be able to use the qsiprep mapmri recon workflow, unfortunately). I'm not sure how it will impact the multi shell - multi tissue methods.
Slightly off topic: you will need to make sure you have "PhaseEncodingDirection" and "TotalReadoutTime" defined in these sidecars.

Thank you for your feedback! Another source pointed out by a colleague:
https://community.mrtrix.org/t/dwi-images-with-different-echo-times/5892
@mattcieslak thanks for the note, these two values are defined in the sidecars.

So it seems that the steps would be to:

preprocess the dwis separately (with --separate-all-dwis)
do some kind of normalization: @jdtournier proposes to do a "matching and concatenation based on histogram matching of the b=0 images" (link), @arokem "normalized to its average b=0", any thoughts?

For further processing, which might be beyond the scope of this thread, such as pyAFQ and especially FOD computing, it seems most wouldn't be appropriate (ref in link above), but MSMT-CSD should work? I'd be curious to understand that last part better.
Thank you all for your help & insights!

Do you have a plan for correcting geometric distortion? Does your TotalReadoutTime vary between the series?

The only differences are highlighted in the screenshot above, TotalReadoutTime is the same for both series.

Ah OK. I was thinking you can theoretically use topup if the echo spacing varies, even if the phase encode dir is the same.


Update protos end of utterance params

With these changes, clients can now configure end and start of utterance for streaming ASR client

@manishaj-nv let's go ahead with specific message for end of utterance config.
it will be better to rename EOUConfig to EndpointingConfig for better clarity

LGTM. Will wait for other MRs (server/clients) to be ready, so we can merge everything together.


Add Support for Highlight to VS Options

@madskristensen what does it look like I screwed up here? I threw this together a bit too quickly.

Here's what it says
D:\a\MarkdownEditor2022\MarkdownEditor2022\src\Editor\ClassificationTypes.cs(57,52): error CS0102: The type 'ClassificationTypes' already contains a definition for 'MarkdownClassificationLink'


Updated Mod 5 Lab 1, providing the correct steps to install the agent

Module: 05
Lab: Configuring Agent Pools and Understanding Pipeline Styles
Fixes #57.
Changes proposed in this pull request:

Prepare the PowerShell commands to be copied&pasted directly without the need for modification.

updated steps approved


Next iteration of x-element (soon to be 1.0.0).

This is a clean version of #58 — that PR began as an exploration and turned into a promising candidate for our initial 1.0.0. Since the discussions got lengthy in there, I decided to start fresh with a better branch name and a clean slate.
Significant changes:

Static analysis is done up-front, once.
Anything that can be validated statically throws errors
Environment / runtime errors console.warn (e.g., inherited property shadowing, data-* attributes, etc.)
Almost all of the XElement interface is static.
observer >> observe is now a function (proper context is maintained if it's a constructor method).
computed >> input + compute. compute is now a function. input is an array of property names which will be resolved to arguments at runtime and passed to compute.
value >> initial + default. initial is used if initial value is nullish. default is used if property value is ever nullish.
Type coercion is no longer done on set.
Errors are thrown when you set a value with an incorrect type in the runtime.
Concept of readOnly is first-class.
Concept of internal is first-class.
Internal setting/getting and read-only setting can be done via the .internal proxy.
Computed properties are now lazily evaluated.
Observation, reflection, and computation are no longer synchronous. Importantly, this allows us to set properties one-by-one and then get a single compute at the end.
Concept of a "render root" is now supported via createRenderRoot.
We always allow computation of computed properties before any arguments are defined. Previously, we had questioned that approach.
Swapped the order of values in observe callbacks to be value, oldValue — it was previously oldValue, value.
Order of operations are now compute, reflect, render, then observe.
Listener logic has been improved and interface is now a function, not a string.
All callbacks are bound to the constructor (e.g., compute, listen, observe, etc).
Coercion of null and undefined to '' is removed, the underlying templating engine takes care of this for us.
Deserialization of anything other than [Boolean, String, Number] now throws a halting error (e.g., setting an attribute for a property that is of type: Object).

FYI @klebba — I think we're finally ready to merge this!

Note — we will probably bump to 1.0.0-rc.41 before finally moving to 1.0.0. The important part is that we should be clear to merge this in and release 👌

@theengineear awesome work!


is_sorted in o(n) solution

Solves Issue #

Description:
Checklist

- [x ] I've followed the Contributing guidelines provided in the repository.
- [x ] I've made the changes which were demanded in the linked issue.
- [x ] My code gave a clean output on debugging. (NO warnings/errors)

LGTM, Thanks @jerryxu158 for the contribution!
Meanwhile, we review your PR you can create or work on the issues!
Happy Open Sourcing


Each item in the list has a checkbox allowing me to mark individual publications. The titlebar has a checkbox which will check all checkboxes, marking all publications. A counter in the titlebar shows the number of publications marked.

Will fix this with the new import flow.


Follow up to PR 1606 to avoid int overflow during star tree creation.

When computing offsets that are larger than Integer.MAX_VALUE (as a
result of multiplication), we need to ensure that the result of
multiplication does not cause integer overflow, and is properly upcasted
to long.

Codecov Report

Merging #1664 into master will increase coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1664      +/-   ##
==========================================
+ Coverage   67.77%   67.79%   +0.02%
==========================================
  Files         829      829
  Lines       40244    40245       +1
  Branches     5300     5300
==========================================
+ Hits        27274    27286      +12
+ Misses      11131    11122       -9
+ Partials     1839     1837       -2

Impacted Files
Coverage Δ

...nkedin/pinot/core/startree/StarTreeDataSorter.java
77.89% <0%> (-0.83%)
:arrow_down:

...not/common/segment/fetcher/HttpSegmentFetcher.java
28.57% <0%> (-19.05%)
:arrow_down:

...m/linkedin/pinot/common/utils/FileUploadUtils.java
45.58% <0%> (-7.36%)
:arrow_down:

...filter/SortedInvertedIndexBasedFilterOperator.java
71.62% <0%> (-5.41%)
:arrow_down:

...afkaHighLevelConsumerBasedRoutingTableBuilder.java
89.28% <0%> (-3.58%)
:arrow_down:

...core/retention/strategy/TimeRetentionStrategy.java
63.33% <0%> (-3.34%)
:arrow_down:

...edin/pinot/common/metadata/ZKMetadataProvider.java
68.5% <0%> (-1.58%)
:arrow_down:

...e/operator/dociditerators/MVScanDocIdIterator.java
62.68% <0%> (-1.5%)
:arrow_down:

...lix/core/realtime/PinotRealtimeSegmentManager.java
73.14% <0%> (-1.15%)
:arrow_down:

...ot/broker/requesthandler/BrokerRequestHandler.java
88.02% <0%> (-0.65%)
:arrow_down:

... and 11 more

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 c68c42c...af590a8. Read the comment docs.


cannot be preloaded (cannot open shared object file): ignored.

After this;
!rm -r render
!mkdir render
if upload_type == 'gdrive_relative':
if not drive_path.endswith('/'):
drive_path += '/'
!cp -r '/drive/My Drive/{drive_path}.' 'render/'
elif uploaded_filename.lower().endswith('.zip'):
!unzip -o $uploaded_filename -d 'render/'
elif uploaded_filename.lower().endswith('.blend'):
shutil.copy(uploaded_filename, 'render/')
blend_file_path = uploaded_filename
else:
raise SystemExit("Invalid file extension, only .blend and .zip can be uploaded.")
I GET THIS FOR A SINGLE CUBE BLEND FILE
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libtcmalloc_minimal.so.4.3.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

This comment is for the developer of this Script @ynshung:
You can solve this error by replacing os.environ["LD_PRELOAD"] = "/usr/lib/x86_64-linux-gnu/libtcmalloc_minimal.so.4.3.0" with os.environ["LD_PRELOAD"] = "/usr/lib/x86_64-linux-gnu/libtcmalloc_minimal.so.4.5.9"
The updated version of libtcmalloc_minimal i.e., 4.5.9 works without an error.
Additionally, I have my own render script which is in my opinion a little more stable, future proof and easier to use and I will not mind if you use my script to improve this script but would be happy if you do so, link down below:
Colab Link: https://colab.research.google.com/github/Dev123456689/Google_Colab_Render/blob/main/Free_Render.ipynb
Github File link: https://github.com/Dev123456689/Google_Colab_Render/blob/main/Free_Render.ipynb
And for @HTPCall:
Just ignore the error, it will do no harm


doc: correct some translations of heft/overview

There are some same pronounced words.
In case "It's easy to write your own plugins", previous version translated "write" into "边写" which means "write and do something in the meanwhile", and "编写" is the correct word.

It's maybe a long-term job to validate the translation. I just start reading doc and I will check confused words and correct them in this PR.


help docs: Fix a wrong link in create-a-stream doc

Discussion:
https://chat.zulip.org/#narrow/stream/19-documentation/topic/Wrong.20link.20.28stream.20creation.29/near/1380786

Merged, thanks @chrisbobbe!


Fix C# server start when not all ports have been bound.

Fixes https://github.com/grpc/grpc/issues/18100.
The issue was that throwing the IOException terminated the normal C# server startup process and the server got stuck in a half-initialized state.  The fix makes it possible to start a server even if some of the ports failed to bind (which matches the C core behavior that allows that).

@chwarr  feel free to review.


jackson ident not working

jackson ident doesn't seem to work. This is probably an I durm situation.
I have this... but the json is only output on a single line, suggestions? client is super simple, I suspect you could client up anything with log level full to test this.
@SpringBootTest
@ActiveProfiles("dev")
@TestPropertySource(
  properties = [
    "cof.devexchange.feign-log-level = full", // is output but only on a single line
    "spring.jackson.serialization.indent-output= true"
  ]
)
internal class BusinessDivisionClientLiveTest @Autowired constructor(val client: BusinessDivisionClient) {
  @Test
  @WithMockUser
  fun findAllBy() {
    val res = client.findAllBy(BusinessDivisionQueryParams(includeRoles = true))
    assertThat(res.divisions).isNotEmpty
  }
}

Which version are you using @xenoterracide ?

Also, could you provide a full executable sample that we could verify?

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Serialize metadata as blob in tx RPC when binary flag is true

In the tx command, transaction metadata is always returned in expanded JSON form, even if binary is set to true in the request. The transaction itself is encoded as a blob if binary is set to true, just not the metadata. This PR fixes that.

This change is

Just confirmed that this is a regression in 1.7.0. The command works as expected in 1.6.0.

This PR should also add unit tests for this so it doesn't happen again.

I spent some time looking at history.  If I'm reading the history correctly, the binary flag caused the metadata to be returned in binary until 1.5.0-b6.  So, since then, the metadata has been returned as JSON regardless of the state of the binary flag.
I'm of two minds.  When the bug was released to the wild with 1.5.0 nobody noticed.  So apparently no one was using the feature a year ago.  A year has passed, and probably no one is relying on the changed behavior?  But we don't know for sure until we change the behavior back and potentially break someone.
If we put this change in now then the bug will be resident in released software versions for approximately 1.5 years before we switch it back.
The best path forward is not clear to me.  There are advantages and disadvantages to leaving the bug in place or fixing it.

Oh! Thanks @mDuo13.  A test is better than me mis-reading the code.
Since the behavior was correct in 1.6.0, I think the best choice is to release the fix in a 1.7.1.  That way we don't have 6 months of users getting the wrong interface and having it switched back at the end of it.
And, yes, I agree with @mDuo, the final version of this commit wants a unit test to verify the behavior.

I'll add some unit tests, hopefully tomorrow. If we had those unit tests before, we could have caught this during review. So we definitely need the unit tests.

Looks like this bug is on me, here's where the regression occurred (#3564).
Will approve after unit tests are added, and I defer to y'all about the best path forward.

Looks like this bug is my fault, here's where the regression occurred (#3564).
Will approve after unit tests are added, and I defer to y'all about the best path forward.

I reviewed your original PR and didn't catch this, so also my fault.

@natenichols @cjcobb23 Post-mortems are valuable to determine ways to prevent a problem from recurring; blame less so. As a group, we all share responsibility for what is released, from the coders to the formal reviewers to the informal reviewers to the testers to the mergers to the bosses to those who didn't look at all ("Eh, it's got two reviews. I'm sure it's fine."). The important things are that the problem got caught and fixed before it caused too many problems, and that unit tests are being added to catch similar mistakes in the future.

haha, I read that as " bosses who didn't look at all " somehow

to those who didn't look at all

I was specifically thinking about myself with this one, because there are a lot of PRs I don't pay attention to. :grinning:


Feat/meeting card container/create

Description
The scope of the changes in this pull request are to create the core <MeetingCardContainer /> component that will be utilized for all upcoming Meeting Container components. This component can be later used as the root for <MeetingListItem /> container once the Meeting Container components are generated.
Note - The changes in this pull request also allow for localized CSS Variables to be created to help reduce code footprint and improve readability when multiple variations of a component utilize similar values from our design tokens.
Screenshots

Links
SPARK-313907
Figma Article.

Nit: the screenshot for status color is showing "rounding = inactive". Is that an old shot?

Nit: the screenshot for status color is showing "rounding = inactive". Is that an old shot?

This needed to be fixed, but i didn't notice it. Thanks! it's been updated/fixed!

I have updated the naming from <MeetingCardContainer /> to <CalendarCard /> to better match the design articles.

Also, still seeing both MeetingCardContainer and CalendarCard in storybook if i run it.

Also, still seeing both MeetingCardContainer and CalendarCard in storybook if i run it.

Not sure why this is, I am not seeing this:

This has been updated to accepted the new tokens in the tokens repo. as well as reflect the new design specifying card instead of calendar card.


[css-masks] Update resource blog post link

As suggested in https://github.com/Fyrd/caniuse/issues/4474

Thanks!


[WIP] 27/adoption

This PR adds

transfer action
claim action
relevant UI

Do not merge, only comment for now.

Nice PR Fridger!
So I was reviewing here and we cant add new_owner to the pet table. We can't add new fields in tables like that after the contract is in production, because it would require more ram for all the users, so we would need to do a migration (like I did with petconfig/petconfig2).
The thing here is we may not need to migrate. What if we create a table called petorders. It would be the beginning of the pet transfer market. So people can announce their pet to sell and people would be able to browse the market to buy other pets.
At the end of the process if the order is complete we change the ownership of the pet (in the original table that didn't need to add a new field), if not, if they cancel it, we just delete the order.

That sounds good! Let's do that.


useMediaControls: Add volumechange event listener

If you change the volume or muted values by native controls (or in devtools) it does not effect reactive variables. Here is a demonstration.

Wrong repo 😅


Edit Settings button does not work in High Sierra

Is there a another way to edit the settings?

Apologies, I completely forgot about this!
Will push a fix in a minute.

Awesome :)
Thanks


adds docs for time operators

Please lmk if there are other areas to update tests.

Will use this, thanks. But gonna do a refactoring of docs.


Fix log tests

Fix the name of a log test to include the .spec.js suffix and added a batch job to run tests in a loop.

:tada: This PR is included in version 0.368.0 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


some git-2.35.1 tests fail with zlib-ng-2.0.6 in compat mode

Three git-2.35.1 tests fail on my system with libz.so.1 provided by zlib-ng-2.0.6:
not ok 35 - basic atom: head objectsize:disk
not ok 91 - basic atom: tag objectsize:disk
not ok 92 - basic atom: tag *objectsize:disk

By LD_PRELOAD the original libz.so (from old zlib) these tests pass.
I'm not sure if this is a bug in zlib-ng, or a mere difference unexpected by git.

I think they are relying on the output size of zlib datastream which is not necessary the same for zlib-ng. See https://github.com/zlib-ng/zlib-ng/discussions/905.

If you find out there is an actual bug please reopen.

If you find out there is an actual bug please reopen.

I don't think this is an actual bug.


More collection item editor options

Changes

Add shouldDrawGotoButton and shouldDrawPreviewButton to CollectionItemEditorOptions, use auto-properties

Added OptionsAttribute getting and passing through to CollectionItemPropertyDrawer

Changed CollectionItemPropertyDrawer to allow for OptionsAttribute to be provided in constructor

Refactored CollectionItemIndirectReferencePropertyDrawer OnGUI into subfunctions for readability

Change DrawGotoButton to use the same parameters as DrawEditFoldoutButton

Renamed CollectionItemItemPropertyDrawer to CollectionItemPropertyDrawer

Unrelated to Expanded Options:

Fix T is also used as the Type variable of the class by using TInstance instead of T (+5 squashed commit)
Add [Preserve] to AoT helper code, so that it survives code stripping

Nice work! :)
Thanks for the contribution!


Run nvcc via ccache in flash-attn

On my test box, compiling candle-flash-attn from scratch in debug takes about 3 minutes, but most of this time is spent running nvcc on the flash attention kernels. Running nvcc via ccache brings this down to around 15 seconds (on the second build). Also, the ccache is shared between debug and release builds.
Do you think it's OK to always run via ccache? It seems straightforward to install.

Actually we already have a caching mechanism for this though you need to use an environment variable to set it, see this comment.

Closing this as stale.


BUG: As a user, I can't find the Dublin city in location picker

When I tried to search for the Dublin, the We couldn't find what you were looking for message appears.
Steps:

open location picker
write Dublin
no results

When I checked the graphql console I saw this error

I got the same or similar when I was searching for Malaga. Appeared that it spelled like Málaga and I didnt even know about it before (lived there for 3-4 years 😅)
And the search didnt give any suggestions


delay sending proposal callback to apply worker

Now for every write request, we will do:

Raftstore sends a Proposal message to Apply worker
If the raft log is committed, sends the Raft Log to Apply worker
Apply worker applies the Raft log and calls the Proposal callback

As we can see, for every write, we do the message communication between Raftstore and Apply worker twice, we can combine 1 and 2 together.
The Raftstore can hold the Proposal and send to the Apply worker with the committed raft log. so we can reduce one message exchange.

@siddontang I would like to work on this.
you want to send the proposal and applies in a single task, right?
(i.e after writing kv wal and raft wal)


Nats jetstream arguments

Hi guys, when I read messages from nats-jetstream, it hasn't arguments such as since (start by time), sequence,.. like nats streaming. I think if nats-jetstream has these arguments above will be better. Hopefully, you guys can improve it asap. many thanks guys !!!

Great suggestion @edarha! We will work on getting those added shortly

@blinktag is cutting a new release as v1.10.1.
This new release supports consumer usage and has things like StartSequence, StartTime and more.
The docs and examples are updated as well. Thanks for submitting the issue!


Set config.json to serve Drummer blog and render/serve local html/opml files?

Using pagePark on Digital Ocean droplet. [It works!]  In pagePark, tried config.json of :
{
"urlSiteContents": "http://oldschool.scripting.com/sbwTweet"
}
In browser, the blog rendered, but then browser would show locally stored ".opml" files unrendered.
Then tried:
{
"defaultExtension": "opml",
"urlSiteContents": {
"/": { "http://oldschool.scripting.com/sbwTweet"
}
}
Browser showed local ".opml" file rendered, but browser showed blog as a 404.
Goal is to get Drummers’ Blog, Links, and About to show in browser and then serve other ".html" and ."opml" files to serve/render from pagePark files in the domains folder.
Didn’t find in the docs, comments where this is addressed. Thank you for help and or pointers.

The best way to approach this imho, is to forget for a moment what you're telling PP to do, but rather, what you want to be done.
And write it down, carefully, using common web terminology, so that you're sure anyone who understands how the web works will understand what you want to do.
That part is your responsibility. No one can read your mind. And no one can solve problems like that without a clear understanding of what the goal is.
Unscatter this, and you know what -- I don't think you're going to need any help.

Using the http://theviewfromafar.com/ domain hosted on my Digital Ocean pagePark, I want to serve these pages in your cloud-based Drummer:
http://oldschool.scripting.com/sbwTweet/
http://oldschool.scripting.com/sbwTweet/?tab=links
http://oldschool.scripting.com/sbwTweet/?tab=about
as coming from the url http://theviewfromafar.com
Then I want to serve every other page of .md, .opml, and .html from /domains/theviewfromafar.com folders and/or subfolders.
I get stuck on using:
{"urlSiteContents":  "http://oldschool.scripting.com/sbwTweet"}
since don’t see in config.jspn how to specify to serve everything else from files local to /domains/theviewfromafar.com
Thank you!

Another specification of the issue: A config.json of:
{
"redirects": {
"/": "http://oldschool.scripting.com/sbwTweet",
"/?tab=links": "http://oldschool.scripting.com/sbwTweet/?tab=links",
"/?tab=about": "http://oldschool.scripting.com/sbwTweet/?tab=about"
}
}
"works" but the web browser displays in the browser URL field:
http://oldschool.scripting.com/sbwTweet
instead of
http://theviewfromafar.com
which is what the config.json attribute "urlContents" would display.
Is there a way to display the original URL rather than the redirected url?


Fix typo in buffered_client.rs

untill -> until
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[ ] I've included a screenshot or gif (if applicable)
[ ] I've added a line to CHANGELOG.md (if this is a big enough change to warrant it)

Thanks :)


Why was cloc downgraded from 1.80 to 1.70?

See commit https://github.com/lukesampson/scoop/commit/781bc072bebbc388a83532d1dbf202e52c6719b0

1.80 is not marked as the latest release.
The following checkver syntax always uses the latest release.
"checkver": {
        "github": "https://github.com/AlDanial/cloc"
},


fix: Update logging config to include both standard categorised logs but also ILogger as traces

LGTM

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


[Calphad 2021] Update pycalphad agenda

I'd like to see a little more time dedicated to getting people comfortable with the returned xarray Datasets, if possible. Inspecting them, but also using them for plotting and common operations. Some places where 2020 workshop's 03 Calculation Results.ipynb can be improved:

it can be difficult to understand the multi-dimensionality, dimensions, coordinates, data variables. We should try to make this clear in fewer words. Notebook 03 is a little too wordy for a workshop tutorial and is more reference material (my fault - I wrote it). Maybe borrow from xarray's images or tutorials? Could use a link to the xarray documentation too.
explanation of how pycalphad pads the arrays with nan or '', how to tell the difference from convergence failures
avoid dropping down into NumPy arrays and preserve the xarray semantics (see also: https://github.com/pycalphad/pycalphad/issues/321)
some worked examples of how to inspect the datasets/dataarray values
worked examples that specifically illustrate how to plot data and issues around dataarray shapes (use of squeeze, broadcast_like)
some discussion on how where works and worked examples for filtering for certain criteria (see cookbook examples) - make the connection to "screening" for phases, properties (NP), etc. of interest
How to save the data: CSV and/or NetCDF


mxnet fail to import onnx model

Description
mxnet fail to import onnx model exported by pytorch. The model is from https://github.com/biubug6/Pytorch_Retinaface
Error Message
(Paste the complete error message. Please also include stack trace by setting environment variable DMLC_LOG_STACK_TRACE_DEPTH=10 before running your script.)
  File "/disk/zhitingz/video-pipeline/sprocket/platform/lambda_program/onnxruntime/detection/detect.py", line 139, in mx_init
    sym, arg_params, aux_params = onnx_mxnet.import_model(mpath)
  File "/disk/zhitingz/mxnet-cpu/lib/python3.6/site-packages/mxnet/contrib/onnx/onnx2mx/import_model.py", line 59, in import_model
    sym, arg_params, aux_params = graph.from_onnx(model_proto.graph)
  File "/disk/zhitingz/mxnet-cpu/lib/python3.6/site-packages/mxnet/contrib/onnx/onnx2mx/import_onnx.py", line 115, in from_onnx
    inputs = [self._nodes[i] for i in node.input]
  File "/disk/zhitingz/mxnet-cpu/lib/python3.6/site-packages/mxnet/contrib/onnx/onnx2mx/import_onnx.py", line 115, in <listcomp>
    inputs = [self._nodes[i] for i in node.input]
KeyError: '1'

To Reproduce
(If you developed your own code, please provide a short script that reproduces the error. For existing examples, please provide link.)
Get the exported onnx model. I fork the above link: https://github.com/photoszzt/Pytorch_Retinaface with some helper script to reproduce this issue easier.

download the pretrain pytorch model and export the model

cd weights
./download_all_pretrain.sh
cd -
./export_models.sh

try to load the model with the follwoing code.

from mxnet.contrib import onnx as onnx_mxnet
sym, arg_params, aux_params = onnx_mxnet.import_model('./mnet.0.25.onnx')

What have you tried to solve it?

I try to print the node.input. It's ['input0', '1'].

I update the issue with my forked repo that contains some helpful script to reproduce this issue.

cc @josephevans and @ChaiBapchya

@Zha0q1 Have MXNet 1.x made any progress for this issue?

no.. the recent onnx development has been focused on exporting rather than importing

Thanks, @Zha0q1. Import might be more important if a user  want to test the performance on different frameworks.   @szha @sandeep-krishnamurthy Do we have any project to imporve the ONNX model importing?

@photoszzt @Zha0q1   you can add args  keep_initializers_as_inputs=True  when you  run   torch.onnx.export  function.
but  after that,  i meet another problem -----  mxnet dont have resize op .
i found it's because there's a  torch.nn.functional.interpolate  function in retinaface,  which will be transform to resize op   by onnx, but mxnet dont have resize op.
i tried to add a  resize op , but i'm not familiar with  mxnet.