[QUESTION] Fresh install of k3s on Fedora 33 with latest docker fails to create clusters.

What did you do

How was the cluster created?

k3d cluster create

What did you do afterwards?

Tried to reinstall

What did you expect to happen
A Cluster to be presented to me.
Which OS & Architecture

Linux

Which version of k3d

k3s version v1.19.3-k3s3 (default)

Which version of docker

output of docker version and docker info

Client: Docker Engine - Community
 Version:           20.10.0-rc1
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        5cc2396
 Built:             Tue Nov 17 22:52:47 2020
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.0-rc1
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       131bf7e
  Built:            Tue Nov 17 22:50:28 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.1
  GitCommit:        c623d1b36f09f8ef6536a057bd658b3aa8632828
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.4.2-docker)

Server:
 Containers: 2
  Running: 0
  Paused: 0
  Stopped: 2
 Images: 3
 Server Version: 20.10.0-rc1
 Storage Driver: overlay2
  Backing Filesystem: btrfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: c623d1b36f09f8ef6536a057bd658b3aa8632828
 runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.9.11-200.fc33.x86_64
 Operating System: Fedora 33 (KDE Plasma)
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 31.33GiB
 Name: cray
 ID: IHCN:T6MJ:D2DO:I23H:EAG7:TPRB:AZIM:UCN3:OSSW:6UBW:BGQ5:43YZ
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

WARNING: No kernel memory TCP limit support
WARNING: No oom kill disable support
WARNING: Support for cgroup v2 is experimental

[dfogle@cray ~]$ k3d cluster create
INFO[0000] Created network 'k3d-k3s-default'
INFO[0000] Created volume 'k3d-k3s-default-images'
INFO[0001] Creating node 'k3d-k3s-default-server-0'
ERRO[0003] Failed waiting for log message 'k3s is up and running' from node 'k3d-k3s-default-server-0'
ERRO[0003] Server node 'k3d-k3s-default-server-0' failed to get ready: Node 'k3d-k3s-default-server-0' (container 'a650392171e033b695a52f5f7f9be5085ceb556c49092988e41925d6369a0aa0') not running
ERRO[0003] Failed to create cluster >>> Rolling Back
INFO[0003] Deleting cluster 'k3s-default'
INFO[0003] Deleted k3d-k3s-default-server-0
INFO[0003] Deleting cluster network 'fd80dc2cdb7367c319c84b30e05d78425ecdfec48e8a3e649c3e4bceb79e2d73'
FATA[0003] Cluster creation FAILED, all changes have been rolled back!

[dfogle@cray ~]$ k3d cluster create  dev --trace
DEBU[0000] Selected runtime is 'docker.Docker'
DEBU[0000] API-Port Mapping didn't specify hostPort, choosing one randomly...

Hi @birdiesanders , thanks for opening this issue!
Nothing suspicious in the k3d logs, so let's check the k3s logs :+1:
Can you please create a cluster and prevent rollback via k3d cluster create dev --no-rollback and then check the logs of the server container via docker logs k3d-dev-server-0?
There are probably some error messages and a fatal message near the end of the log stream.
Would be cool if you could post this output here for further debugging.

[birdie@dawanda]: ~/civo-work/operators/civo-stack-operator>$ docker logs k3d-dev-server-0
time="2020-12-03T16:07:44.366499784Z" level=info msg="Starting k3s v1.18.9+k3s1 (630bebf9)"
time="2020-12-03T16:07:45.057953757Z" level=info msg="Kine listening on unix://kine.sock"
time="2020-12-03T16:07:45.245207943Z" level=info msg="Active TLS secret  (ver=) (count 8): map[listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-kubernetes:kubernetes listener.cattle.io/cn-kubernetes.default:kubernetes.default listener.cattle.io/cn-kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local listener.cattle.io/cn-localhost:localhost listener.cattle.io/hash:df2ece2e551e24fb8e81154f0d8023b5da59d8358726e78ba0a117279ccdcada]"
time="2020-12-03T16:07:45.254891513Z" level=info msg="Running kube-apiserver --advertise-port=6443 --allow-privileged=true --anonymous-auth=false --api-audiences=unknown --authorization-mode=Node,RBAC --basic-auth-file=/var/lib/rancher/k3s/server/cred/passwd --bind-address=<IP_ADDRESS> --cert-dir=/var/lib/rancher/k3s/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction --etcd-servers=unix://kine.sock --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/k3s/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.key --proxy-client-cert-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/k3s/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6444 --service-account-issuer=k3s --service-account-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-cluster-ip-range=<IP_ADDRESS>/16 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
Flag --basic-auth-file has been deprecated, Basic authentication mode is deprecated and will be removed in a future release. It is not recommended for production environments.
I1203 16:07:45.255550       6 server.go:645] external host was not specified, using <IP_ADDRESS>
I1203 16:07:45.256375       6 server.go:162] Version: v1.18.9+k3s1
I1203 16:07:45.946490       6 plugins.go:158] Loaded 12 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,RuntimeClass,DefaultIngressClass,MutatingAdmissionWebhook.
I1203 16:07:45.946519       6 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
I1203 16:07:45.948115       6 plugins.go:158] Loaded 12 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,RuntimeClass,DefaultIngressClass,MutatingAdmissionWebhook.
I1203 16:07:45.948135       6 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
I1203 16:07:45.991842       6 master.go:270] Using reconciler: lease
I1203 16:07:46.033364       6 rest.go:113] the default service ipfamily for this cluster is: IPv4
W1203 16:07:46.416905       6 genericapiserver.go:409] Skipping API batch/v2alpha1 because it has no resources.
W1203 16:07:46.426747       6 genericapiserver.go:409] Skipping API discovery.k8s.io/v1alpha1 because it has no resources.
W1203 16:07:46.439741       6 genericapiserver.go:409] Skipping API node.k8s.io/v1alpha1 because it has no resources.
W1203 16:07:46.459312       6 genericapiserver.go:409] Skipping API rbac.authorization.k8s.io/v1alpha1 because it has no resources.
W1203 16:07:46.463591       6 genericapiserver.go:409] Skipping API scheduling.k8s.io/v1alpha1 because it has no resources.
W1203 16:07:46.481965       6 genericapiserver.go:409] Skipping API storage.k8s.io/v1alpha1 because it has no resources.
W1203 16:07:46.515192       6 genericapiserver.go:409] Skipping API apps/v1beta2 because it has no resources.
W1203 16:07:46.515229       6 genericapiserver.go:409] Skipping API apps/v1beta1 because it has no resources.
I1203 16:07:46.525940       6 plugins.go:158] Loaded 12 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,RuntimeClass,DefaultIngressClass,MutatingAdmissionWebhook.
I1203 16:07:46.525963       6 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
I1203 16:07:48.898630       6 dynamic_cafile_content.go:167] Starting request-header::/var/lib/rancher/k3s/server/tls/request-header-ca.crt
I1203 16:07:48.898641       6 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/server/tls/client-ca.crt
I1203 16:07:48.899008       6 dynamic_serving_content.go:130] Starting serving-cert::/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt::/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key
I1203 16:07:48.899657       6 secure_serving.go:178] Serving securely on <IP_ADDRESS>:6444
I1203 16:07:48.899740       6 tlsconfig.go:240] Starting DynamicServingCertificateController
I1203 16:07:48.899776       6 crd_finalizer.go:266] Starting CRDFinalizer
I1203 16:07:48.899780       6 available_controller.go:387] Starting AvailableConditionController
I1203 16:07:48.899791       6 cache.go:32] Waiting for caches to sync for AvailableConditionController controller
I1203 16:07:48.899816       6 controller.go:86] Starting OpenAPI controller
I1203 16:07:48.899837       6 customresource_discovery_controller.go:209] Starting DiscoveryController
I1203 16:07:48.899852       6 naming_controller.go:291] Starting NamingConditionController
I1203 16:07:48.899869       6 establishing_controller.go:76] Starting EstablishingController
I1203 16:07:48.899858       6 apiservice_controller.go:94] Starting APIServiceRegistrationController
I1203 16:07:48.899891       6 nonstructuralschema_controller.go:186] Starting NonStructuralSchemaConditionController
I1203 16:07:48.899894       6 cache.go:32] Waiting for caches to sync for APIServiceRegistrationController controller
I1203 16:07:48.899917       6 apiapproval_controller.go:186] Starting KubernetesAPIApprovalPolicyConformantConditionController
I1203 16:07:48.899996       6 autoregister_controller.go:141] Starting autoregister controller
I1203 16:07:48.900017       6 cache.go:32] Waiting for caches to sync for autoregister controller
I1203 16:07:48.900053       6 crdregistration_controller.go:111] Starting crd-autoregister controller
I1203 16:07:48.900072       6 shared_informer.go:223] Waiting for caches to sync for crd-autoregister
I1203 16:07:48.900130       6 controller.go:81] Starting OpenAPI AggregationController
I1203 16:07:48.900387       6 cluster_authentication_trust_controller.go:440] Starting cluster_authentication_trust_controller controller
I1203 16:07:48.900401       6 shared_informer.go:223] Waiting for caches to sync for cluster_authentication_trust_controller
I1203 16:07:48.900447       6 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/server/tls/client-ca.crt
I1203 16:07:48.900486       6 dynamic_cafile_content.go:167] Starting request-header::/var/lib/rancher/k3s/server/tls/request-header-ca.crt
I1203 16:07:49.000029       6 cache.go:39] Caches are synced for AvailableConditionController controller
I1203 16:07:49.000050       6 cache.go:39] Caches are synced for APIServiceRegistrationController controller
I1203 16:07:49.000154       6 cache.go:39] Caches are synced for autoregister controller
I1203 16:07:49.000221       6 shared_informer.go:230] Caches are synced for crd-autoregister
I1203 16:07:49.000550       6 shared_informer.go:230] Caches are synced for cluster_authentication_trust_controller
E1203 16:07:49.038383       6 controller.go:151] Unable to perform initial Kubernetes service initialization: Service "kubernetes" is invalid: spec.clusterIP: Invalid value: "<IP_ADDRESS>": cannot allocate resources of type serviceipallocations at this time
E1203 16:07:49.042789       6 controller.go:156] Unable to remove old endpoints from kubernetes service: StorageError: key not found, Code: 1, Key: /registry/masterleases/<IP_ADDRESS>, ResourceVersion: 0, AdditionalErrorMsg:
I1203 16:07:49.898479       6 controller.go:130] OpenAPI AggregationController: action for item : Nothing (removed from the queue).
I1203 16:07:49.898646       6 controller.go:130] OpenAPI AggregationController: action for item k8s_internal_local_delegation_chain_0000000000: Nothing (removed from the queue).
I1203 16:07:49.904376       6 storage_scheduling.go:134] created PriorityClass system-node-critical with value<PHONE_NUMBER>
I1203 16:07:49.908524       6 storage_scheduling.go:134] created PriorityClass system-cluster-critical with value<PHONE_NUMBER>
I1203 16:07:49.908544       6 storage_scheduling.go:143] all system priority classes are created successfully or already exist.
I1203 16:07:50.253918       6 controller.go:606] quota admission added evaluator for: roles.rbac.authorization.k8s.io
I1203 16:07:50.291315       6 controller.go:606] quota admission added evaluator for: rolebindings.rbac.authorization.k8s.io
W1203 16:07:50.375684       6 lease.go:224] Resetting endpoints for master service "kubernetes" to [<IP_ADDRESS>]
I1203 16:07:50.376711       6 controller.go:606] quota admission added evaluator for: endpoints
I1203 16:07:50.380074       6 controller.go:606] quota admission added evaluator for: endpointslices.discovery.k8s.io
I1203 16:07:50.915859       6 registry.go:150] Registering EvenPodsSpread predicate and priority function
I1203 16:07:50.915902       6 registry.go:150] Registering EvenPodsSpread predicate and priority function
time="2020-12-03T16:07:50.917559187Z" level=info msg="Running kube-scheduler --bind-address=<IP_ADDRESS> --kubeconfig=/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig --leader-elect=false --port=10251 --secure-port=0"
time="2020-12-03T16:07:50.918727861Z" level=info msg="Running kube-controller-manager --allocate-node-cidrs=true --bind-address=<IP_ADDRESS> --cluster-cidr=<IP_ADDRESS>/16 --cluster-signing-cert-file=/var/lib/rancher/k3s/server/tls/server-ca.crt --cluster-signing-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --kubeconfig=/var/lib/rancher/k3s/server/cred/controller.kubeconfig --leader-elect=false --port=10252 --root-ca-file=/var/lib/rancher/k3s/server/tls/server-ca.crt --secure-port=0 --service-account-private-key-file=/var/lib/rancher/k3s/server/tls/service.key --use-service-account-credentials=true"
time="2020-12-03T16:07:50.930512167Z" level=info msg="Waiting for cloudcontroller rbac role to be created"
I1203 16:07:50.934106       6 controllermanager.go:161] Version: v1.18.9+k3s1
I1203 16:07:50.935758       6 deprecated_insecure_serving.go:53] Serving insecurely on [::]:10252
time="2020-12-03T16:07:50.941636570Z" level=info msg="Creating CRD addons.k3s.cattle.io"
I1203 16:07:50.945623       6 registry.go:150] Registering EvenPodsSpread predicate and priority function
I1203 16:07:50.945665       6 registry.go:150] Registering EvenPodsSpread predicate and priority function
W1203 16:07:50.950384       6 authorization.go:47] Authorization is disabled
W1203 16:07:50.950439       6 authentication.go:40] Authentication is disabled
I1203 16:07:50.950470       6 deprecated_insecure_serving.go:51] Serving healthz insecurely on [::]:10251
time="2020-12-03T16:07:50.953923630Z" level=info msg="Creating CRD helmcharts.helm.cattle.io"
time="2020-12-03T16:07:50.964374325Z" level=info msg="Waiting for CRD addons.k3s.cattle.io to become available"
time="2020-12-03T16:07:51.470920158Z" level=info msg="Done waiting for CRD addons.k3s.cattle.io to become available"
time="2020-12-03T16:07:51.471007997Z" level=info msg="Waiting for CRD helmcharts.helm.cattle.io to become available"
time="2020-12-03T16:07:51.940847883Z" level=info msg="Waiting for cloudcontroller rbac role to be created"
time="2020-12-03T16:07:51.977304529Z" level=info msg="Done waiting for CRD helmcharts.helm.cattle.io to become available"
time="2020-12-03T16:07:51.988272695Z" level=info msg="Writing static file: /var/lib/rancher/k3s/server/static/charts/traefik-1.81.0.tgz"
time="2020-12-03T16:07:51.988780730Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/local-storage.yaml"
time="2020-12-03T16:07:51.988970920Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/aggregated-metrics-reader.yaml"
time="2020-12-03T16:07:51.989122528Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/auth-delegator.yaml"
time="2020-12-03T16:07:51.989270641Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/auth-reader.yaml"
time="2020-12-03T16:07:51.989392851Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/metrics-apiservice.yaml"
time="2020-12-03T16:07:51.989562638Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/rolebindings.yaml"
time="2020-12-03T16:07:51.989704953Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/ccm.yaml"
time="2020-12-03T16:07:51.989925557Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/coredns.yaml"
time="2020-12-03T16:07:51.990071348Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-deployment.yaml"
time="2020-12-03T16:07:51.990197074Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-service.yaml"
time="2020-12-03T16:07:51.990319454Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/resource-reader.yaml"
time="2020-12-03T16:07:51.990520135Z" level=info msg="Writing manifest: /var/lib/rancher/k3s/server/manifests/traefik.yaml"
time="2020-12-03T16:07:52.091109100Z" level=info msg="Starting k3s.cattle.io/v1, Kind=Addon controller"
time="2020-12-03T16:07:52.091229283Z" level=info msg="Waiting for master node  startup: resource name may not be empty"
time="2020-12-03T16:07:52.091710358Z" level=info msg="Node token is available at /var/lib/rancher/k3s/server/token"
time="2020-12-03T16:07:52.091821879Z" level=info msg="To join node to cluster: k3s agent -s https://<IP_ADDRESS>:6443 -t ${NODE_TOKEN}"
I1203 16:07:52.121373       6 controller.go:606] quota admission added evaluator for: addons.k3s.cattle.io
I1203 16:07:52.133953       6 controller.go:606] quota admission added evaluator for: serviceaccounts
2020-12-03 16:07:52.146079 I | http: TLS handshake error from <IP_ADDRESS>:49136: remote error: tls: bad certificate
time="2020-12-03T16:07:52.154186729Z" level=info msg="Wrote kubeconfig /output/kubeconfig.yaml"
time="2020-12-03T16:07:52.154216969Z" level=info msg="Run: k3s kubectl"
time="2020-12-03T16:07:52.154224715Z" level=info msg="k3s is up and running"
time="2020-12-03T16:07:52.154378124Z" level=info msg="module overlay was already loaded"
time="2020-12-03T16:07:52.154418250Z" level=info msg="module nf_conntrack was already loaded"
time="2020-12-03T16:07:52.154443766Z" level=info msg="module br_netfilter was already loaded"
2020-12-03 16:07:52.156024 I | http: TLS handshake error from <IP_ADDRESS>:49144: remote error: tls: bad certificate
2020-12-03 16:07:52.161532 I | http: TLS handshake error from <IP_ADDRESS>:49150: remote error: tls: bad certificate
I1203 16:07:52.177894       6 controller.go:606] quota admission added evaluator for: deployments.apps
time="2020-12-03T16:07:52.192087774Z" level=info msg="Starting helm.cattle.io/v1, Kind=HelmChart controller"
time="2020-12-03T16:07:52.192127700Z" level=info msg="Starting /v1, Kind=Endpoints controller"
time="2020-12-03T16:07:52.192103963Z" level=info msg="Starting /v1, Kind=Node controller"
time="2020-12-03T16:07:52.192106764Z" level=info msg="Starting /v1, Kind=Service controller"
time="2020-12-03T16:07:52.192114509Z" level=info msg="Starting batch/v1, Kind=Job controller"
time="2020-12-03T16:07:52.192116800Z" level=info msg="Starting /v1, Kind=Pod controller"
time="2020-12-03T16:07:52.255603971Z" level=info msg="Logging containerd to /var/lib/rancher/k3s/agent/containerd/containerd.log"
time="2020-12-03T16:07:52.255729246Z" level=info msg="Running containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd"
time="2020-12-03T16:07:52.255842860Z" level=info msg="Waiting for containerd startup: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /run/k3s/containerd/containerd.sock: connect: no such file or directory\""
time="2020-12-03T16:07:52.350834576Z" level=info msg="Starting /v1, Kind=Secret controller"
time="2020-12-03T16:07:52.358136908Z" level=info msg="Active TLS secret k3s-serving (ver=182) (count 8): map[listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-<IP_ADDRESS>:<IP_ADDRESS> listener.cattle.io/cn-kubernetes:kubernetes listener.cattle.io/cn-kubernetes.default:kubernetes.default listener.cattle.io/cn-kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local listener.cattle.io/cn-localhost:localhost listener.cattle.io/hash:df2ece2e551e24fb8e81154f0d8023b5da59d8358726e78ba0a117279ccdcada]"
I1203 16:07:52.410742       6 request.go:621] Throttling request took 1.044629112s, request: GET:https://<IP_ADDRESS>:6444/apis/apiextensions.k8s.io/v1beta1?timeout=32s
I1203 16:07:52.415369       6 controller.go:606] quota admission added evaluator for: helmcharts.helm.cattle.io
I1203 16:07:53.114081       6 plugins.go:100] No cloud provider specified.
I1203 16:07:53.118575       6 shared_informer.go:223] Waiting for caches to sync for tokens
I1203 16:07:53.218767       6 shared_informer.go:230] Caches are synced for tokens
time="2020-12-03T16:07:53.256540686Z" level=info msg="Waiting for containerd startup: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /run/k3s/containerd/containerd.sock: connect: no such file or directory\""
I1203 16:07:53.297790       6 trace.go:116] Trace[325877377]: "Create" url:/apis/k3s.cattle.io/v1/namespaces/kube-system/addons,user-agent:k3s/v1.18.9+k3s1 (linux/amd64) kubernetes/630bebf,client:<IP_ADDRESS> (started: 2020-12-03 16:07:52.592287061 +0000 UTC m=+10.980395300) (total time: 705.407252ms):
Trace[325877377]: [705.16385ms] [704.921366ms] Object stored in database
time="2020-12-03T16:07:53.306017141Z" level=info msg="Waiting for master node k3d-dev-server-0 startup: nodes \"k3d-dev-server-0\" not found"
time="2020-12-03T16:07:53.306393101Z" level=info msg="Running cloud-controller-manager --allocate-node-cidrs=true --allow-untagged-cloud=true --bind-address=<IP_ADDRESS> --cloud-provider=k3s --cluster-cidr=<IP_ADDRESS>/16 --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --node-status-update-frequency=1m --secure-port=0"
Flag --allow-untagged-cloud has been deprecated, This flag is deprecated and will be removed in a future release. A cluster-id will be required on cloud instances.
I1203 16:07:53.314150       6 controllermanager.go:120] Version: v1.18.9+k3s1
W1203 16:07:53.314173       6 controllermanager.go:132] detected a cluster without a ClusterID.  A ClusterID will be required in the future.  Please tag your cluster to avoid any future issues
I1203 16:07:53.319026       6 node_controller.go:110] Sending events to api server.
I1203 16:07:53.319114       6 controllermanager.go:247] Started "cloud-node"
I1203 16:07:53.321688       6 node_lifecycle_controller.go:78] Sending events to api server
I1203 16:07:53.321854       6 controllermanager.go:247] Started "cloud-node-lifecycle"
E1203 16:07:53.327980       6 core.go:90] Failed to start service controller: the cloud provider does not support external load balancers
W1203 16:07:53.328000       6 controllermanager.go:244] Skipping "service"
W1203 16:07:53.328009       6 core.go:108] configure-cloud-routes is set, but cloud provider does not support routes. Will not configure cloud provider routes.
W1203 16:07:53.328015       6 controllermanager.go:244] Skipping "route"
E1203 16:07:53.342815       6 namespaced_resources_deleter.go:161] unable to get all supported resources from server: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
I1203 16:07:53.342941       6 controllermanager.go:533] Started "namespace"
I1203 16:07:53.342969       6 namespace_controller.go:200] Starting namespace controller
I1203 16:07:53.342983       6 shared_informer.go:223] Waiting for caches to sync for namespace
I1203 16:07:53.357010       6 controllermanager.go:533] Started "daemonset"
I1203 16:07:53.357215       6 daemon_controller.go:286] Starting daemon sets controller
I1203 16:07:53.357253       6 shared_informer.go:223] Waiting for caches to sync for daemon sets
I1203 16:07:53.372809       6 controllermanager.go:533] Started "csrcleaner"
I1203 16:07:53.372902       6 cleaner.go:82] Starting CSR cleaner controller
I1203 16:07:53.388564       6 controllermanager.go:533] Started "endpoint"
I1203 16:07:53.388711       6 endpoints_controller.go:181] Starting endpoint controller
I1203 16:07:53.388744       6 shared_informer.go:223] Waiting for caches to sync for endpoint
I1203 16:07:53.403379       6 controllermanager.go:533] Started "replicationcontroller"
I1203 16:07:53.403462       6 replica_set.go:182] Starting replicationcontroller controller
I1203 16:07:53.403486       6 shared_informer.go:223] Waiting for caches to sync for ReplicationController
I1203 16:07:53.423987       6 trace.go:116] Trace[1349030457]: "Create" url:/api/v1/namespaces/kube-system/serviceaccounts,user-agent:k3s/v1.18.9+k3s1 (linux/amd64) kubernetes/630bebf,client:<IP_ADDRESS> (started: 2020-12-03 16:07:52.420582014 +0000 UTC m=+10.808690254) (total time: 1.003361285s):
Trace[1349030457]: [1.003253236s] [1.003139643s] Object stored in database
E1203 16:07:53.445716       6 memcache.go:206] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
I1203 16:07:53.578492       6 controller.go:606] quota admission added evaluator for: jobs.batch
E1203 16:07:53.873367       6 memcache.go:111] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
W1203 16:07:53.876164       6 garbagecollector.go:644] failed to discover some groups: map[metrics.k8s.io/v1beta1:the server is currently unable to handle the request]
E1203 16:07:53.892595       6 memcache.go:206] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
time="2020-12-03T16:07:54.257402453Z" level=info msg="Waiting for containerd startup: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /run/k3s/containerd/containerd.sock: connect: no such file or directory\""
W1203 16:07:54.285598       6 handler_proxy.go:102] no RequestInfo found in the context
E1203 16:07:54.285771       6 controller.go:114] loading OpenAPI spec for "v1beta1.metrics.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: service unavailable
, Header: map[Content-Type:[text/plain; charset=utf-8] X-Content-Type-Options:[nosniff]]
I1203 16:07:54.285804       6 controller.go:127] OpenAPI AggregationController: action for item v1beta1.metrics.k8s.io: Rate Limited Requeue.
time="2020-12-03T16:07:54.311564393Z" level=info msg="Waiting for master node k3d-dev-server-0 startup: nodes \"k3d-dev-server-0\" not found"
E1203 16:07:54.328826       6 memcache.go:111] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
I1203 16:07:54.334571       6 garbagecollector.go:133] Starting garbage collector controller
I1203 16:07:54.334615       6 shared_informer.go:223] Waiting for caches to sync for garbage collector
I1203 16:07:54.334725       6 graph_builder.go:282] GraphBuilder running
I1203 16:07:54.334919       6 controllermanager.go:533] Started "garbagecollector"
I1203 16:07:54.341589       6 controllermanager.go:533] Started "csrapproving"
W1203 16:07:54.341625       6 controllermanager.go:512] "bootstrapsigner" is disabled
I1203 16:07:54.341653       6 certificate_controller.go:119] Starting certificate controller "csrapproving"
I1203 16:07:54.341689       6 shared_informer.go:223] Waiting for caches to sync for certificate-csrapproving
I1203 16:07:54.361259       6 controllermanager.go:533] Started "pv-protection"
W1203 16:07:54.361326       6 controllermanager.go:525] Skipping "root-ca-cert-publisher"
I1203 16:07:54.361373       6 pv_protection_controller.go:83] Starting PV protection controller
I1203 16:07:54.361399       6 shared_informer.go:223] Waiting for caches to sync for PV protection
I1203 16:07:54.379489       6 controllermanager.go:533] Started "serviceaccount"
I1203 16:07:54.379591       6 serviceaccounts_controller.go:117] Starting service account controller
I1203 16:07:54.379616       6 shared_informer.go:223] Waiting for caches to sync for service account
I1203 16:07:54.412479       6 controllermanager.go:533] Started "horizontalpodautoscaling"
I1203 16:07:54.412636       6 horizontal.go:169] Starting HPA controller
I1203 16:07:54.412672       6 shared_informer.go:223] Waiting for caches to sync for HPA
I1203 16:07:54.429827       6 node_lifecycle_controller.go:78] Sending events to api server
E1203 16:07:54.429939       6 core.go:229] failed to start cloud node lifecycle controller: no cloud provider provided
W1203 16:07:54.429970       6 controllermanager.go:525] Skipping "cloud-node-lifecycle"
I1203 16:07:54.443217       6 controllermanager.go:533] Started "persistentvolume-binder"
I1203 16:07:54.443312       6 pv_controller_base.go:295] Starting persistent volume controller
I1203 16:07:54.443341       6 shared_informer.go:223] Waiting for caches to sync for persistent volume
I1203 16:07:54.459438       6 controllermanager.go:533] Started "clusterrole-aggregation"
I1203 16:07:54.459570       6 clusterroleaggregation_controller.go:149] Starting ClusterRoleAggregator
I1203 16:07:54.459609       6 shared_informer.go:223] Waiting for caches to sync for ClusterRoleAggregator
I1203 16:07:54.477334       6 controllermanager.go:533] Started "replicaset"
I1203 16:07:54.477507       6 replica_set.go:182] Starting replicaset controller
I1203 16:07:54.477546       6 shared_informer.go:223] Waiting for caches to sync for ReplicaSet
I1203 16:07:54.491987       6 controllermanager.go:533] Started "ttl"
I1203 16:07:54.492017       6 ttl_controller.go:118] Starting TTL controller
I1203 16:07:54.492026       6 shared_informer.go:223] Waiting for caches to sync for TTL
I1203 16:07:54.499233       6 node_lifecycle_controller.go:384] Sending events to api server.
I1203 16:07:54.499658       6 taint_manager.go:163] Sending events to api server.
I1203 16:07:54.499826       6 node_lifecycle_controller.go:512] Controller will reconcile labels.
I1203 16:07:54.499885       6 controllermanager.go:533] Started "nodelifecycle"
W1203 16:07:54.499912       6 controllermanager.go:525] Skipping "ttl-after-finished"
I1203 16:07:54.499955       6 node_lifecycle_controller.go:546] Starting node controller
I1203 16:07:54.499991       6 shared_informer.go:223] Waiting for caches to sync for taint
I1203 16:07:54.561990       6 controllermanager.go:533] Started "disruption"
I1203 16:07:54.562045       6 disruption.go:331] Starting disruption controller
I1203 16:07:54.562078       6 shared_informer.go:223] Waiting for caches to sync for disruption
I1203 16:07:54.615502       6 controllermanager.go:533] Started "csrsigning"
W1203 16:07:54.615547       6 core.go:243] configure-cloud-routes is set, but no cloud provider specified. Will not configure cloud provider routes.
W1203 16:07:54.615561       6 controllermanager.go:525] Skipping "route"
I1203 16:07:54.615582       6 certificate_controller.go:119] Starting certificate controller "csrsigning"
I1203 16:07:54.615622       6 shared_informer.go:223] Waiting for caches to sync for certificate-csrsigning
I1203 16:07:54.615664       6 dynamic_serving_content.go:130] Starting csr-controller::/var/lib/rancher/k3s/server/tls/server-ca.crt::/var/lib/rancher/k3s/server/tls/server-ca.key
I1203 16:07:55.208954       6 trace.go:116] Trace[360670374]: "Create" url:/apis/batch/v1/namespaces/kube-system/jobs,user-agent:k3s/v1.18.9+k3s1 (linux/amd64) kubernetes/630bebf,client:<IP_ADDRESS> (started: 2020-12-03 16:07:53.564301081 +0000 UTC m=+11.952409384) (total time: 1.644551429s):
Trace[360670374]: [1.643191471s] [1.631424149s] Object stored in database
E1203 16:07:55.226819       6 resource_quota_controller.go:161] initial discovery check failure, continuing and counting on future sync update: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request
I1203 16:07:55.227003       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for ingresses.extensions
I1203 16:07:55.227093       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for replicasets.apps
I1203 16:07:55.227171       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for events.events.k8s.io
I1203 16:07:55.227217       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for cronjobs.batch
I1203 16:07:55.227270       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for networkpolicies.networking.k8s.io
I1203 16:07:55.227327       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for addons.k3s.cattle.io
I1203 16:07:55.227453       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for endpointslices.discovery.k8s.io
I1203 16:07:55.228049       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for ingresses.networking.k8s.io
I1203 16:07:55.228154       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for helmcharts.helm.cattle.io
I1203 16:07:55.228236       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for deployments.apps
I1203 16:07:55.228306       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for rolebindings.rbac.authorization.k8s.io
I1203 16:07:55.228381       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for leases.coordination.k8s.io
I1203 16:07:55.228496       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for statefulsets.apps
I1203 16:07:55.228569       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for roles.rbac.authorization.k8s.io
I1203 16:07:55.228998       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for serviceaccounts
I1203 16:07:55.229108       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for endpoints
I1203 16:07:55.229161       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for controllerrevisions.apps
I1203 16:07:55.229213       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for horizontalpodautoscalers.autoscaling
I1203 16:07:55.229277       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for poddisruptionbudgets.policy
I1203 16:07:55.229346       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for podtemplates
I1203 16:07:55.229444       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for limitranges
I1203 16:07:55.229514       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for daemonsets.apps
I1203 16:07:55.229578       6 resource_quota_monitor.go:228] QuotaMonitor created object count evaluator for jobs.batch
I1203 16:07:55.229613       6 controllermanager.go:533] Started "resourcequota"
I1203 16:07:55.229670       6 resource_quota_controller.go:272] Starting resource quota controller
I1203 16:07:55.229708       6 shared_informer.go:223] Waiting for caches to sync for resource quota
I1203 16:07:55.229744       6 resource_quota_monitor.go:303] QuotaMonitor running
I1203 16:07:55.269716       6 controllermanager.go:533] Started "statefulset"
I1203 16:07:55.269764       6 stateful_set.go:146] Starting stateful set controller
I1203 16:07:55.269786       6 shared_informer.go:223] Waiting for caches to sync for stateful set
I1203 16:07:55.278023       6 node_ipam_controller.go:94] Sending events to api server.
time="2020-12-03T16:07:55.281248575Z" level=info msg="Connecting to proxy" url="wss://<IP_ADDRESS>:6443/v1-k3s/connect"
time="2020-12-03T16:07:55.288128885Z" level=info msg="Handling backend connection request [k3d-dev-server-0]"
time="2020-12-03T16:07:55.289288493Z" level=warning msg="Disabling CPU quotas due to missing cpu.cfs_period_us"
time="2020-12-03T16:07:55.290758723Z" level=info msg="Running kubelet --address=<IP_ADDRESS> --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/k3s/agent/client-ca.crt --cloud-provider=external --cluster-dns=<IP_ADDRESS> --cluster-domain=cluster.local --cni-bin-dir=/bin --cni-conf-dir=/var/lib/rancher/k3s/agent/etc/cni/net.d --container-runtime-endpoint=/run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --cpu-cfs-quota=false --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=<IP_ADDRESS> --hostname-override=k3d-dev-server-0 --kubeconfig=/var/lib/rancher/k3s/agent/kubelet.kubeconfig --kubelet-cgroups=/systemd --node-labels= --read-only-port=0 --resolv-conf=/tmp/k3s-resolv.conf --runtime-cgroups=/systemd --serialize-image-pulls=false --tls-cert-file=/var/lib/rancher/k3s/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/k3s/agent/serving-kubelet.key"
time="2020-12-03T16:07:55.290990849Z" level=info msg="Running kube-proxy --cluster-cidr=<IP_ADDRESS>/16 --healthz-bind-address=<IP_ADDRESS> --hostname-override=k3d-dev-server-0 --kubeconfig=/var/lib/rancher/k3s/agent/kubeproxy.kubeconfig --proxy-mode=iptables"
Flag --containerd has been deprecated, This is a cadvisor flag that was mistakenly registered with the Kubelet. Due to legacy concerns, it will follow the standard CLI deprecation timeline before being removed.
W1203 16:07:55.291155       6 server.go:225] WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP.
I1203 16:07:55.292194       6 server.go:413] Version: v1.18.9+k3s1
I1203 16:07:55.300038       6 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/agent/client-ca.crt
W1203 16:07:55.302595       6 fs.go:206] stat failed on /dev/mapper/root with error: no such file or directory
time="2020-12-03T16:07:55.306158736Z" level=info msg="waiting for node k3d-dev-server-0: nodes \"k3d-dev-server-0\" not found"
W1203 16:07:55.311202       6 info.go:51] Couldn't collect info from any of the files in "/etc/machine-id,/var/lib/dbus/machine-id"
I1203 16:07:55.312119       6 server.go:645] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /
I1203 16:07:55.313140       6 container_manager_linux.go:277] container manager verified user specified cgroup-root exists: []
I1203 16:07:55.313171       6 container_manager_linux.go:282] Creating Container Manager object based on Node Config: {RuntimeCgroupsName:/systemd SystemCgroupsName: KubeletCgroupsName:/systemd ContainerRuntime:remote CgroupsPerQOS:true CgroupRoot:/ CgroupDriver:cgroupfs KubeletRootDir:/var/lib/kubelet ProtectKernelDefaults:false NodeAllocatableConfig:{KubeReservedCgroupName: SystemReservedCgroupName: ReservedSystemCPUs: EnforceNodeAllocatable:map[pods:{}] KubeReserved:map[] SystemReserved:map[] HardEvictionThresholds:[{Signal:imagefs.available Operator:LessThan Value:{Quantity:<nil> Percentage:0.05} GracePeriod:0s MinReclaim:<nil>} {Signal:nodefs.available Operator:LessThan Value:{Quantity:<nil> Percentage:0.05} GracePeriod:0s MinReclaim:<nil>}]} QOSReserved:map[] ExperimentalCPUManagerPolicy:none ExperimentalCPUManagerReconcilePeriod:10s ExperimentalPodPidsLimit:-1 EnforceCPULimits:false CPUCFSQuotaPeriod:100ms ExperimentalTopologyManagerPolicy:none}
I1203 16:07:55.313347       6 topology_manager.go:126] [topologymanager] Creating topology manager with none policy
I1203 16:07:55.313370       6 container_manager_linux.go:312] [topologymanager] Initializing Topology Manager with none policy
I1203 16:07:55.313386       6 container_manager_linux.go:317] Creating device plugin manager: true
W1203 16:07:55.313654       6 util_unix.go:103] Using "/run/k3s/containerd/containerd.sock" as endpoint is deprecated, please consider using full url format "unix:///run/k3s/containerd/containerd.sock".
W1203 16:07:55.313786       6 util_unix.go:103] Using "/run/k3s/containerd/containerd.sock" as endpoint is deprecated, please consider using full url format "unix:///run/k3s/containerd/containerd.sock".
I1203 16:07:55.313890       6 kubelet.go:317] Watching apiserver
time="2020-12-03T16:07:55.316370678Z" level=info msg="Waiting for master node k3d-dev-server-0 startup: nodes \"k3d-dev-server-0\" not found"
W1203 16:07:55.326784       6 proxier.go:625] Failed to read file /lib/modules/5.9.3-zen1-1-zen/modules.builtin with error open /lib/modules/5.9.3-zen1-1-zen/modules.builtin: no such file or directory. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
I1203 16:07:55.327099       6 kuberuntime_manager.go:217] Container runtime containerd initialized, version: v1.3.3-k3s2, apiVersion: v1alpha2
W1203 16:07:55.327502       6 probe.go:268] Flexvolume plugin directory at /usr/libexec/kubernetes/kubelet-plugins/volume/exec/ does not exist. Recreating.
I1203 16:07:55.328161       6 server.go:1124] Started kubelet
I1203 16:07:55.328268       6 server.go:145] Starting to listen on <IP_ADDRESS>:10250
W1203 16:07:55.329498       6 fs.go:540] stat failed on /dev/mapper/root with error: no such file or directory
E1203 16:07:55.329544       6 cri_stats_provider.go:375] Failed to get the info of the filesystem with mountpoint "/var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs": failed to get device for dir "/var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs": could not find device with major: 0, minor: 27 in cached partitions map.
E1203 16:07:55.329583       6 kubelet.go:1308] Image garbage collection failed once. Stats initialization may not have completed yet: invalid capacity 0 on image filesystem
I1203 16:07:55.330851       6 server.go:393] Adding debug handlers to kubelet server.
I1203 16:07:55.332611       6 fs_resource_analyzer.go:64] Starting FS ResourceAnalyzer
I1203 16:07:55.332840       6 volume_manager.go:265] Starting Kubelet Volume Manager
I1203 16:07:55.333053       6 desired_state_of_world_populator.go:139] Desired state populator starts to run
E1203 16:07:55.344404       6 controller.go:228] failed to get node "k3d-dev-server-0" when trying to set owner ref to the node lease: nodes "k3d-dev-server-0" not found
I1203 16:07:55.354346       6 kubelet_node_status.go:294] Setting node annotation to enable volume controller attach/detach
I1203 16:07:55.356824       6 cpu_manager.go:184] [cpumanager] starting with none policy
I1203 16:07:55.356846       6 cpu_manager.go:185] [cpumanager] reconciling every 10s
I1203 16:07:55.356879       6 state_mem.go:36] [cpumanager] initializing new in-memory state store
I1203 16:07:55.409128       6 status_manager.go:158] Starting to sync pod status with apiserver
I1203 16:07:55.409190       6 kubelet.go:1824] Starting kubelet main sync loop.
E1203 16:07:55.409314       6 kubelet.go:1848] skipping pod synchronization - [container runtime status check may not have completed yet, PLEG is not healthy: pleg has yet to be successful]
I1203 16:07:55.433005       6 kubelet_node_status.go:294] Setting node annotation to enable volume controller attach/detach
E1203 16:07:55.433133       6 kubelet.go:2270] node "k3d-dev-server-0" not found
I1203 16:07:55.435273       6 kubelet_node_status.go:70] Attempting to register node k3d-dev-server-0
E1203 16:07:55.509545       6 kubelet.go:1848] skipping pod synchronization - container runtime status check may not have completed yet
E1203 16:07:55.533296       6 kubelet.go:2270] node "k3d-dev-server-0" not found
W1203 16:07:55.544094       6 proxier.go:635] Failed to load kernel module ip_vs with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1203 16:07:55.544839       6 proxier.go:635] Failed to load kernel module ip_vs_rr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1203 16:07:55.545573       6 proxier.go:635] Failed to load kernel module ip_vs_wrr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1203 16:07:55.546206       6 proxier.go:635] Failed to load kernel module ip_vs_sh with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1203 16:07:55.546735       6 proxier.go:635] Failed to load kernel module nf_conntrack with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
I1203 16:07:55.631474       6 policy_none.go:43] [cpumanager] none policy: Start
W1203 16:07:55.631619       6 fs.go:540] stat failed on /dev/mapper/root with error: no such file or directory
F1203 16:07:55.631653       6 kubelet.go:1386] Failed to start ContainerManager failed to get rootfs info: failed to get device for dir "/var/lib/kubelet": could not find device with major: 0, minor: 27 in cached partitions map

@birdiesanders are you on btrfs or the like?
You may want to have a look and try the stuff from our FAQ: https://k3d.io/faq/faq/#issues-with-btrfs (it's about /dev/mapper)

This works in Arch as a workaround but fails on Fedora, and both Arch and my Fedora system are on btrfs.

Error from Fedora:
Failed to find cpuset cgroup, you may need to add \"cgroup_enable=cpuset\" to your linux cmdline (/boot/cmdline.txt on a Raspberry Pi)"

Okay, so this is definitely no bug in k3d and also cannot be worked around with k3d features.
It's probably caused by Fedora using cgroups v2 which is still in experimental support (as stated at the end of the docker info output) and your using an RC version of docker.
Here are some more general solutions for docker on Fedora, related to cgroups v2: https://www.linuxuprising.com/2019/11/how-to-install-and-use-docker-on-fedora.html?m=1

Hi @birdiesanders , did you get any further with this issue?

Hi @birdiesanders , did you get any further with this issue?


Added Hebrew locale

Please update this mod to Factorio 0.13 (#2)
I've added hebrew to your mod :)

Thanks!

your welcome :)
On Friday, July 1, 2016 11:03 PM, Suprcheese<EMAIL_ADDRESS>wrote:

Thanks!—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Add tests for member mutations

We recently had some failures on our member mutations that passed unnoticed because the test coverage in there is not sufficient. Given that these mutations are quite important features, we want to cover at least:
Here's the skeleton that we want to implement in test/server/graphql/v2/mutation/MemberMutations.test.ts:
describe('memberMutations', () => {
  describe('editMember', () => {
    it('should edit a member role, description and since and documents the changes in an activity', () => {});
    it('must be authenticated as an admin of the collective', () => {});
    it('must not change the role of the last admin', () => {});
    it('can only update role to accountant, admin or member', () => {});
  });

  describe('removeMember', () => {
    it('should remove a member from the collective and document the change in an activity', () => {});
    it('should remove the invitation (if not accepted yet) and document the change in an activity', () => {});
    it('must be authenticated as an admin of the collective', () => {});
    it('can only remove members with role accountant, admin or member', () => {});
    it('can remove an invitation', () => {});
  });
});

Tip: run with npm run test -- --watch test/server/graphql/v2/mutation/MemberMutations.test.ts

:gift: :money_with_wings: A $100 bounty was attached to this issue. Anyone submitting a Pull Request will be rewarded with $100 when the Pull Request is reviewed, accepted and merged.
:arrow_right: More info

:trophy: This issue has been completed by @ersachin3112
To claim the bounty, you can either:

Submit an invoice to https://opencollective.com/engineering/expenses/new (please mention the issue number)
Or ask for an Open Collective gift card of the same value (to donate to other collectives)


Add list and delete commands in policy recommendation CLI

Fix #49
Signed-off-by: Yongming Ding<EMAIL_ADDRESS>

Not introduced by this PR, I just recall previously there is a discussion on replacing the empty state string when we get a NewState by running theia pr status xxx. Maybe we can fix it here or in a new PR?

Not introduced by this PR, I just recall previously there is a discussion on replacing the empty state string when we get a NewState by running theia pr status xxx. Maybe we can fix it here or in a new PR?

No problem, I will take care of it.

/theia-test-e2e

/theia-test-e2e


Support raw binary injection

Some ARM vendors (Allwinner) expect a binary blob loader to exist on the MMC(SD CARD).
I've added some basic logic around this here:
https://github.com/haiku/firmware/blob/master/manifest.json#L49
(My idea at the time was "detect" the integer at the beginning of the string and using that as the seek)
Rune needs to detect this integer, and write the binary at the offset mentioned.

Moved here:
https://dev.haiku-os.org/ticket/14373


App release: Update macOS release process for notarization

overview
With the next release of macOS (10.15 Catalina, Q3 2019), notarization is going to be required for all apps.
acceptance criteria

[ ] Mac app releases are submitted to Apple for notarization and notary ticket is "stapled" to release

implementation details
See the following links:

https://github.com/electron/electron-notarize
https://kilianvalkhof.com/2019/electron/notarizing-your-electron-application/
https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_cs_allow-unsigned-executable-memory

This could be a good time to implement our much-discussed alignment of the app release process with the web release process, where:

CI builds to sandbox bucket
sandbox artifacts are sanity checked
sandbox artifacts are "promoted" to staging / production via an S3 copy

Updates after research and testing:

This is going to necessitate a bump from Electron v3 (which has been EOL'd) to Electron v6 (current)

This will bump our minimum supported macOS version from 10.9 to 10.10
Discussed in Slack with @opatel0 et. al.

I'm going to say that changing our deploy process as part of this is definitively out of scope given the increased testing burden from the Electron bump
It is a good time, however, to finally address #2567

Followup items of work to ticket:

Align app deploy process with other web projects (CI deploys to sandbox location, human promotes to staging/production)

We should also (finally) create stable app links so we don't have to update the website with new app links every time

Update the repo node version to the soon-to-be LTS v12


Fix : Runtime errors

Fix : Runtime erors. Non-existent variables   _stack and _lora_adapter were being accessed for destruction.

This is proposed  fix for following issue : https://github.com/abetlen/llama-cpp-python/issues/1631

Thanks, this should fix these Phi-3 models too!

@shamitv thank you so much for the fix. LGTM


Import/Export

Currently there is no proper import and export functionality. Currently I'm using two python scripts, but one has to set the database connection values as hardcoded string in the file or as parameter. If we only want one function/script for all instances we should either call the script from php and get the values from the .env file or re-implement it in php. First solution would be easier, but it is a bit ugly...
Nethertheless we need the following functionality:

[x] Import tree

[ ] leave existing concepts as they are + add new concepts from the upload
[ ] update existing concepts based on the upload + add new concepts from the upload
[x] purge all existing concepts + add new concepts from the upload

[x] Export tree

[x] Export selected element and it's descendants

[ ] Disable GUI during import/export (because it takes long)

There are a couple of php libraries for parsing rdf files

EasyRDF
DOM
SimpleXML

Any preference? @derntl

I started working with EasyRDF, because it already has all the logic for rdf files. Starting something new would result in a lot of debugging and may not be compatible with other software.

As mentioned in #46 the import wipes the whole database and inserts the data from the rdf file. Is this the desired behaviour or should the code instead update existing entries and add missing ones? @eScienceCenter/spacialists

@AngusLeBoeuf @dirkseidensticker  please answer the last comment.

during import and or export (takes long) the gui should be disabled (loading pizza at top level)

Not all aspects fixed by PR #46

@v1r0x @derntl Generally speaking a more subtle behavior would be preferential. Good options could be:
A. leave existing concepts as they are + add new concepts from the upload
B. update existing concepts based on the upload + add new concepts from the upload
C. purge all existing concepts + add new concepts from the upload

@dirkseidensticker I added your options to OP. Am I right that C. is the current (default) behaviour?

@v1r0x Yes, I think C should be default.


npm start gives "Module build failed: Error: Failed to load plugin import: Cannot find module 'eslint-plugin-import'"

Is this a bug report?
Yes, seems like it to me.

Can you also reproduce the problem with npm 4.x?

I haven't tried yet. I think that would be a wild goose chase. This problem just started today out of the blue. My hunch is that is an environment problem of some sort.
Which terms did you search for in User Guide?

I did a google search instead. Found no help.
Environment

node -v: v8.1.2
npm -v: 5.2.0
yarn --version (if you use Yarn): don't use
npm ls react-scripts (if you haven’t ejected<EMAIL_ADDRESS>
Then, specify:

Operating system: macOS 10.12.5
Browser and version (if relevant): Chrome Version 59.0.3071.115 (Official Build) (64-bit)

Steps to Reproduce

(Write your steps here:)
Invoke:

create-react-app my-app (no issues here)
cd my-app
npm start

After step #3 the console window shows:
Failed to compile.

./src/index.js
Module build failed: Error: Failed to load plugin import: Cannot find module 'eslint-plugin-import'
Referenced from:
    at Array.forEach (native)
    at Array.reduceRight (native)

Expected Behavior

(Write what you thought would happen.)
Actual Behavior

(Write what happened. Please add screenshots!)
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

npm install eslint-plugin-import is a temporary fix while you await a proper fix!

I had same issue.
Installing manually following modules was a fix for me:
eslint-plugin-import
eslint-plugin-react
eslint-plugin-flowtype
eslint-plugin-jsx-a11y

Can confirm I'm seeing this too. Doesn't seem to be a problem when I use yarn, however. I'm at<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>

The following is working fine:
$ npx create-react-app test-eslint
$ cd test-eslint/
$ yarn start

$ npm -v
5.2.0
$ node -v
v8.1.4

Switching back to<EMAIL_ADDRESS>solved the issue for me.

Thanks for confirming @tjkSec; closing this as author failed to follow the issue template.

Users on reddit reporting the same issue. Agree it's a problem with NPM.

I've commented on Reddit, @NathanCH. Thanks for the heads up.

Please file bugs with npm too so they can fix.

@tenzan thanks for the full list of plugins that npm 5.2 finds missing. One thing to bear in mind is that eslint-plugin-jsx-a11y should be v5 instead of the latest (v6); otherwise each file creates a warning:
npm start

Compiled with warnings.

./src/index.js
  Line 1:  Definition for rule 'jsx-a11y/href-no-hash' was not found  jsx-a11y/href-no-hash

./src/registerServiceWorker.js
  Line 11:  Definition for rule 'jsx-a11y/href-no-hash' was not found  jsx-a11y/href-no-hash

./src/App.js

  Line 1:  Definition for rule 'jsx-a11y/href-no-hash' was not found  jsx-a11y/href-no-hash

Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.

Here's a one-liner hack that temporary helped me:
npm install --save-dev eslint-plugin-import eslint-plugin-react eslint-plugin-flowtype eslint-plugin-jsx-a11y@5

Here's a one-liner hack that temporary helped me npm start without downgrading npm to v4

May I ask why you're against downgrading to npm v4?
npm@5 was a rushed release so that it could be included with Node 8; I would not expect it to be stable for some time.
In the interim, I'd continue to use npm@4 or Yarn if you're concerned about having a Lockfile.
I'm not sure what the npm cli team is really doing -- for example, 5.2.0 was released which contained this bug; they reverted the commit but have not made a patch release, leaving people to suffer with this problem for days.

I've tried with npm v4 and I confirm it works. I had the same issue, so downgrading to v4 it takes only 20 secs and it's the "best" solution...

I can empathize with npm here because the only way they can find bugs after a rewrite is by pushing out releases and fixing regressions. I’m hopeful that it should get better after 2.5.1.

I'd like to stress that I'm very grateful for the effort the npm team puts in.
I do not want to undermine what they're doing in any way; I just wish they'd push bug fixes on a quicker-schedule.
I hope I didn't come off too aggressive.

All worked for me after upgrading to npm 5.3. Can anyone else confirm please?

Upgrading to<EMAIL_ADDRESS>solves the problem.

Upgrade to npm v5.3.0 didin't work for me, I had to switch to yarn


[snapshot] Make sure matched window has a non-empty frame

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

When finding a window to call screenshot() on, the provided code in SnapshotHelper.swift doesn't ensure that said window has a non-empty frame. This results in the call to screenshot() raising the following error: Element Window cannot request screenshot data because it has an empty frame SnapshotHelper.swift:164

This change solves https://github.com/fastlane/fastlane/issues/12140.

SnapshotHelper.swift does not appear to be tested at all. My apologies if this is the case and I just missed it.
Description

Rather than using firstMatch on app.windows, we make sure that the selected window has a non-empty frame by using allElementsBoundByIndex.first(where: { $0.frame.isEmpty == false }).

@googlebot I signed it!

You would have to increase the version in the file in the last line to get this merged and released (1.9 => 1.10).

Oh, I guess our version regex doesn't support two-digit version numbers

Thanks for the PR @sirdharma 👍


change a js file content

Hi @twitchax
How can I change content a js file and load proxy url
I mean when user open https://example.com and I proxy him to https://example2.com How can I change a js file in https://example2.com
Thanks

Hello!  You will need to use the WithAfterReceive hook.  Essentially, you have access to the entire proxied response before it goes back down to the client.  You can edit any part of the headers or content as you wish.
From the README:
.WithAfterReceive((c, hrm) =>
        {
            // Alter the content in  some way before sending back to client.
            var newContent = new StringContent("It's all greek...er, Latin...to me!");
            hrm.Content = newContent;

            return Task.CompletedTask;
        })


usb_device_phdc.h instead of usb_function_phdc.h

In usb_device_phdc.c#L32, the usb_function_phdc.h does not exist.
Maybe it should be usb_device_phdc.h ?

Same for usb_device_ccid.c#L25


Allow more developer commands with HOMEBREW_INSTALL_FROM_API

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This PR modifies the handling of developer commands with HOMEBREW_INSTALL_FROM_API. I've vetted every developer command and separated those that will still work with HOMEBREW_INSTALL_FROM_API set so that only those are forbidden. This means that developers can have it set and still run things like brew irb, brew style, brew typecheck, brew pr-automerge, etc.
The list mostly comes from this comment with the only changes being that brew pr-automerge and brew unbottled both seem to work with HOMEBREW_INSTALL_FROM_API even though they weren't on that list.
I also added a check in brew install and brew reinstall to make sure that you can't pass --build-from-source as this isn't currently supported (and likely won't be).

Review period will end on 2022-06-20 at 01:42:50 UTC.

I also added a check in brew install and brew reinstall to make sure that you can't pass --build-from-source as this isn't currently supported (and likely won't be).

It's worth noting this isn't the only scenario a build from source can occur. For example, it can for non-default prefixes and legacy macOS versions. So we might have to think about that at some point.

Could also be a relevant question for post-installs unless we can make old formulae readable or tell people to upload new bottles for post-install changes (we currently don't).

Review period skipped due to critical label.


Support for a single worker pool with min=0

How to categorize this issue?
/area control-plane
/kind discussion
What happened:
DWD only interacts with shoot control plane components apart from a Cluster resource. For writing integration tests for DWD we only need a seed with the control plane of a shoot under test. There is no need to spin up worker nodes. Currently there is a limitation being enforced wherein if there is a single worker pool created for the cluster, then workers.minimum cannot be 0 it has to be a minimum of 1. However, if more than 1 worker pool is there then barring 1, rest all of the worker pools can have workers.minimum set to 0.
What you expected to happen:
I wish to have an ability to only have a shoot control plane being provisioned and have the worker provisioning as optional. This could be achieved if the current constraint of having workers.minimum=1 for a single worker pool  is relaxed and allows it to be 0. Then, using test machinery one could only provision a shoot control plane without provisioning a worker which not only takes time but also adds unnecessary cost as this worker will be quite useless from the perspective of the tests.
What were the reasons for having this constraint?

If you are only concerned about testing, it is probably more sensible to simply use provider-local for e2e tests of dependency-watchdog.
You could take a look at https://github.com/gardener/gardener/blob/master/hack/test-e2e-local.sh, https://github.com/gardener/gardener-extension-shoot-oidc-service/blob/master/hack/test-e2e-provider-local.sh and https://github.com/gardener/ci-infra/blob/master/config/jobs/extension-shoot-oidc-service/extension-shoot-oidc-service-e2e-kind.yaml.

Currently testing is the scope. I wait for https://github.com/gardener/gardener/pull/5937 to be merged so that KIND cluster supports DWD prober. Once that is merged then it would definitely be sensible to use the KIND cluster instead of test machinery as DWD does not interact or need worker machines.
Thanks for the links - i think this was also presented in the last core weekly review meeting and i also made a note of it.
@vlerenc  also mentioned that vasu requested for "control plane as a service" feature, so i opened this issue to understand why the current constraint has been put and whether there are use cases where control-plan only would be useful.

@unmarshall This is the ticket that was opened back then: https://github.com/gardener/gardener/issues/1907
It was opened by @vpnachev, but I "think" @vasu1124 brought it up some time before, though I am not sure anymore.

Currently testing is the scope. I wait for #5937 to be merged so that KIND cluster supports DWD prober. Once that is merged then it would definitely be sensible to use the KIND cluster instead of test machinery as DWD does not interact or need worker machines. Thanks for the links - i think this was also presented in the last core weekly review meeting and i also made a note of it.

https://github.com/gardener/gardener/pull/5937 is merged now. So I think, we can
/close
this issue.

@unmarshall if you are interested in running a Kubernetes control plane in your cluster you could use the following project from the @onmetal team: https://github.com/onmetal/matryoshka
It allows you to deploy the kube-apiserver and kube-controller-manager via CRs into your cluster. You can find the sample manifest here: https://github.com/onmetal/matryoshka/tree/main/config/samples
Together with the cert-manager and Gardener's etcd-druid operator you can spin up relatively quickly a fully functional headless Kubernetes with automatic backup and restore (via etcd-druid) and certificate creation/rotation via the cert-manager.
/cc @adracus @vasu1124


c11_atomics: align signedness of host types

Some HOST_ types were declared with signedness different from the HOST_ATOMIC_ counterparts, leading to sign-compare warnings when comparing between types.  Fix by aligning the signedness.

Merging as discussed on the November 14th teleconference.


Cannot count the previous peers

Hi,
Please try opening this link in 2 tabs: http://tv.vnoo.net/livetv/vh1/vh1.html
and open Network panel

When PeerConnect is triggered, you can see tab 1 report that have 1 device is paired, but in the tab 2 is not.
TAB1:

TAB2:

        engine.on(p2pml.core.Events.PeerConnect, function(peer){
            mem_peers.push(peer);
            console.log(peer);
        });

        //show the count devices in the update View function (has setInterval function in there):
        var total_peers = mem_peers.length;
        network_views.innerHTML = total_peers + (total_peers > 1 ? " devices" : " device");

It's caused by my wrong code or it's a bug?
Thanks,

Most like you set the event handler after the peer is already connected.
And another advice - the stream will not share well over P2P because it has only 3 segments in the playlist.
Consider having 20 segments with 4-10 seconds duration for best P2P performance.

P.S>
engine.on(p2pml.core.Events.PeerConnect, function() {console.log("CONNECTED");});engine.on(p2pml.core.Events.PeerClose, function() {console.log("CLOSED");});

I run the code directly in the browser's console right after the page loads and engine object exists. I see CONNECTED message but your network panel still shows 0 peers, while the peer is actually connected.

Most like you set the event handler after the peer is already connected.
And another advice - the stream will not share well over P2P because it has only 3 segments in the playlist.
Consider having 20 segments with 4-10 seconds duration for best P2P performance.

Does it cause delay? I mean latency. 20 segments with 3 seconds duration for Live stream

Yes. But is up to you to choose between shorter delay and better P2P ratio


Pie Charts

What can we do to make ScottPlot better?
A new Pie Chart plottable:

var pieChart = plt.PlotPie(proportions, labels);

Check the ScottPlot Roadmap to see if your feature is already planned for an upcoming release:
https://github.com/swharden/ScottPlot/blob/master/dev/roadmap.md

This would be awesome if you want to give it a stab!
This might be a little more straightforward than the heatmap (#420)

#423

Pie charts will be in ScottPlot 4.0.35, thanks @Benny121221!


Table data update

I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request

Current behavior
When updating data, the cells update only when clicking on them (blur), not when the data changes. This worked well in 0.11.2.
Expected behavior
Table updates, when data updates.
Reproduction of the problem
Just change some data in the background (e.g. button click) and then click the cell that was supposed to reflect the change. The cell updates only on click.
What is the motivation / use case for changing the behavior?
To see the updated data.

Table version: 1.0.0

Angular version: 2.1.1

Browser: [Chrome 54 ]

This is a side effect of the OnPush change detection strategy. See: https://swimlane.gitbooks.io/angular2-data-table/content/introduction/architecture.html#onpush for more info.

Oh, ok thanks.

So how do I update the table now? I read the article, but it is still not clear to me.

@nirhu  you can do row = row.slice() to force change the reference of row if it is modified in place.


Add support for nbqa for Jupyter Notebooks

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Super Linter cannot lint Jupyter Notebooks
Expected Behavior
Super Linter can perform linting on Jupyter Notebooks.
nbqa is a tool that adds compatibility of Python linters for Jupyter notebooks
Anything else?
No response

This is an interesting proposal. We'll happily review PRs about this.
Thanks for taking the time to send this idea!


applicationinsights package incompatibilities with ESM

Package Name:  applicationinsights
Package Version:  3.1.0
Operating system: Doesn't matter
[x] nodejs

version: 20

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
applicationinsights doesn't work properly in ESM environment
To Reproduce
Steps to reproduce the behavior:

Set "type": "module", in package.json
Addimport { setup, defaultClient } from 'applicationinsights';
setup().start();

console.log(defaultClient);

Run the app and check the console output, defaultClient would be undefined.

Expected behavior
defaultClient should be fulfilled
Additional context
This happened because of the differences how native ESM and transpiled to CJS modules works.
If you look to the entry point of the 'applicationinsights' package you will see:
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });

exports.dispose =
  exports.TelemetryClient =
    exports.DistributedTracingModes =
      exports.Contracts = exports.defaultClient =
        exports.Configuration = exports.wrapWithCorrelationContext =
          exports.startOperation = exports.getCorrelationContext = exports.start = exports.setup = void 0;

var applicationinsights_1 = require("./src/shim/applicationinsights");
Object.defineProperty(exports, "setup", { enumerable: true, get: function () { return applicationinsights_1.setup; } });
Object.defineProperty(exports, "defaultClient", { enumerable: true, get: function () { return applicationinsights_1.defaultClient; } });
// ... other exports

When this package would be requested in CJS context, those getters would be invoked only when user's code will actually access them, but in ESM context, ESM loader enumerate all properties which are exported from the package and save  result internally, so getter for defaultClient is executed only once and before this client ever initialized.
There is no simple way to fix this, other than don't use late-binding at all. So instead of  defaultClient expose a function getDefaultClient()
To workaround the issue, i created a cjs file which is called from my ESM modules with the following content:
// telemetry.cjs
const applicationinsights = require('applicationinsights');
applicationinsights.setup().start();

module.exports = {
  telemetryClient: applicationinsights.defaultClient
}

@thekip thanks for reporting the issue! The applicationinsights package is maintained in another GitHub repository https://github.com/microsoft/ApplicationInsights-node.js.  Could you please log an issue there instead? I was unable to transfer the issue.

Sure, https://github.com/microsoft/ApplicationInsights-node.js/issues/1354


Prevent race condition when tracking starts

There's a race condition when the tracking alert is received by the automator and coordinator.
The coordinator checks if recording is enabled. If it is, it disables recording and instructs the DAQs to record. There is a short gap of a few hundred milliseconds before the DAQs respond to the Redis messages and start recording.
The automator runs maybe_start_recording() on every incoming alerts message. That means it also checks if recording should be enabled when the tracking alert is received. In at least one occasion, this check was performed in the gap between when the coordinator disabled recording and when recording started (example logs below). The automator, seeing that the DAQs were not currently recording, and that rec_enabled was 0, re-enabled recording in this gap.
The result was that no processing took place when the timer ran out, since the automator saw that recording was still enabled and therefore did not process. In addition, we later on recorded another track, probably completely filling the NVMe drives and causing the DAQs to have issues.
To fix this, I think we should not call maybe_start_recording() when a tracking message is received. I also think we should call maybe_start_recording() after processing is complete, to re-enable recording for the next track right away.
Example logs:
coordinator:
[2023-05-11 01:18:47,529 - INFO - redis_util.py:83] rec_setting 1, setting to 0
...
[2023-05-11 01:18:47,697 - INFO - coordinator.py:931] Published PKTSTART=46353408 to channel bluse:array_1///set
...
[2023-05-11 02:20:28,966 - INFO - redis_util.py:83] rec_setting 1, setting to 0

automator:
[2023-05-11 01:16:23,828 - INFO - redis_util.py:75] rec_setting 0, setting to 1
...
[2023-05-11 01:18:47,481 - INFO - automator.py:124] subarray array_1 is now in state: tracking
...
[2023-05-11 01:18:47,640 - INFO - redis_util.py:75] rec_setting 0, setting to 1
...
[2023-05-11 02:20:18,675 - INFO - automator.py:124] subarray array_1 is now in state: tracking

I don't think it's the right fix to alter when exactly maybe_start_recording is called. The contract of maybe_start_recording is that it can be called at any time, and it will do the right thing. If you change the contract to "it can be called at any time, except in the period of time between event X and event Y happening", then you have an opportunity for bugs at any point that maybe_start_recording is called. Including times like on startup, where you can't possibly avoid these bugs.
Instead, I think the right fix is to make it so that maybe_start_recording doesn't try to start recording when the system is already in the "recording state". Something like:

write a method that returns what state the system is currently in, whether it is "recording", or "processing", or "idle", whatever you ended up calling these states in the flow chart that you want to be the official one. if the flow chart is going to be an accurate depiction of the system, then we really should have a way to determine what the current state is, right?

make sure this method is correct in the situation where we currently have this race condition bug

use this method instead of the "is_rec_enabled" call to determine whether we should start processing

I should be more specific - I think it's okay to add more calls to maybe_start_recording in order to make things transition faster. The part I don't think is okay is to solve a bug where maybe_start_recording starts recording when it shouldn't, by just not calling maybe_start_recording at that point.

I agree with your recommendations and am thinking about the best way to make these (and other) changes. In the meantime, I've made some changes to the coordinator such that maybe_start_recording can be called without having to cater for special cases. After the coordinator instructs the DAQs to start recording, it checks to ensure that they have actually started recording before disabling subsequent recordings. So maybe_start_recording can be called without fear of a race condition.
This is just for now, I agree with removing the rec_enabled key.


Add SVG diagrams

Add main diagrams for white background as SVG. All diagrams have been exported from Excalidraw.
Added diagrams per type

primitive
fixed-size string
variable string
variable string view
fixed-size list
variable-size list
variable-size list view
struct
dictionary

Ready for review =)

Can you also add a combined file? (can be the mermaid specific file format, or a single svg, as long as it is something that allows you to open and edit all figures together?)

cc @amoeba

Let's already merge this so it is easier to go forward with the other PRs, we can further tweak the figures if needed in follow-ups
Thanks @AlenkaF!


Terminal stops when "/dev/console" is selected

Behavior when an executable file is selected is not taken into account

https://github.com/dijdzv/easychangedirectory/blob/f14e377fde344f43cbdd7c9a24e5cc0edb9c63bd/src/app/item/_item.rs#L49 で

I can't predict what will happen when I read the executable file with fs::read_to_string.
https://github.com/dijdzv/easychangedirectory/blob/f14e377fde344f43cbdd7c9a24e5cc0edb9c63bd/src/app/item/_item.rs#L48
We need to eliminate executables here.


[Election contract] change schema type of byte registrations to hex strings

Description
To improve the experience when submitting ballots through the voting app (and also view contract state for debugging), it would be useful to represent byte arrays registered in the contract as hex strings.

[x] Ballot submissions
[ ] Guardian public key registration
[ ] Guardian encrypted shares registration
[ ] Guardian decryption share registration
[ ] Guardian decryption proof registration

Reopened this as only the ballot submission had the schema type added to represent the associated byte array as hex. The rest are not as critical, as users will not be exposed to them.

I would argue we should just close this. I don't see any point in spending time on making something that is not exposed to users from one incomprehensible representation to another.


Dead "restricted" links cant be regenerated

When a torrent finishes downloading, RealDebrid generates restricted links that first need to be unrestricted to get access to the files.
Working restricted links that havent been unrestricted yet, or their unrestricted link has been removed after one week, will automatically be unrestricted by rclone.
Sometimes though, a restricted link might become broken on RealDebrids servers. When opening a file with a broken link this rather large error is produced:
> failed to open source: 404 Not Found (404): <!DOCTYPE html>
> <!--[if IE 8]> <html lang="en" class="ie8"> <![endif]-->
> <!--[if IE 9]> <html lang="en" class="ie9"> <![endif]-->
> <!--[if !IE]><!--> <html lang="en"> <!--<![endif]-->
>
> [Large HTML page here]
>
> <!-- a padding to disable MSIE and Chrome friendly error page -->
> <!-- a padding to disable MSIE and Chrome friendly error page -->
> <!-- a padding to disable MSIE and Chrome friendly error page -->

Rclone cant determine when a restricted link breaks, and cant regenerate this broken restricted link since that would entail the following: re-downloading the torrent, determining all cached files, selecting all cached files and regenerating the unrestricted links - all within the Open() function that is called multiple times in parrallel.
Im not sure how to solve this.

Could be possible, Im kind of waiting on realdebrid to finish their webdav implementation at the moment. When they say theyre done, i'll check it out again and see if I can write some improvements into rclone :)
One possibility could be to remove the torrent and have plex_debrid simply download it again.

Will close this as the issue is being continued in #14


Question: How to pass tuples with dicts?

I'm trying to pass a list (of one) tuple that has a dict with some values to a function that just passes the input arg back. Empty dicts work, but populated dicts do not (aware of mutability nuances):
def do_something(row):
    return row

tups = [('STOCK', {'opens': [99, 100], 'closes': [100, 101]})]

c = Context(webui=False)
out = c.parallelize(tups).map(do_something).collect()

Error:
File "/usr/local/lib64/python3.9/site-packages/tuplex/context.py", line 163, in parallelize
    ds._dataSet = self._context.parallelize(value_list, columns, schema)
IndexError: map::at

Is there a better way to do this?

out = c.parallelize(tups, schema=(str, Dict[str, List[int]])).map(do_something).collect()

Results:
[2021-07-23 15:20:29.128] [local execution engine] [info] started local executor E/8 (1.00 GB, 32.00 MB default partition size)
[2021-07-23 15:20:29.140] [memory] [info] allocated bitmap managed memory region (1.00 GB, 32.00 MB block size)
[2021-07-23 15:20:29.140] [local execution engine] [info] started driver (1.00 GB, 32.00 MB default partition size)
[2021-07-23 15:20:29.128] [E/6] [info] starting detached process queue
[2021-07-23 15:20:29.159] [E/6] [info] initialized runtime memory (4.00 MB)
[2021-07-23 15:20:29.536] [python] [info] transferring 1 elements to tuplex

Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

Though this (replacing py < 3.9 Dict with built-in type dict):
out = c.parallelize(tups, schema=(str, dict[str, List[int]])).map(do_something).collect()

Results:
File "/usr/local/lib64/python3.9/site-packages/tuplex/context.py", line 163, in parallelize
    ds._dataSet = self._context.parallelize(value_list, columns, schema)
RuntimeError: you submitted an empty list to be parallelized. Any pipeline transforming this list will yield an empty list! Aborting here.

Using tuples instead of lists:
tups = [('STOCK', {'opens': (99, 100), 'closes': (100, 101)})]

out = c.parallelize(tups, schema=(str, dict[str, tuple[int, ...]])).map(do_something).collect()

Results:
 File "/usr/local/lib64/python3.9/site-packages/tuplex/context.py", line 163, in parallelize
    ds._dataSet = self._context.parallelize(value_list, columns, schema)
RuntimeError: you submitted an empty list to be parallelized. Any pipeline transforming this list will yield an empty list! Aborting here.

Using all tuples:
tups = [('STOCK', ('opens', (99, 100)), ('closes', (100, 101)))]

out = c.parallelize(tups, schema=(str, tuple[str, tuple[int, ...]], tuple[str, tuple[int, ...]])).map(do_something).collect()

Results:
File "/usr/local/lib64/python3.9/site-packages/tuplex/context.py", line 163, in parallelize
    ds._dataSet = self._context.parallelize(value_list, columns, schema)
RuntimeError: you submitted an empty list to be parallelized. Any pipeline transforming this list will yield an empty list! Aborting here.

What's the correct way? Is this possible?

Thanks for bringing this up! We're currently working on adding better dictionary support. Hopefully, this feature will be merged within the next weeks.

@LeonhardFS I'm hoping to have some more time to take a look at any additions to tuplex in the next day or so. Has any of the dictionary work been merged yet by chance?


Scaffolded project is broken

As discovered in https://kubernetes.slack.com/archives/C0181L6JYQ2/p1716234751101299 the hybrid plugin successfully scaffolds an operator project but it is not functional. We need to identify the issues and fix them before a new release is cut.
Additionally, we should add e2e test to verify that the scaffolded projects are functional.
Additional findings related to this can/should be added as a comment or by updating this description.

Just for ease of discovery, copying our existing findings here.
In testdata/hybrid/memcached-operator/

[ ] Dockerfile Go builder base image is incompatible with go.mod
[ ] make install fails. It assumes there will be a config/crd/kustomization.yaml file and there is not one.

Manually fixing these two things allows me to make docker-build, load the image into the kind cluster, and then make install deploy successfully. After that, I see that the controller deployment startup successfully.


SvelteWrapper plugin does not render

Example shows the error, in the console:
"[Grid.js] [ERROR]: Duplicate plugin ID: email"
Error: Component is not a constructor
message: "Component is not a constructor"
stack: "TypeError: Component is not a constructor…"

Is the plugin broken or maybe the example just needs to be updated?

Having the same issue too:

Running locally gives the error Component is not a constructor   at SvelteWrapper.componentDidMount (plugins.js:13:25)
Running the official example to run a Svelte component in cell (at REPL), gives 2 errors:

"[Grid.js] [ERROR]: Duplicate plugin ID: email"

and
Error: Component is not a constructor
message: "Component is not a constructor"
stack: "TypeError: Component is not a constructor\n" +
" at SvelteWrapper.componentDidMount (eval at handle_message (about:srcdoc:14:8), <anonymous>:895:29)\n" +
" at eval (eval at handle_message (about:srcdoc:14:8), <anonymous>:471:8380)\n" +
" at Array.some (<anonymous>)\n" +
" at eval (eval at handle_message (about:srcdoc:14:8), <anonymous>:471:8361)\n" +
" at Array.some (<anonymous>)\n" +
" at O (eval at handle_message (about:srcdoc:14:8), <anonymous>:471:8321)\n" +
" at eval (eval at handle_message (about:srcdoc:14:8), <anonymous>:471:3683)\n" +
" at Array.some (<anonymous>)\n" +
" at I (eval at handle_message (about:srcdoc:14:8), <anonymous>:471:3495)"

I'm not sure why yet...

Has someone found a solution or workaround for this already?

As a workaround I downgraded gridjs to version 5.1.0.
npm install<EMAIL_ADDRESS>
Thanks, it's working


There should have an explanation about colors and line numbers on the readme, gh-pages or on the report itself

Related to #111: What do the colors and the line numbers means?

So the meaning of the colors are explained on comments on this issue. But one might not know what do the numbers means (51, 18, 45 on the image above).
I think it should be on the README, on the gh-pages branch or on the report itself.
Thanks.

If your mouse cursor hovers around the colored area, there is a tool tip describing the meaning.
But I do agree, the color coding needs to be embedded in the report itself.

there is a tool tip describing the meaning

Devs, you should put a legend of some sort on the index.html page. I had to come here to figure out what the I and E etc means.


Adding iptables fix for issue with kube-proxy

kube-proxy requries an iptables chain created by kubelet.
This is intended to be a stop-gap until we can do the necessary work to run kubelet on the masters.

Please link to lp bug.

https://bugs.launchpad.net/charm-kubernetes-master/+bug/1831845


Allow resources to be created in controller namespace

This change allows the Terraform task pod and other resources to be created in the namespace that the controller is running in.
This should address #173.

This is great. I understand the security implication here. And I really appreciate the time and effort in this PR!
One question, shouldn't the controller be namespaced in such a way so that is only watches and acts on a single namespace?  I feel a namespaced controller is really the heart of the conversation. If the controller is limited to a namespace, it should not create, or even be aware, of resources outside of its own namespace.  Instead, namespace the controller, and  add more controllers where TF resources need to be.
I personally use the tf-operator in a larger platform and name-spacing is a little harder to manage, but I can definitely see why it would be appealing.
I love the helper functions and the label prefix, these were much needed improvements! But what do you think of having the option to make the controller "namespace" aware instead or forcing all the tasks into a namespace?

I have to refresh my memory on this, but I think the motivation for this is that my organization's policy was restricting cluster-scoped access to resources like Secrets and ConfigMaps, which is a security concern to grant at a wide scope, but it was not a security concern to grant cluster-scoped access to CRDs owned by a controller.
The deployment scenario that this change was supposed to enable is one where a particular service owner in a multi-tenant cluster would have its own namespace (separate from the Terraform controller), and would be able to make the Terraform controller provision resources on its behalf by creating a Terraform CR in its own namespace.


Change default limit of 'pagination_item'

Hi,
Can we customize the default limit of 'pagination_item', like set it to 200, 300, all..? If yes please share how it can be done. Thanks!
If this is not the right way/place/page  to ask questions and improvements please move this thread to correct page and share the link for the same.

Hello @jeevantm!
Can you explain why you want to change the default?
In any script you can do:
options = TSC.RequestOptions(pagenumber=300)

Or better yet, use Pager:
for item in TSC.Pager(server.workbooks):
    ...

And let pager manage the paging for you.

Closing out old issues.  @t8y8 's response seems reasonable.

Hi,
I am sorry I'm commenting on this after long time, but the TSC.Pager doesn't seem to work properly with RequestOptions.
I have set request_options = TSC.RequestOptions(pagesize=1000) and when I do -
for schedule in TSC.Pager(server.schedules, request_options), although I have less than 1000 schedules but more than 500 schedules (622 to be precise), it doesn't give all schedules in a single page. It returns less than 500 schedules instead of 622.
Could you please check why. Many thanks!

What happens when you set the request options to 1000 and don't use pager?
I'll review the pager code, but it's pretty old and baked, my guess is that schedules might have an issue on the Server side.

Hi,
I am using RequestOptions(pagesize=1000) in TSC.Pager(server.schedules, request_options) and I receive the below error -
400006: Bad Request
Invalid page number '2'
In my case there are less than 1000 objects to return, why is it even going to page number 2 even if I gave the pagesize to be 1000.
Thanks for your help!


feat: CCode component

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes
/start features)

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

What is the new behavior?

Introduced c-code component
Added c-code examples
Added c-code documentation

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information / questions

This is my first PR to the library, I like using the React library and I wanted to see the Vue library grow as well. I am looking forward to contributing more and more, this is just a start. 😃

Regarding the CHANGELOG.md I was unable to run the command yarn changeset or yarn release and referring to the CBadge #22 I didn't see any commits regarding that file.
I know there might be with my code, I hope you can excuse this and I will work on improving it as I move on.
I wasn't sure about the documentation props table, the Markdown preview on VSCode wasn't accurate about the table I am assuming the documentation website has its own parser for the tables. If not let me know and I can work on changing the documentation again.

Hey @codebender828 I just made the changes you requested I followed your recommendations for all of them. But for the test case I removed c-code-color.test.ts and instead added all of the variants to the c-code.test.ts I hope that is fine since there isn't much of a difference.
About the running the yarn changeset command I had the following error. Have you ever experienced this previously?
🦋  error Error: Failed to find where HEAD diverged from master. Does master exist?
🦋  error     at getDivergedCommit (user/chakra-ui-vue-next/node_modules/@changesets/git/dist/git.cjs.dev.js:58:11)
🦋  error     at async getChangedFilesSince (user/chakra-ui-vue-next/node_modules/@changesets/git/dist/git.cjs.dev.js:169:22)
🦋  error     at async Object.getChangedPackagesSinceRef (user/chakra-ui-vue-next/node_modules/@changesets/git/dist/git.cjs.dev.js:208:24)
🦋  error     at async add (user/chakra-ui-vue-next/node_modules/@changesets/cli/dist/cli.cjs.dev.js:409:29)
🦋  error     at async run$1 (user/chakra-ui-vue-next/node_modules/@changesets/cli/dist/cli.cjs.dev.js:1096:5)
error Command failed with exit code 1.

I couldn't find much when searching it as well. All I found was this issue, do you think it could be an issue about how my forked repo manages it's remote HEAD? Here is my branch list (git branch -a) :
  develop
* feat/c-code
  remotes/origin/HEAD -> origin/develop

I will also make sure to ask about the changeset issue in discord!

I closed this because I had to recreate the branch.

Hi @danielcnascimento
What workaround are you looking for ? This PR was about the CCode component, which is currently available in the alpha version.

Hey @Shyrro
Glad to talk to you,
I'm facing the same problem with changeset, i would like to know what was the workaround for him, because he didn't mention it in the thread.


[BEAM-XXX] Fix minor typo in big_query_file_loads.py

Fixed a very minor typo in big_query_file_loads.py

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Run Python PreCommit

R: @pabloem

Thanks Tanay! this is grea.


Coverity fixes

TODO: Verify that co-verity no longer renders these issues in the UI. Currently showing that I marked the 4 issues as false positive.

The fix head for coverity_scan was on this build: https://travis-ci.org/01org/tpm2.0-tools/builds/252944097
That build didn't upload due to bootstrap not being done and ./configure failing. Uploaded new head to coverity_scan.

Verified that coverity shows 0 defects on version: d2c6a1f