Enhance compressed image tarball logging

Is your feature request related to a problem? Please describe.
Related to: https://github.com/rancher/k3s/issues/2145#issuecomment-689656848
Describe the solution you'd like

Add logs at INFO level for every file encountered in the images drop-in directory and indicate whether they will be skipped or processed.
When processing files we should not assume that we own anything we encounter. This means that we may need to setup a k3s-local data directory for recording the hashes of tarballs we have successfully processed (to prevent re-processing at every start)

Describe alternatives you've considered
N/A
Additional context
These are additional user-enhancements to supply operators with more information on what is happening during k3s startup, and save time and system power when a potential restart happens.

@rancher-max would you be able to re-validate to see if this still needs to be changed

I quickly checked a tarball airgap setup I have using v1.21.3 and still do not see any logs at INFO level mentioning the encountered files in the images dir.
For the second part of this issue, I'm not entirely sure, although we still do not have a k3s-local data dir configured so it seems this is still occurring as well.

It tells you what it's importing and from where, do you not have these lines?
time="2021-07-29T12:34:03.470068895-07:00" level=info msg="Importing images from /var/lib/rancher/k3s/agent/images/k3s-airgap-images-amd64.tar.zst"
time="2021-07-29T12:34:09.536074627-07:00" level=info msg="Imported docker.io/rancher/pause:3.1"
time="2021-07-29T12:34:09.536095116-07:00" level=info msg="Imported docker.io/rancher/coredns-coredns:1.8.3"
time="2021-07-29T12:34:09.536106757-07:00" level=info msg="Imported docker.io/rancher/klipper-helm:v0.6.1-build20210616"
time="2021-07-29T12:34:09.536115824-07:00" level=info msg="Imported docker.io/rancher/klipper-lb:v0.2.0"
time="2021-07-29T12:34:09.536133958-07:00" level=info msg="Imported docker.io/rancher/library-busybox:1.32.1"
time="2021-07-29T12:34:09.536142825-07:00" level=info msg="Imported docker.io/rancher/library-traefik:2.4.8"
time="2021-07-29T12:34:09.536154257-07:00" level=info msg="Imported docker.io/rancher/local-path-provisioner:v0.0.19"
time="2021-07-29T12:34:09.536162452-07:00" level=info msg="Imported docker.io/rancher/metrics-server:v0.3.6"

Hmmmm, I do, but they are buried. See snippet of my logs below that contains all of that if you search for "Import".
That said, I've noticed those logs you posted before, and my logs being less dirty before. This could be due to my setup being uninstalled and reinstalled a few times with different versions. Given that, I'm actually personally okay with closing this issue out.
# k3s server 2>&1 &
[1] 27170
root@ip-172-31-5-153:~# INFO[0000] Acquiring lock file /var/lib/rancher/k3s/data/.lock
INFO[0000] Preparing data dir /var/lib/rancher/k3s/data/9df574741d2573cbbe6616e8624488b36b3340d077bc50da7cb167f1b08a64d1
INFO[2021-07-29T18:34:54.438866947Z] Starting k3s v1.21.3+k3s1 (1d1f220f)
INFO[2021-07-29T18:34:54.447291800Z] Configuring sqlite3 database connection pooling: maxIdleConns=2, maxOpenConns=0, connMaxLifetime=0s
INFO[2021-07-29T18:34:54.447365451Z] Configuring database table schema and indexes, this may take a moment...
INFO[2021-07-29T18:34:54.450726615Z] Database tables and indexes are up to date
INFO[2021-07-29T18:34:54.453256075Z] Kine listening on unix://kine.sock
INFO[2021-07-29T18:34:54.467891810Z] certificate CN=system:admin,O=system:masters signed by CN=k3s-client-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.468766822Z] certificate CN=system:kube-controller-manager signed by CN=k3s-client-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.469580073Z] certificate CN=system:kube-scheduler signed by CN=k3s-client-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.470439832Z] certificate CN=kube-apiserver signed by CN=k3s-client-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.471347029Z] certificate CN=system:kube-proxy signed by CN=k3s-client-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.472162711Z] certificate CN=system:k3s-controller signed by CN=k3s-client-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.473005007Z] certificate CN=k3s-cloud-controller-manager signed by CN=k3s-client-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.474400387Z] certificate CN=kube-apiserver signed by CN=k3s-server-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.475582564Z] certificate CN=system:auth-proxy signed by CN=k3s-request-header-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.476774103Z] certificate CN=etcd-server signed by CN=etcd-server-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.477547469Z] certificate CN=etcd-client signed by CN=etcd-server-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.478640593Z] certificate CN=etcd-peer signed by CN=etcd-peer-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.840487960Z] certificate CN=k3s,O=k3s signed by CN=k3s-server-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:54 +0000 UTC
INFO[2021-07-29T18:34:54.841188045Z] 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-kubernetes:kubernetes listener.cattle.io/cn-kubernetes.default:kubernetes.default listener.cattle.io/cn-kubernetes.default.svc:kubernetes.default.svc listener.cattle.io/cn-kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local listener.cattle.io/cn-localhost:localhost listener.cattle.io/fingerprint:SHA1=B05F40177D8FFF8DF3C6B69267C8D94ADFCD845E]
INFO[2021-07-29T18:34:54.850288200Z] Running kube-apiserver --advertise-port=6443 --allow-privileged=true --anonymous-auth=false --api-audiences=https://kubernetes.default.svc.cluster.local,k3s --authorization-mode=Node,RBAC --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 --profiling=false --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=https://kubernetes.default.svc.cluster.local --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 --service-node-port-range=30000-32767 --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 --insecure-port has been deprecated, This flag has no effect now and will be removed in v1.24.
I0729 18:34:54.851816   27170 server.go:656] external host was not specified, using <IP_ADDRESS>
I0729 18:34:54.852134   27170 server.go:195] Version: v1.21.3+k3s1
INFO[2021-07-29T18:34:55.116685099Z] Cluster-Http-Server 2021/07/29 18:34:55 http: TLS handshake error from <IP_ADDRESS>:45326: remote error: tls: bad certificate
I0729 18:34:55.555751   27170 shared_informer.go:240] Waiting for caches to sync for node_authorizer
I0729 18:34:55.559447   27170 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.
I0729 18:34:55.559634   27170 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
I0729 18:34:55.564192   27170 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.
I0729 18:34:55.564397   27170 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
I0729 18:34:55.595855   27170 instance.go:283] Using reconciler: lease
I0729 18:34:55.700355   27170 rest.go:130] the default service ipfamily for this cluster is: IPv4
W0729 18:34:56.309678   27170 genericapiserver.go:425] Skipping API node.k8s.io/v1alpha1 because it has no resources.
W0729 18:34:56.322369   27170 genericapiserver.go:425] Skipping API rbac.authorization.k8s.io/v1alpha1 because it has no resources.
W0729 18:34:56.327207   27170 genericapiserver.go:425] Skipping API scheduling.k8s.io/v1alpha1 because it has no resources.
W0729 18:34:56.334964   27170 genericapiserver.go:425] Skipping API storage.k8s.io/v1alpha1 because it has no resources.
W0729 18:34:56.338302   27170 genericapiserver.go:425] Skipping API flowcontrol.apiserver.k8s.io/v1alpha1 because it has no resources.
W0729 18:34:56.344353   27170 genericapiserver.go:425] Skipping API apps/v1beta2 because it has no resources.
W0729 18:34:56.344417   27170 genericapiserver.go:425] Skipping API apps/v1beta1 because it has no resources.
I0729 18:34:56.357504   27170 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.
I0729 18:34:56.357556   27170 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
INFO[2021-07-29T18:34:56.374465186Z] Running kube-scheduler --address=<IP_ADDRESS> --bind-address=<IP_ADDRESS> --kubeconfig=/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig --leader-elect=false --port=10251 --profiling=false --secure-port=0
INFO[2021-07-29T18:34:56.375199056Z] Running kube-controller-manager --address=<IP_ADDRESS> --allocate-node-cidrs=true --bind-address=<IP_ADDRESS> --cluster-cidr=<IP_ADDRESS>/16 --cluster-signing-kube-apiserver-client-cert-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --cluster-signing-kube-apiserver-client-key-file=/var/lib/rancher/k3s/server/tls/client-ca.key --cluster-signing-kubelet-client-cert-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --cluster-signing-kubelet-client-key-file=/var/lib/rancher/k3s/server/tls/client-ca.key --cluster-signing-kubelet-serving-cert-file=/var/lib/rancher/k3s/server/tls/server-ca.crt --cluster-signing-kubelet-serving-key-file=/var/lib/rancher/k3s/server/tls/server-ca.key --cluster-signing-legacy-unknown-cert-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --cluster-signing-legacy-unknown-key-file=/var/lib/rancher/k3s/server/tls/client-ca.key --configure-cloud-routes=false --controllers=*,-service,-route,-cloud-node-lifecycle --kubeconfig=/var/lib/rancher/k3s/server/cred/controller.kubeconfig --leader-elect=false --port=10252 --profiling=false --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
INFO[2021-07-29T18:34:56.375867156Z] Running cloud-controller-manager --allocate-node-cidrs=true --bind-address=<IP_ADDRESS> --cloud-provider=k3s --cluster-cidr=<IP_ADDRESS>/16 --configure-cloud-routes=false --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect=false --node-status-update-frequency=1m0s --port=0 --profiling=false
INFO[2021-07-29T18:34:56.376870927Z] Node token is available at /var/lib/rancher/k3s/server/token
INFO[2021-07-29T18:34:56.376935986Z] To join node to cluster: k3s agent -s https://<IP_ADDRESS>:6443 -t ${NODE_TOKEN}
INFO[2021-07-29T18:34:56.378972892Z] Wrote kubeconfig /etc/rancher/k3s/k3s.yaml
INFO[2021-07-29T18:34:56.379014318Z] Run: k3s kubectl
INFO[2021-07-29T18:34:56.379445433Z] Waiting for API server to become available
INFO[2021-07-29T18:34:56.426267966Z] Cluster-Http-Server 2021/07/29 18:34:56 http: TLS handshake error from <IP_ADDRESS>:56428: remote error: tls: bad certificate
INFO[2021-07-29T18:34:56.431493920Z] Cluster-Http-Server 2021/07/29 18:34:56 http: TLS handshake error from <IP_ADDRESS>:56436: remote error: tls: bad certificate
INFO[2021-07-29T18:34:56.445753499Z] certificate CN=ip-172-31-5-153 signed by CN=k3s-server-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:56 +0000 UTC
INFO[2021-07-29T18:34:56.449622629Z] certificate CN=system:node:ip-172-31-5-153,O=system:nodes signed by CN=k3s-client-ca@1627583694: notBefore=2021-07-29 18:34:54 +0000 UTC notAfter=2022-07-29 18:34:56 +0000 UTC
INFO[2021-07-29T18:34:56.834037602Z] Module overlay was already loaded
INFO[2021-07-29T18:34:56.834071987Z] Module nf_conntrack was already loaded
INFO[2021-07-29T18:34:56.834084519Z] Module br_netfilter was already loaded
INFO[2021-07-29T18:34:56.834095640Z] Module iptable_nat was already loaded
INFO[2021-07-29T18:34:56.835961920Z] Logging containerd to /var/lib/rancher/k3s/agent/containerd/containerd.log
INFO[2021-07-29T18:34:56.836175082Z] 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
INFO[2021-07-29T18:34:57.185102451Z] Cluster-Http-Server 2021/07/29 18:34:57 http: TLS handshake error from <IP_ADDRESS>:45328: remote error: tls: bad certificate
INFO[2021-07-29T18:34:57.213595995Z] Cluster-Http-Server 2021/07/29 18:34:57 http: TLS handshake error from <IP_ADDRESS>:45332: remote error: tls: bad certificate
INFO[2021-07-29T18:34:57.600706452Z] Cluster-Http-Server 2021/07/29 18:34:57 http: TLS handshake error from <IP_ADDRESS>:56938: remote error: tls: bad certificate
INFO[2021-07-29T18:34:57.855885749Z] Containerd is now running
INFO[2021-07-29T18:34:57.862263645Z] Importing images from /var/lib/rancher/k3s/agent/images/k3s-airgap-images-amd64.tar
INFO[2021-07-29T18:34:58.321075347Z] Cluster-Http-Server 2021/07/29 18:34:58 http: TLS handshake error from <IP_ADDRESS>:45338: remote error: tls: bad certificate
I0729 18:35:00.928829   27170 secure_serving.go:197] Serving securely on <IP_ADDRESS>:6444
I0729 18:35:00.929099   27170 dynamic_cafile_content.go:167] Starting request-header::/var/lib/rancher/k3s/server/tls/request-header-ca.crt
I0729 18:35:00.929255   27170 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
I0729 18:35:00.929392   27170 tlsconfig.go:240] Starting DynamicServingCertificateController
I0729 18:35:00.930636   27170 controller.go:83] Starting OpenAPI AggregationController
I0729 18:35:00.941520   27170 apf_controller.go:294] Starting API Priority and Fairness config controller
I0729 18:35:00.941697   27170 available_controller.go:475] Starting AvailableConditionController
I0729 18:35:00.941819   27170 cache.go:32] Waiting for caches to sync for AvailableConditionController controller
I0729 18:35:00.941968   27170 autoregister_controller.go:141] Starting autoregister controller
I0729 18:35:00.942052   27170 cache.go:32] Waiting for caches to sync for autoregister controller
I0729 18:35:00.942393   27170 dynamic_serving_content.go:130] Starting aggregator-proxy-cert::/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt::/var/lib/rancher/k3s/server/tls/client-auth-proxy.key
I0729 18:35:00.943432   27170 apiservice_controller.go:97] Starting APIServiceRegistrationController
I0729 18:35:00.943509   27170 cache.go:32] Waiting for caches to sync for APIServiceRegistrationController controller
I0729 18:35:00.943852   27170 customresource_discovery_controller.go:209] Starting DiscoveryController
I0729 18:35:00.943965   27170 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/server/tls/client-ca.crt
I0729 18:35:00.971752   27170 crdregistration_controller.go:111] Starting crd-autoregister controller
I0729 18:35:00.971909   27170 shared_informer.go:240] Waiting for caches to sync for crd-autoregister
I0729 18:35:00.972381   27170 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/server/tls/client-ca.crt
I0729 18:35:00.972512   27170 dynamic_cafile_content.go:167] Starting request-header::/var/lib/rancher/k3s/server/tls/request-header-ca.crt
I0729 18:35:00.972639   27170 cluster_authentication_trust_controller.go:440] Starting cluster_authentication_trust_controller controller
I0729 18:35:00.972725   27170 shared_informer.go:240] Waiting for caches to sync for cluster_authentication_trust_controller
I0729 18:35:00.973108   27170 controller.go:86] Starting OpenAPI controller
I0729 18:35:00.973271   27170 naming_controller.go:291] Starting NamingConditionController
I0729 18:35:00.973411   27170 establishing_controller.go:76] Starting EstablishingController
I0729 18:35:00.973546   27170 nonstructuralschema_controller.go:192] Starting NonStructuralSchemaConditionController
I0729 18:35:00.973682   27170 apiapproval_controller.go:186] Starting KubernetesAPIApprovalPolicyConformantConditionController
I0729 18:35:00.973817   27170 crd_finalizer.go:266] Starting CRDFinalizer
I0729 18:35:01.047742   27170 apf_controller.go:299] Running API Priority and Fairness config worker
I0729 18:35:01.047921   27170 cache.go:39] Caches are synced for AvailableConditionController controller
I0729 18:35:01.048023   27170 cache.go:39] Caches are synced for autoregister controller
I0729 18:35:01.048448   27170 cache.go:39] Caches are synced for APIServiceRegistrationController controller
I0729 18:35:01.061309   27170 shared_informer.go:247] Caches are synced for node_authorizer
I0729 18:35:01.072159   27170 shared_informer.go:247] Caches are synced for crd-autoregister
I0729 18:35:01.085889   27170 shared_informer.go:247] Caches are synced for cluster_authentication_trust_controller
I0729 18:35:01.098495   27170 controller.go:611] quota admission added evaluator for: namespaces
E0729 18:35:01.185138   27170 controller.go:151] Unable to perform initial Kubernetes service initialization: Service "kubernetes" is invalid: spec.clusterIPs: Invalid value: []string{"<IP_ADDRESS>"}: failed to allocated ip:<IP_ADDRESS> with error:cannot allocate resources of type serviceipallocations at this time
E0729 18:35:01.199214   27170 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:
INFO[2021-07-29T18:35:01.806323043Z] Cluster-Http-Server 2021/07/29 18:35:01 http: TLS handshake error from <IP_ADDRESS>:1024: remote error: tls: bad certificate
INFO[2021-07-29T18:35:01.927599965Z] Cluster-Http-Server 2021/07/29 18:35:01 http: TLS handshake error from <IP_ADDRESS>:56952: remote error: tls: bad certificate
I0729 18:35:01.928911   27170 controller.go:132] OpenAPI AggregationController: action for item : Nothing (removed from the queue).
I0729 18:35:01.928944   27170 controller.go:132] OpenAPI AggregationController: action for item k8s_internal_local_delegation_chain_0000000000: Nothing (removed from the queue).
I0729 18:35:01.941425   27170 storage_scheduling.go:132] created PriorityClass system-node-critical with value<PHONE_NUMBER>
I0729 18:35:01.952066   27170 storage_scheduling.go:132] created PriorityClass system-cluster-critical with value<PHONE_NUMBER>
I0729 18:35:01.952218   27170 storage_scheduling.go:148] all system priority classes are created successfully or already exist.
INFO[2021-07-29T18:35:02.195057773Z] Cluster-Http-Server 2021/07/29 18:35:02 http: TLS handshake error from <IP_ADDRESS>:45350: remote error: tls: bad certificate
INFO[2021-07-29T18:35:02.220837040Z] Cluster-Http-Server 2021/07/29 18:35:02 http: TLS handshake error from <IP_ADDRESS>:45354: remote error: tls: bad certificate
INFO[2021-07-29T18:35:02.543979402Z] Cluster-Http-Server 2021/07/29 18:35:02 http: TLS handshake error from <IP_ADDRESS>:45358: remote error: tls: bad certificate
I0729 18:35:02.567112   27170 controller.go:611] quota admission added evaluator for: roles.rbac.authorization.k8s.io
I0729 18:35:02.617209   27170 controller.go:611] quota admission added evaluator for: rolebindings.rbac.authorization.k8s.io
W0729 18:35:02.703816   27170 lease.go:233] Resetting endpoints for master service "kubernetes" to [<IP_ADDRESS>]
I0729 18:35:02.704887   27170 controller.go:611] quota admission added evaluator for: endpoints
I0729 18:35:02.709202   27170 controller.go:611] quota admission added evaluator for: endpointslices.discovery.k8s.io
INFO[2021-07-29T18:35:03.065953078Z] Kube API server is now running
INFO[2021-07-29T18:35:03.066043051Z] k3s is up and running
INFO[2021-07-29T18:35:03.067142176Z] Waiting for cloud-controller-manager privileges to become available
Flag --address has been deprecated, see --bind-address instead.
I0729 18:35:03.082970   27170 controllermanager.go:175] Version: v1.21.3+k3s1
I0729 18:35:03.083508   27170 deprecated_insecure_serving.go:53] Serving insecurely on <IP_ADDRESS>:10252
W0729 18:35:03.094669   27170 authorization.go:47] Authorization is disabled
W0729 18:35:03.094789   27170 authentication.go:47] Authentication is disabled
I0729 18:35:03.094865   27170 deprecated_insecure_serving.go:51] Serving healthz insecurely on <IP_ADDRESS>:10251
INFO[2021-07-29T18:35:03.118762259Z] Creating CRD addons.k3s.cattle.io
INFO[2021-07-29T18:35:03.172900120Z] Creating CRD helmcharts.helm.cattle.io
INFO[2021-07-29T18:35:03.187654283Z] Creating CRD helmchartconfigs.helm.cattle.io
INFO[2021-07-29T18:35:03.209154148Z] Waiting for CRD helmcharts.helm.cattle.io to become available
INFO[2021-07-29T18:35:03.596383892Z] Cluster-Http-Server 2021/07/29 18:35:03 http: TLS handshake error from <IP_ADDRESS>:45362: remote error: tls: bad certificate
I0729 18:35:03.687158   27170 shared_informer.go:240] Waiting for caches to sync for tokens
I0729 18:35:03.700268   27170 controller.go:611] quota admission added evaluator for: serviceaccounts
I0729 18:35:03.703800   27170 controllermanager.go:574] Started "daemonset"
I0729 18:35:03.704065   27170 daemon_controller.go:285] Starting daemon sets controller
I0729 18:35:03.704143   27170 shared_informer.go:240] Waiting for caches to sync for daemon sets
I0729 18:35:03.715771   27170 controllermanager.go:574] Started "statefulset"
I0729 18:35:03.716035   27170 stateful_set.go:146] Starting stateful set controller
I0729 18:35:03.716111   27170 shared_informer.go:240] Waiting for caches to sync for stateful set
INFO[2021-07-29T18:35:03.716475356Z] Done waiting for CRD helmcharts.helm.cattle.io to become available
INFO[2021-07-29T18:35:03.716570800Z] Waiting for CRD helmchartconfigs.helm.cattle.io to become available
I0729 18:35:03.725972   27170 controllermanager.go:574] Started "ttl-after-finished"
I0729 18:35:03.726222   27170 ttlafterfinished_controller.go:109] Starting TTL after finished controller
I0729 18:35:03.726317   27170 shared_informer.go:240] Waiting for caches to sync for TTL after finished
I0729 18:35:03.740865   27170 controllermanager.go:574] Started "endpoint"
I0729 18:35:03.741028   27170 endpoints_controller.go:189] Starting endpoint controller
I0729 18:35:03.741136   27170 shared_informer.go:240] Waiting for caches to sync for endpoint
I0729 18:35:03.761102   27170 controllermanager.go:574] Started "csrapproving"
I0729 18:35:03.761360   27170 certificate_controller.go:118] Starting certificate controller "csrapproving"
I0729 18:35:03.761384   27170 shared_informer.go:240] Waiting for caches to sync for certificate-csrapproving
I0729 18:35:03.778559   27170 controllermanager.go:574] Started "persistentvolume-expander"
I0729 18:35:03.778908   27170 expand_controller.go:327] Starting expand controller
I0729 18:35:03.779139   27170 shared_informer.go:240] Waiting for caches to sync for expand
I0729 18:35:03.787468   27170 shared_informer.go:247] Caches are synced for tokens
I0729 18:35:03.803602   27170 controllermanager.go:574] Started "ephemeral-volume"
I0729 18:35:03.804037   27170 controller.go:170] Starting ephemeral volume controller
I0729 18:35:03.804065   27170 shared_informer.go:240] Waiting for caches to sync for ephemeral
I0729 18:35:03.868056   27170 node_lifecycle_controller.go:377] Sending events to api server.
I0729 18:35:03.868279   27170 taint_manager.go:163] "Sending events to api server"
I0729 18:35:03.868406   27170 node_lifecycle_controller.go:505] Controller will reconcile labels.
I0729 18:35:03.868474   27170 controllermanager.go:574] Started "nodelifecycle"
I0729 18:35:03.868673   27170 node_lifecycle_controller.go:539] Starting node controller
I0729 18:35:03.868696   27170 shared_informer.go:240] Waiting for caches to sync for taint
I0729 18:35:03.923762   27170 controllermanager.go:574] Started "clusterrole-aggregation"
I0729 18:35:03.923932   27170 clusterroleaggregation_controller.go:194] Starting ClusterRoleAggregator
I0729 18:35:03.923960   27170 shared_informer.go:240] Waiting for caches to sync for ClusterRoleAggregator
I0729 18:35:03.958716   27170 controllermanager.go:574] Started "podgc"
I0729 18:35:03.958979   27170 gc_controller.go:89] Starting GC controller
I0729 18:35:03.959002   27170 shared_informer.go:240] Waiting for caches to sync for GC
I0729 18:35:04.076334   27170 controllermanager.go:574] Started "namespace"
I0729 18:35:04.076615   27170 namespace_controller.go:200] Starting namespace controller
I0729 18:35:04.076705   27170 shared_informer.go:240] Waiting for caches to sync for namespace
I0729 18:35:04.118737   27170 controllermanager.go:574] Started "deployment"
I0729 18:35:04.120736   27170 deployment_controller.go:153] "Starting controller" controller="deployment"
I0729 18:35:04.120839   27170 shared_informer.go:240] Waiting for caches to sync for deployment
INFO[2021-07-29T18:35:04.222187783Z] Done waiting for CRD helmchartconfigs.helm.cattle.io to become available
INFO[2021-07-29T18:35:04.233601795Z] Writing static file: /var/lib/rancher/k3s/server/static/charts/traefik-9.18.2.tgz
INFO[2021-07-29T18:35:04.234983552Z] Writing static file: /var/lib/rancher/k3s/server/static/charts/traefik-crd-9.18.2.tgz
I0729 18:35:04.397249   27170 controllermanager.go:574] Started "cronjob"
I0729 18:35:04.397583   27170 cronjob_controllerv2.go:125] Starting cronjob controller v2
I0729 18:35:04.397612   27170 shared_informer.go:240] Waiting for caches to sync for cronjob
INFO[2021-07-29T18:35:04.432876296Z] Failed to get existing traefik HelmChart      error="helmcharts.helm.cattle.io \"traefik\" not found"
INFO[2021-07-29T18:35:04.433172630Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/local-storage.yaml
INFO[2021-07-29T18:35:04.433349137Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/aggregated-metrics-reader.yaml
INFO[2021-07-29T18:35:04.433474876Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/auth-delegator.yaml
INFO[2021-07-29T18:35:04.433596124Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/auth-reader.yaml
INFO[2021-07-29T18:35:04.433732624Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/traefik.yaml
INFO[2021-07-29T18:35:04.433859473Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/ccm.yaml
INFO[2021-07-29T18:35:04.434072245Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/coredns.yaml
INFO[2021-07-29T18:35:04.434194834Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-service.yaml
INFO[2021-07-29T18:35:04.434319012Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/resource-reader.yaml
INFO[2021-07-29T18:35:04.434457723Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/rolebindings.yaml
INFO[2021-07-29T18:35:04.434573770Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/metrics-apiservice.yaml
INFO[2021-07-29T18:35:04.434716412Z] Writing manifest: /var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-deployment.yaml
I0729 18:35:04.545616   27170 controllermanager.go:574] Started "root-ca-cert-publisher"
I0729 18:35:04.545914   27170 publisher.go:102] Starting root CA certificate configmap publisher
I0729 18:35:04.546041   27170 shared_informer.go:240] Waiting for caches to sync for crt configmap
INFO[2021-07-29T18:35:04.639426598Z] Starting k3s.cattle.io/v1, Kind=Addon controller
INFO[2021-07-29T18:35:04.763366979Z] Waiting for control-plane node ip-172-31-5-153 startup: nodes "ip-172-31-5-153" not found
I0729 18:35:04.870354   27170 controllermanager.go:574] Started "replicationcontroller"
I0729 18:35:04.870673   27170 replica_set.go:182] Starting replicationcontroller controller
I0729 18:35:04.870755   27170 shared_informer.go:240] Waiting for caches to sync for ReplicationController
INFO[2021-07-29T18:35:04.950473725Z] Cluster dns configmap has been set successfully
INFO[2021-07-29T18:35:04.963761758Z] Starting helm.cattle.io/v1, Kind=HelmChartConfig controller
INFO[2021-07-29T18:35:04.964099829Z] Starting helm.cattle.io/v1, Kind=HelmChart controller
INFO[2021-07-29T18:35:04.964383172Z] Starting batch/v1, Kind=Job controller
INFO[2021-07-29T18:35:05.201786692Z] Cluster-Http-Server 2021/07/29 18:35:05 http: TLS handshake error from <IP_ADDRESS>:45366: remote error: tls: bad certificate
INFO[2021-07-29T18:35:05.207661363Z] Cluster-Http-Server 2021/07/29 18:35:05 http: TLS handshake error from <IP_ADDRESS>:45370: remote error: tls: bad certificate
INFO[2021-07-29T18:35:05.217556788Z] Cluster-Http-Server 2021/07/29 18:35:05 http: TLS handshake error from <IP_ADDRESS>:45374: remote error: tls: bad certificate
INFO[2021-07-29T18:35:05.235341635Z] Cluster-Http-Server 2021/07/29 18:35:05 http: TLS handshake error from <IP_ADDRESS>:45378: remote error: tls: bad certificate
INFO[2021-07-29T18:35:05.247342786Z] Cluster-Http-Server 2021/07/29 18:35:05 http: TLS handshake error from <IP_ADDRESS>:45382: remote error: tls: bad certificate
I0729 18:35:05.312655   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for statefulsets.apps
I0729 18:35:05.312828   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for ingresses.extensions
I0729 18:35:05.312953   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for poddisruptionbudgets.policy
I0729 18:35:05.313143   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for addons.k3s.cattle.io
I0729 18:35:05.313277   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for limitranges
I0729 18:35:05.313388   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for replicasets.apps
I0729 18:35:05.313513   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for helmchartconfigs.helm.cattle.io
I0729 18:35:05.313682   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for daemonsets.apps
I0729 18:35:05.313794   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for jobs.batch
I0729 18:35:05.313949   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for deployments.apps
I0729 18:35:05.314066   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for events.events.k8s.io
I0729 18:35:05.314186   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for helmcharts.helm.cattle.io
I0729 18:35:05.314308   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for ingresses.networking.k8s.io
I0729 18:35:05.314429   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for networkpolicies.networking.k8s.io
I0729 18:35:05.314563   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for rolebindings.rbac.authorization.k8s.io
I0729 18:35:05.314683   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for endpointslices.discovery.k8s.io
I0729 18:35:05.314792   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for leases.coordination.k8s.io
W0729 18:35:05.314896   27170 shared_informer.go:494] resyncPeriod 21h28m24.918934309s is smaller than resyncCheckPeriod 22h37m21.509050895s and the informer has already started. Changing it to 22h37m21.509050895s
I0729 18:35:05.315021   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for serviceaccounts
I0729 18:35:05.315130   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for endpoints
I0729 18:35:05.315277   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for roles.rbac.authorization.k8s.io
I0729 18:35:05.315394   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for controllerrevisions.apps
I0729 18:35:05.315507   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for horizontalpodautoscalers.autoscaling
I0729 18:35:05.315619   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for cronjobs.batch
I0729 18:35:05.315774   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for csistoragecapacities.storage.k8s.io
I0729 18:35:05.315893   27170 resource_quota_monitor.go:229] QuotaMonitor created object count evaluator for podtemplates
I0729 18:35:05.315986   27170 controllermanager.go:574] Started "resourcequota"
I0729 18:35:05.317828   27170 resource_quota_controller.go:273] Starting resource quota controller
I0729 18:35:05.317940   27170 shared_informer.go:240] Waiting for caches to sync for resource quota
I0729 18:35:05.318045   27170 resource_quota_monitor.go:304] QuotaMonitor running
INFO[2021-07-29T18:35:05.368294948Z] Starting /v1, Kind=Secret controller
INFO[2021-07-29T18:35:05.368609415Z] Starting /v1, Kind=Node controller
INFO[2021-07-29T18:35:05.368741875Z] Starting /v1, Kind=Service controller
INFO[2021-07-29T18:35:05.368883937Z] Starting /v1, Kind=Pod controller
INFO[2021-07-29T18:35:05.369017747Z] Starting /v1, Kind=Endpoints controller
I0729 18:35:05.388707   27170 controllermanager.go:574] Started "serviceaccount"
I0729 18:35:05.388932   27170 serviceaccounts_controller.go:117] Starting service account controller
I0729 18:35:05.389071   27170 shared_informer.go:240] Waiting for caches to sync for service account
I0729 18:35:05.466769   27170 controllermanager.go:574] Started "ttl"
W0729 18:35:05.466935   27170 controllermanager.go:553] "tokencleaner" is disabled
I0729 18:35:05.467189   27170 ttl_controller.go:121] Starting TTL controller
I0729 18:35:05.467294   27170 shared_informer.go:240] Waiting for caches to sync for TTL
I0729 18:35:05.483987   27170 node_ipam_controller.go:91] Sending events to api server.
INFO[2021-07-29T18:35:05.535299989Z] Active TLS secret k3s-serving (ver=275) (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-kubernetes:kubernetes listener.cattle.io/cn-kubernetes.default:kubernetes.default listener.cattle.io/cn-kubernetes.default.svc:kubernetes.default.svc listener.cattle.io/cn-kubernetes.default.svc.cluster.local:kubernetes.default.svc.cluster.local listener.cattle.io/cn-localhost:localhost listener.cattle.io/fingerprint:SHA1=B05F40177D8FFF8DF3C6B69267C8D94ADFCD845E]
INFO[2021-07-29T18:35:05.788003274Z] Waiting for control-plane node ip-172-31-5-153 startup: nodes "ip-172-31-5-153" not found
INFO[2021-07-29T18:35:06.143846421Z] Cluster-Http-Server 2021/07/29 18:35:06 http: TLS handshake error from <IP_ADDRESS>:45386: remote error: tls: bad certificate
INFO[2021-07-29T18:35:06.550827228Z] Cluster-Http-Server 2021/07/29 18:35:06 http: TLS handshake error from <IP_ADDRESS>:45390: remote error: tls: bad certificate
I0729 18:35:06.656264   27170 controller.go:611] quota admission added evaluator for: addons.k3s.cattle.io
INFO[2021-07-29T18:35:06.665615376Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"ccm", UID:"920a0074-1f91-4ff4-b9a1-effbae71a93f", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"284", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/ccm.yaml"
INFO[2021-07-29T18:35:06.701033319Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"ccm", UID:"920a0074-1f91-4ff4-b9a1-effbae71a93f", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"284", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/ccm.yaml"
INFO[2021-07-29T18:35:06.720830588Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"coredns", UID:"a459050e-a3d7-4d1a-964d-9316cb2566d7", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"289", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/coredns.yaml"
INFO[2021-07-29T18:35:06.794060353Z] Waiting for control-plane node ip-172-31-5-153 startup: nodes "ip-172-31-5-153" not found
I0729 18:35:06.823975   27170 controller.go:611] quota admission added evaluator for: deployments.apps
INFO[2021-07-29T18:35:06.852553337Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"coredns", UID:"a459050e-a3d7-4d1a-964d-9316cb2566d7", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"289", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/coredns.yaml"
INFO[2021-07-29T18:35:06.869594243Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"local-storage", UID:"a417cf94-7a1b-4b4c-8295-87c1a45a0059", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"301", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/local-storage.yaml"
INFO[2021-07-29T18:35:06.952810865Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"local-storage", UID:"a417cf94-7a1b-4b4c-8295-87c1a45a0059", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"301", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/local-storage.yaml"
INFO[2021-07-29T18:35:06.965152147Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"aggregated-metrics-reader", UID:"15a954fb-3d0b-46a9-92c3-bd9f1c4c181b", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"312", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/aggregated-metrics-reader.yaml"
INFO[2021-07-29T18:35:06.975885787Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"aggregated-metrics-reader", UID:"15a954fb-3d0b-46a9-92c3-bd9f1c4c181b", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"312", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/aggregated-metrics-reader.yaml"
INFO[2021-07-29T18:35:06.990022877Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"auth-delegator", UID:"3bd4dbfc-2a16-4b6e-81bd-5ef792a842b7", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"315", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/auth-delegator.yaml"
INFO[2021-07-29T18:35:07.003044280Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"auth-delegator", UID:"3bd4dbfc-2a16-4b6e-81bd-5ef792a842b7", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"315", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/auth-delegator.yaml"
INFO[2021-07-29T18:35:07.015680946Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"auth-reader", UID:"a4ac0942-b767-4cb2-a587-1e507036741f", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"318", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/auth-reader.yaml"
INFO[2021-07-29T18:35:07.038219597Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"auth-reader", UID:"a4ac0942-b767-4cb2-a587-1e507036741f", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"318", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/auth-reader.yaml"
INFO[2021-07-29T18:35:07.124138705Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"metrics-apiservice", UID:"1160c51b-fdec-4f6a-9a99-13ec537939c5", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"324", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/metrics-apiservice.yaml"
INFO[2021-07-29T18:35:07.164678595Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"metrics-apiservice", UID:"1160c51b-fdec-4f6a-9a99-13ec537939c5", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"324", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/metrics-apiservice.yaml"
INFO[2021-07-29T18:35:07.199070414Z] Cluster-Http-Server 2021/07/29 18:35:07 http: TLS handshake error from <IP_ADDRESS>:45392: remote error: tls: bad certificate
INFO[2021-07-29T18:35:07.250416736Z] Cluster-Http-Server 2021/07/29 18:35:07 http: TLS handshake error from <IP_ADDRESS>:45396: remote error: tls: bad certificate
INFO[2021-07-29T18:35:07.624149726Z] Cluster-Http-Server 2021/07/29 18:35:07 http: TLS handshake error from <IP_ADDRESS>:57002: remote error: tls: bad certificate
INFO[2021-07-29T18:35:07.645157197Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"metrics-server-deployment", UID:"96ff2c49-5df8-4fe6-b85d-520b109f0541", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"329", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-deployment.yaml"
INFO[2021-07-29T18:35:07.831460383Z] Waiting for control-plane node ip-172-31-5-153 startup: nodes "ip-172-31-5-153" not found
INFO[2021-07-29T18:35:07.913077175Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"metrics-server-deployment", UID:"96ff2c49-5df8-4fe6-b85d-520b109f0541", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"329", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-deployment.yaml"
INFO[2021-07-29T18:35:08.027063173Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"metrics-server-service", UID:"c0abf699-b53e-40a5-9282-b9e934273637", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"335", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-service.yaml"
INFO[2021-07-29T18:35:08.084718091Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"metrics-server-service", UID:"c0abf699-b53e-40a5-9282-b9e934273637", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"335", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/metrics-server-service.yaml"
INFO[2021-07-29T18:35:08.431750806Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"resource-reader", UID:"7b0b2707-c7a9-4fa2-b8fd-9f9d076e6dc1", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"342", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/resource-reader.yaml"
INFO[2021-07-29T18:35:08.599144035Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"resource-reader", UID:"7b0b2707-c7a9-4fa2-b8fd-9f9d076e6dc1", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"342", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/metrics-server/resource-reader.yaml"
INFO[2021-07-29T18:35:08.725548286Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"rolebindings", UID:"94bdb13f-cf3c-4569-89f5-562ae4fe2ee3", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"347", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/rolebindings.yaml"
INFO[2021-07-29T18:35:08.772283766Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"rolebindings", UID:"94bdb13f-cf3c-4569-89f5-562ae4fe2ee3", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"347", FieldPath:""}): type: 'Normal' reason: 'AppliedManifest' Applied manifest at "/var/lib/rancher/k3s/server/manifests/rolebindings.yaml"
I0729 18:35:08.892766   27170 serving.go:354] Generated self-signed cert in-memory
INFO[2021-07-29T18:35:08.928111710Z] Waiting for control-plane node ip-172-31-5-153 startup: nodes "ip-172-31-5-153" not found
INFO[2021-07-29T18:35:09.128129423Z] Event(v1.ObjectReference{Kind:"Addon", Namespace:"kube-system", Name:"traefik", UID:"9ab78c0f-f02e-42b0-8147-224886dee123", APIVersion:"k3s.cattle.io/v1", ResourceVersion:"353", FieldPath:""}): type: 'Normal' reason: 'ApplyingManifest' Applying manifest at "/var/lib/rancher/k3s/server/manifests/traefik.yaml"
INFO[2021-07-29T18:35:09.128711370Z] Imported docker.io/rancher/pause:3.1
INFO[2021-07-29T18:35:09.128939324Z] Imported docker.io/rancher/coredns-coredns:1.8.3
INFO[2021-07-29T18:35:09.129095228Z] Imported docker.io/rancher/klipper-helm:v0.6.1-build20210616
INFO[2021-07-29T18:35:09.129264723Z] Imported docker.io/rancher/klipper-lb:v0.2.0
INFO[2021-07-29T18:35:09.129411715Z] Imported docker.io/rancher/library-busybox:1.32.1
INFO[2021-07-29T18:35:09.129611855Z] Imported docker.io/rancher/library-traefik:2.4.8
INFO[2021-07-29T18:35:09.129779920Z] Imported docker.io/rancher/local-path-provisioner:v0.0.19
INFO[2021-07-29T18:35:09.129931943Z] Imported docker.io/rancher/metrics-server:v0.3.6
I0729 18:35:09.174580   27170 controller.go:611] quota admission added evaluator for: helmcharts.helm.cattle.io
INFO[2021-07-29T18:35:09.183526902Z] Connecting to proxy                           url="wss://<IP_ADDRESS>:6443/v1-k3s/connect"
INFO[2021-07-29T18:35:09.191222137Z] Handling backend connection request [ip-172-31-5-153]

If I grep for "Import" the lines I shared are the only ones I see, which I think meets the ask?

Yeah exactly, it's just not as clean in mine so I didn't see it when looking (I was looking for the output visually like how it is in yours since I thought there was something, but wasn't sure of the exact verbage).

Yeah, you get the first Importing message when the tarball is opened, and then all the Imported messages once processing is complete. That's just sorta how it works with the containerd import API.

Cool, I'm happy with this. I'm closing it


[Bug]: Jest clears console log when test fails

Version
27.5.1
Steps to reproduce
Run a test that fails in your favorite IDE (WebStorm for example)
console logging disappears before you can read it
Expected behavior
console logging works when the test passes but is cleared when it fails - which is when it is needed the most for debugging. I found several closed issues with no clear resolution to this specific use case (--useStderr for example does not help here). Would love an option to not clear the console on a test fail.
Actual behavior
console is cleared when test fails.
Additional context
No response
Environment
System:
    OS: macOS 10.15.4
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
  Binaries:
    Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
  npmPackages:
    jest: ^27.5.1 => 27.5.1

Closing - this looks like a webstorm thing and not a jest thing. clicking up the chain of describes reveals the log.


Gradle project sync failed

It is from the afternoon of the 15th of June that it is not possible to compile the Android application because Gradle fails to sync the project when it tries to connect with "maven.sumup.com" repository.
Checking the server status it seems the the "maven.sumup.com" repository is not available as from the attached images:

And AndroidStudio is not able to download the required libraries as from the attached images:

If you need more information, do not hesitate to ask..

Fixed manually changing build.config file forcing a rename for every maven repository:
allprojects {
repositories {
google()
jcenter()
maven {
url 'https://maven.google.com/'
name 'Google'
}
    maven {
        url 'https://maven.sumup.com/releases'
        name 'SumUp'
    }
}

}


String matching regex in JsonLexer causes catastrophic backtracking

(Original issue 1361 created by howardchris on 2017-07-11T08:45:49.801114+00:00)
The attached text file contains JSON data, downloaded from a request to google.co.uk (the text isn't actually legal JSON, but that's besides the point).
When using the JsonLexer to parse this file, the process hangs for a very long time, and the CPU of one core is maxed out.
The reason is catastrophic backtracking in the regex engine, caused by the regex used to match strings:
#!python
r'"(\\\\|\\"|[^"])*"'

I believe the problem is that the groups in the regex are not mutually exclusive, as the last group can match a backslash character.
The solution I have found is to make each group in the regex mutually exclusive, by adding a backslash character to the final group:
#!python

r'"(\\\\|\\"|[^"\\])*"'

Note that this particular regex is actually in two places (in both the simplevalue and objectvalue sections), and so both regexes should be updated.
A good description of the problem can be found here:
http://www.regular-expressions.info/catastrophic.html
After making these changes, the data in the attached file can be formatted in ~1s on my machine.

I ran into a problem with the same regex. a repro case can be found on this file:
https://github.com/simdjson/simdjson/blob/master/jsonchecker/adversarial/issue150/1005.json
e.g. the following will hang: pygmentize 1005.json
I pulled the regex and pos by asking RegexLexer to log as it applies regexes. This snippet illustrates the issue in isolation.
import re

regex = re.compile(r'"(\\\\|\\"|[^"])*"', re.DOTALL)
example = r'{"\u00D0000\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\63CD'
m = regex.match(example, 1)

print(str(m))

and this snippet illustrates the fix:
import re

regex = re.compile(r'"(\\\\|\\"|[^"\\])*"', re.DOTALL)
example = r'{"\u00D0000\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\63CD'
m = regex.match(example, 1)

print(str(m))

Also, I think it's funny that the pygments lexer hangs while trying to process an adversarial example from another parser.

not, so fast. the suggested fix doesn't work. it'll fail test: tests/examplefiles/http_response_example
specifically there's an embedded json document in this test that fails to parse, and also fails to parse correctly when using pygmentize on the command line:
[{"contributors_enabled":false,"profile_background_tile":true,"followers_count":644,"protected":false,"profile_image_url":"http:\/\/a0.twimg.com\/profile_images\/69064242\/gb_normal.jpg","screen_name":"birkenfeld","default_profile_image":false,"following":null,"friends_count":88,"profile_sidebar_fill_color":"7AC3EE","url":"http:\/\/pythonic.pocoo.org\/","name":"Georg Brandl","default_profile":false,"is_translator":false,"utc_offset":3600,"profile_sidebar_border_color":"65B0DA","description":"","profile_background_image_url_https":"https:\/\/si0.twimg.com\/images\/themes\/theme10\/bg.gif","favourites_count":0,"profile_use_background_image":true,"created_at":"Tue Dec 30 22:25:11 +0000 2008","status":{"retweet_count":10,"favorited":false,"geo":null,"possibly_sensitive":false,"coordinates":null,"in_reply_to_screen_name":null,"in_reply_to_status_id_str":null,"retweeted":false,"in_reply_to_status_id":null,"in_reply_to_user_id_str":null,"created_at":"Sat Jul 09 13:42:35 +0000 2011","truncated":false,"id_str":"89690914515206144","contributors":null,"place":null,"source":"web","in_reply_to_user_id":null,"id":89690914515206144,"retweeted_status":{"retweet_count":10,"favorited":false,"geo":null,"possibly_sensitive":false,"coordinates":null,"in_reply_to_screen_name":null,"in_reply_to_status_id_str":null,"retweeted":false,"in_reply_to_status_id":null,"in_reply_to_user_id_str":null,"created_at":"Sat Jul 09 13:07:04 +0000 2011","truncated":false,"id_str":"89681976755372032","contributors":null,"place":null,"source":"web","in_reply_to_user_id":null,"id":89681976755372032,"text":"Excellent Python posts from @mitsuhiko - http:\/\/t.co\/k1wt6e4 and @ncoghlan_dev - http:\/\/t.co\/eTxacgZ (links fixed)"},"text":"RT @jessenoller: Excellent Python posts from @mitsuhiko - http:\/\/t.co\/k1wt6e4 and @ncoghlan_dev - http:\/\/t.co\/eTxacgZ (links fixed)"},"follow_request_sent":null,"statuses_count":553,"geo_enabled":false,"notifications":null,"profile_text_color":"3D1957","id_str":"18490730","lang":"en","profile_background_image_url":"http:\/\/a1.twimg.com\/images\/themes\/theme10\/bg.gif","profile_image_url_https":"https:\/\/si0.twimg.com\/profile_images\/69064242\/gb_normal.jpg","show_all_inline_media":true,"listed_count":65,"profile_link_color":"FF0000","verified":false,"id":18490730,"time_zone":"Berlin","profile_background_color":"642D8B","location":"Bavaria, Germany"}]

I fixed a very similar issue here: https://github.com/pygments/pygments/commit/ab0537fbf5a3d4154b2a70dac5410988e725a58d, but the solution was to go to a different state to not have the problematic regex. I'm obviously curious to see if the regex can be massaged into shape, but I'm not super optimistic it can.

You're suggesting changing the parser to, instead of trying to parse the quoted string in one shot, recognize the start of the string and then move to parsing the inside of the string and then move back to the outer state?
This would be simpler than for ruby which supports two kinds of strings (single and double), whereas json only supports one. But this would still be a somewhat complex change because both object names and "simplevalue" will both need to dive into new states for string parsing, whereas your fix for ruby was on top of code already diving into a string parsing state. Does that sound correct?
Sorry, I'm not super familiar with the pygments model of lexing (or lexing in general). But I am motivated to fix this.

rather than adding new states what about this?
r'"(\\(["\\/bfnrt]|u[a-fA-F0-9]]{4})|[^\\"])+"'

I'm about 95% sure what the original regex was trying to accomplish and I think this one should capture the same things. Here's what this one does:

match an opening quote
match either an escaped character ("/bfnrt as per json spec) or a non escape or quote character
match a closing quote

the whole thing turns into Name.Tag in the case of object attribute name or String.Double in the case of value. Tests all pass with this and the 1005.json adversarial string is totally unmatched and doesn't hang because of catastrophic backtracking.
I did code up a solution with more states, but I don't like that it splits the strings into many tokens and I needed one state for the attribute name and one for the string value which seemed clunky.
I'll submit a PR, unless there is some objection.


Delete .tool-version and docs.md files

Summary

Delete the global .tool-versions and the empty docs.md file from the docs directory.

Could I grab this task?


OSX Quicklook Plugin

Has any work been done on creating a .BPMN quick look plugin for Mac so you can view the process without opening Modeler?  If no work to date, any thoughts?

We have not done any work there. We appreciate PRs on quick look support.
Our underlying technology is Electron.

I was having a look into this as I found it to be an interesting problem. Unfortunately, there is no way to run JavaScript in the sandboxed Quicklook as it would be required by bpmn-js without exploiting a now fixed vulnerability of OSX.

Quick Look
Available for: OS X Yosemite v10.10 to v10.10.4
Impact: Searching for a previously viewed website may launch the web browser and render that website
Description: An issue existed where QuickLook had the capability to execute JavaScript. The issue was > addressed by disallowing execution of JavaScript.

@bentrm could we go from something like BPMN>PNG>SVG? or just use the code that generates pictures/PNG and have that generate in QuickLook?

looking at the code for Generate-image, looks like a no go as it is just the Canvas in js.

We are happy to take external contributions that implement this feature.


Tween for camera Y?

Describe your problem here.
Hi! I would like to know if there is something like a tweenCameraY(); in the Lua? I say like becuase it obv doesn't exist, but, what could be some easy alternatives?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
nope!

doTweenY("yourTweenHere", "camGame", 100, 5, "Linear")
camGame can be camHUD or camOther
Yes they act as objects.

doTweenY("yourTweenHere", "camGame", 100, 5, "Linear")
camGame can be camHUD or camOther
Yes they act as objects.

WHAT??
thanks for letting me know!

doTweenY("yourTweenHere", "camGame", 100, 5, "Linear")
camGame can be camHUD or camOther
Yes they act as objects.

going back on this, it does not load anything outside of camera view. just a black void

doTweenY("yourTweenHere", "camGame", 100, 5, "Linear")

camGame can be camHUD or camOther

Yes they act as objects.

going back on this, it does not load anything outside of camera view. just a black void

I think that's how it's supposed to work.
If you want to move the camera itself the use triggerEvent("Camera Follow Pos", "x", "y")


Demote KleisliIO from being a function

Hi
I tried to solve issue #14 (but have the feeling that my solution is to simple ;)

@fabianpage Just about correct. Left a few comments. Thanks for the contribution!!!

Sorry i reopened the rebased pull request in #30


Mismatched c ptr types warning in closures when using cdef classes

Am attempting to compile complex legacy code with cython (for speed) and am running into warnings in the generated .c code
Given the following:
import sys

cdef class Foo(object):
     def __init(self, log):
         self.log = log

     def bar(self):
         def inner(a):
             return self.log.write(str(a))

         self.log = sys.stdout
         inner(42)

cython-0.13 and latest cython-devel handles it, but I get compilation warnings from gcc on compiling the generated .c code:
$ cython innerfunction.pyx
$ gcc -I/usr/include/python2.6 -lpython2.6 innerfunction.c
innerfunction.c: In function ‘__pyx_pf_13innerfunction_3Foo_bar’:
innerfunction.c:547: warning: assignment from incompatible pointer type
innerfunction.c:575: warning: passing argument 1 of ‘PyObject_SetAttr’ from incompatible pointer type
/usr/include/python2.6/object.h:472: note: expected ‘struct PyObject *’ but argument is of type ‘struct __pyx_obj_13innerfunction_Foo *’

The error in question at line 547 is on this line:
  __pyx_cur_scope->__pyx_v_self = __pyx_v_self;

where:
struct __pyx_obj_13innerfunction___pyx_scope_struct_bar {
  PyObject_HEAD
  PyObject *__pyx_v_inner;
  struct __pyx_obj_13innerfunction_Foo *__pyx_v_self;
};

and the locals are:
  PyObject *__pyx_v_self
  struct __pyx_obj_13innerfunction___pyx_scope_struct_bar *__pyx_cur_scope;

so the closure struct has a ptr to the underlying struct class, whereas self is a PyObject*
Similarly, at line 575, we have:
  if (PyObject_SetAttr(__pyx_cur_scope->__pyx_v_self, __pyx_n_s__log, __pyx_t_2) < 0)

where the compiler is unhappy with the passing of the subclass_, rather than a PyObject_
Obviously these are safely cast-able in both cases, but it would be nicer to avoid compilation warnings.
Migrated from http://trac.cython.org/ticket/573

This looks to have been fixed at some point...


Detect negated content absent buffer 2224 v9

Ticket
Redmine ticket: https://redmine.openinfosecfoundation.org/issues/2224
#1914 with keywords optional syntax

Continued in https://github.com/OISF/suricata-verify/pull/1957


Upgraded to Lagom 1.3

Upgraded to Lagom 1.3 and changed the prompts to align with the exercises

Closing as we just released lagom 1.3.1


ACLs shapes underspecified

Neither the ACL specs at https://www.w3.org/wiki/WebAccessControl nor at http://www.w3.org/ns/auth/acl.n3 tells us what this means:
[ a acl:Authorization,
  acl:agent <alice>, <bob>;
  acl:mode acl:Read;
  acl:accessTo <foo> ]

Does that mean alice and bob both have read access to foo?  Or is it malformed?
If we allow it, it will probably cause problems for acl editors, possibly with dangerous results.
Suggested solution: don't allow it.
That is, say that ACLs must have a datashape where num(agent)+num(agentClass) == 1 and num(accessTo)+num(accessToClass) == 1.
In ShEx that looks something like:
<Authorization> {
   (:accessTo | :accessToClass),
   (:agent | :agentClass),
   :mode ( :Read :Write :Append :Control )*

Ooops, moved to solid, not solid-spec


no uefi support

https://www.plop.at/en/bootmanagers.html. Look at his new bootmanager.   I also like supergrub2 UEFI boot file that you copy to the ESP EFI partition.
Copy file to the EFI fat32 boot partition among the other UEFI boot files.  Use this supergrub2_x86-64.EFI boot file to help select / manage which partition you wish to boot when grub is borked.  Supergrub2 will search and display all the bootable partition/files and give you the choice to select which one to boot.
https://sourceforge.net/projects/supergrub2/files/2.02s10/super_grub2_disk_2.02s10/super_grub2_disk_standalone_x86_64_efi_2.02s10.EFI/download
Have you looked at ConvergenceOS bash shell script for turning a Debian 9.6-9 , Ubuntu 18.03, Linux Mint 19.1 into a game controller based big picture STEAM game play from the couch.
https://github.com/wb7odyfred/ConvergenceOS
What I forked from  John Bitzen
https://github.com/jonbitzen/ConvergenceOS/issues/1
Best Wishes, Fred
You project was mentioned on Linux for everyone Telegram group channel.
https://github.com/gamer-os/gamer-os
Anybody know anything about this distro or tried it?

https://t.me/linux4everyone/5118

implemented in gamerOS 5


[#3897] batch refactoring base on partitioning

Codecov Report

Merging #3900 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #3900      +/-   ##
=========================================
- Coverage    40.7%   40.7%   -0.01%
=========================================
  Files        2200    2202       +2
  Lines       71460   71443      -17
  Branches     9841    9836       -5
=========================================
- Hits        29091   29084       -7
+ Misses      39611   39605       -6
+ Partials     2758    2754       -4

Impacted Files
Coverage Δ

...p/pinpoint/web/batch/flink/HealthCheckTasklet.java
0% <ø> (ø)
:arrow_up:

...navercorp/pinpoint/web/alarm/AlarmPartitioner.java
100% <100%> (+11.11%)
:arrow_up:

...m/navercorp/pinpoint/web/batch/DefaultDivider.java
100% <100%> (ø)

.../com/navercorp/pinpoint/web/alarm/AlarmReader.java
84% <100%> (+2.18%)
:arrow_up:

.../pinpoint/web/batch/job/AgentCountPartitioner.java
100% <100%> (ø)

...npoint/rpc/server/SimpleServerMessageListener.java
80% <0%> (-20%)
:arrow_down:

...corp/pinpoint/rpc/stream/StreamChannelManager.java
70.68% <0%> (-1.73%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
79.16% <0%> (-1.05%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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


Do i have to have a headset in cs:go?

When i type exec slam then i do la to see what i can play then i type the number to play it then i got out of console and i press the assigned key i have to play whatever music i want to play and it doesn't play it. So do i need a headset to play the music?

No, you don't need headset . Have you binded play button in settings of slam?


100% at prompt?

Issue
Since updating my prompt just says 100%? Is that supposed to be the case?
Screenshot

Environment
Operating system: macOS
Terminal emulator: Hyper.app
ZSH version: 5.4.1
Relevant .zshrc
export PATH=$PATH:"/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/usr/local/mysql/bin:/opt/local/bin"
export PATH=/opt/local/bin:/opt/local/sbin:$PATH  # brew

alias brew="env PATH=${PATH//$(pyenv root)\/shims:/} brew"

export ZSH=/Users/cdrum/.oh-my-zsh

export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
export PATH="/Users/cdrum/miniconda2/bin:$PATH"

eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"

ZSH_THEME="spaceship"
SPACESHIP_TIME_SHOW=false

plugins=(git bundler osx rake ruby pass brew common-aliases node npm pip pyenv rails tig rvm nvm)

source $ZSH/oh-my-zsh.sh

alias zshconfig="atom ~/.zshrc"
alias ohmyzsh="atom ~/.oh-my-zsh"
alias alac='for f in ./*.flac; do ffmpeg -n -i "$f" -c:a alac "${f%.*}.m4a" && rm "$f"; done'
alias dirhistory="find . -newerct 'yesterday' -print0 | xargs -0 ls -tlr"

[[ -f /Users/cdrum/.sentinel/current/bin/sentinel ]] && eval "$(/Users/cdrum/.sentinel/current/bin/sentinel init -)"

ssh-add ~/.ssh/custom > /dev/null 2>&1

export PATH="$PATH:$HOME/.rvm/bin" # ruby duh

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

source "/Users/cdrum/.oh-my-zsh/custom/themes/spaceship.zsh-theme"

This indicator means you have a fully charged battery. Check out battery section. You could disable the battery prompt by setting SPACESHIP_BATTERY_SHOW=false.
Duplicate of #215 , #204 , #203


Windows7 Audio Noise Fix

[ ] I have read the FAQ.
[ ] I have searched in existing issues.

Environment

OS: Windows7
scrcpy version:1.12.1
installation method: Windows release
device model:VMWare Player
Android version: 11,12,13

Describe the bug
Windows7 Audio Noise.Need edit audio_player.c function sc_audio_player_frame_sink_open

.samples = SC_AUDIO_OUTPUT_BUFFER_MS * ctx->sample_rate / 1000,*  change to .samples = 2048 or .samples = 1024

On dev branch: 39544f34b4d63a6cdb91802a9c6136b3d6a6003a
scrcpy --audio-output-buffer=10


pause uploading function

How to pause uploading before cancel

Hi @Aadriya
Mmmm so are you wanting to pause the post request? There isn't really a way to do that with xhr requests. Can you explain your use case a little bit more?
Thanks,
Rowan


where'd fommil/spray-json-shapeless go?

@fommil ?

I had a clone sitting around on my laptop which I've put at https://github.com/scalacommunitybuild/spray-json-shapeless — last commit in what I had was March 2017

in both 2.11 community builds, only ensime depends on spray-json-shapeless, and we have spray-json-shapeless frozen at v1.1.0, which is old enough to be included in https://github.com/scalacommunitybuild/spray-json-shapeless
in the 2.12 community build, nothing depends on spray-json-shapeless, so it's okay to just drop if it's effectively a dead project

provisionally dropped from 2.12 in 51b548f8480c73d6834547b5ca7c7a1cc8def388

Oh yeah, i put everything I'm not maintaining into an attic at gitlab. Off with its head!

You can kill ensime from 2.11

ok, thanks for clarifying.
ensime is already frozen in the 2.11 build.... actually deleting it there isn't necessary, freezing is adequate. I'll go ahead and use the scalacommunitybuild fork of spray-json-shapeless

6f44121f310e4d76772cd5dd81df3a38b8e4031f (closing on the assumption this will work)


Create TACLS-Declutter.netkan

After much trial an error, I think I finally figured out how to create a proper netkan file.

@TheFarix : You rock. Does the following look correct to you?
TAC Life Support Declutter Revised: Reduces 30 TAC Life Support parts down to 6, or even 2 if using TweekScale.

Module info:
- version:	0.1.2
- authors:	Farix
- status:	stable
- license:	MIT

Depends:
- TACLS
- InterstellarFuelSwitch-Core
- ModuleManager

Provides:
- TACLS-Declutter

Resources:
- homepage: http://forum.kerbalspaceprogram.com/threads/40667?p=2001257&viewfull=1#post2001257
- kerbalstuff: https://kerbalstuff.com/mod/1216/TAC%20Life%20Support%20Declutter%20Revised
- repository: https://github.com/TheFarix/TACLS-Declutter-Revised/

Filename: DAC577AA-TACLS-Declutter-0.1.2.zip

Showing 3 installed files:
- GameData/TACLS-Declutter
- GameData/TACLS-Declutter/TACLS-Declutter.cfg
- GameData/TACLS-Declutter/TACLS-Declutter.version

Most importantly, this is really a single .cfg file, along with the .version?
If so, this looks good to me. :)

Yes, just the .cfg and .version files. I wasn't sure if I set up the dependencies correctly

@TheFarix : The deps look good to me! We will always be insisting on IntersetellarFuelSwitch-Core (I note the KS page says one can use the Firespitter core instead), but I trust that's not a big problem. :)

Nope, I've tested it and it works with both, but will prefer Intersetellar Fuel Switch if it is available.

Excellent! Merging with great thanks!


Plugged a potential (but unlikely) SQL injection issue

There is an endpoint in GSIP that allows to serialize a record in GeoJSON from postgresql
eg: https://geoconnex.ca/gsip/geo/remote/gsip/rich_bedrock/194
The last 3 segments of the URL identifies the connection id (from META-INF/context.xml), the table name and the id of the row,
so /gsip/rich_bedrock/194 is connection 'gsip', table rich_bedrock and id=194
I was not checking the table name, but it is somewhat constrained by the structure of a URL path.  And also, the table must have a very specific structure (MUST have id, name, unit_code, uri and geom fields)
gsip/rich_bedrock
returns the whole table.. this one is a bit more dangerous (if you actually configured a connection).
So, I restricted this table name to a valid posgresql tablename and I forbid names starting with pg_

fixed in 5b819f9


Coverage is missing coverage files from tmp test dirs

The test suite runs the tests in separate directories which are deleted after the test is finished.
When using coverage with subprocess it will write files into those directories and miss some of the coverage data when all the coverage data is combined at the end. This PR keeps the tmp test directories from getting deleted and gathers the locations of all the coverage data files for the combine command.
Also this PR is using pythons user site to create a usercustomize.py instead of hardcoding to 2.7 dist site.

Coverage increased (+20.5%) to 80.324% when pulling 1a6de1b9ec85b8856f9b0b977493d3bac1ebfeb2 on dmoody256:CoverageImprovements into a3f0e74a8a6dd5af4d2e8a6673ff820fe6ad4df4 on SCons:master.

wouldn't setting COVERAGE_FILE be simpler?
http://coverage.readthedocs.io/en/coverage-4.2/cmd.html#data-file

Coverage.py collects execution data in a file called ”.coverage”. If need be, you can set a new file name with the COVERAGE_FILE environment variable. This can include a path to another directory.

Coverage increased (+20.5%) to 80.332% when pulling 573c0510aa57e5e1ba228226a2fdbbb1f633d3f8 on dmoody256:CoverageImprovements into a3f0e74a8a6dd5af4d2e8a6673ff820fe6ad4df4 on SCons:master.

It seemed that wouldn't work with the multi-process build, because that section also says:

By default, each run of your program starts with an empty data set.

And the next section talks about combining coverage data from multiple processes:
https://coverage.readthedocs.io/en/coverage-4.2/cmd.html#combining-data-files

If you need to collect coverage data from different machines or processes, coverage.py can combine multiple files into one for reporting.

I didn't try using the COVERAGE_FILE file because it didn't seem that multiple processes writing to one file was how it was intended to work (due to concurrency issues of which files have io access or which data gets written when).

hmm... o.k .I think it might work if you don't run runtest.py -j (>1)...
Trying to simplify the underlying changes and also not make changes when
not running via coverage or travis,etc..
It should still  work as it did when running on your own machine.
(though supporting coverage on a local test is good, but it shouldn't be
mandated)
On Sat, Dec 30, 2017 at 5:03 PM, Daniel Moody<EMAIL_ADDRESS>wrote:

It seemed that wouldn't work with the multi-process build, because that
section also says:
By default, each run of your program starts with an empty data set.
And the next section talks about combining coverage data from multiple
processes:
https://coverage.readthedocs.io/en/coverage-4.2/cmd.html#
combining-data-files
If you need to collect coverage data from different machines or processes,
coverage.py can combine multiple files into one for reporting.
I didn't try using the COVERAGE_FILE file because it didn't seem that
multiple processes writing to one file was how it was intended to work (due
to concurrency issues of which files have io access or which data gets
written when).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SCons/scons/pull/36#issuecomment-354578632, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFBNMykrD4S2Q25QK6noU0WXpbZwv4-ks5tFt1WgaJpZM4RPrQW
.

I tested the coverage_file env var and it worked, I'll update the travis script to use that as it is a bit simpler

Coverage increased (+24.3%) to 84.138% when pulling a90dd653a51ac7be36122a456b3667fe45d30154 on dmoody256:CoverageImprovements into a3f0e74a8a6dd5af4d2e8a6673ff820fe6ad4df4 on SCons:master.

Coverage increased (+24.3%) to 84.138% when pulling a90dd653a51ac7be36122a456b3667fe45d30154 on dmoody256:CoverageImprovements into a3f0e74a8a6dd5af4d2e8a6673ff820fe6ad4df4 on SCons:master.

Coverage increased (+24.3%) to 84.138% when pulling a90dd653a51ac7be36122a456b3667fe45d30154 on dmoody256:CoverageImprovements into a3f0e74a8a6dd5af4d2e8a6673ff820fe6ad4df4 on SCons:master.

Coverage increased (+24.3%) to 84.138% when pulling a90dd653a51ac7be36122a456b3667fe45d30154 on dmoody256:CoverageImprovements into a3f0e74a8a6dd5af4d2e8a6673ff820fe6ad4df4 on SCons:master.


Space before function arguments

There should be flag to force a space before the function arguments like this:
function foo (bar, baz) {
    // …
}

maybe: {"space_before_arguments": true}

There's a --space-after-anon-function.  Probably call this --space-after-function.

:+1:

Yes, please.

so?

It's an enhancement. I'm fixing higher priority issues.  Pull requests are welcome.

Can somebody please point me in a direction on how to hack this into /js/lib/js-beautify.js myself? In line 681 I found the statement handling anon_functions. I couldn't get anything going by fiddling with different kinds of statements, e.g.: `if (current_token.text === '(' && last_last_word === 'function') ...

@bitwiseman I think calling it --space-after-named-function would be the most clear, yes? Like @atrioom, I'm interested to work on this. Where do I start?

@atrioom I don't really know what I'm looking at, but maybe here's a good place to look?

@jsejcksn - Name sounds fine.
And you're in the right area, but you'll want to separate else if with last_type === 'TK_WORD'.

Please also consider async functions
const a = async () {...}
async function b () {...}

--space-after-named-function is a good name

+1
i do really hope this gets some more attention as 'javascript standard style' is getting more popular.

@zekida And it should, it's "standard"! 😄

Not to sound mean, but given this is a specification of js standard it's kind of surprising it hasn't been a higher priority. I imagine most of us lint with standard these days, heck, most Vue frameworks have it by default.

@jaysaurus
The existence of this project (and its ever growing list of requests for different formatting options) is one more living proof that formatting wars are alive and well in the land of JavaScript.  Your "standard" is an other developer's "never-doing-it-that-way".


Default ssh user in node

This PR moves the default_ssh_user from being a public attribute of a cluster to a public attribute of each Node of the cluster. It also sets the default_ssh_user to be the default by which SSH commands are issues using Node.run, Node.popen and Node.sendfile. Therefore it is no longer required to pass a user to those functions.

        # Logically a SSH user should be part of a `Node`.
        # However with the DC/OS config there is a notion of a SSH user for
        # an entire DC/OS cluster, which in our case maps to a single SSH user
        # for every cluster created with the corresponding backend. Maybe
        # we're better off making this a `default_ssh_user` of a
        # `ClusterManager` instead.
        self._default_ssh_user = cluster_backend.default_ssh_user

That's part of _docker/__init__.py.
I'll leave the choice to you but this should be removed.

The coverage is failing because there is no coverage for the invisible else case of if user is None:.


Tabular: Updated CatBoost colsample_bylevel value based on feature count

Issue #, if available:
Description of changes:
Tabular: Updated CatBoost colsample_bylevel value based on feature count.
TODO: Will benchmark this change.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Benchmark shows that this change harms accuracy, closing.


Optimize generated code via the CLI by default

This commit updates the behavior of the CLI and adds a new flag. It
first enables the --optimize flag by default, ensuring that usage of
the wasmtime CLI will enable cranelift optimizations by default. Next
it also adds a --opt-level flag which is similar to Rust's
-Copt-level where it takes a string argument of how to optimize. This
is updates to support 0/1/2/s, where 1 is currently the same as 2 but
added for consistency with other compilers. The default setting is
--opt-level=2.
When the -O flag is not passed the --opt-level flag is used,
otherwise -O takes precedent in the sense that it implies
--opt-level=2 which is the highest optimization level. The thinking is
that these flags will in general select the highest optimization level
specified as the final optimization level.

Looks like a test needs updating given the new signature for compile_to_obj.


Bug: Property 'geometry' does not exist on type Graphics

Current Behavior
It seems the typescript defninitions for @pixi/react Graphics doesn't correctly contain the geometry property
Expected Behavior
The geometry property (and any others that might be missing) should be valid on the JSX component
Steps to Reproduce
Typescript flags  as
 Property 'geometry' does not exist on type 'IntrinsicAttributes & Partial<Omit<Graphics, P | ReadonlyKeys<Graphics> | "draw"> & WithPointLike<P>> & { ...; } & InteractionEvents & { ...; }'.
Environment

@pixi/react version: e.g. 7.0.0
pixi.js version: e.g. 7.1.0
React version: e.g. 18.0.0
ReactDOM version: e.g. 18.0.0
Browser & Version: e.g. Chrome 108
OS & Version: e.g. Ubuntu 22.04
Running Example: e.g. https://pixiplayground.com/

Possible Solution
I believe the type definitions just need to be updated
Additional Information
No response

Same for SimpleRope and SimpleMesh. No points argument. And also not accepting textureScale besides typization (points atleast works with ts-nocheck)


⚠ ClamAV has degraded performance

In 44f9544, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 62 ms

Resolved: ClamAV performance has improved in 066ec97 after 5 minutes.


Add missing libcap dependency.

Add missing libcap.
Also updates the .devcontainer.json to current format.
fixes #143

Fixed in https://github.com/EVerest/everest-utils/pull/148


ROC on casia

Hi.
I ran the 20170512-110547 model that was until recently provided here on the LFW test and got good results.
Then I ran the same model on a random selection of 1000 "same" and 1000 "different" pairs taken from casia. This time I got only 0.785 true-positive at 0.001 false positive.
Does it make sense to get such results on casia, even though the model was trained on casia? I realize that casia is a much harder dataset than LFW, but did anyone else get the same results?
I would appreciate any comments.
Thanks!

Did you manually checked the test set? Can you make sure there is no noise (or reasonable low noise) in the CASIA?

I ran it about 10 times, each time randomly selecting different sets of pairs, and got the same results every time. I found some errors in casia, as well as twins and so on, but I didn't think these issues can amount to such low performance, especially compared with the very good performance of the same model on LFW.
One thing I did notice is that the alignment code provided with this package (mtcnn) does not rotate faces to make the eyes level, or at the same coordinates for all faces. Could this be the problem?


Spelling/grammar fixes.

Some minor corrections and editing of the readme.  Cheers!

I updated the branch as requested.


Harmonize Worker names

Issue by rfranzke
Tuesday Nov 28, 2017 at 08:22 GMT
Originally opened as https://git.removed/kubernetes-attic/garden-operator/issues/230

@I820491 propsed here to harmonize the worker names as follows:
shoot-${shoot_name}-${worker_name}-${worker_az}-${worker_count}
The length of ${shoot_name} is restricted by 10 characters.
The length of ${worker_name} is restricted by 15 characters.
The length of ${worker_az} is restricted by ~ 25 characters.
The length of ${worker_count} is restricted by 4 characters.
In sum, we'll get a length of maximum 63 characters (whereas the ${worker_az} is usually much shorter).
Does that sound reasonable to everybode?

@rfranzke, @dkistner, @AndreasBurger What's the status of this ticket? Still something to do? Proposal still valid? Source is not accessible publicly. Length restriction does not apply anymore.

With the machine-controller-manager we will get harmony regarding the VM/instance names.
The scheme will look like as follows:
shoot-<project>-<shoot-name>-<worker-name>-z<zone-nr>, so for example shoot-myproject-cluster1-cpu-worker-z1. For clouds where no availability zones exist (at the moment only Azure) the zone number is simply omitted.
However, for AWS Shoots we still need to use the VM's internal DNS name for the name of the resulting nodes (because the AWS cloud provider expects it like that).
Thus, let's close the ticket.

Thanks for the update!


error during patch phase

INFO: * Applying missing-dependencies.patch (1/106)
patching file chrome/browser/extensions/BUILD.gn
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file chrome/browser/extensions/BUILD.gn.rej
patching file chrome/common/BUILD.gn
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file chrome/common/BUILD.gn.rej
patching file content/browser/BUILD.gn
Reversed (or previously applied) patch detected!  Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file content/browser/BUILD.gn.rej
patching file services/passage_embeddings/BUILD.gn
Traceback (most recent call last):
  File "/build/ungoogled-chromium/src/ungoogled-chromium-126.0.6478.55-1/utils/patches.py", line 257, in <module>
    main()
  File "/build/ungoogled-chromium/src/ungoogled-chromium-126.0.6478.55-1/utils/patches.py", line 253, in main
    args.callback(args, parser.error)
  File "/build/ungoogled-chromium/src/ungoogled-chromium-126.0.6478.55-1/utils/patches.py", line 204, in _apply_callback
    apply_patches(generate_patches_from_series(patch_dir, resolve=True),
  File "/build/ungoogled-chromium/src/ungoogled-chromium-126.0.6478.55-1/utils/patches.py", line 138, in apply_patches
    subprocess.run(cmd, check=True)
  File "/usr/lib/python3.12/subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,

it seems to be in conflicts with ninja-out-of-order-generation-fix.patch
Also, the pkgbuild of this repo is out-of-sync with what's offered in [AUR](https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ungoogled-chromium）

it seems to be in conflicts with ninja-out-of-order-generation-fix.patch

Both patches serve the same purpose.

Ah, my bad, I forgot that this is now included upstream.

Also, the pkgbuild of this repo is out-of-sync with what's offered in [AUR]

the non -bin aur version is maintained by someone else

the non -bin aur version is maintained by someone else

The package is generally poorly and slow maintained. If you the AUR maintainer of it, would be interested to give someone co-maintainer - we would welcome it.

The package is generally poorly

rude

and slow maintained

that might be true, but that happens when the maintainers are volunteers and it can happen to anyone

If you the AUR maintainer of it, would be interested to give someone co-maintainer - we would welcome it.

I'm actually a co-maintainer and handled everything before @networkException came in. I think it'd be better to integrate the OBS workflow for the AUR as well. We'd need to ask seppia (https://aur.archlinux.org/account/seppia) to give maintainer to us or just fill an orphan request.

Looks like the maintainance status got transferred fully?
I guess we'll adjust the CI here to just push this repo to the AUR minus some folders and with a .SRCINFO

we need another user and add that user's ssh key here.

for -bin I use my personal account's ssh key (which isn't used anywhere else)

alright then, just added your account.

inb4 jia tan 2.0

:( /lh
(with what's publically accessible online about me that'd be a pretty bad idea though lol)
I added a new CI step and pushed a new tag, looks good so far. I copied things that looked important from the other PKGBUILD, feel free to add things back if needed though.


[CloudFront]Provisioning CF Distributions with tags.

What problem are you facing?
Enable the possibility of provisioning de CloudFront Distributions with tags on the resource.

/fresh

I would like this feature also

/refresh

/fresh


Adapter to engine and engine-toolkit latest dev/0.8

ref: https://github.com/oasis-engine/engine/pull/844


Closes #1839 dummy function created

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Review the Cheat Sheet. Make any required updates to it by editing the file inst/cheatsheet/admiral_cheatsheet.pptx and re-upload a PDF version of it to the same folder.
[x] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md under the header # admiral (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers). A Developer Notes section is available in NEWS.md for tracking developer-facing issues.
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

Great job @Siddhesh2097 - looks almost perfect, just two outstanding tasks:

Add "onboarding" to inst/WORDLIST so that spellcheck passes

Run roxygen2::roxygenize('.', roclets = c('rd', 'collate', 'namespace')) so that man check passes

@Siddhesh2097 looks good now! If you check every item in the tasklist then the final check should pass as well, then you are good to go!

Thank You @manciniedoardo. I have checked all items and the final check has passed. I clicked on Ready for Review. Can you tell me the next step, whether I need to close this issue or it will done by you.

@Siddhesh2097 all good now - i will close this PR now and you can start working on admiralmetabolic!

@Siddhesh2097 can I add you to the admiral community team?  We ping this team occasionally on admiral developments?

@bms63 Sure, please add me


Feature/spv 792 transactions api

Pull Request Checklist

[ ] 📖 I created my PR using provided  : CODE_STANDARDS
[ ] 📖 I have read the short Code of Conduct: CODE_OF_CONDUCT
[ ] 🏠 I tested my changes locally.
[ ] ✅ I have provided tests for my changes.
[ ] 📝 I have used conventional commits.
[ ] 📗 I have updated any related documentation.
[ ] 💾 PR was issued based on the Github or Jira issue.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 4.28571% with 67 lines in your changes missing coverage. Please review.

Project coverage is 48.53%. Comparing base (e6a10da) to head (436c8a4).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #634      +/-   ##
==========================================
- Coverage   48.79%   48.53%   -0.26%
==========================================
  Files         257      257
  Lines       11524    11591      +67
==========================================
+ Hits         5623     5626       +3
- Misses       5316     5380      +64
  Partials      585      585

Flag
Coverage Δ

unittests
48.53% <4.28%> (-0.26%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

actions/transactions/broadcast_callback.go
0.00% <ø> (ø)

docs/docs.go
0.00% <ø> (ø)

server/server.go
44.76% <100.00%> (+1.62%)
:arrow_up:

actions/transactions/new.go
0.00% <0.00%> (ø)

actions/transactions/record.go
0.00% <0.00%> (ø)

actions/transactions/get.go
0.00% <0.00%> (ø)

actions/transactions/update.go
0.00% <0.00%> (ø)

actions/transactions/routes.go
52.77% <0.00%> (-47.23%)
:arrow_down:

actions/transactions/search.go
0.00% <0.00%> (ø)

Continue to review full report in Codecov by Sentry.

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


Explains no-store in the correct way.

Before this, the german text explained the exact opposite of what the no-store attribute does.
Before: "The browser and all intermediate caches can simply cache a copy of any version of the response."
After: "The browser and all intermediate caches are simply not allowed to cache a copy of any version of the response."

I signed it!

@pbakaus - can you take a super quick look at this and verify it looks good? If it's good, please LGTM

LGTM


[SPARK-15721][ML] Make DefaultParamsReadable, DefaultParamsWritable public

What changes were proposed in this pull request?
Made DefaultParamsReadable, DefaultParamsWritable public.  Also added relevant doc and annotations.  Added UnaryTransformerExample to demonstrate use of UnaryTransformer and DefaultParamsReadable,Writable.
How was this patch tested?
Wrote example making use of the now-public APIs.  Compiled and ran locally

Test build #59812 has started for PR 13461 at commit b42d503.

Test build #59812 has finished for PR 13461 at commit b42d503.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
  class MyTransformer(override val uid: String)
trait DefaultParamsWritable extends MLWritable
trait DefaultParamsReadable[T] extends MLReadable[T]

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

Merged build finished. Test PASSed.

CC: @yanboliang What do you think of this?  The only real change is making DefaultParamsReadable/Writable public; the other changes are just documentation + example code.

@jkbradley This change looks good overall, please see my inline comments. I think currently only Scala example is enough, since the Java example may hit the same issue with SPARK-15605. We can add the corresponding Java example when SPARK-15605 is resolved. Thanks!

@yanboliang Thanks! updated now

Test build #59956 has started for PR 13461 at commit 1b1bc93.

Test build #59956 has finished for PR 13461 at commit 1b1bc93.

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

Merged build finished. Test PASSed.

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

LGTM

Test build #3067 has started for PR 13461 at commit 1b1bc93.

Test build #3067 has finished for PR 13461 at commit 1b1bc93.

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

Thanks!  I'll merge it with master


Using with react-native-navigation package and getting an error on Android

I'm trying to use this package with the wix react-native-navigation package and when I add GoogleAnalyticsBridgePackage to the public List createAdditionalReactPackages() { method and try to build I get the following error:
react-native-google-analytics-bridge/android/src/main/java/com/idehub/GoogleAnalyticsBridge/GoogleAnalyticsBridgePackage.java:13: error: GoogleAnalyticsBridgePackage is not abstract and does not override abstract method createJSModules() in ReactPackage
public class GoogleAnalyticsBridgePackage implements ReactPackage {
       ^
1 error

Any ideas? This is the first library that I've had this issue integrating with.

Nevermind. I see this was removed purposely in 5.2.0. Looks like I need to upgrade my RN.  I'll drop back to 5.1.0 for now. Thanks!

@jbolter createJSModules removed created the breaking change? Did not expect that. Crap.
@eggybot Use version 5.1.0 of this module.

@jbolter @eggybot I've published a version 5.2.1 which reverts the breaking change. I'll revisit it when RN 0.47.0 is released (which introduces this breaking change).
TLDR; You can both use 5.2.1 of this library.