Not able to run Kind or Minikube through ctlptl

hi there,
I simply tried to spin up a either a kind or a minikube server with:

kind create cluster --image=kindest/node:v1.21.2
ctlptl create cluster minikube --registry=ctlptl-registry --kubernetes-version=v1.21.6

I have to mention, that I am NOT using Docker Desktop (that was eating up all my CPU and memory and was impossible to work with). So I work with brew install hyperkit, and brew install docker
A regular minikube start --memory=4096 --driver=virtualbox --kubernetes-version=v1.21.6 --cpus=4 works as expected.
Do I miss something?
Thank you in advance
PS:
I saw, that ctlptl is using "docker" as guest driver. Maybe that's relevant:
💢  Exiting due to GUEST_DRIVER_MISMATCH: The existing "minikube" cluster was created using the "docker" driver, which is incompatible with requested "virtualbox" driver. (that happened when I tried to create another minikube cluster, while the ctlptlcluster was failed.
That's the complete output of ctlptl KIND...

Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.21.2) 🖼
 ✓ Preparing nodes 📦
 ✓ Writing configuration 📜
 ✗ Starting control-plane 🕹
ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged kind-control-plane kubeadm init --skip-phases=preflight --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1
Command Output: I1102 09:46:36.417274     210 initconfiguration.go:246] loading configuration from "/kind/kubeadm.conf"
[config] WARNING: Ignored YAML document with GroupVersionKind kubeadm.k8s.io/v1beta2, Kind=JoinConfiguration
[init] Using Kubernetes version: v1.21.2
[certs] Using certificateDir folder "/etc/kubernetes/pki"
I1102 09:46:36.437468     210 certs.go:110] creating a new certificate authority for ca
[certs] Generating "ca" certificate and key
I1102 09:46:36.722944     210 certs.go:487] validating certificate period for ca certificate
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [kind-control-plane kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local localhost] and IPs [<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>]
[certs] Generating "apiserver-kubelet-client" certificate and key
I1102 09:46:37.345725     210 certs.go:110] creating a new certificate authority for front-proxy-ca
[certs] Generating "front-proxy-ca" certificate and key
I1102 09:46:37.577422     210 certs.go:487] validating certificate period for front-proxy-ca certificate
[certs] Generating "front-proxy-client" certificate and key
I1102 09:46:37.883405     210 certs.go:110] creating a new certificate authority for etcd-ca
[certs] Generating "etcd/ca" certificate and key
I1102 09:46:38.047485     210 certs.go:487] validating certificate period for etcd/ca certificate
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [kind-control-plane localhost] and IPs [<IP_ADDRESS> <IP_ADDRESS> ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [kind-control-plane localhost] and IPs [<IP_ADDRESS> <IP_ADDRESS> ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
I1102 09:46:38.726407     210 certs.go:76] creating new public/private key files for signing service account users
[certs] Generating "sa" key and public key
I1102 09:46:38.834593     210 kubeconfig.go:101] creating kubeconfig file for admin.conf
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
I1102 09:46:39.013447     210 kubeconfig.go:101] creating kubeconfig file for kubelet.conf
[kubeconfig] Writing "kubelet.conf" kubeconfig file
I1102 09:46:39.123278     210 kubeconfig.go:101] creating kubeconfig file for controller-manager.conf
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
I1102 09:46:39.425823     210 kubeconfig.go:101] creating kubeconfig file for scheduler.conf
[kubeconfig] Writing "scheduler.conf" kubeconfig file
I1102 09:46:39.678982     210 kubelet.go:63] Stopping the kubelet
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
I1102 09:46:39.779861     210 manifests.go:96] [control-plane] getting StaticPodSpecs
I1102 09:46:39.782608     210 certs.go:487] validating certificate period for CA certificate
I1102 09:46:39.782827     210 manifests.go:109] [control-plane] adding volume "ca-certs" for component "kube-apiserver"
I1102 09:46:39.782848     210 manifests.go:109] [control-plane] adding volume "etc-ca-certificates" for component "kube-apiserver"
I1102 09:46:39.782854     210 manifests.go:109] [control-plane] adding volume "k8s-certs" for component "kube-apiserver"
I1102 09:46:39.782858     210 manifests.go:109] [control-plane] adding volume "usr-local-share-ca-certificates" for component "kube-apiserver"
I1102 09:46:39.782861     210 manifests.go:109] [control-plane] adding volume "usr-share-ca-certificates" for component "kube-apiserver"
I1102 09:46:39.790326     210 manifests.go:126] [control-plane] wrote static Pod manifest for component "kube-apiserver" to "/etc/kubernetes/manifests/kube-apiserver.yaml"
I1102 09:46:39.790354     210 manifests.go:96] [control-plane] getting StaticPodSpecs
[control-plane] Creating static Pod manifest for "kube-controller-manager"
I1102 09:46:39.790789     210 manifests.go:109] [control-plane] adding volume "ca-certs" for component "kube-controller-manager"
I1102 09:46:39.790834     210 manifests.go:109] [control-plane] adding volume "etc-ca-certificates" for component "kube-controller-manager"
I1102 09:46:39.790840     210 manifests.go:109] [control-plane] adding volume "flexvolume-dir" for component "kube-controller-manager"
I1102 09:46:39.790843     210 manifests.go:109] [control-plane] adding volume "k8s-certs" for component "kube-controller-manager"
I1102 09:46:39.790846     210 manifests.go:109] [control-plane] adding volume "kubeconfig" for component "kube-controller-manager"
I1102 09:46:39.790849     210 manifests.go:109] [control-plane] adding volume "usr-local-share-ca-certificates" for component "kube-controller-manager"
I1102 09:46:39.790852     210 manifests.go:109] [control-plane] adding volume "usr-share-ca-certificates" for component "kube-controller-manager"
I1102 09:46:39.791645     210 manifests.go:126] [control-plane] wrote static Pod manifest for component "kube-controller-manager" to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
I1102 09:46:39.791671     210 manifests.go:96] [control-plane] getting StaticPodSpecs
[control-plane] Creating static Pod manifest for "kube-scheduler"
I1102 09:46:39.791907     210 manifests.go:109] [control-plane] adding volume "kubeconfig" for component "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
I1102 09:46:39.792397     210 manifests.go:126] [control-plane] wrote static Pod manifest for component "kube-scheduler" to "/etc/kubernetes/manifests/kube-scheduler.yaml"
I1102 09:46:39.793138     210 local.go:74] [etcd] wrote Static Pod manifest for a local etcd member to "/etc/kubernetes/manifests/etcd.yaml"
I1102 09:46:39.793300     210 waitcontrolplane.go:87] [wait-control-plane] Waiting for the API server to be healthy
I1102 09:46:39.793877     210 loader.go:372] Config loaded from file:  /etc/kubernetes/admin.conf
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
I1102 09:46:39.817565     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:40.318258     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:40.818594     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:41.319035     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:41.818587     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:42.318663     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:42.819415     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:43.318759     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:43.819619     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:44.319229     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:44.819810     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:45.318928     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:45.818592     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:46.318763     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:46.818981     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:47.319231     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:47.818305     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:48.318925     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:48.819466     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:49.318670     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:49.818017     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:50.318088     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:50.820623     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:51.318743     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:51.819496     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:52.318593     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:52.818510     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:53.318118     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:53.819099     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:54.318610     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:54.819845     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:55.319201     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:55.818470     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:56.318407     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:56.818549     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:57.318912     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:57.819130     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:58.318204     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:58.818741     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:59.318967     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:46:59.819331     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:00.318486     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:00.820312     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:01.318987     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:01.818123     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:02.318776     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:02.818732     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:03.318507     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:03.818109     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:04.318268     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:04.818463     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:05.318530     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:05.818790     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:06.318990     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:06.817996     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:07.318796     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:07.818764     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:08.317913     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:08.818759     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:09.318802     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:09.818968     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:10.317977     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:10.818559     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:11.318964     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:11.818820     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:12.318237     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:12.817990     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:13.319049     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:13.818566     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:14.318090     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:14.818582     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:15.318412     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:15.818679     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:16.318930     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:16.819681     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:17.318454     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:17.818497     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:18.318702     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:18.818358     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:19.317957     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.
I1102 09:47:19.818528     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:20.319618     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:20.819165     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:21.319423     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:21.818633     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:22.318218     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:22.819329     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:23.318841     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:23.818548     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:24.318271     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.
I1102 09:47:24.818731     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:25.318645     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:25.818680     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:26.318860     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:26.819675     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:27.319954     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:27.818555     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:28.319557     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:28.818236     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:29.318355     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:29.818344     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:30.318990     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:30.818580     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:31.318690     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:31.818696     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:32.318057     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:32.817999     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:33.318439     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:33.819417     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:34.318181     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.
I1102 09:47:34.817943     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:35.318490     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:35.819449     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:36.319133     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:36.818899     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:37.319032     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:37.819540     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:38.319255     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:38.819338     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:39.319175     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:39.821109     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:40.318323     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:40.819136     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:41.318604     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:41.819153     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:42.318135     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:42.818602     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:43.318827     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:43.818679     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:44.319036     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:44.818761     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:45.319589     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:45.819823     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:46.318756     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:46.818539     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:47.318822     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:47.818901     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:48.318527     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:48.818785     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:49.318819     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:49.819608     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:50.318745     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:50.818680     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:51.318863     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:51.818673     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:52.319618     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:52.818962     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:53.318829     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:53.818002     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:54.318633     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
I1102 09:47:54.819412     210 round_trippers.go:454] GET https://kind-control-plane:6443/healthz?timeout=10s  in 0 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.

	Unfortunately, an error has occurred:
		timed out waiting for the condition

	This error is likely caused by:
		- The kubelet is not running
		- The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

	If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
		- 'systemctl status kubelet'
		- 'journalctl -xeu kubelet'

	Additionally, a control plane component may have crashed or exited when started by the container runtime.
	To troubleshoot, list all containers using your preferred container runtimes CLI.

	Here is one example how you may list all Kubernetes containers running in cri-o/containerd using crictl:
		- 'crictl --runtime-endpoint unix:///run/containerd/containerd.sock ps -a | grep kube | grep -v pause'
		Once you have found the failing container, you can inspect its logs with:
		- 'crictl --runtime-endpoint unix:///run/containerd/containerd.sock logs CONTAINERID'

couldn't initialize a Kubernetes cluster
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/init.runWaitControlPlanePhase
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/init/waitcontrolplane.go:114
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:234
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:421
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:207
k8s.io/kubernetes/cmd/kubeadm/app/cmd.newCmdInit.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/init.go:152
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:850
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:958
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:895
k8s.io/kubernetes/cmd/kubeadm/app.Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:50
main.main
	_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
	/usr/local/go/src/runtime/proc.go:225
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1371
error execution phase wait-control-plane
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:235
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:421
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:207
k8s.io/kubernetes/cmd/kubeadm/app/cmd.newCmdInit.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/init.go:152
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:850
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:958
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:895
k8s.io/kubernetes/cmd/kubeadm/app.Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:50
main.main
	_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
	/usr/local/go/src/runtime/proc.go:225
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1371

and that's the output of minikube
❯ ctlptl create cluster minikube --registry=ctlptl-registry --kubernetes-version=v1.21.6
😄  minikube v1.23.2 on Darwin 11.6
    ▪ MINIKUBE_EXISTING_DOCKER_TLS_VERIFY=1
    ▪ MINIKUBE_EXISTING_DOCKER_HOST=tcp://<IP_ADDRESS>:2376
    ▪ MINIKUBE_EXISTING_DOCKER_CERT_PATH=/Users/jan/.docker/machine/machines/default
    ▪ MINIKUBE_ACTIVE_DOCKERD=minikube
✨  Using the docker driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🚜  Pulling base image ...
🔥  Creating docker container (CPUs=2, Memory=1992MB) ...
❗  Listening to <IP_ADDRESS> on external docker host <IP_ADDRESS>. Please be advised
🤦  StartHost failed, but will try again: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de -d /var/lib: exit status 125
stdout:

stderr:
docker: Error response from daemon: cgroups: cannot find cgroup mount destination: unknown.

📌  Noticed you have an activated docker-env on docker driver in this terminal:
❗  Please re-eval your docker-env, To ensure your environment variables have updated ports:

	'minikube -p minikube docker-env'

🤷  docker "minikube" container is missing, will recreate.
🔥  Creating docker container (CPUs=2, Memory=1992MB) ...
❗  Listening to <IP_ADDRESS> on external docker host <IP_ADDRESS>. Please be advised
😿  Failed to start docker container. Running "minikube delete" may fix it: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de -d /var/lib: exit status 125
stdout:

stderr:
docker: Error response from daemon: cgroups: cannot find cgroup mount destination: unknown.

❌  Exiting due to PR_DOCKER_IP_CONFLICT: Failed to start host: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.27@sha256:89b4738ee74ba28684676e176752277f0db46f57d27f0e08c3feec89311e22de -d /var/lib: exit status 125
stdout:

stderr:
docker: Error response from daemon: cgroups: cannot find cgroup mount destination: unknown.

💡  Suggestion: Run: 'minikube delete --all' to clean up all the abandoned networks.
🍿  Related issue: https://github.com/kubernetes/minikube/issues/9605

creating minikube cluster: exit status 60

Thanks for the report!
Currently, ctlptl assumes you're using either Docker Desktop or a standalone Docker daemon.
Here's a guide on how to use it with a standalone Docker daemon - https://blog.tilt.dev/2021/10/11/old-school-remote-dev-clusters.html
You can also eval $(minikube docker-env), and use ctlptl to create a cluster inside a Minikube VM running Docker.
If you want to use ctlptl with hyperkit, there's a separate issue for that: https://github.com/tilt-dev/ctlptl/issues/93


Spyder ide GUI is not starting. When I click on spyder icon a command prompt open it run then nothing.

From<EMAIL_ADDRESS>on 2014-04-25T04:19:31Z
Please note that reporting bugs from Spyder's help menu ("?" > "Report
issue...") will fill version details for Spyder, Python and Qt in this description for you.
What steps will reproduce the problem?

What is the expected output? What do you see instead? What version of the product are you using? On what operating system?

Please provide any additional information below
.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1801

From ccordoba12 on 2015-01-01T15:13:27Z
I hope things are working ok for you now :-)
Status: Invalid


Style: Cards image is clipped

In the original page, the image of cards is not clipped:

while in our version it is (because it is set to cover instead of contains):

fixed in #354


onnx_qnn convert deploy problems

I'm having a conversion problem  use BackendType.ONNX_QNN. The networks is seems like above,  and the error code is  " op_type=Conv not in FAKE_QUANTIZE_OP"(in fused relu pass), looking forward to a reply

when i update mqbench to latest version, there is another error ，''assert _next_node.op_type in self.qlinear_op_type
AssertionError''

I look at  the code and found that 'Concat' was not supported.

Any code(especially model definition) to reproduce?

Any code(especially model definition) to reproduce?

I  added 'replace_concat_to_qlinearconcat'  in deploy_onnx_qnn myself， it works.


[9.x] Allow appending query strings to paginators globally

This PR adds a new Paginator::appendQueryString() method that appends query strings by default to all Paginator instances. This method can be added in a service provider.
 My main use case is paginating and filtering with query strings using Inertia.

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

@taylorotwell Is it an implementation issue? Honestly, I think this would be pretty useful. Having to call ->withQueryString() along with every single ->paginate() call is cumbersome.
Happy to discuss another way to solve this.


Add option to Gradle plugin to specify which source-set generated code is included in

It is useful to generate a server, implement it and then generate a client for testing that server. Adding a sourceSet option would allow generating these test clients in the test source-set; among other possibilities.

Fixed in #64


Getting error message when running in lambda: message: "Too many open files"

Discussed in https://github.com/delta-io/delta-rs/discussions/2352

Originally posted by rob3000 March 28, 2024
Hi' i'm currently running the deltra-rs rust library in lambda to do a merge query into delta lake. However i noticed i'm getting the following error:
Error: hyper::Error(Connect, ConnectError("tcp open error", Os { code: 24, kind: Uncategorized, message: "Too many open files" }))

It looks like its coming from the DynamoDBLock;
{
    "timestamp": "Mar 28 09:06:04.847",
    "level": "ERROR",
    "fields": {
        "message": "dynamodb client failed to write log entry: GenericDynamoDb { source: HttpDispatch(HttpDispatchError { message: \"Error during dispatch: error trying to connect: dns error: Too many open files (os error 24)\" }) }"
    },
    "target": "deltalake_aws::logstore"
}

I suspect the logstore is trying to create new connections when running through a batch for records to save to deltalake, I'm still quite new to rust, but when i normally talk to dynamoDB i create a a reference outside of the handler and pass the reference through, do i need to look at doing the same with the logstore? And if so how?

There probably isn't much delta-rs can do here. The Too many open files error is an operating system error. Most operating systems set a limit as to how many open file descriptors one can have opened at once - and each network connection also counts as an open file descriptor.
On macOS and Debian this can be adjusted using ulimit command or by editing /etc/sysctl.conf.
macOS
# see your current limit
ulimit -n

# change the limit
ulimit -n 30000

https://man7.org/linux/man-pages/man3/ulimit.3.html
https://serverfault.com/questions/20387/too-many-open-files-on-debian

@rob3000 fyi


Adding support for Facebook Notification Settings (Regular Push, Silent Push, Silent)

Apropo #432

Thank you for this!


pythonPackages.asttokens: 2.0.8 -> 2.1.0

Description of changes

Commits: https://github.com/gristlabs/asttokens/compare/2.0.8...2.1.0
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Thanks for taking a look at this also! I merged it earlier in https://github.com/NixOS/nixpkgs/pull/201670, but it targeted staging because of the number of rebuilds.

I will close this then, I think?


KDevelop can't find qdbus

Issue description
$ kdevelop! -s "{0b43abee-b9ca-4c21-87ea-85efc2154220}"
which: no qdbus in (/nix/store/zx4vl80ndps9jciiwmxp4xyic26i1749-qttools-5.9.1/bin:/nix/store/qgbikwdx1bn1jm5nnvr8fif40d9cff7d-kde-cli-tools-5.10.5/bin:/home/glaebhoerl/bin:/run/wrappers/bin:/etc/per-user-pkgs/glaebhoerl/bin:/home/glaebhoerl/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/run/current-system/sw/bin)
Error: The qdbus utility is missing.
$ ls /nix/store/zx4vl80ndps9jciiwmxp4xyic26i1749-qttools-5.9.1/bin
ls: cannot access '/nix/store/zx4vl80ndps9jciiwmxp4xyic26i1749-qttools-5.9.1/bin': No such file or directory
$ ls /nix/store/zx4vl80ndps9jciiwmxp4xyic26i1749-qttools-5.9.1/
lib/         nix-support/ phrasebooks/
$ ls /nix/store/qgbikwdx1bn1jm5nnvr8fif40d9cff7d-kde-cli-tools-5.10.5/bin
kbroadcastnotification  kcmshell5  kdecp5  kdemv5  kde-open5  keditfiletype5  kioclient5  kmimetypefinder5  kstart5  ksvgtopng5  ktraderclient5

kdevelop.nix contains the lines:
  postInstall = ''
    # The kdevelop! script (shell environment) needs qdbus and kioclient5 in PATH.
    wrapProgram "$out/bin/kdevelop!" --prefix PATH ":" "${qttools}/bin:${kde-cli-tools}/bin"

maybe this is no longer correct?
Edit: based on grepping /nix/store it seems it has moved here: /nix/store/6js8gxdx98ky8jg8adcpva9sm56198vv-qttools-5.9.1-bin/bin/qdbus
Steps to reproduce
Start KDevelop, open the built-in konsole panel.
Technical details

System: 17.09.1756.c99239bca0 (Hummingbird)
Nix version: nix-env (Nix) 1.11.15
Nixpkgs version: "17.09.1756.c99239bca0"
Sandboxing enabled: build-use-sandbox = false

@glaebhoerl as of the 19.03 version of KDevelop this no longer appears to be an issue. Can you please confirm and close?

Will do after it is released and I upgrade to it.

Apologies for the delay! (Previously I'd always managed to upgrade to the new release within a few weeks...)
Indeed it seems to be fixed now.


AboutSpecial open a website

is it possible to open a website with AboutSpecial button ?
thanks

@JordanGout you can hook in any functionality you want.
There is the LibsConfiguration which allows you to set any listener for it:
https://github.com/mikepenz/AboutLibraries/blob/develop/library/src/main/java/com/mikepenz/aboutlibraries/LibsConfiguration.java
Use it like:
LibsConfiguration.getInstance().setListener(...)

You are looking for this: onExtraClicked. Return false if you have consumed the event

I missed this event on the listener. Thank You.

@JordanGout no problem ;)


Make the 4xx apache logs alarm more specific

Only fire the alarm if the rate of 400 - 403s goes over the limit. 404s happen quite frequently and are not indicative of anything going wrong.
See https://github.com/alphagov/digitalmarketplace-search-api/pull/50

:+1:


photoflare: <IP_ADDRESS> -> 1.6.9

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/PhotoFlare/photoflare/releases.
meta.description for photoflare is: "A cross-platform image editor with a powerful features and a very friendly graphical user interface"
meta.homepage for photoflare is: "https://photoflare.io"
meta.changelog for photoflare is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

Warning: no invocation of /nix/store/i69rrnqmxjmsv85xv0fjbhsgxjfz2n7i-photoflare-1.6.9/bin/photoflare had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/i69rrnqmxjmsv85xv0fjbhsgxjfz2n7i-photoflare-1.6.9/bin/.photoflare-wrapped had a zero exit code or showed the expected version

0 of 2 passed binary check by having a zero exit code.

0 of 2 passed binary check by having the new version present in output.

found 1.6.9 with grep in /nix/store/i69rrnqmxjmsv85xv0fjbhsgxjfz2n7i-photoflare-1.6.9

found 1.6.9 in filename of file in /nix/store/i69rrnqmxjmsv85xv0fjbhsgxjfz2n7i-photoflare-1.6.9

directory tree listing: https://gist.github.com/856e3f1842d5db7549867a4ab30e896b

du listing: https://gist.github.com/6b03557df87fd8419a664cdd761ba380

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
photoflare

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/i69rrnqmxjmsv85xv0fjbhsgxjfz2n7i-photoflare-1.6.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A photoflare https://github.com/r-ryantm/nixpkgs/archive/41f3acb037f0dc4fb70ecc6f75195118b08fca0b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/i69rrnqmxjmsv85xv0fjbhsgxjfz2n7i-photoflare-1.6.9
ls -la /nix/store/i69rrnqmxjmsv85xv0fjbhsgxjfz2n7i-photoflare-1.6.9/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

photoflare

Maintainer pings
cc @omgbebebe for testing.

@omgbebebe  Okay, I set it to draft so it won't be merged or regenerated. Please ask to close this when there is a new release is made.

1.6.10 is out. Let's close this.


Firefox manifest.json

Related to/see issue #4

Hey, thanks for you contribution but we have to keep supporting v3 for the chrome web store so I can't merge this. I'm going to setup a build system to switch out the manifests for the different stores.
For now I've submitted to the firefox store with this manifest and I'll let everyone know when its approved.

My pleasure to help :)


Show a thumbnail for each paper

@freeman-lab's pdf-to-png allows creating a thumbnail from a PDF.
It will be slow to generate these on the fly for each client - it requires downloading a full PDF to create the thumbnail. So a nice setup task is to generate a dataset of thumbnail images from all the papers in our set.
We can start with EuropePMC - download all the PDFs and use pdf-to-png to generate thumbnails with DOIs as filenames. But it should be equally doable for all the open access sources, and even for non-OA papers a thumbnail should be legitimate.
It would be cool to put the images somewhere reusable and behind a nice API.

@blahah Maybe S3?

@onbjerg that's definitely an option - somewhere free would be even better :)

@blahah GitHub? 😁

@onbjerg yeah that's what I'm thinking! Could also do zenodo and use some sort of comtent addressable format to store a collection of images.

This is really related to PDFs, which aren't planned to be included in v1. Closing this but we can revisit later if we decide to add PDFs.


When executing chef-runner second time: rsync permission errors

It tries to rsync the cookbooks but there appear a big list of delete_file permission errors.
The strange thing is that it works the first time.
rsync: delete_file: unlink(local-mode-cache/cache/cookbooks/yum/templates/default/repo.erb) failed: Permission denied (13)
rsync: delete_file: unlink(local-mode-cache/cache/cookbooks/yum/templates/default/main.erb) failed: Permission denied (13)

The problem is that Chef now stores the additional folders nodes and local-mode-cache in /tmp/chef-runner:
INFO: Uploading local files to machine. This may take a while...
DEBUG: Uploading files from .chef-runner/sandbox to /tmp/chef-runner on machine
DEBUG: exec: rsync --archive --delete --compress --rsh 'ssh' '-F' '.chef-runner/vagrant/machines/f6ee376/ssh_config' .chef-runner/sandbox/ default:/tmp/chef-runner
rsync: delete_file: unlink(nodes/vagrant-ubuntu-trusty-64.json) failed: Permission denied (13)
cannot delete non-empty directory: nodes
rsync: delete_file: unlink(local-mode-cache/cache/cookbooks/yum/templates/default/repo.erb) failed: Permission denied (13)
rsync: delete_file: unlink(local-mode-cache/cache/cookbooks/yum/templates/default/main.erb) failed: Permission denied (13)
cannot delete non-empty directory: local-mode-cache/cache/cookbooks/yum/templates/default

We either need to exclude them from rsync or, if possible, configure Chef to use a different folder.


invidious: unstable-2023-08-07 -> unstable-2023-08-25

Description of changes
Update invidious.
@infinisil @999eagle
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

invidious


iOS crash fix

Implementing handleAdPlayedForCustomEventNetwork used in Unity MoPub and
part of the MPRewardedVideoCustomEvent interface. Otherwise the app
crashes after V4VC is viewed.

Thanks Mihailo!


When an ethernet connection is active, the wifi connection stops working

With Ethernet+WiFi (wlp1s0 addresses in use for proxy):
curl -x socks5://<IP_ADDRESS>:1080 http://api.ipify.org
(hangs)

With WiFi only (wlp1s0 addresses in use for proxy):
curl -x socks5://<IP_ADDRESS>:1080 http://api.ipify.org
85.XX.XX.XX

With Ethernet+Wifi (eno1 addresses in use for proxy):
curl -x socks5://<IP_ADDRESS>:1080 http://api.ipify.org
84.XXX.XXX.XXX

Using socks4 with any configuration results in curl: (97) Recv failure: Connection reset by peer.
Running on Arch Linux, have ethernet and wifi. Is this a kernel limitation or something wrong with rust's networking/this program?

Doesn't seem to be a limitation of the kernel:
curl --interface eno1 http://api.ipify.org
84.XXX.XXX.XXX
curl --interface wlp1s0 http://api.ipify.org
85.XX.XX.XX

cURL inhibits this behaviour too (only with specific ip, by interface name works as before):
curl --interface <IP_ADDRESS> http://api.ipify.org
84.XXX.XXX.XXX
curl --interface <IP_ADDRESS> http://api.ipify.org
(hangs)

Fixed myself. Will create PR soon.

I wanted to use your solution because I thought I might have the same problem as you.
So I compiled your source and :

It doesn't work on Windows because you're using a function that isn't implemented on Windows, so I wouldn't recommend @alexkirsz to accept the PR #27 (You can use Conditional compilation to make it a Linux-only feature.)


display of

Dear Axelle,
It seems that the display conventions for <space> are not yet listed on https://erc-dharma.github.io/editorial.
I notice that the display of <space> is not consistent depending on whether @quantity is encoded. See screenshot.

I suppose it will be better to display  <space type="descender"> consistently.
@danbalogh : any suggestion?

Dear Arlo,
I'm not sure I understand the problem correctly, but I believe you are saying that the code behind your screenshot involves <space type="descender" quantity="2" unit="character"/> If so, then this is a problem with your encoding, not with the display.
The EGD §4.3.5 says, "imposed spaces must always be encoded without further attributes, i.e. never use @quantity and @unit to encode their size".
We agreed on this long ago and I'd like to keep it that way. The reason we're encoding imposed spaces is that they interrupt the flow of text - but their size in number of characters is not relevant, since they are not space left vacant for subsequent inscribing. The size and shape of imposed spaces is a layout detail that can be described in human-readable terms in the metadata.

thanks Dan! it was en encoding error in Chloé's file.


Include ability to use CudnnLSTM for max GPU utilization

I started making a patch for CudnnLSTM support but in its current state it's quite a mess. However, I can say that step_size dropped from 0.64 to 0.23s in my testing and CPU usage is down from 1100% to 180%. GPU usage is up from 20-70% to 80-100%. I will continue trying to improve and clean up the patch and try to implement everything so it's fully usable, and others are welcome to help as well. Used master branch and ran with TensorFlow 1.5.
Also, I only tried it with one GPU so far. As far as I can tell the model is working properly to some extent. Only encoder part is converted and only for gnmt, but this yielded good performance increases. Didn't check out the decoder yet. For other areas of the code where LSTM is used it may fall back to CudnnCompatibleLSTMCell which doesn't seem to help performance.
Zip file contains params file I used, and the patch.
cudnn_lstm_patch_xtknight_alpha000.zip
UPDATE: further patching will be done on my fork's cudnn branch here:  https://github.com/xtknight/nmt/tree/cudnn

Hi,
I would like to ask how's progress with that patch? As far as i can read, improvements look awesome.
Unfortunately I can't help with that, but if it works, will save me a lot of time.
Regards,
Daniel

Hello,
The patch seems to work for the encoder and everything does run, and it is faster. As far as I can tell there are no issues.
However, for further speed increase, the decoder needs "Attention". Based on my research, attention is not currently possible with CuDNN because the CuDNN framework fuses the entire LSTM into something that can be thought of as "one GPU operation". That means we don't have access to intermediate states and can't implement the attention mechanism. Therefore, I was not able to change the decoder part. It turns out that most of the speed advantage of replacing normal LSTM with CudNNLSTM comes, in fact, from this ability of CuDNN to fuse the LSTM steps into this one operation.

First of all, thank you for your response.
So for my understanding decoder part remains untouched, so attention mechanism can be used still.
Do you think you could implement your patch for bi-directional encoder as well? I would really like to do that, if I only could. :) That will really help us with our project using NMT a lot.


Add support for OpenSSL, improve base image and build script

The PR consists of 2 commits.
The first one is pretty straightforward, just adds an environment variable that allows building the openssl-sys crate.
The second one is a major refactor of the build script, and the base image (rust). The reasoning for such changes consists of:

Use the container itself as the build cache, dismissing the volume setup.
The container is a stateful component, and as such is capable of caching build artefacts. We just need to start/stop instead of delete/create.

Have the container run as root, allowing dependency installation after the base image.
Some projects require extra dependencies, commonly libfl-dev and libsqlite3. With the container running as root, it's easier to run the installation command for such dependencies, without having to build a new base image.

Remove sudo calls, allowing docker cp to setup the correct file ownership.
Without sudo, docker cp adjusts the files' ownership automatically. This implies the user must be in the docker group, which he should be in anyway.

Remove TTY allocation for container, allowing piping scripts into the container.
As the container will be mainly used in build scripts, having a nice scripting interface is preferred over having a nice interactive interface. Unfortunately, AFAIK, one can only have one with docker containers.

Thanks for this. I've seen the start/stop container approach elsewhere and personally I'm not a huge fan of it. It feels a little too stateful. However, I see that in this case it's not all that different from the volumes approach I was already doing.
The rest of the changes seems fine. One minor thing that I would like changed is you changed all the docker instructions to lowercase. I would like them to remain uppercase as I think this is the standard format and is what is used in the Docker documentation. https://docs.docker.com/engine/reference/builder/#format

Thanks for the tips. I've reset the docker instructions to upper case, please let me know if you have any other suggestions.

Thanks!


Discover only blocks with events

Resolves L2B-2864
Issues
The issue arose when trying to synchronize Arbitrum's changelog using an EventIndexer, which signals when to run discovery based on emitted events indicating a change in contract configuration. The DiscoveryIndexer was designed to trigger discovery on the earliest event in the list. However, a problem was encountered due to the use of UnixTimestamps to represent safeHeight. In Arbitrum, multiple blocks can have the same timestamp. As a result, when discovery was run on block 7934557 and its timestamp was marked as completed, it overlooked events in blocks 7934560 and 7934564 because they shared the same timestamp. This issue underscores the challenges of using timestamps as heights in the UIF framework. It's suggested that this approach be reconsidered for future projects to prevent unforeseen issues. The underlying problem was a bug introduced unintentionally, but the framework could potentially be improved to prevent such errors.

I'm only afraid a bit about discovery cache, since now we may launch few discoveries 'at once'

We have a promise.all anyway in the handlerExecutor inside discovery, but a fair point.

I'm only afraid a bit about discovery cache, since now we may launch few discoveries 'at once'

We have a promise.all anyway in the handlerExecutor inside discovery, but a fair point.


animationend

This  Feature help to understand the support of animation end callback

This should already be covered by http://caniuse.com/#feat=css-animation

Yup. Just added it as keyword.

Yup. Just added it as keyword.


[WIP] Allow to disable selected providers

Allow users or backend to 'disable' a provider:

Disallow inventory\metric\event collection
Disable a provider prior to destroy in order to prevent workers from running tasks for it

@blomquisg @durandom @Fryguy @cben @moolitayer
@miq-bot add_label wip

@dclarizio Please review

@zeari Along the lines of @Fryguy's comment

I'm pretty sure you're going to need an enable_ems, or the user is out of luck 😆

Will there be a way to see which providers are enabled/disabled?  Perhaps a column at least in the list view.
Also, can you add tests for this new action?
@h-kataria can you review the code and suggest some tests?  Thx, Dan

Thinking, we could still merge this if it was enabled by a feature toggle. But I dont know if we have means for this...

But I'm not sure if we should implement this UI first

@durandom @dclarizio  So lets hold off with the UI here until we define what disable actually does. In general, if the user would have the ability to disable the provider, this is how i would imagine it - similar to refresh.

cc @simon3z, this is a solution for https://bugzilla.redhat.com/show_bug.cgi?id=1369359

Please split the UI parts of this PR into https://github.com/ManageIQ/manageiq-ui-classic

The bug was closed: https://bugzilla.redhat.com/show_bug.cgi?id=1369359
But maybe disabling a provider is a valid use-case we want to support. What do you think @Loicavenel?

@simon3z Yes, this is a valid use case, this will be useful when running demo you can disable provider you are not demoing, when QE/support doing testing they can isolate a provider and we have couple of customers cases where Amazon Provider went "Crazy" and they had to delete it.
but I have addition questions:

Related workers to the provider will be stopped but what I can still do in UI? Browsing ? run actions?
When I enable it again, we will have to collect Inventory but also metrics gaps, not sure all providers can do it.

but I have addition questions:

Related workers to the provider will be stopped but what I can still do in UI? Browsing ? run actions?

@Loicavenel I assume this will be consistent with the other providers. I think you should be allowed to browse but not run actions.

When I enable it again, we will have to collect Inventory but also metrics gaps, not sure all providers can do it.

@Loicavenel this goes into a wider scaling discussion. What is the threshold of time for us to close the gaps?
Of course closing gaps is good but if the Provider is down for a week closing the gaps means collecting hundred of thousands of data points per object (Containers, Pods, Nodes).
The Provider being disabled is just a private case of that: if it's disabled for a reasonable amount of time we'll close the gaps, otherwise we won't.
We just have to decide what's the reasonable amount of time.

@simon3z So, the question is how long time we go back in time to collect metrics? It is configurable?

@Loicavenel in production environments, having a downtime of a day is intolerable for most of the cases I suppose.
So maybe something in a range of 1-2 days could be a good default[1] and feasible to think that we may be able to close those gaps without crashing the workers (just a guess of course).
[1] Reasoning here is that if you're down for more than a day you have bigger problems than metrics not collected.
Configurable in the advanced settings seems a good compromise.

And on the UI part, I don't think there is anything done at that time.. correct?

Correct.

@Loicavenel for completeness it's worth mentioning that it should be the infrastructure duty to identify that on large gaps the collection should be split in multiple jobs with a max interval collection. E.g. "Am I not collecting metrics since 1 day? OK, let's close the gap by scheduling many small collection of max 15 minutes data-points".

@simon3z We should bring this as a performance topic and try to solve it for all providers. We had the issue with other providers.

@simon3z @Loicavenel Closing in favor of #14675


chore(master): release 1.1.55

:robot: I have created a release beep boop
1.1.55 (2023-09-04)
Miscellaneous

deps: update dependency wayofdev/cs-fixer-config to v1.2.51 (d3e4445)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-webhook-client/releases/tag/v1.1.55 :sunflower:


[DOC] Security Analytics - integration with Data Lake

What do you want to do?

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
There is a new feature on security analytics coming out in 2.6: Support cohesive integrated experience between observability and security event log data; Support integration with Amazon Security Data Lake
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
samenp (Praveen) [Praveen Sameneni] is the SDM.

Based on a message from the SDM, this update will not go into 2.6 but will be tied to another enhancement in a future release.

@praveensameneni Is this issue possibly covered by updates in issue #4500 : "Update Mappings to support Open Cybersecurity Schema Framework (OCSF)"? If yes, I'll close this one. Thanks.

Data Lake is still on the roadmap, but the date for the integration is TBD. Closing this for now.


How to integrate locally deployed models, such as the Qwen model deployed with vLLM, with an AI gateway?

What Happened?
I would like to use AI Gateway to manage a series of locally deployed models, but I'm not sure how to proceed.
What Should Have Happened?
No response
Relevant Code Snippet
No response
Your Twitter/LinkedIn
No response

If your local models expose an api endpoint that is compatible with any of the already integrated providers, you can use them like this https://docs.portkey.ai/docs/integrations/llms/byollm otherwise you can write your own integration within the gateway (would love to have your contributions) if you have a custom endpoint

So instead of routing to the local model API interface, you have to write your own code to integrate your model API according to the provider's architecture in the project

So there is no way to route to the local model API interface,
i had to write my own code to integrate my model API according to the provider's architecture in the project

This means that it can not be routed to an API other than this,
for example, the COMFYUI API can not be invoked through this integration

Correct! If ComfyUI exposes endpoints like /images/generations (from here) though, you could absolutely route to it using Portkey.
I'll explore Portkey's integration with ComfyUI and see what's possible!

@AI3721 we also have the concept of "Gateway for other APIs" where you can just use Portkey as a proxy to call any target provider you want. Would that be useful?

@AI3721 If your local model has an OpenAI compliant endpoint, you can use it without writing an integration.
Here's an example with ollama: https://docs.portkey.ai/docs/integrations/llms/ollama

Okay, I get it. I think I might have to write my own integration,
thank you very much for your answers


Server works Successfully on iPokeGo!

Hi guys,
I have tried all days and successfully install the iPokeGo on my iphone and set up the server which is deployed by myself on Amazon AWS. Below is a brief instruction of what I did today. As it is 2:00 Germany, sorry I cannot write down in detail.

We should install iPokeGo app on our iPhone. There are video instructions and text instructions. It is not difficult.

We should deploy a Free Windows Server on Amazon AWS. Everybody can register a free server on AWS with a Credit card. Please be aware of what kind of server you want. Only choose the free version if you do not want to pay for anything.

Follow the video instruction like this.
https://www.youtube.com/watch?v=RJKAulPCkRI
Install the python, pip, latest version of Pokemon Go Map V2.0. (I did not choose develop branch. Because there is no credentials file in config fold in develop branch.)
When you are going to run the server, be sure that the host address is the internal IP(Private IP) address of the server!

Disable all the Firewalls in Windows Server! At least two firewalls you need to disable.

Becareful that your server is without any protection. Do use the server on own phone.

Good luck!
Yueyang

Another possibility, spin up an AWS instance of ubuntu or similar, install the docked engine, build a Pokémon go map image, spin up a container. That's what I did. I just spin up a new container on a different port when a buddy wants me to host their map. Super easy!

The Deploy with heroku is the easiest option, have you tried the button? It worked out of box for me, just set the config variables and go. Only downside to that is it will have a spin up time after 30 mins of inactivity for free accounts.

Hello, i deployed successfully with heroku, but when i try it, no pokemon, pokestop, pokegym in the map? Did this server include databse for pokemon, pokestop, pokegym?pokemon, pokestop, pokegym

Hi,
yes, I can see everything, Pokemon, Gyms. I show it in the picture.
But I am sorry I did not do it in Heroku. So I do not know the possible solution for you. Yesterday, I did it in a AWS Win Server. And today, I deployed one on AWS ubuntu. Both of them works. I can connect the map from both PC browser and iOS app.
Good luck,Yueyang
Date: Thu, 28 Jul 2016 03:39:51 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [istornz/iPokeGo] Server works Successfully on iPokeGo! (#66)
Hello, i deployed successfully with heroku, but when i try it, no pokemon, pokestop, pokegym in the map? Did this server include databse for pokemon, pokestop, pokegym?pokemon, pokestop, pokegym
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey buddy, i have managed to get it running on my IP address and can access it from my phone browser but i cant get it to work inside the app (tried it using home address with 4G in Iphone Browser)
what should i be doing to get it to work in the app?

Hi,
It is really strange.. You should add the "http://" before the ip address in the app. Did you do that?
And the port number is also needed to put at the end of the IP address.
Date: Fri, 29 Jul 2016 00:15:12 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [istornz/iPokeGo] Server works Successfully on iPokeGo! (#66)
Hey buddy, i have managed to get it running on my IP address and can access it from my phone browser but i cant get it to work inside the app (tried it using home address with 4G in Iphone Browser)
what should i be doing to get it to work in the app?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Can somebody give me an example of what to put into the "Server name" and "Server" field (and anything other fields if they are necessary)? I have tried Server name = "<IP_ADDRESS>:12345" and Server = "http://pool-123-45-67-89.phlapa.fios.verizon.net" and a few variations of inputting this info, but nothing is working. How should I be inputting this info in?


Native library loading error

Following update to 1.0.0 I still see an error like on 0.8.0 (see #9 for details)
[info] Exception encountered when attempting to run a suite with class name: com.gu.contentapi.porter.integration.flexible.ZstdCompressionTest *** ABORTED ***
[info]   java.lang.UnsatisfiedLinkError: com.github.luben.zstd.ZstdOutputStream.recommendedCOutSize()J
[info]   at com.github.luben.zstd.ZstdOutputStream.recommendedCOutSize(Native Method)
[info]   at com.github.luben.zstd.ZstdOutputStream.<clinit>(ZstdOutputStream.java:29)
[info]   at com.gu.contentapi.porter.integration.ZstdCompression$.compress(Compression.scala:51)
[info]   at com.gu.contentapi.porter.integration.flexible.ZstdCompressionTest$$anonfun$1.apply$mcV$sp(ZstdCompressionTests.scala:12)
[info]   at com.gu.contentapi.porter.integration.flexible.ZstdCompressionTest$$anonfun$1.apply(ZstdCompressionTests.scala:10)
[info]   at com.gu.contentapi.porter.integration.flexible.ZstdCompressionTest$$anonfun$1.apply(ZstdCompressionTests.scala:10)
[info]   at org.scalatest.Transformer$$anonfun$apply$1.apply$mcV$sp(Transformer.scala:22)
[info]   at org.scalatest.OutcomeOf$class.outcomeOf(OutcomeOf.scala:85)
[info]   at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
[info]   at org.scalatest.Transformer.apply(Transformer.scala:22)

I will try tomorrow to test with a version published locally.

Thanks for opening the issue. I will look again what may be the difference. I am using travis-ci to build the mac os native object: https://travis-ci.org/luben/zstd-jni/jobs/157779438
BTW, if a local build works, can you give me the output of:
~/zstd-jni(branch:master) » ls -Rl target/classes

to see what may be the difference.
Thanks in advance helping me debug it.

I think I found the problem - I was packaging a older version of the dylib. Fixing it now and will re-upload the release shortly

pushed to maven, can you test it, it will land on the index in 2-3 hours.

@luben thanks, I have just tested it (adding changing()to my dependency in sbt to redownload the jar) and it works fine now 👍
[info] ZstdCompressionTest:
[info] - zstd should compress the content
[info] - ztsd and then unzstd should return the same content


Update httpRequestManager method declaration

Update httpRequestManager method declaration

[x] Fix 1 : Remove the auto definition of argument, e.g.:  requestType : HttpRequestType = "GET"

public async send(url : string, requestType : HttpRequestType = "GET", headers : Headers = new Headers(), body : string = "")

This default parameter allowed caller not to explicitly write GET, which reduces readability and is more error-prone, thus I removed it.


hdl._ir: Remove all support for fragment flattening.

Fixes #823

Does this fix any other bugs?

Does this fix any other bugs?

Didn't find any


It takes a very long time to build a map

#1193 I already asked a similar question.
[ x] Question
[ ] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
Description and/or steps/code to reproduce the problem
Hello! Thanks for your work!
Is this the problem only with me?
This is problem -> https://drive.google.com/file/d/1R9LnZ8n1HWngGeD8Fx2_r537q-AD5RlM/view?usp=drivesdk
My application is also long too ..
For the test I used this application: https://play.google.com/store/apps/details?id=org.osmdroid&hl=ru
Environment
If it's a bug, version(s) of android this affects:
I checked for 7.1 and 9.0
Version of osmdroid the issue relates to:
6.1.0

I guess you're using the default tiles (openstreetmap). Do you still find it slow with other tile sources, like opentopo?

thats about what is expected due to osm's tile policy. we can definitely make it faster but they do not want us to do so. It is free after all. you can either use another tile source or host your own server

I guess you're using the default tiles (openstreetmap). Do you still find it slow with other tile sources, like opentopo?

Using another source becomes faster.

thats about what is expected due to osm's tile policy. we can definitely make it faster but they do not want us to do so. It is free after all. you can either use another tile source or host your own server

Yes, we will soon post our OSM map source.
I will definitely report the results! I hope the speed will be like in google maps)


refactor(eds/store): store_test.go cleanup

Overview
Self explanatory

Codecov Report

Merging #1538 (9b8a8c4) into main (0ab5df6) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1538      +/-   ##
==========================================
+ Coverage   55.06%   55.09%   +0.02%
==========================================
  Files         211      211
  Lines       12953    12953
==========================================
+ Hits         7133     7136       +3
+ Misses       5093     5091       -2
+ Partials      727      726       -1

Impacted Files
Coverage Δ

header/core/listener.go
52.83% <0.00%> (-5.67%)
:arrow_down:

share/ipld/get.go
93.41% <0.00%> (+1.23%)
:arrow_up:

share/eds/byzantine/bad_encoding.go
69.00% <0.00%> (+3.00%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[TVMC] Global pass context for compile and tune

Comes as a followup from conversations in #13216. By making the pass context a global value for both compile and tune commands, we can ensure the pass context is exactly as the user expected and also test components such as convert_graph_layout under a pass context suitable for testing (e.g. add instruments). With this change, it becomes the users responsibility to ensure the PassContext they select is suitable for the passes that will be run. By default, opt_level remains as 3 so current workflows that do not alter the pass context from the command line / TVMC Python API should not be affected.

also cc @leandron @ekalda

Thanks @ekalda @lhutton1


 I suggest to add this to all subconfigs, to avoid the same issue to happen.

All windows, including NewGame, now set their ZPos to 1 when accepting handshakes (e.g. when opened up or when a new game is being inspected) as of a recent commit.

Perfect, thanks!


How to show which track is playing

When I start playing the first track on a list of several to play, the track is highlighted.  However, when play continues to the next track on the list, the first track remains highlighted, not the track currently playing.  In my older version of VUPlayer, I could tell at a glance which track I was hearing because that track on the list was always highlighted.   I can't find a setting that would make this happen.

Hi,
Yes, for the next version, I am hoping to add an option to use the old VUPlayer behaviour of 'following' the current selection during playback (and selecting the currently playing track in the list).
Thanks,
James

Great!  Thanks for letting me know.
Stephen
From: James Chapman @.>
Sent: October 12, 2023 9:51 AM
To: jfchapman/VUPlayer @.>
Cc: rocky1913 @.>; Author @.>
Subject: Re: [jfchapman/VUPlayer] How to show which track is playing (Issue #38)
Hi,
Yes, for the next version, I am hoping to add an option to use the old VUPlayer behaviour of 'following' the current selection during playback (and selecting the currently playing track in the list).
Thanks,
James
—
Reply to this email directly, view it on GitHubhttps://github.com/jfchapman/VUPlayer/issues/38#issuecomment-1759993934, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDDVRZ674DPSKRTKWAUKFX3X7ANXXANCNFSM6AAAAAA5XGDRVQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Hi,
The latest 4.18 release now has a 'Follow Track Selection' playback mode, which mimics the behaviour of legacy application versions. Specifically (from the wiki), when reaching the end of the currently playing track:

If the currently playing track is selected, playback will continue with the next track in the playlist, and the next track will be selected.
If the currently playing track is not selected, playback will continue with the next selected track in the currently displayed playlist.
If no tracks are selected, playback will stop.

This is about as close as I could get to the old behaviour, bearing in mind the legacy application versions only supported a single playlist. This mode could also be used to queue up the next track from another playlist, so that might prove useful in some cases.
Thanks,
James

Thank you so much! I’ve tried it, and it does exactly what I need.  What a nice Christmas present!
Stephen Peithman
From: James Chapman @.>
Sent: December 9, 2023 6:16 AM
To: jfchapman/VUPlayer @.>
Cc: rocky1913 @.>; Author @.>
Subject: Re: [jfchapman/VUPlayer] How to show which track is playing (Issue #38)
Closed #38https://github.com/jfchapman/VUPlayer/issues/38 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/jfchapman/VUPlayer/issues/38#event-11200667341, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDDVRZY65VOIBHWCPLF6ZQTYIRXBPAVCNFSM6AAAAAA5XGDRVSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGIYDANRWG4ZTIMI.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


Android O support

Due to new Android O background policies, the service no longer works properly on API 26.
Linked to: https://github.com/eclipse/paho.mqtt.android/issues/195

so how can i use it in an android Oreo device?