aws-private control-plane kube-controller-manager errors

What happened: In a brand new VPC, with one default/main Public Subnet and one default/main Private subnet, each with no tags. When I run terraform apply, and after all infrastructure is provisioned including newly tagged subnets and routes, I run 'kubeone install config.yaml --tfjson .', everything is set up and provisioned. When I check the logs of the kube-controller-managers, I see errors on two of the 3 pods.
Running well:
Cortlands-MacBook-Pro:aws-private cmoone$ kubectl logs kube-controller-manager-ip-10-0-157-112.us-gov-east-1.compute.internal -n kube-system  --kubeconfig=kubeone-avalon-cluster-kubeconfig
I0217 18:45:36.877289       1 serving.go:319] Generated self-signed cert in-memory
I0217 18:45:37.349738       1 controllermanager.go:161] Version: v1.16.1
I0217 18:45:37.350355       1 secure_serving.go:123] Serving securely on <IP_ADDRESS>:10257
I0217 18:45:37.350918       1 deprecated_insecure_serving.go:53] Serving insecurely on [::]:10252
I0217 18:45:37.350962       1 leaderelection.go:241] attempting to acquire leader lease  kube-system/kube-controller-manager...
Odd error retrieving resource lock:
Cortlands-MacBook-Pro:aws-private cmoone$ kubectl logs kube-controller-manager-ip-10-0-128-11.us-gov-east-1.compute.internal -n kube-system  --kubeconfig=kubeone-avalon-cluster-kubeconfig
I0217 18:44:22.152076       1 serving.go:319] Generated self-signed cert in-memory
I0217 18:44:22.630885       1 controllermanager.go:161] Version: v1.16.1
I0217 18:44:22.631842       1 secure_serving.go:123] Serving securely on <IP_ADDRESS>:10257
I0217 18:44:22.632443       1 deprecated_insecure_serving.go:53] Serving insecurely on [::]:10252
I0217 18:44:22.632491       1 leaderelection.go:241] attempting to acquire leader lease  kube-system/kube-controller-manager...
E0217 18:44:29.263350       1 leaderelection.go:330] error retrieving resource lock kube-system/kube-controller-manager: rpc error: code = Unavailable desc = etcdserver: leader changed
Multiple routes error:
Cortlands-MacBook-Pro:aws-private cmoone$ kubectl logs kube-controller-manager-ip-10-0-112-26.us-gov-east-1.compute.internal -n kube-system  --kubeconfig=kubeone-avalon-cluster-kubeconfig
I0217 18:44:32.157410       1 serving.go:319] Generated self-signed cert in-memory
I0217 18:44:32.521272       1 controllermanager.go:161] Version: v1.16.1
I0217 18:44:32.521928       1 secure_serving.go:123] Serving securely on <IP_ADDRESS>:10257
I0217 18:44:32.522435       1 deprecated_insecure_serving.go:53] Serving insecurely on [::]:10252
I0217 18:44:32.522484       1 leaderelection.go:241] attempting to acquire leader lease  kube-system/kube-controller-manager...
I0217 18:44:51.595468       1 leaderelection.go:251] successfully acquired lease kube-system/kube-controller-manager
I0217 18:44:51.595885       1 event.go:255] Event(v1.ObjectReference{Kind:"Endpoints", Namespace:"kube-system", Name:"kube-controller-manager", UID:"3f7d91dd-507a-4a35-9d44-6cacf4fcd980", APIVersion:"v1", ResourceVersion:"508", FieldPath:""}): type: 'Normal' reason: 'LeaderElection' ip-10-0-112-26_5441b7bd-3d74-4cc0-b34b-6d44bb85e113 became leader
W0217 18:44:51.802842       1 plugins.go:115] WARNING: aws built-in cloud provider is now deprecated. The AWS provider is deprecated and will be removed in a future release
I0217 18:44:51.803116       1 aws.go:1212] Building AWS cloudprovider
I0217 18:44:51.803193       1 aws.go:1178] Zone not specified in configuration file; querying AWS metadata service
I0217 18:44:51.904329       1 tags.go:79] AWS cloud filtering on ClusterID: kubeone-avalon-cluster
I0217 18:44:51.904375       1 aws.go:769] Setting up informers for Cloud
I0217 18:44:51.905598       1 shared_informer.go:197] Waiting for caches to sync for tokens
I0217 18:44:51.939605       1 controllermanager.go:534] Started "namespace"
I0217 18:44:51.939803       1 namespace_controller.go:186] Starting namespace controller
I0217 18:44:51.939900       1 shared_informer.go:197] Waiting for caches to sync for namespace
I0217 18:44:51.945993       1 controllermanager.go:534] Started "ttl"
I0217 18:44:51.946044       1 ttl_controller.go:116] Starting TTL controller
I0217 18:44:51.946277       1 shared_informer.go:197] Waiting for caches to sync for TTL
I0217 18:44:51.946287       1 shared_informer.go:204] Caches are synced for TTL
I0217 18:44:51.954430       1 controllermanager.go:534] Started "persistentvolume-expander"
I0217 18:44:51.954677       1 expand_controller.go:300] Starting expand controller
I0217 18:44:51.954766       1 shared_informer.go:197] Waiting for caches to sync for expand
I0217 18:44:51.965111       1 controllermanager.go:534] Started "attachdetach"
W0217 18:44:51.965129       1 controllermanager.go:513] "endpointslice" is disabled
I0217 18:44:51.965232       1 attach_detach_controller.go:334] Starting attach detach controller
I0217 18:44:51.965239       1 shared_informer.go:197] Waiting for caches to sync for attach detach
W0217 18:44:51.965298       1 actual_state_of_world.go:506] Failed to update statusUpdateNeeded field in actual state of world: Failed to set statusUpdateNeeded to needed true, because nodeName="ip-10-0-112-26.us-gov-east-1.compute.internal" does not exist
W0217 18:44:51.965311       1 actual_state_of_world.go:506] Failed to update statusUpdateNeeded field in actual state of world: Failed to set statusUpdateNeeded to needed true, because nodeName="ip-10-0-128-11.us-gov-east-1.compute.internal" does not exist
I0217 18:44:51.971986       1 controllermanager.go:534] Started "csrsigning"
I0217 18:44:51.972142       1 certificate_controller.go:113] Starting certificate controller
I0217 18:44:51.972243       1 shared_informer.go:197] Waiting for caches to sync for certificate
I0217 18:44:51.978321       1 controllermanager.go:534] Started "csrapproving"
I0217 18:44:51.978441       1 certificate_controller.go:113] Starting certificate controller
I0217 18:44:51.978462       1 shared_informer.go:197] Waiting for caches to sync for certificate
I0217 18:44:52.005859       1 shared_informer.go:204] Caches are synced for tokens
I0217 18:44:52.186275       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for ingresses.networking.k8s.io
I0217 18:44:52.186320       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for controllerrevisions.apps
I0217 18:44:52.186364       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for statefulsets.apps
I0217 18:44:52.186391       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for rolebindings.rbac.authorization.k8s.io
I0217 18:44:52.186428       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for poddisruptionbudgets.policy
I0217 18:44:52.186452       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for horizontalpodautoscalers.autoscaling
I0217 18:44:52.186477       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for jobs.batch
I0217 18:44:52.186518       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for ingresses.extensions
I0217 18:44:52.186544       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for deployments.apps
I0217 18:44:52.186569       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for events.events.k8s.io
I0217 18:44:52.186620       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for podtemplates
I0217 18:44:52.186646       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for cronjobs.batch
I0217 18:44:52.186688       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for roles.rbac.authorization.k8s.io
W0217 18:44:52.186707       1 shared_informer.go:415] resyncPeriod<PHONE_NUMBER>9323 is smaller than resyncCheckPeriod<PHONE_NUMBER>9822 and the informer has already started. Changing it to<PHONE_NUMBER>9822
I0217 18:44:52.186784       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for limitranges
I0217 18:44:52.186840       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for leases.coordination.k8s.io
I0217 18:44:52.186864       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for endpoints
I0217 18:44:52.186900       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for replicasets.apps
I0217 18:44:52.186928       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for networkpolicies.networking.k8s.io
W0217 18:44:52.186940       1 shared_informer.go:415] resyncPeriod<PHONE_NUMBER>5147 is smaller than resyncCheckPeriod<PHONE_NUMBER>9822 and the informer has already started. Changing it to<PHONE_NUMBER>9822
I0217 18:44:52.186988       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for serviceaccounts
I0217 18:44:52.187019       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for daemonsets.apps
I0217 18:44:52.187038       1 controllermanager.go:534] Started "resourcequota"
I0217 18:44:52.187229       1 resource_quota_controller.go:271] Starting resource quota controller
I0217 18:44:52.187278       1 shared_informer.go:197] Waiting for caches to sync for resource quota
I0217 18:44:52.187297       1 resource_quota_monitor.go:303] QuotaMonitor running
I0217 18:44:52.194939       1 controllermanager.go:534] Started "deployment"
I0217 18:44:52.195152       1 deployment_controller.go:152] Starting deployment controller
I0217 18:44:52.195246       1 shared_informer.go:197] Waiting for caches to sync for deployment
I0217 18:44:52.202128       1 controllermanager.go:534] Started "route"
I0217 18:44:52.202268       1 route_controller.go:101] Starting route controller
I0217 18:44:52.202421       1 shared_informer.go:197] Waiting for caches to sync for route
I0217 18:44:52.202524       1 shared_informer.go:204] Caches are synced for route
I0217 18:44:52.214919       1 controllermanager.go:534] Started "job"
I0217 18:44:52.215118       1 job_controller.go:143] Starting job controller
I0217 18:44:52.215187       1 shared_informer.go:197] Waiting for caches to sync for job
I0217 18:44:52.221911       1 controllermanager.go:534] Started "pv-protection"
I0217 18:44:52.221953       1 pv_protection_controller.go:81] Starting PV protection controller
I0217 18:44:52.221966       1 shared_informer.go:197] Waiting for caches to sync for PV protection
E0217 18:44:52.237701       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
I0217 18:44:52.506764       1 controllermanager.go:534] Started "disruption"
I0217 18:44:52.506815       1 disruption.go:333] Starting disruption controller
I0217 18:44:52.506831       1 shared_informer.go:197] Waiting for caches to sync for disruption
I0217 18:44:52.657149       1 controllermanager.go:534] Started "statefulset"
I0217 18:44:52.657160       1 stateful_set.go:145] Starting stateful set controller
I0217 18:44:52.657297       1 shared_informer.go:197] Waiting for caches to sync for stateful set
I0217 18:44:52.807341       1 node_lifecycle_controller.go:77] Sending events to api server
I0217 18:44:52.807386       1 controllermanager.go:534] Started "cloud-node-lifecycle"
I0217 18:44:52.957595       1 controllermanager.go:534] Started "persistentvolume-binder"
W0217 18:44:52.957621       1 controllermanager.go:526] Skipping "root-ca-cert-publisher"
I0217 18:44:52.957637       1 pv_controller_base.go:282] Starting persistent volume controller
I0217 18:44:52.957656       1 shared_informer.go:197] Waiting for caches to sync for persistent volume
I0217 18:44:53.107270       1 controllermanager.go:534] Started "podgc"
I0217 18:44:53.107319       1 gc_controller.go:75] Starting GC controller
I0217 18:44:53.107337       1 shared_informer.go:197] Waiting for caches to sync for GC
I0217 18:44:53.257402       1 controllermanager.go:534] Started "serviceaccount"
I0217 18:44:53.257449       1 serviceaccounts_controller.go:116] Starting service account controller
I0217 18:44:53.257477       1 shared_informer.go:197] Waiting for caches to sync for service account
I0217 18:44:53.960885       1 garbagecollector.go:130] Starting garbage collector controller
I0217 18:44:53.960951       1 controllermanager.go:534] Started "garbagecollector"
I0217 18:44:53.960986       1 graph_builder.go:282] GraphBuilder running
I0217 18:44:53.960957       1 shared_informer.go:197] Waiting for caches to sync for garbage collector
I0217 18:44:53.968219       1 node_ipam_controller.go:94] Sending events to api server.
E0217 18:45:02.238783       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
I0217 18:45:03.971794       1 range_allocator.go:82] Sending events to api server.
I0217 18:45:03.971988       1 range_allocator.go:116] No Secondary Service CIDR provided. Skipping filtering out secondary service addresses.
I0217 18:45:03.972071       1 controllermanager.go:534] Started "nodeipam"
I0217 18:45:03.972232       1 node_ipam_controller.go:154] Starting ipam controller
I0217 18:45:03.972313       1 shared_informer.go:197] Waiting for caches to sync for node
I0217 18:45:03.972332       1 shared_informer.go:204] Caches are synced for node
I0217 18:45:03.972916       1 range_allocator.go:172] Starting range CIDR allocator
I0217 18:45:03.973032       1 shared_informer.go:197] Waiting for caches to sync for cidrallocator
I0217 18:45:03.973058       1 shared_informer.go:204] Caches are synced for cidrallocator
I0217 18:45:03.979704       1 controllermanager.go:534] Started "clusterrole-aggregation"
I0217 18:45:03.979800       1 clusterroleaggregation_controller.go:148] Starting ClusterRoleAggregator
I0217 18:45:03.979822       1 shared_informer.go:197] Waiting for caches to sync for ClusterRoleAggregator
I0217 18:45:03.993039       1 controllermanager.go:534] Started "pvc-protection"
I0217 18:45:03.996656       1 pvc_protection_controller.go:100] Starting PVC protection controller
I0217 18:45:03.996687       1 shared_informer.go:197] Waiting for caches to sync for PVC protection
I0217 18:45:04.004674       1 controllermanager.go:534] Started "daemonset"
I0217 18:45:04.004699       1 daemon_controller.go:267] Starting daemon sets controller
I0217 18:45:04.005065       1 shared_informer.go:197] Waiting for caches to sync for daemon sets
I0217 18:45:04.012614       1 controllermanager.go:534] Started "csrcleaner"
I0217 18:45:04.012724       1 cleaner.go:81] Starting CSR cleaner controller
I0217 18:45:04.020299       1 controllermanager.go:534] Started "bootstrapsigner"
I0217 18:45:04.020411       1 shared_informer.go:197] Waiting for caches to sync for bootstrap_signer
I0217 18:45:04.028151       1 controllermanager.go:534] Started "tokencleaner"
I0217 18:45:04.028224       1 tokencleaner.go:117] Starting token cleaner controller
I0217 18:45:04.028364       1 shared_informer.go:197] Waiting for caches to sync for token_cleaner
I0217 18:45:04.028375       1 shared_informer.go:204] Caches are synced for token_cleaner
I0217 18:45:04.035247       1 controllermanager.go:534] Started "service"
W0217 18:45:04.035269       1 controllermanager.go:526] Skipping "ttl-after-finished"
I0217 18:45:04.035429       1 service_controller.go:219] Starting service controller
I0217 18:45:04.035504       1 shared_informer.go:197] Waiting for caches to sync for service
I0217 18:45:04.043099       1 controllermanager.go:534] Started "replicationcontroller"
I0217 18:45:04.043167       1 replica_set.go:182] Starting replicationcontroller controller
I0217 18:45:04.043231       1 shared_informer.go:197] Waiting for caches to sync for ReplicationController
I0217 18:45:04.050724       1 controllermanager.go:534] Started "replicaset"
I0217 18:45:04.050911       1 replica_set.go:182] Starting replicaset controller
I0217 18:45:04.050926       1 shared_informer.go:197] Waiting for caches to sync for ReplicaSet
I0217 18:45:04.058163       1 controllermanager.go:534] Started "cronjob"
I0217 18:45:04.058313       1 cronjob_controller.go:96] Starting CronJob Manager
I0217 18:45:04.124450       1 controllermanager.go:534] Started "endpoint"
I0217 18:45:04.124517       1 endpoints_controller.go:176] Starting endpoint controller
I0217 18:45:04.124559       1 shared_informer.go:197] Waiting for caches to sync for endpoint
I0217 18:45:04.723775       1 controllermanager.go:534] Started "horizontalpodautoscaling"
I0217 18:45:04.723843       1 horizontal.go:156] Starting HPA controller
I0217 18:45:04.723861       1 shared_informer.go:197] Waiting for caches to sync for HPA
I0217 18:45:04.874072       1 node_lifecycle_controller.go:294] Sending events to api server.
I0217 18:45:04.874173       1 node_lifecycle_controller.go:327] Controller is using taint based evictions.
I0217 18:45:04.875388       1 taint_manager.go:162] Sending events to api server.
I0217 18:45:04.875952       1 node_lifecycle_controller.go:421] Controller will reconcile labels.
I0217 18:45:04.876116       1 node_lifecycle_controller.go:434] Controller will taint node by condition.
I0217 18:45:04.876165       1 controllermanager.go:534] Started "nodelifecycle"
I0217 18:45:04.877139       1 shared_informer.go:197] Waiting for caches to sync for resource quota
I0217 18:45:04.878575       1 node_lifecycle_controller.go:458] Starting node controller
I0217 18:45:04.878596       1 shared_informer.go:197] Waiting for caches to sync for taint
I0217 18:45:04.920198       1 shared_informer.go:197] Waiting for caches to sync for garbage collector
I0217 18:45:04.939574       1 shared_informer.go:204] Caches are synced for service
I0217 18:45:04.940549       1 shared_informer.go:204] Caches are synced for namespace
I0217 18:45:04.959496       1 shared_informer.go:204] Caches are synced for service account
I0217 18:45:04.979630       1 shared_informer.go:204] Caches are synced for taint
I0217 18:45:04.979801       1 node_lifecycle_controller.go:1208] Initializing eviction metric for zone: us-gov-east-1::us-gov-east-1a
I0217 18:45:04.979924       1 node_lifecycle_controller.go:1208] Initializing eviction metric for zone: us-gov-east-1::us-gov-east-1b
W0217 18:45:04.980042       1 node_lifecycle_controller.go:903] Missing timestamp for Node ip-10-0-112-26.us-gov-east-1.compute.internal. Assuming now as a timestamp.
W0217 18:45:04.980171       1 node_lifecycle_controller.go:903] Missing timestamp for Node ip-10-0-128-11.us-gov-east-1.compute.internal. Assuming now as a timestamp.
I0217 18:45:04.980198       1 event.go:255] Event(v1.ObjectReference{Kind:"Node", Namespace:"", Name:"ip-10-0-112-26.us-gov-east-1.compute.internal", UID:"bb0498ce-6db8-4957-9a5e-66d4f55a6e98", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'RegisteredNode' Node ip-10-0-112-26.us-gov-east-1.compute.internal event: Registered Node ip-10-0-112-26.us-gov-east-1.compute.internal in Controller
I0217 18:45:04.980293       1 shared_informer.go:204] Caches are synced for ClusterRoleAggregator
I0217 18:45:04.980385       1 node_lifecycle_controller.go:1058] Controller detected that all Nodes are not-Ready. Entering master disruption mode.
I0217 18:45:04.980477       1 event.go:255] Event(v1.ObjectReference{Kind:"Node", Namespace:"", Name:"ip-10-0-128-11.us-gov-east-1.compute.internal", UID:"8fcbab86-39c5-481e-a772-1567313dd649", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'RegisteredNode' Node ip-10-0-128-11.us-gov-east-1.compute.internal event: Registered Node ip-10-0-128-11.us-gov-east-1.compute.internal in Controller
I0217 18:45:04.979808       1 taint_manager.go:186] Starting NoExecuteTaintManager
I0217 18:45:04.995504       1 shared_informer.go:204] Caches are synced for deployment
I0217 18:45:05.006951       1 shared_informer.go:204] Caches are synced for daemon sets
I0217 18:45:05.009669       1 shared_informer.go:204] Caches are synced for GC
I0217 18:45:05.009920       1 shared_informer.go:204] Caches are synced for disruption
I0217 18:45:05.009932       1 disruption.go:341] Sending events to api server.
 Proceeding to collect garbage
I0217 18:45:05.420687       1 shared_informer.go:204] Caches are synced for garbage collector
I0217 18:45:05.422084       1 shared_informer.go:204] Caches are synced for PV protection
I0217 18:45:05.455295       1 shared_informer.go:204] Caches are synced for expand
I0217 18:45:05.457772       1 shared_informer.go:204] Caches are synced for persistent volume
I0217 18:45:05.465364       1 shared_informer.go:204] Caches are synced for attach detach
E0217 18:45:12.238756       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
E0217 18:45:22.238689       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
I0217 18:45:31.461407       1 log.go:172] [INFO] signed certificate with serial number<PHONE_NUMBER>01600361585721866020884259774439024930
W0217 18:45:31.643308       1 actual_state_of_world.go:506] Failed to update statusUpdateNeeded field in actual state of world: Failed to set statusUpdateNeeded to needed true, because nodeName="ip-10-0-157-112.us-gov-east-1.compute.internal" does not exist
I0217 18:45:31.666411       1 range_allocator.go:359] Set node ip-10-0-157-112.us-gov-east-1.compute.internal PodCIDR to [<IP_ADDRESS>/24]
I0217 18:45:31.672108       1 event.go:255] Event(v1.ObjectReference{Kind:"DaemonSet", Namespace:"kube-system", Name:"kube-proxy", UID:"43f3d216-d4ba-4a87-994a-9c8cfe763262", APIVersion:"apps/v1", ResourceVersion:"532", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: kube-proxy-lh9jd
E0217 18:45:32.233827       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
I0217 18:45:34.981496       1 node_lifecycle_controller.go:1208] Initializing eviction metric for zone: us-gov-east-1::us-gov-east-1c
W0217 18:45:34.981695       1 node_lifecycle_controller.go:903] Missing timestamp for Node ip-10-0-157-112.us-gov-east-1.compute.internal. Assuming now as a timestamp.
I0217 18:45:34.981759       1 node_lifecycle_controller.go:1058] Controller detected that all Nodes are not-Ready. Entering master disruption mode.
I0217 18:45:34.981832       1 event.go:255] Event(v1.ObjectReference{Kind:"Node", Namespace:"", Name:"ip-10-0-157-112.us-gov-east-1.compute.internal", UID:"7b0be200-6f74-41f9-ac06-8831affa7b6f", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'RegisteredNode' Node ip-10-0-157-112.us-gov-east-1.compute.internal event: Registered Node ip-10-0-157-112.us-gov-east-1.compute.internal in Controller
E0217 18:45:42.239664       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
I0217 18:45:51.669904       1 event.go:255] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"kube-system", Name:"metrics-server", UID:"c49fc3a8-9557-445e-9223-28fca6eb89ac", APIVersion:"apps/v1", ResourceVersion:"677", FieldPath:""}): type: 'Normal' reason: 'ScalingReplicaSet' Scaled up replica set metrics-server-59bb664678 to 1
I0217 18:45:51.686210       1 event.go:255] Event(v1.ObjectReference{Kind:"ReplicaSet", Namespace:"kube-system", Name:"metrics-server-59bb664678", UID:"0ba68aee-c590-4e6d-919f-2f28a2923ef4", APIVersion:"apps/v1", ResourceVersion:"678", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: metrics-server-59bb664678-8lpck
E0217 18:45:52.239017       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
E0217 18:45:52.428284       1 daemon_controller.go:1070] pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
E0217 18:45:52.428314       1 daemon_controller.go:302] kube-system/canal failed with : pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
I0217 18:45:52.428604       1 event.go:255] Event(v1.ObjectReference{Kind:"DaemonSet", Namespace:"kube-system", Name:"canal", UID:"b79050a3-2a47-4297-b18b-b67348904d40", APIVersion:"apps/v1", ResourceVersion:"700", FieldPath:""}): type: 'Warning' reason: 'FailedCreate' Error creating: pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
E0217 18:45:52.438259       1 daemon_controller.go:1070] pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
E0217 18:45:52.438285       1 daemon_controller.go:302] kube-system/canal failed with : pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
I0217 18:45:52.438767       1 event.go:255] Event(v1.ObjectReference{Kind:"DaemonSet", Namespace:"kube-system", Name:"canal", UID:"b79050a3-2a47-4297-b18b-b67348904d40", APIVersion:"apps/v1", ResourceVersion:"700", FieldPath:""}): type: 'Warning' reason: 'FailedCreate' Error creating: pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
E0217 18:45:52.453203       1 daemon_controller.go:1070] pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
E0217 18:45:52.453227       1 daemon_controller.go:302] kube-system/canal failed with : pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
I0217 18:45:52.453339       1 event.go:255] Event(v1.ObjectReference{Kind:"DaemonSet", Namespace:"kube-system", Name:"canal", UID:"b79050a3-2a47-4297-b18b-b67348904d40", APIVersion:"apps/v1", ResourceVersion:"700", FieldPath:""}): type: 'Warning' reason: 'FailedCreate' Error creating: pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
E0217 18:45:52.478458       1 daemon_controller.go:1070] pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
E0217 18:45:52.478486       1 daemon_controller.go:302] kube-system/canal failed with : pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
I0217 18:45:52.478667       1 event.go:255] Event(v1.ObjectReference{Kind:"DaemonSet", Namespace:"kube-system", Name:"canal", UID:"b79050a3-2a47-4297-b18b-b67348904d40", APIVersion:"apps/v1", ResourceVersion:"700", FieldPath:""}): type: 'Warning' reason: 'FailedCreate' Error creating: pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
E0217 18:45:52.524199       1 daemon_controller.go:1070] pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
E0217 18:45:52.524391       1 daemon_controller.go:302] kube-system/canal failed with : pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
I0217 18:45:52.524489       1 event.go:255] Event(v1.ObjectReference{Kind:"DaemonSet", Namespace:"kube-system", Name:"canal", UID:"b79050a3-2a47-4297-b18b-b67348904d40", APIVersion:"apps/v1", ResourceVersion:"700", FieldPath:""}): type: 'Warning' reason: 'FailedCreate' Error creating: pods "canal-" is forbidden: error looking up service account kube-system/canal: serviceaccount "canal" not found
I0217 18:45:52.613799       1 event.go:255] Event(v1.ObjectReference{Kind:"DaemonSet", Namespace:"kube-system", Name:"canal", UID:"b79050a3-2a47-4297-b18b-b67348904d40", APIVersion:"apps/v1", ResourceVersion:"700", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: canal-n8znr
I0217 18:45:52.622726       1 event.go:255] Event(v1.ObjectReference{Kind:"DaemonSet", Namespace:"kube-system", Name:"canal", UID:"b79050a3-2a47-4297-b18b-b67348904d40", APIVersion:"apps/v1", ResourceVersion:"700", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: canal-v4gpq
I0217 18:45:52.629717       1 event.go:255] Event(v1.ObjectReference{Kind:"DaemonSet", Namespace:"kube-system", Name:"canal", UID:"b79050a3-2a47-4297-b18b-b67348904d40", APIVersion:"apps/v1", ResourceVersion:"700", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: canal-699rk
I0217 18:46:01.411636       1 event.go:255] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"kube-system", Name:"machine-controller", UID:"c75b7ad9-73e9-4647-9c63-d922738ba1b1", APIVersion:"apps/v1", ResourceVersion:"838", FieldPath:""}): type: 'Normal' reason: 'ScalingReplicaSet' Scaled up replica set machine-controller-5c58fb6c4f to 1
I0217 18:46:01.549416       1 event.go:255] Event(v1.ObjectReference{Kind:"ReplicaSet", Namespace:"kube-system", Name:"machine-controller-5c58fb6c4f", UID:"750e296d-bd91-4ec1-99c8-41ecf4f615d2", APIVersion:"apps/v1", ResourceVersion:"841", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: machine-controller-5c58fb6c4f-stlpl
E0217 18:46:02.242072       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
I0217 18:46:03.816046       1 event.go:255] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"kube-system", Name:"machine-controller-webhook", UID:"cd68535d-1738-4b05-b7d7-831744488018", APIVersion:"apps/v1", ResourceVersion:"872", FieldPath:""}): type: 'Normal' reason: 'ScalingReplicaSet' Scaled up replica set machine-controller-webhook-5846d9686b to 1
I0217 18:46:03.830745       1 event.go:255] Event(v1.ObjectReference{Kind:"ReplicaSet", Namespace:"kube-system", Name:"machine-controller-webhook-5846d9686b", UID:"a6d1aeef-9181-4e54-b2ab-91e2fa3eb064", APIVersion:"apps/v1", ResourceVersion:"873", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: machine-controller-webhook-5846d9686b-gtjhg
I0217 18:46:04.983247       1 node_lifecycle_controller.go:1085] Controller detected that some Nodes are Ready. Exiting master disruption mode.
E0217 18:46:05.930388       1 resource_quota_controller.go:407] unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
I0217 18:46:05.930559       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for machinesets.cluster.k8s.io
I0217 18:46:05.930601       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for clusters.cluster.k8s.io
I0217 18:46:05.930630       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for machines.cluster.k8s.io
I0217 18:46:05.930657       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for machinedeployments.cluster.k8s.io
I0217 18:46:05.930693       1 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for networkpolicies.crd.projectcalico.org
I0217 18:46:05.930753       1 shared_informer.go:197] Waiting for caches to sync for resource quota
I0217 18:46:06.130923       1 shared_informer.go:204] Caches are synced for resource quota
W0217 18:46:07.823619       1 garbagecollector.go:640] failed to discover some groups: map[metrics.k8s.io/v1beta1:the server is currently unable to handle the request]
E0217 18:46:08.175226       1 memcache.go:199] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0217 18:46:08.225079       1 memcache.go:111] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
I0217 18:46:08.226480       1 shared_informer.go:197] Waiting for caches to sync for garbage collector
I0217 18:46:08.326697       1 shared_informer.go:204] Caches are synced for garbage collector
I0217 18:46:09.983569       1 node_lifecycle_controller.go:1108] Controller detected that zone us-gov-east-1::us-gov-east-1a is now in state Normal.
E0217 18:46:12.250953       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
E0217 18:46:22.248705       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
E0217 18:46:32.262166       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
E0217 18:46:36.482360       1 resource_quota_controller.go:407] unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
W0217 18:46:40.528139       1 garbagecollector.go:640] failed to discover some groups: map[metrics.k8s.io/v1beta1:the server is currently unable to handle the request]
E0217 18:46:42.266598       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
E0217 18:46:52.250130       1 route_controller.go:119] Couldn't reconcile node routes: error listing routes: found multiple matching AWS route tables for AWS cluster: kubernetes
What is the expected behavior: All three pods should be running properly.
How to reproduce the issue: Standard build from example in new VPC using kubeone/examples/terraform/aws-private
Anything else we need to know?
Information about the environment:
KubeOne version (kubeone version): v0.10.0
Operating system: MacOS v10.15
Provider you're deploying cluster on: AWS GovCloud
Operating system you're deploying on: ubuntu

@cmoone thanks for the report!
I see you're running outdated kubeone, and even now removed aws-private example configuration (which was regarded as failed experiment and thus removed). Is it possible that you try to use latest master of KubeOne (you'd have to build it locally for now), and existing aws example config?

@kron4eg Thanks for the response. Unfortunately, we needed the security of a private cluster, so I attempted to use this previous version. I'll give the current master a shot and report back. I'll try one cluster with the baseline config, and one with our needed modifications.

@kron4eg I'm currently attempting a default cluster build using v0.11.0-beta.3 of KubeOne. Terraform provisions infrastructure successfully, but the kubeone install step fails with timeouts to the instance. Investigation has led me to believe this is due to the Bastion host being created on a subnet with a route to a NAT and not an IGW. FYI, I think this is a bug. I'll create an issue for your tracking.

@kron4eg just wanted to let you know that with some modifications I'm seeing some possibilities of success using v0.11.0-beta.3 of KubeOne. I'll let you know if this ultimately works for us.


Panic during creation of Glossary

Hey! Sorry, its me again. Just noticed the Libary is able to panic. This seems to be caused by the API responding to a request by anything  that isn't expected. In this case using EN_US as a target language, which would return:
{
    "message": "Unsupported glossary source and target language pair"
}

I assume having no glossary entries would also panic, as that would return:
{
    "message": "Invalid glossary entries provided"
}

thread 'tokio-runtime-worker' panicked at C:\Users\Tim\.cargo\registry\src\index.crates.io-6f17d22bba15001f\deepl-0.6.0\src\endpoint\glossary.rs:92:26:
Unmatched response to CreateGlossaryResp, please open issue on https://github.com/Avimitin/deepl.: reqwest::Error { kind: Decode, source: Error("missing field `glossary_id`", line: 1, column: 66) }
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/fdaaaf9f923281ab98b865259aa40fbf93d72c7a/library\std\src\panicking.rs:645
   1: core::panicking::panic_fmt
             at /rustc/fdaaaf9f923281ab98b865259aa40fbf93d72c7a/library\core\src\panicking.rs:72
   2: core::result::unwrap_failed
             at /rustc/fdaaaf9f923281ab98b865259aa40fbf93d72c7a/library\core\src\result.rs:1653
   3: enum2$<core::result::Result<deepl::endpoint::glossary::GlossaryResp,reqwest::error::Error> >::expect<deepl::endpoint::glossary::GlossaryResp,reqwest::error::Error>
             at /rustc/fdaaaf9f923281ab98b865259aa40fbf93d72c7a\library\core\src\result.rs:1034
   4: deepl::endpoint::glossary::impl$1::into_future::async_block$0
             at C:\Users\Tim\.cargo\registry\src\index.crates.io-6f17d22bba15001f\deepl-0.6.0\src\endpoint\glossary.rs:84
   5: core::future::future::impl$1::poll<alloc::boxed::Box<dyn$<core::future::future::Future<assoc$<Output,enum2$<core::result::Result<deepl::endpoint::glossary::GlossaryResp,enum2$<deepl::endpoint::Error> > > > >,core::marker::Send,core::marker::Sync>,alloc::a

Oh, I don't handle edge case and just let them fail. I will fix them up in next release.

Should be fixed in v0.6.1.


python312Packages.fastcore: 1.7.5 -> 1.7.8

Diff: https://github.com/fastai/fastcore/compare/refs/tags/1.7.5...1.7.8
Changelog: https://github.com/fastai/fastcore/blob/1.7.8/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 341789 run on x86_64-linux 1

24 packages built:

ghdorker
ghdorker.dist
python311Packages.execnb
python311Packages.execnb.dist
python311Packages.fastai
python311Packages.fastai.dist
python311Packages.fastcore
python311Packages.fastcore.dist
python311Packages.fastdownload
python311Packages.fastdownload.dist
python311Packages.ghapi
python311Packages.ghapi.dist
python311Packages.nbdev
python311Packages.nbdev.dist
python312Packages.execnb
python312Packages.execnb.dist
python312Packages.fastcore
python312Packages.fastcore.dist
python312Packages.fastdownload
python312Packages.fastdownload.dist
python312Packages.ghapi
python312Packages.ghapi.dist
python312Packages.nbdev
python312Packages.nbdev.dist


Added sbt-build-files-watcher

:point_right: https://github.com/tototoshi/sbt-build-files-watcher

Hi @tototoshi,
Thank you for your contribution! We really value the time you've taken to put this together.
We see that you have signed the Typesafe Contributors License Agreement before, however, the CLA has changed since you last signed it.
Please review the new CLA and sign it before we proceed with reviewing this pull request:
http://www.typesafe.com/contribute/cla


SNOS output

[ ] issue #7
[ ] follows contribution guide
[ ] breaking change

Hi @drspacemn, I created a new output.rs file and wrote the function there. Please review and let me know if I should move it to the src/snos_output.cairo file.

@Xaxxoo not sure if you're still on this one. Don't hesitate to re-open if you're still working on it and switched to cairo.
If not, don't hesitate to comment on the issue if you have any blockers.


general-purpose cluster-friendly tidy up script

can't tidy up simulation results on local version (exceed memory limit even after adjustment). need to make sure the thing cluster spits out is visualization-ready. current version specific to one set of parameter changes.

implemented


Does this distribution support lichee nano?

Does this distribution support lichee nano? If not, can you help with what we can do? There are minor differences between Lichee Zero and Nano. Thanks!

Yes, it is planned soon in this month.
Regards

Great, looking forward to it !


Combobox not showing initial value

Describe the bug
If the SelectedItem is set before the Items property, the ComboBox does not display the initial selection.
Swap the order and the initial selection displays correctly.
To Reproduce
Run the repo, the ComboBox is displayed with an empty selection.
Expected behavior
The ComboBox should show the SelectedItem; i.e. "hello", as this was already set when the bound items property was changed.
The order of setting Items and SelectedItem should not matter.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Version 0.11-preview1

Additional context
https://github.com/aguahombre/ComboTest.git

imo it should work like this.

I also think this is the intended behavior and WPF (along with other XAML frameworks) is the same. If you set the selected item before the collection the control has no way of knowing what to do with it. It needs the collection of values first.
Here is one of the older discussions for this: https://stackoverflow.com/questions/1301119/silverlight-xaml-attribute-definition-order-matters
I think this should probably be documented but closed as an issue.

It wouldn't be too difficult to observe Items property changes and set the SelectedIndex to match the SelectedItem.
The control must already be doing this when SelectedItem is set.
This would remove all ordering dependencies and make Avalonia better than WPF.
Why copy bad practice from WPF?

I think if you find a reliable way to do, you may provide a PR.

It wouldn't be too difficult to observe Items property changes and set the SelectedIndex to match the SelectedItem. The control must already be doing this when SelectedItem is set. This would remove all ordering dependencies and make Avalonia better than WPF. Why copy bad practice from WPF?

The real problem is match, how to define match?

I don't think this logic is actually in ComboBox itself. You will probably need to go into ItemsControl or perhaps somewhere else. This means you will improve this for many controls at once.

The real problem is match, how to define match?

"Match" is well defined in this case. object.Equals() is called or any overridden implementation of such. For ref types this compares by reference as default, for value type is uses the default equality method which should be implemented. Works exactly the same as the IList methods for IndexOf(), Contains(), etc.
https://github.com/AvaloniaUI/Avalonia/blob/6a3804bfde7867ab0c419a71d504636f1e196b4b/src/Avalonia.Controls/ItemsControl.cs#L243


Why ReverseRuleConfigBackend but no ForwardRuleConfigBackend?

If I understand correctly, AbstractDifferentiation is compatible with ChainRules backends that work in reverse mode, but not in forward mode?

Yeah I did have Diffractor in mind, but also a potential translator from ChainRules to EnzymeRules. I don't think the PR would be hard, I can draft it if there is interest

ForwardDiff2 was essentially replaced by TaylorDiff.jl which will be using ChainRules for its vector rules.

It would be good to add this

It would be good to add this

Could this have something to do with a certain v0.2.0 release that just came out :innocent: ?

It would be good to add this

I can give it a shot but IIUC we can't test it on 1.9 since we need Diffractor?

Also, the Diffractor backend already exists without being a special case of the (yet-to-be-written) ForwardRuleConfigBackend, is that an issue?


Do not run some tests if not run with a TTY

Forwarding a bug report from Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806480). Looks like some tests fail with closed stdin and if stdout is redirected to a file. Could this tests be protected with some kind of check?

If this produced the same environment,
import sys
import nose

if __name__ == '__main__':
    sys.stdin.close()
    sys.stdout.close()
    nose.run()

then https://github.com/thomasballinger/curtsies/commit/5384f455631a973661af84bbe823b9d59af4d5b1 should fix it.

This is in a released version now because I needed to release for the FtmStr equality bug FYI

I see the failing test with version 0.2.4 and this patch.

Ah rats. I assume 0.1.21 is failing in the same way? That's the one I was trying to fix, but I assume results would be the same with 0.2.4 and the patch applied.
@jlec or @sebastinas, could you point me to how to run these tests in this way? Or happen to know how to mimic whatever aspect of these conditions is causing the failures?

Doing a sys.stdin.isatty check now, was silly of me to assume that stdin would be closed at the Python level. Fixed in both 0.1.x and master, no releases yet.

Doing a sys.stdin.isatty check now, was silly of me to assume that stdin would be closed at the Python level. Fixed in both 0.1.x and master, no releases yet.

This has been released as curtsies-0.1.22, and curtsies-0.2.5

For both versions I see
======================================================================
ERROR: test_array_from_text (test_window.TestBaseWindow)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/portage/dev-python/curtsies-0.2.5/work/curtsies-0.2.5/tests/test_window.py", line 42, in test_array_from_text
    a = window.array_from_text('.\n.\n.')
  File "/var/tmp/portage/dev-python/curtsies-0.2.5/work/curtsies-0.2.5-python2_7/lib/curtsies/window.py", line 79, in array_from_text
    return self.array_from_text_rc(msg, rows, columns)
  File "/var/tmp/portage/dev-python/curtsies-0.2.5/work/curtsies-0.2.5-python2_7/lib/curtsies/window.py", line 86, in array_from_text_rc
    if i >= rows * columns:
TypeError: unsupported operand type(s) for *: 'NoneType' and 'NoneType'
-------------------- >> begin captured logging << --------------------
curtsies.window: DEBUG: -------initializing Window object <curtsies.window.BaseWindow object at 0x7fd3f29ad190>------

@jlec There's now a 0.1.23 and a 0.2.6, is it fixed in these?

There's now a 0.1.23 and a 0.2.6, is it fixed in these?
Works perfectly.


simple CLI interface

Hello Doormatlka,
Thank you for your work. I am not used to the workflow of TS. I believe I did a npm i -g twitter-scraper
Any chance, we can use with CLI like drawrowfly/tiktok-scraper ?
Thank you!
Best

Hi AkimParis,
Thank you for checking out this library!
I will add the CLI shipped with other features I plan to do.

It's been implemented with the v1.1.0 update. I'll add more features as time goes on


At /winners add stats about participants, winners and claimed prizes

That will be important to show some numbers to support to decide if we can spin the wheel more times.

total participants
total winners who claimed prizes
total winners pending to claim prizes

I like the idea! Do you want to go ahead and implement this? I think this could also be something for Copilot Workspace :)

Both ways works. :)

Awesome. It would be great if you could create a PR for this as I don't have a lot of capacity in the coming weeks.


shouldCrawl doesnt call onAllFinished

When returning false to avoid crawl last url (i think) it doest call onAllFinished

I will take a look and try to reproduce the issue.

👍

A couple of e2e tests for shouldCrawl were added. One of them failed, most likely because of the same bug described in this issue: when all the urls in the active crawler queue should not be crawled according to shouldCrawl, then the crawler would not call onAllFinished. This issue has been fixed https://github.com/antivanov/js-crawler/commit/bcd98cabfdf28581737e9c6fda59d92e0144ffd5 in the latest version and published to NPM.
Please, re-open the issue if it is still reproducible after the recent fix and, please, provide more details if possible.


[BUG] Go compilation results in JS error

Describe the bug
When I compile https://godbolt.org/z/roCvhv, I see the following "compiler" error:
Internal Compiler Explorer error: TypeError: (intermediate value) is not iterable
    at /compiler-explorer-image/.deploy/lib/base-compiler.js:731:39

Compiler returned: -1

Also reported over email. Thanks for digging in to this. Seems to affect all gc compilers

Separately; this server-side error isn't getting to sentry.io so we weren't notified of it earlier


Convert to TypeScript and use React Hooks

Converts the codebase to TypeScript
Uses React hooks
Use GitHub Actions. Running ci: https://github.com/aminya/react-table/actions/runs/441516345

Closes #22
Closes #23
Closes #25

Thank you @aminya! Please ping me by the weekend if it's ready, I'd love to take this for a spin
and thanks again for working on this! I love TS!

@steelbrain You're welcome. This is ready now. I tested it with linter-ui-default. The issue was because of some type of mismatch.

My main goal is to replace React/Etch with solid-js to improve their runtime and loading performance.
solid-js uses functional components and converting a functional React component to solid-js is very easy. So, I will create a repository calling it solid-table to convert this library to solid-js. But I saw it useful that we do thin incrementally. 😄
React classes -> React functional components -> solid-js
https://blogreact.com/introduction-to-solidjs/


[Civl] fixed pack rule when linear types are involved

What is the pack rule?

After datatypes were added to Boogie and linear types were added to Civl, I had to deal with the problem of safely nesting linear types inside datatypes. So I decided to add two operations pack and unpack. Both use the assignment syntax on the surface and look as follows:
x := Foo(a, b); // pack a Foo value
Foo(a, b) := x; // unpack a Foo value
Pack piggybacks on Boogie AssignCmd but unpack has a new UnpackCmd.
Typing machinery needs to be added so that duplicates of linear values do not get packed or unpacked.
This particular PR appears to be some adjustment to the type checking for pack.

In your example Foo(a, b), let's assume the type of a is linear. (It's based on the type, right? Meaning it's not possible to declare the field as linear.) I can see two approaches for the type checking. 1) Require that the input for a is available in a pack, and only allow a single unpack on any path that'll make the output for a available. 2) Mark the result of a pack as available if a is available and otherwise the result is just not available (but it is not an error), and only mark the output for a as available if the packed value is available (making the packed value unavailable). Is either of these approaches what happens?
I guess Foo could itself be linear, but there is a priori no semantic connection between its permissions and the permissions of its fields.

Both approaches are possible. Based on the error messages on lines 72 and 78 on this test, it seems the implementation is taking (1).


[Bugfix] Fix guided decoding with tokenizer mode mistral

This PR address the issues on #11045.
Changelog:

Fix mistral tokenizer when decode is overwritten by outlines processors, the adapter change this method and when the tokenizer calls this function it gets a wrong response.
Added support for mistral tokenizer with XGrammar
Added tests to cover mistral tokenizer mode
Minor refactor on the xgrammar decoding
Fix tests on test_guided_processors and added then to CI which were not executing to validate changes

FIX #11045 (link existing issues this PR will resolve)

It appears that AMD CI isn't using the correct version of outlines.

I checked the image of the CI for AMD and found this:
lark==0.12.0

On my environment I have
lark==1.2.2

Not sure the best way to fix besides set it in requirements... Any suggestion?

@DarkLight1337 updated it. Let's see what CI says now.


New-TunnelfromVpnForm

Create a function that uses example vpn form and import excel to generate the selected tunnel type.
Need to exclaim this only works if cell values maintain their same position, otherwise reference examples.
Use environment variable to surpress disclaimer after first acknowledgement.

done