text:
High CPU and Memory Load on single node k3s cluster

HI,
i have an ubuntu 20.02 machine, which has k3s installe. After installing rancher, the memory and cpu consumption of the k3s service is skyrocketing.
versions:
"Ubuntu 20.04.1 LTS"
- export INSTALL_K3S_VERSION=v1.19.2+k3s1; curl -sfL https://get.k3s.io | sh -
PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
715 root      20   0 4148060   3.0g  52692 S 100.0  38.9  30:03.70 k3s-server

the server running the k3s is a normal x86 vserver with 4 cores and 8 gb ram.
 # install k3s
    - export INSTALL_K3S_VERSION=v1.19.2+k3s1; curl -sfL https://get.k3s.io | sh -

    # install helm
    - curl https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash
    - starting=true ;while $starting ; do kubectl get ns && starting=false;sleep 1;done

    # install cert-manager
    - kubectl create namespace cert-manager
    - helm repo add jetstack https://charts.jetstack.io
    - helm repo update
    - KUBECONFIG=/etc/rancher/k3s/k3s.yaml helm install cert-manager jetstack/cert-manager --wait --namespace cert-manager --version v1.0.2 --set installCRDs=true

    # install rancher
    - helm repo add rancher-latest https://releases.rancher.com/server-charts/latest
    - helm repo update
    - kubectl create namespace cattle-system
    - KUBECONFIG=/etc/rancher/k3s/k3s.yaml helm install rancher rancher-latest/rancher  --wait --namespace cattle-system --set replicas=1

● k3s.service - Lightweight Kubernetes
     Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2020-10-12 09:58:20 CEST; 10min ago
       Docs: https://k3s.io
    Process: 2277 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
    Process: 2279 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
   Main PID: 2280 (k3s-server)
      Tasks: 191
     Memory: 3.3G

any idea what could cause the high load?
kind regards
Philipp

I'm not able to reproduce this on a local server. I do see that the CPU and memory utilization increase and use ~2 cores while Rancher is installing, but it settles down once all the pods are running. The only difference is that I haven't used LetsEncrypt since my dev node is not exposed to the internet.
install:
echo "y" | ufw enable
ufw allow ssh
ufw allow http
ufw allow https
ufw default deny incoming
ufw default allow outgoing
ufw allow from any to 10.0.0.0/8
ufw allow from 10.0.0.0/8 to any

export INSTALL_K3S_VERSION=v1.19.2+k3s1; curl -sfL https://get.k3s.io | sh -

curl https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash
helm repo add jetstack https://charts.jetstack.io
helm repo add rancher-latest https://releases.rancher.com/server-charts/latest
helm repo update

kubectl create namespace cert-manager
KUBECONFIG=/etc/rancher/k3s/k3s.yaml helm install cert-manager jetstack/cert-manager --wait --namespace cert-manager --version v1.0.2 --set installCRDs=true

kubectl create namespace cattle-system
KUBECONFIG=/etc/rancher/k3s/k3s.yaml helm install rancher rancher-latest/rancher  --wait --namespace cattle-system --set replicas=1 --set hostname=ubuntu01.lan.khaus

kubectl get pods -A:
NAMESPACE                 NAME                                       READY   STATUS      RESTARTS   AGE
kube-system               metrics-server-7b4f8b595-pgb4z             1/1     Running     0          13m
kube-system               local-path-provisioner-7ff9579c6-cbj2h     1/1     Running     0          13m
kube-system               coredns-66c464876b-bq6z6                   1/1     Running     0          13m
kube-system               helm-install-traefik-cvw8c                 0/1     Completed   0          13m
kube-system               svclb-traefik-tnmt6                        2/2     Running     0          13m
kube-system               traefik-5dd496474-zdp4t                    1/1     Running     0          13m
cert-manager              cert-manager-cainjector-5f988f74c6-jmllv   1/1     Running     0          11m
cert-manager              cert-manager-57b65b7fc-v5w5f               1/1     Running     0          11m
cert-manager              cert-manager-webhook-7cf554f879-tdkzk      1/1     Running     0          11m
cattle-system             rancher-7797675cb7-4szmj                   1/1     Running     0          10m
fleet-system              gitjob-68cbf8459-hcn8w                     1/1     Running     0          8m43s
fleet-system              fleet-controller-5db6bcbb9-prf9l           1/1     Running     0          8m43s
cattle-system             helm-operation-9dllc                       0/2     Completed   0          8m54s
cattle-system             helm-operation-n6x4z                       0/2     Completed   0          8m32s
rancher-operator-system   rancher-operator-6659bbb889-hqfrk          1/1     Running     0          8m25s
cattle-system             helm-operation-2sdrn                       0/2     Completed   0          8m27s
fleet-system              fleet-agent-7584f654d9-sg2kc               1/1     Running     0          8m10s
cattle-system             rancher-webhook-6f69f5fd94-qjdvx           1/1     Running     0          8m10s
cattle-system             helm-operation-2kxhq                       0/2     Completed   0          8m12s
cattle-system             helm-operation-h5tqz                       0/2     Completed   0          8m3s

top:
    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
   1183 root      20   0 2412884   1.6g  92228 S  13.0  20.2   3:29.67 /usr/local/bin/k3s server
   4174 root      20   0 1025056 303564  71080 S   1.0   3.8   0:13.73 rancher --http-listen-port=80 --https-listen-port=443 --audit-log-path=/var/log/auditlog/ran+
   1198 root      20   0  893332 148572  71228 S   0.3   1.8   0:36.39 containerd
   3401 sysadm    20   0  806308  94092  22756 S   0.3   1.2   0:03.06 /app/cmd/cainjector/cainjector --v=2 --leader-election-namespace=kube-system
   5023 root      20   0  759568  78972  38532 S   0.0   1.0   0:02.59 fleetcontroller
   6715 root      20   0  758972  74308  36792 S   0.3   0.9   0:01.18 fleetagent

Can you confirm the version you're running? The process name (k3s-server) in your top output is not what I would expect to see. What do you get from kubectl get nodes -o wide and kubectl get pods -A

Hi @brandond , Hi @philipp1992 . I have the same issue.
top:
top - 21:58:36 up 48 days,  5:17,  1 user,  load average: 6.31, 6.68, 6.91
Tasks: 168 total,   1 running, 118 sleeping,   0 stopped,   0 zombie
%Cpu(s):  6.2 us,  1.2 sy,  0.0 ni, 68.9 id, 23.6 wa,  0.0 hi,  0.2 si,  0.0 st
KiB Mem :  4038784 total,   116712 free,  2991612 used,   930460 buff/cache
KiB Swap:  4038652 total,  3455996 free,   582656 used.  1275144 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
  560 root      20   0 1258400 1.061g  81772 S  24.6 27.5   7:58.63 k3s-server
17432 mysql     20   0 5089688 259096   6660 S   6.6  6.4   2507:05 mysqld

kubectl get nodes -o wide :
NAME       STATUS   ROLES    AGE   VERSION        INTERNAL-IP     EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION       CONTAINER-RUNTIME
mynode   Ready    master   48d   v1.18.9+k3s1   192.168.0.2   <none>        Ubuntu 18.04.4 LTS   4.15.0-112-generic   containerd://1.3.3-k3s2

kubectl get pods -A
NAMESPACE           NAME                                                       READY   STATUS      RESTARTS   AGE
kube-system         metrics-server-7566d596c8-2pksv                            1/1     Running     0          48d
kube-system         svclb-traefik-j58rf                                        2/2     Running     0          48d
cattle-prometheus   prometheus-operator-monitoring-operator-5bb7ddcd65-lwf9c   1/1     Running     0          48d
cattle-system       cattle-cluster-agent-7cf8c7bb67-7jtns                      1/1     Running     0          25d
cattle-system       cattle-node-agent-t8gnn                                    1/1     Running     0          25d
cattle-system       system-upgrade-controller-585f9d68f9-nd6hf                 1/1     Running     0          51m
cert-manager        cert-manager-7cb75cf6b4-w6bm6                              1/1     Running     1          48d
kube-system         coredns-7944c66d8d-qfrtl                                   1/1     Running     0          48d
cert-manager        cert-manager-webhook-7c75b89bf6-m9bcj                      1/1     Running     0          48d
kube-system         traefik-758cd5fc85-5s68b                                   1/1     Running     0          48d
kube-system         local-path-provisioner-6d59f47c7-dtcbs                     1/1     Running     5          48d
cert-manager        cert-manager-cainjector-759496659c-hnlmk                   1/1     Running     5          48d
cattle-system       rancher-5745c55b85-6wrgk                                   1/1     Running     0          25d
cattle-system       rancher-5745c55b85-wcdmp                                   1/1     Running     1          25d
cattle-system       rancher-5745c55b85-hc2v5                                   1/1     Running     0          25d
kube-system         helm-install-traefik-gtnm2                                 0/1     Completed   0          47m

@risayew 25% of one core and ~1GB of RAM is not unusual for k3s, especially one hosting Rancher, which is pretty hard on the apiserver due to all the custom resources.

@risayew

Thanks for the answer. And what do you think about load averages? They increase with the time. I have seen even >12. I have such values because the kubernetes was just upgraded several minutes ago to 1.18.9

Which version were you using before?
Am I crazy if I say that I didn't have any high CPU and memory usage on k3s 1.17?

@unixfox Thats interesting. The previous version of the Kubernetes was 1.18.8.
On another rancher setup i manage 4 -Nodes Cluster too and have the same rancher version 2.4.8.
And on that 4-Nodes (more or less same specs) Cluster with Kubernetes v1.16.15 i observe way lower cpu/load averages.
4 Nodes Cluster on v1.18.9

VS
4 Nodes Cluster on v1.16.15

May be CPU utilization does not have anything to do with k3s or rancher, but with Kubernetes version.

I encountered this problem too, repeated created/deleted resources(deployment, job, etc), memory increased continuously.
if I use hostpath volume mount the database file to hostpath, k3s will consume a lot of disk space, remaining 20K disk. then memory increase crazily
k3s version: container image  rancher/k3s:v1.16.14-k3s1

Additionally i observe too often ETCD downs and leader changes. Somebody has an idea, where should i start to look?

@risayew excessive storage latency is the usual cause of etcd leader changes.

I have noticed this before on longer-running clusters, but for me was indicative of something else wrong going on in my cluster, most often this being a pod that was stuck in a perpetual CrashLoopBackoff state. I've tried over the last few days to reproduce this by running a continuous script that would add a few, deployments, pods, and services and then delete them every few seconds, but still did not notice any increase in CPU or memory.
I was using 2cpus, 4gb ram, 10gb disk and saw my node consistently utilizing approx. 13% cpu and 41% mem with minor fluctuations. These numbers were grabbed from the scenario using v1.19.2+k3s1, with rancher deployed on the cluster.

Looks like this bug has been fixed with https://github.com/rancher/kine/commit/3faf3a7028014a5baf96454b2b3fe04984ebc69f in kine 0.5.1, hasn't it?

Experiencing the same issue myself on a system with 1GB memory.
Events:
  Type     Reason               Age                 From        Message
  ----     ------               ----                ----        -------
  Normal   Starting             36m                 kube-proxy  Starting kube-proxy.
  Warning  SystemOOM            36m                 kubelet     System OOM encountered, victim process: node, pid: 472672
  Warning  SystemOOM            36m                 kubelet     System OOM encountered, victim process: node, pid: 279787
  Warning  SystemOOM            36m                 kubelet     System OOM encountered, victim process: node, pid: 187226
  Warning  SystemOOM            36m                 kubelet     System OOM encountered, victim process: node, pid: 622867
  Warning  SystemOOM            36m                 kubelet     System OOM encountered, victim process: node, pid: 358468
  Normal   Starting             36m                 kubelet     Starting kubelet.
  Warning  SystemOOM            36m                 kubelet     System OOM encountered, victim process: node, pid: 572610
  Warning  SystemOOM            36m                 kubelet     System OOM encountered, victim process: node, pid: 574172
  Warning  SystemOOM            36m                 kubelet     System OOM encountered, victim process: node, pid: 574653
  Warning  SystemOOM            36m                 kubelet     System OOM encountered, victim process: node, pid: 575095
  Warning  InvalidDiskCapacity  36m                 kubelet     invalid capacity 0 on image filesystem
  Warning  SystemOOM            36m (x14 over 36m)  kubelet     (combined from similar events): System OOM encountered, victim process: node, pid: 1005670
  Normal   Starting             19m                 kube-proxy  Starting kube-proxy.
  Normal   Starting             19m                 kubelet     Starting kubelet.
  Warning  SystemOOM            19m                 kubelet     System OOM encountered, victim process: node, pid: 621313
  Warning  SystemOOM            19m                 kubelet     System OOM encountered, victim process: node, pid: 187226
  Warning  SystemOOM            19m                 kubelet     System OOM encountered, victim process: node, pid: 279787
  Warning  SystemOOM            19m                 kubelet     System OOM encountered, victim process: node, pid: 358468
  Warning  SystemOOM            19m                 kubelet     System OOM encountered, victim process: node, pid: 472672
  Warning  SystemOOM            19m                 kubelet     System OOM encountered, victim process: node, pid: 572610
  Warning  SystemOOM            19m                 kubelet     System OOM encountered, victim process: node, pid: 574172
  Warning  SystemOOM            19m                 kubelet     System OOM encountered, victim process: node, pid: 574653
  Warning  SystemOOM            19m                 kubelet     System OOM encountered, victim process: node, pid: 575095
  Warning  InvalidDiskCapacity  19m                 kubelet     invalid capacity 0 on image filesystem
  Warning  SystemOOM            19m (x14 over 19m)  kubelet     (combined from similar events): System OOM encountered, victim process: node, pid: 1005670

We've added some resource profiling figures to our documentation feel free to take a look:
https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/resource-profiling/

Hey, This "bug" seems to be the most relatable one to my issue. Since upgrading to >=1.21 .0 the cpu usage on my raspberry is ~20% higher. I have tried up to v1.21.2+k3s1 but eventually rolled back to v1.20.8+k3s1. I'm on armv7 and I remember that there was a regression with kubernetes and the go version build for armv7 (I can't remember exactly when that was). I had that issue before and was happy when it finally dissipated with a newer version. with 1.21 the issue seems to be back. I'll attach a screenshot of the cpu usage. (The timeframes are quite large because I do not spend too much time up/downgrading).
Upgrade to 1.21:

Downgrade back to 1.20

@transacid thank you for pointing that out. I am having the same issue with v1.21.2+k3s1 deployed as a master. I have a cluster of 4 rapsberry pi 4, and the truth is that I dunno if I am experiencing this after I upgraded my master node to this version or not. The cpu load is extremely high, above 130% using the top command. I will give it a try and then posting the results

I can confirm that I've had the exact same experience as @transacid. Downgrading immediately rectified the problem.

The perf regression in 1.21 is an upstream issue, see https://github.com/kubernetes/kubernetes/issues/101989

i have same problem, But with version v1.19.4+k3s1
k3s single node (VM on proxmox), with 12 cores and 16GB RAM.
Tasks: 628 total,   1 running, 618 sleeping,   0 stopped,   9 zombie
%Cpu(s): 58.9 us, 12.5 sy,  0.0 ni, 22.9 id,  0.1 wa,  0.0 hi,  0.6 si,  5.0 st
MiB Mem :  16022.1 total,   5875.5 free,   8096.4 used,   2050.2 buff/cache
MiB Swap:      0.0 total,      0.0 free,      0.0 used.   7930.5 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  530 root      20   0 2571432   1.4g  49964 S 827.6   9.2  58021:36 k3s-server
  713 root      20   0 1090024 240376  43608 S  23.9   1.5  15813:46 containerd

I'm seeing the same CPU usage creep on a 3 node AWS t3a.small cluster (all master's w/ embedded etcd). The cluster was deployed with k3sup for the default 1.21 version of k3s.
Restarting a node would fix the CPU usage, but after about 6-12 hours, it's starting to go from a baseline of 10% up to about 15% CPU.
This cluster is running a few containers that are mostly idle, and running top seems to show that the k3s-server process is consuming the vast majority.
Also of note, most of the CPU time is actually in si or software interrupt, according to top's documentation.

@brandond that is correct. The craxy part is that cpu credits build up for a day or three, then as the CPU starts increasing over time, it starts draining them.
Its always annoyijg when reboots solve the issue.

i have same problem, But with version v1.19.4+k3s1
k3s single node (VM on proxmox), with 12 cores and 16GB RAM.

Yesterday the problem got worse, k8s api became unavailable, and an attempt to restart the k3s service repeatedly failed. (A long time until the database loads, then nothing.)
I found that the database file reached a size of 25G total, and after running a vacuum (sqlite),
db size is 4.8G and  k3s was able to run successfully.
The CPU usage is still very high, about 1000%.. reboot didn't help.  WTF 🤕

I've just done a

Fresh install of ubuntu server 20.04
Fresh install of k3s
No k8s/k3s workloads running. No other workloads, either.

I am also seeing 20% CPU usage on an intel i5. If k3s is suitable for raspberry pi level hardware, why does it need 20% constant cpu to do nothing?
Hats of for a super slick installation procedure, though!

I am experiencing the same problem on a Raspberry Pi 3B+. k3s uses so much CPU that the device is barely functional. k3s is using about 30-50% of CPU on a relatively fresh install of Ubuntu Server 20.04.3 LTS 64-bit. I can't even run any k3s commands. It just hangs.

I have similar issue. To find root cause I tried deploy with disabled all components:
k3s server \
    --disable coredns \
    --disable servicelb \
    --disable traefik \
    --disable local-storage \
    --disable metrics-server \
    --disable-scheduler \
    --disable-cloud-controller \
    --disable-kube-proxy \
    --disable-network-policy \
    --disable-helm-controller

and still got CPU load about 10%.
Disabling of metrics server has the most effect on decreasing CPU usage. (but only decrease LA to 30%)

can't find a similar issue on k0s though, wonder what they are doing differently :thinking:

Disabling of metrics server has the most effect on decreasing CPU usage. (but only decrease LA to 30%)

That's what I noticed as well. Is it expected?

authors: MrSaints a5r0n askoriy brandond henkesn moio nilbacardit26 pcgeek86 philipp1992 pletnes prandelicious rancher-max risayew technicool transacid unixfox volume-ji xavier83


text:
[release-1.23] --enable-pprof apparently incompatible with cert-manager

Backport: #6634

Validated on commit f19152cf2ae63558bc74f166f85fbc37800b3834
$ k3s -v
k3s version v1.23.16+k3s-f19152cf (f19152cf)
go version go1.19.5

Environment Details

Infrastructure

[ ] Cloud
[ ] Hosted

Node(s) CPU architecture, OS, and Version:

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Cluster Configuration:

1 server

Config.yaml:

$ cat config.yaml
write-kubeconfig-mode: 644
debug: true
token: puravida
enable-pprof: true

Testing Steps

Copy config.yaml

$ sudo mkdir -p /etc/rancher/k3s && sudo cp config.yaml /etc/rancher/k3s

Install k3s curl -sfL https://get.k3s.io | INSTALL_K3S_COMMIT=f19152cf2ae63558bc74f166f85fbc37800b3834 INSTALL_K3S_EXEC="server " sh -
Run curl -fsSL -o get_helm.sh https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
helm repo add jetstack https://charts.jetstack.io
helm repo update.
Run kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.11.0/cert-manager.crds.yaml
Run helm install cert-manager jetstack/cert-manager --namespace cert-manager --create-namespace --version v1.11.0
Once you have everything up run $ kubectl get pods -A -o wide, you should see the cert-manager namespace whit their pods / kubectl get pods -n cert-manager -o wide
Verify that  cert-manager-startupapicheck finished correctly with this flag enabled! kubectl get events -A | grep -i -e startupapicheck that everything it's ok!

Validation Results:

$ kubectl get pods -n cert-manager -o wide
NAME                                       READY   STATUS    RESTARTS   AGE   IP           NODE              NOMINATED NODE   READINESS GATES
cert-manager-cainjector-59f8d9f696-xzb8r   1/1     Running   0          11m   10.42.0.9    ip-172-31-46-13   <none>           <none>
cert-manager-6b4d84674-nz282               1/1     Running   0          11m   10.42.0.10   ip-172-31-46-13   <none>           <none>
cert-manager-webhook-56889bfc96-nnnd2      1/1     Running   0          11m   10.42.0.11   ip-172-31-46-13   <none>           <none>

$ kubectl get events -A | grep -i -e startupapicheck
cert-manager   12m         Normal    SuccessfulCreate          job/cert-manager-startupapicheck                Created pod: cert-manager-startupapicheck-88k9p
cert-manager   12m         Normal    Scheduled                 pod/cert-manager-startupapicheck-88k9p          Successfully assigned cert-manager/cert-manager-startupapicheck-88k9p to ip-172-31-46-13
cert-manager   12m         Normal    Pulling                   pod/cert-manager-startupapicheck-88k9p          Pulling image "quay.io/jetstack/cert-manager-ctl:v1.11.0"
cert-manager   12m         Normal    Pulled                    pod/cert-manager-startupapicheck-88k9p          Successfully pulled image "quay.io/jetstack/cert-manager-ctl:v1.11.0" in 4.642971047s (4.642987474s including waiting)
cert-manager   12m         Normal    Created                   pod/cert-manager-startupapicheck-88k9p          Created container cert-manager-startupapicheck
cert-manager   12m         Normal    Started                   pod/cert-manager-startupapicheck-88k9p          Started container cert-manager-startupapicheck
cert-manager   11m         Normal    Completed                 job/cert-manager-startupapicheck                Job completed

$ kubectl get node,all -A
NAME                   STATUS   ROLES                  AGE   VERSION
node/ip-172-31-46-13   Ready    control-plane,master   14m   v1.23.16+k3s-f19152cf

NAMESPACE      NAME                                           READY   STATUS      RESTARTS   AGE
kube-system    pod/coredns-5cfbb9f57c-hmdjd                   1/1     Running     0          14m
kube-system    pod/local-path-provisioner-5f8bbd68f9-k7sf5    1/1     Running     0          14m
kube-system    pod/helm-install-traefik-crd-kwdkk             0/1     Completed   0          14m
kube-system    pod/svclb-traefik-a6b313d8-r4kjg               2/2     Running     0          14m
kube-system    pod/helm-install-traefik-m4tgg                 0/1     Completed   1          14m
kube-system    pod/traefik-5cd8994cdd-sv2zf                   1/1     Running     0          14m
kube-system    pod/metrics-server-65cd754bcd-wjb8v            1/1     Running     0          14m
cert-manager   pod/cert-manager-cainjector-59f8d9f696-xzb8r   1/1     Running     0          12m
cert-manager   pod/cert-manager-6b4d84674-nz282               1/1     Running     0          12m
cert-manager   pod/cert-manager-webhook-56889bfc96-nnnd2      1/1     Running     0          12m

NAMESPACE      NAME                           TYPE           CLUSTER-IP      EXTERNAL-IP    PORT(S)                      AGE
default        service/kubernetes             ClusterIP      10.43.0.1       <none>         443/TCP                      14m
kube-system    service/kube-dns               ClusterIP      10.43.0.10      <none>         53/UDP,53/TCP,9153/TCP       14m
kube-system    service/metrics-server         ClusterIP      10.43.222.75    <none>         443/TCP                      14m
kube-system    service/traefik                LoadBalancer   10.43.209.39    172.31.46.13   80:31586/TCP,443:30120/TCP   14m
cert-manager   service/cert-manager           ClusterIP      10.43.50.8      <none>         9402/TCP                     12m
cert-manager   service/cert-manager-webhook   ClusterIP      10.43.113.186   <none>         443/TCP                      12m

NAMESPACE     NAME                                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
kube-system   daemonset.apps/svclb-traefik-a6b313d8   1         1         1       1            1           <none>          14m

NAMESPACE      NAME                                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system    deployment.apps/coredns                   1/1     1            1           14m
kube-system    deployment.apps/local-path-provisioner    1/1     1            1           14m
kube-system    deployment.apps/traefik                   1/1     1            1           14m
kube-system    deployment.apps/metrics-server            1/1     1            1           14m
cert-manager   deployment.apps/cert-manager-cainjector   1/1     1            1           12m
cert-manager   deployment.apps/cert-manager              1/1     1            1           12m
cert-manager   deployment.apps/cert-manager-webhook      1/1     1            1           12m

NAMESPACE      NAME                                                 DESIRED   CURRENT   READY   AGE
kube-system    replicaset.apps/coredns-5cfbb9f57c                   1         1         1       14m
kube-system    replicaset.apps/local-path-provisioner-5f8bbd68f9    1         1         1       14m
kube-system    replicaset.apps/traefik-5cd8994cdd                   1         1         1       14m
kube-system    replicaset.apps/metrics-server-65cd754bcd            1         1         1       14m
cert-manager   replicaset.apps/cert-manager-cainjector-59f8d9f696   1         1         1       12m
cert-manager   replicaset.apps/cert-manager-6b4d84674               1         1         1       12m
cert-manager   replicaset.apps/cert-manager-webhook-56889bfc96      1         1         1       12m

NAMESPACE     NAME                                 COMPLETIONS   DURATION   AGE
kube-system   job.batch/helm-install-traefik-crd   1/1           26s        14m
kube-system   job.batch/helm-install-traefik       1/1           27s        14m

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
[Release-1.27] Confusing log when deploying dualStack

Backport: https://github.com/k3s-io/k3s/issues/8797

Validated on release-1.27 branch with commit e3ea0ae9
Environment Details

Infrastructure

[ ] Cloud
[ ] Hosted

Node(s) CPU architecture, OS, and Version:

Linux 5.19.0-1025-aws #26~22.04.1-Ubuntu SMP Mon Apr 24 01:58:15 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
PRETTY_NAME="Ubuntu 22.04.2 LTS"
VERSION_ID="22.04"

Cluster Configuration:

1 server

Config.yaml:

write-kubeconfig-mode: "0644"
tls-san:
  - fake.fqdn.value
cluster-init: true
node-name: ip-xxx-xxx-xx-244.us-west-1.compute.internal
cluster-cidr: 2001:cafe:42:0::/56,10.42.0.0/16
service-cidr: 2001:cafe:43:0::/112,10.43.0.0/16
token: <token>
node-ip: <IPv6>,<PRIVATE IPv4>

Testing Steps

Copy config.yaml

$ sudo mkdir -p /etc/rancher/k3s && sudo cp config.yaml /etc/rancher/k3s

Install k3s
Check logs for the info
Should show both ipv4 and ipv6 IPs in the log in case of dual-stack

Replication Results:

k3s version used for replication:

k3s version v1.27.7+k3s2 (575bce76)
go version go1.20.10

$ sudo journalctl -u k3s | grep -i interface
Nov 21 18:04:01 ip-xxx-xxx-xxx-xxx k3s[21296]: time="2023-11-21T18:04:01Z" level=info msg="The interface ens5 with ipv4 address <PRIVATE IPv4> will be used by flannel"

Validation Results:

k3s version used for validation:

k3s version v1.27.7+k3s-e3ea0ae9 (e3ea0ae9)
go version go1.20.10

$ sudo journalctl -u k3s | grep -i interface
Nov 21 18:11:50 ip-xxx-xxx-xx-244 k3s[24925]: time="2023-11-21T18:11:50Z" level=info msg="Using dual-stack mode. The interface ens5 with ipv4 address <PRIVATE IPv4> and ipv6 address <IPv6> will be used by flannel"

authors: manuelbuil mdrahman-suse


text:
Missing metrics section from common values.yaml ?!?

Details
Helm chart name and version:
Issue with [common] Release v4.5.0 when working with mqtt-exporter.
What steps did you take and what happened:
Possible missing section?  mqtt-exporter section below indicates to check @default -- See values.yaml
metrics:
  # -- Enable and configure a Prometheus serviceMonitor for the chart under this key.
  # @default -- See values.yaml
  enabled: false
  serviceMonitor:
    # -- Interval at which Prometheus should scrape metrics
    interval: 30s
    # -- Timeout after which the scrape is ended
    scrapeTimeout: 10s
    # -- Additional labels for the Kubernetes `ServiceMonitor` object
    labels: {}

When I review the common/values.yaml there is nothing about metrics or serviceMonitor in it, seems like there should be.
What did you expect to happen:
Expected to see metrics section within the common values.yaml
Anything else you would like to add:
The mqtt-exporter chart, creates a service for no clear reason I could see, I assume that is for the serviceMonitor.  This seems incorrect.  a PodMonitor should be used for applications that do not require a service.  It's not clear if a PodMonitor is supported since the metrics section is missing.
When I curl against the serviceMonitor, I get data back but there is really nothing about MQTT included:
$ k get svc -n mosquitto
NAME                               TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)          AGE
mosquitto-mqtt                     LoadBalancer   10.43.57.103   192.168.10.222   1883:31162/TCP   7h14m
mosquitto-exporter-mqtt-exporter   ClusterIP      10.43.23.150   <none>           9000/TCP         84m

$ curl -s http://10.43.23.150:9000/metrics
# HELP python_gc_objects_collected_total Objects collected during gc
# TYPE python_gc_objects_collected_total counter
python_gc_objects_collected_total{generation="0"} 95.0
python_gc_objects_collected_total{generation="1"} 296.0
python_gc_objects_collected_total{generation="2"} 0.0
# HELP python_gc_objects_uncollectable_total Uncollectable object found during GC
# TYPE python_gc_objects_uncollectable_total counter
python_gc_objects_uncollectable_total{generation="0"} 0.0
python_gc_objects_uncollectable_total{generation="1"} 0.0
python_gc_objects_uncollectable_total{generation="2"} 0.0
# HELP python_gc_collections_total Number of times this generation was collected
# TYPE python_gc_collections_total counter
python_gc_collections_total{generation="0"} 43.0
python_gc_collections_total{generation="1"} 3.0
python_gc_collections_total{generation="2"} 0.0
# HELP python_info Python platform information
# TYPE python_info gauge
python_info{implementation="CPython",major="3",minor="10",patchlevel="5",version="3.10.5"} 1.0
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 2.471936e+07
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 1.6093184e+07
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.66009557928e+09
# HELP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 1.39
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 7.0
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1.048576e+06
# HELP mqtt_message_total Counter of received messages
# TYPE mqtt_message_total counter

There is nothing about the broker, clients connected, etc. which I assume there should be?
The exporter is connected and subscribed to the broker:
$ k logs mosquitto-exporter-mqtt-exporter-6dd9f8c77d-hg5n4 -n mosquitto
INFO:mqtt-exporter:subscribing to "#"

Thanks for taking the time to write up this issue. Exposing metrics / serviceMonitor is not a feature of the common library though, so this repo is not the correct place for it. I've moved it over to the charts repo, where it might be better suited.

authors: bjw-s reefland


text:
operator mondoo-operator (1.9.1)

Signed-off-by: Christian Zunker christian@mondoo.com

/merge possible

source: gharchive/pull-request

authors: czunker framework-automation


text:
operator project-quay (3.12.0-nightly.20240619)

Add 3.12.0-nightly.20240619 to community operators

/merge possible

/merge possible

authors: framework-automation quay-devel


text:
operator [CI] mongodb-enterprise (1.30.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

/merge possible

/merge possible

/merge possible

/merge possible

authors: MaciejKaras framework-automation


text:
invoke ipam delete before net namespace check

moving ipam.ExecDel before args.Netns == "" check, this makes sure ip is cleaned up in pod delete retry scenario, because some cases args.Netns is passed with empty string.
found this issue while testing whereabouts PR
Signed-off-by: Periyasamy Palanisamy periyasamy.palanisamy@est.tech

/release-note-none


text:
Make live-/readiness probe settings configurable.

What is missing?
A facility that enables the configuration of the live-/readiness-probes  targeting the cassandra container.  This encompasses the listed settings (values are just for illustration)

delay=15s
timeout=1s
period=15s
success=1
failure=3

Additionally making the stream_throughput_outbound_megabits_per_sec  in the cassandra.yaml configurable could be useful too.
Why do we need it?
When importing a large amount of data with the sstableloader  from within the k8ssandra/cassandra contaier the liveness test can fail a couple of times in a row due to high network load, although the pods  seem not to be affected and continue to import at high velocity. However, due to the probes failing, the pods will be restarted and the import aborted.
Environment

Amazon EKS
Cass Operator version:
k8ssandra/cass-operator:v1.7.1

Anything else we need to know?:
┆Issue is synchronized with this Jiraserver Bug by Unito
┆Issue Number: K8SSAND-610
┆Priority: Medium

Additionally making the stream_throughput_outbound_megabits_per_sec in the cassandra.yaml configurable could be useful too.

This is already configurable.

If there's something missing, please reopen.

authors: burmanm cheapsolutionarchitect jsanda


text:
Fix HCD support and add e2e test

What this PR does:
Fixes hcd support by adding the jvm options mapping rules for it. None of the jvm options were mapped at all for HCD before.
Checklist

[x] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CHANGELOG.md updated (not required for documentation PRs)
[x] CLA Signed:  DataStax CLA

Manual testing results:
Running this on main using the local e2e test CreateSingleDatacenterCluster and swapping out the server type/version/image block for:
serverVersion: 1.0.0
serverImage: datastax/hcd:1.0.0-early-preview
serverType: hcd

I see that:
The cassDC lacks fields for heap size:
config:
    cassandra-env-sh:
      additional-jvm-opts:
      - -Dcassandra.allow_alter_rf_during_range_movement=true
      - -Dcassandra.system_distributed_replication=dc1:3
      - -Dcassandra.jmx.authorizer=org.apache.cassandra.auth.jmx.AuthorizationProxy
      - -Djava.security.auth.login.config=$CASSANDRA_HOME/conf/cassandra-jaas.config
      - -Dcassandra.jmx.remote.login.config=CassandraLogin
      - -Dcom.sun.management.jmxremote.authenticate=true
      - -Dfoo=true
      - -Dbar
    cassandra-yaml:
      authenticator: PasswordAuthenticator
      authorizer: CassandraAuthorizer
      commitlog_directory: /var/lib/cassandra/commitlog2
      data_file_directories:
      - /var/lib/cassandra/data
      - /var/lib/extra/data
      num_tokens: 16
      role_manager: CassandraRoleManager

When I look at the jvm-server-options materialised into the image, I see this:
cat /opt/hcd/resources/cassandra/conf/jvm-server.options
-ea
-da:net.openhft...
-XX:+UseThreadPriorities
-XX:+HeapDumpOnOutOfMemoryError
-Xss256k
-XX:+AlwaysPreTouch
-XX:+UseTLAB
-XX:+ResizeTLAB
-XX:+UseNUMA
-XX:+PerfDisableSharedMem
-Djava.net.preferIPv4Stack=true

However, if I leave this as a Cassandra image with serverVersion: 4.0.6, I see:
CassDC:
<omitting the ones that existed in the HCD version>
jvm-server-options:
      agent_lib_jdwp: false
      always_pre_touch: false
      cassandra_available_processors: 2
      cassandra_disable_auth_caches_remote_configuration: false
      cassandra_force_default_indexing_page_size: false
      cassandra_ring_delay_ms: 100
      cassandra_write_survey: false
      enable_assertions: false
      flight_recorder: false
      heap_dump_on_out_of_memory_error: false
      initial_heap_size: 536870912
      java_net_prefer_ipv4_stack: true
      jmx-connection-type: local-no-auth
      jmx-port: 7199
      jmx-remote-ssl: false
      jmx-remote-ssl-opts: abc
      max_heap_size: 536870912
      per_thread_stack_size: 262144
      perf_disable_shared_mem: false
      resize_tlb: false
      string_table_size: 1048576
      unlock_commercial_features: false
      use-biased-locking: false
      use_thread_priorities: false
      use_tlb: false
    jvm11-server-options:
      conc_gc_threads: 2
      g1r_set_updating_pause_time_percent: 5
      garbage_collector: G1GC
      initiating_heap_occupancy_percent: 75
      max_gc_pause_millis: 500
      parallel_gc_threads: 2

So it does make its way into the cassDC, if I then run cat /opt/cassandra/conf/jvm-server.options inside a container I get:
-XX:+UnlockDiagnosticVMOptions

-Dcassandra.available_processors=2
-Dcassandra.disable_auth_caches_remote_configuration=false
-Dcassandra.force_default_indexing_page_size=false
-Dcassandra.join_ring=true
-Dcassandra.load_ring_state=true
-Dcassandra.ring_delay_ms=100
-Dcassandra.write_survey=false
-XX:+DebugNonSafepoints
-XX:GuaranteedSafepointInterval=300000
-Xms536870912
-Dio.netty.eventLoop.maxPendingTasks=65536
-Djava.net.preferIPv4Stack=true
-Djdk.nio.maxCachedBufferSize=1048576
-Xmx536870912 <THIS ONE!)>
-Dsun.nio.PageAlignDirectMemory=true
-Xss262144 <THIS ONE!)>
-XX:+PreserveFramePointer
-Dcassandra.printHeapHistogramOnOutOfMemoryError=false
-XX:-RestrictContended
-XX:StringTableSize=1048576
-XX:+UseNUMA

-Dcom.sun.management.jmxremote.authenticate=false
-Dcassandra.jmx.local.port=7199

# The newline in the end of file is intentional

And similarly cat /opt/cassandra/conf/jvm.options
...
-Xss256k
...

I'm not sure that we want -Xss set on both files, but I assume that jvm11-server.options takes precedence there. Overall, I think this is a bit of a mess, because things which are defined in the jvm-server-options seem to land in jvm11-server.options. I recall that this was because of backwards compatibility concerns, however I wonder if this situation could e improved in the interests of maintainability.
Running the same test with the HCD blocks on this branch I see:
The cassDC has
jvm-server-options:
        agent_lib_jdwp: false
        always_pre_touch: false
        cassandra_available_processors: 2
        cassandra_disable_auth_caches_remote_configuration: false
        cassandra_force_default_indexing_page_size: false
        cassandra_ring_delay_ms: 100
        cassandra_write_survey: false
        enable_assertions: false
        flight_recorder: false
        heap_dump_on_out_of_memory_error: false
        initial_heap_size: 536870912
        java_net_prefer_ipv4_stack: true
        jmx-connection-type: local-no-auth
        jmx-port: 7199
        jmx-remote-ssl: false
        jmx-remote-ssl-opts: abc
        max_heap_size: 536870912
        per_thread_stack_size: 262144
        perf_disable_shared_mem: false
        resize_tlb: false
        string_table_size: 1048576
        unlock_commercial_features: false
        use-biased-locking: false
        use_thread_priorities: false
        use_tlb: false
      jvm8-server-options:
        conc_gc_threads: 2
        g1r_set_updating_pause_time_percent: 5
        garbage_collector: G1GC
        initiating_heap_occupancy_percent: 75
        max_gc_pause_millis: 500
        parallel_gc_threads: 2

So that looks a bit odd, because we're landing some JVM options in the jvm8-server-options. Validating which java version is running I get:
java -version
openjdk version "11.0.23" 2024-04-16

So I think this is wrong, because I validated the Java version on Cassandra 4 as well and I'm pretty sure that was 11 too - so these should match AFAICT.
Checking the underlying files, there is actually nothing in the directory /opt/hcd/conf, it doesn't exist. Instead, it seems that the conf files may be landed in either /opt/hcd/resources/cassandra/conf/ or /opt/hcd/resources/hcd/conf/.
Examining those files:
cat /opt/hcd/resources/hcd/conf/jvm-server.options | grep Xmx
# If that's the case, uncomment the -Xmx and Xms options below to override the
# It is recommended to set min (-Xms) and max (-Xmx) heap sizes to
#-Xmx4G

This seems unset.
cat /opt/hcd/resources/cassandra/conf/jvm11-server.options | grep Xmx

Also unset.
cat /opt/hcd/resources/cassandra/conf/jvm-server.options | grep Xmx
-Xmx536870912

^^ That looks right, but with so many config files I can't tell where this should come from, so I looked at:
find / -name cassandra-env.sh
find: ‘/proc/tty/driver’: Permission denied
find: ‘/root’: Permission denied
/opt/hcd/resources/cassandra/conf/cassandra-env.sh
find: ‘/etc/ssl/private’: Permission denied
find: ‘/var/cache/ldconfig’: Permission denied
find: ‘/var/cache/apt/archives/partial’: Permission denied
/config/cassandra-env.sh

So it seems that there are actually about 3 different config directories here. So I ps'd the process itself to try to determine what was going on. I do see -Xmx536870912 -Xss262144 -Xms536870912 in the startup options for the JVM there, so this does appear to be working.
I'd like to challenge a few things though that I don't really understand:

Are we sure this should be in the jvm8-server-options in the cassDC? This doesn't match Cassandra's behaviour and isn't in accordance with the fact that this is a JVM11 container.
I don't fully understand where the /config directory is coming from. I've had a look at cass-operator and config-builder, but I can't see any PRs there which would allow things to map to these new HCD config directories. Maybe this is in an entrypoint somewhere?
This whole structure is really quite abstruse, I think we should organise a refactor at some point in the future (potentially we also need to release a new API so we're not bound by backward compatibility) to make it clearer.

My conclusion on this is that this PR does work to make HCD run, and it appears that we get the startup arguments into the Cassandra process that we want.
However, given the wholesale confusion as to which configs are being picked up and where they come from, I think ISSUE: please add an e2e test which runs a ps command inside the container and (with some non-default heap sizes) ensures that the heap configurations make their way into the Cassandra process. It might be good to add some other jvm-options and such in there as well, if they are commonly used.

authors: Miles-Garnsey adejanovski


text:
K9 doesn't allow email address with apostrophe

When creating a new account, K9 doesn't allow email addresses with apostrophe.
Expected behavior
We should be able to add an account for an email address containing an apostrophe.
Actual behavior
The buttons are disabled, we can't continue.
Steps to reproduce

Try to add a new account with an apostrophe inside the email address ;
See the buttons which are disabled.

Environment
K-9 Mail version: 5.208
Android version: 5.1.1
Account type (IMAP, POP3, WebDAV/Exchange): Exchange

Sub case of #1175. Is this a theoretical problem or have you actually got an email with a ' in?

I actually got an email with a ' in it (it is based on my last name... which contains an apostrophe).

Hi, coming from #1175, I'd like to add that I failed to send an email today to an address containing a German umlaut "ä". As K-9 didn't accept it, I replaced the ä with ae, but then the email bounced back. Do you need further information from me? Last but nit meat, thanks for a great mobile email client! :-)

authors: Zoddo digisus philipwhiuk


text:
Feature: Scroll bar and message stars

A feature exists where its possible to toggle the star next to a message in folder view. Unfortunately on my 4.5" screen on generic Android 5.0 it's almost impossible to use - most of the time you hit the scroll bar thing instead, also on the RHS, which is doubly bad as the message you're interested it then disappears off-screen.
Solutions:

Add an option to disable the scroll bar - it's almost redundant anyway.
Add an option to move the star to the LHS (personally, this is where I'd always put flags).

I know this issue has been raised on Google Code (e.g. Issue 6058) but I can't find anything to show it made it to Github.
Thanks, Frank.

Same issue here on Android 6.0 on Nexus 5.

+1

same on nexus 5 (android 6)

I noticed that in the normal inbox I can tap the star without issues, but if I do it in the "Combined Inbox" (or whatever is called in English) then the scrollbar pops out every time and the list jumps to the place I tapped on the scrollbar.
Nexus 5X on 6.0.1. I don't remember this issue with LG G2 on 5.0.x.

Same problem in samsung galaxy tab s2 and lg g3
Please fix!

Keine Probleme mit lg Nexus x5.
Am 23.09.2016 4:41 nachm. schrieb "ddanesin" notifications@github.com:

Same problem in samsung galaxy tab s2 and lg g3
Please fix!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/k9mail/k-9/issues/894#issuecomment-249211015, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVVQbgWLHCEgFsu2B8a4Okr98EGDCF6Yks5qs-T7gaJpZM4Gg305
.

Same on Samsung Galaxy A3 (2015, 2016), 4,6" screen.

No Lg Nexus 5X Android.7
Am 23.09.2016 4:56 nachm. schrieb "Tristan C." notifications@github.com:

Same on Samsung Galaxy A3 (2015, 2016), 4,6" screen.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/k9mail/k-9/issues/894#issuecomment-249215062, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AVVQbowsifuHRMuqZsiLV8t-Vo11M0lfks5qs-iYgaJpZM4Gg305
.

On Android 7 (Nexus 5X) when I touch a star the scroll bar doesn't jump anymore to that point, but still I cannot start/unstar.

This too is a major issue for me. Very intrusive and annoying on LG V10. Searched web for a way to disable scroll bar, led me here. Hopefully, after a year, there will be some movement on this issue, else may have to seek alternative client, not something I wish to do.

+1! same on moto g4 play on stock marshmallow

More an annoyance than a major problem, but it would be great if it could be fixed. Attaching a screenshot of an offending scroll-bar overlapping star icons.

I have 3 accounts on K9, for a total of 5 mailbox items:

the scrollbar bug happens in 4 of the 5 mailboxes of the pictures. For me this is very annoying because my workflow uses starring a lot and I have to open a message before I can star it.
Also, some subfolders exhibit the bug and other don't, apparently with no logic: all of the 3 accounts have some subfolders showing the bug and other without.

I removed comments that added no substance to this issue. The original error description is clear enough for us developers.
If you feel the need to discuss the effect of this bug on your usage of the app, please use the mailing list.

I'm on K-9 Mail Version: 5.208 on Android 7.0
Same issue.

I discovered something more a few days ago. If you select a message first, tapping toggles the star and ignores the scroll bar. If it's not selected it's very difficult to hit the star as the scrollbar takes priority.
For all I know, this may be the intended functionality, although counter-intuitive. I use K9 every day and it's taken me several years to figure it out.
Although this serves as a work-around, I'd still rather I was able to remove the scroll bar completely. On a small screen it's not useful to have one.

Disabling the scroll bar completely would be IMHO an acceptable option indeed.

for some reason, lately the star has been working correctly most of the time (but not always... the scroll bar still gets in the middle every now and then). I have version 5.403 installed.

Disabling the scroll bar completely would be IMHO an acceptable option indeed.

I agree, maybe not by default but there should be an option to do it. I mean, the scroll bar is useful, but starring messages is far more useful!
An alternative: I've seen that the big, clickable scroll bar (the one involved in this bug) appears only if the folder contains more than 25-30 messages. Under that number only a thin, non clickable scroll bar appears (just to show how far you are from the bottom of the list). Well, the option could just always force the thin bar to show, instead of disabling it completely.
Hope you will fix this bug or at least use one of these workarounds.
Thanks for your work

It would be really great to have an option in the settings to change the scrollbar, not only because of the star-feature.
It would be good to select, if it should be on the left or right side or hidden completely.
I always scroll through mails with my thumb on the right side. But due to the scrollbar it happens very often that the cursor jumps to a completely different position in the list, because my thumb was scrolling in the middle of screen for exemple.
Please introduce a fix for the scrollbar behaviour. Thank you in advance.

I personally fixed this issue by switching to Aquamail. Among other features, it allows moving the scroll thumb device to either side or disabling it completely. Because it's just a scroll thumb (handle) instead of a full length bar (so, hidden scroll track), there's no chance of interference with other ui elements. It also only appears when you start scrolling by dragging the list, so it's not obtrusive in the common case where the user is not fast scrolling. That's an alternative that might also work well in K9.

Now it was also enough time for me to switch to professional mail client - R2Mail2, which I can recommend so far. K9 user experience is just horrible and regarding feature set it's way behind.

I don't have direct problem with clicking star but with overall navigation see my reasons here #3984

Note: It should be much easier to hit the star in K-9 Mail versions 5.7xx. There's still room for improvement, though.

This is still a real problem. Please make the scroll bar actually disappear after scrolling. Because it just hides, and is still present on the right side of the stars, still on the stars. You can see that the scroll bar is still there after it "disappears" if  you enable "Show layout bounds" in the Developer options.  Thank you.

Please provide an option to turn off fast scrolling. So frustrating to be searching for something and you hit it by accident and you lose where you are. Otherwise an amazing email client. Thank you for your work.

@siouxchief I don't think they can. I think the problem is they use component with that scroll built in, and they have no control over it. So they would have to code a lot to change it. I have done some Android programming, and I was thinking to do it myself but I'm crazy busy. Also I don't know if they would merge my change, and letting people to install "my version" would sound too suspicious for many.

The "roulette" sudden scrolling 📜 effect still happens sometimes on the new beta version 5.731.  Enable the Layout bounds in the developer options and you'll see 👀 the scroll 📜 line is still there after the scroll 📜 bar hides.

there should be an option to disable the scroll, who needs it, who wants to fast scroll over 1000 emails. you can quickly normal scroll over 100 emails or do search. Most people will read emails as they go so no point to scroll over 50. Also most people will set local message cache to 50-100 so what's the point of that scroll at all?

@skironDotNet It's not really a "fast ⏩ scroll 📜" feature, that's just an undesirable byproduct of how this app has been made.

The way the scrollbar is implemented in K-9 is a rather peculiar and highly unusual pattern for a touch device.
While fast-scrolling by dragging does make sense, the tap interaction is very annoying - especially when the scrollbar is invisible. I think 'roulette' is a good  description as you won't know where exactly the tap takes you anyway.
IMO there's no need for any tap event on the scrollbar at all.

Since 5.8 i don't consider this to be a live problem any more. Thanks for the improvements!

I think there is a threshold that makes the scrollbar appear. With 25 messages it works just fine (no scrollbar) but with a larger inbox the scrollbar appears and obscures the star UI.

@artfulrobot It's quite possible that hardware plays a role here. FWIW I'm on a Samsung Galaxy S8+.

I have a Samsung note 9 with a 3000+ messages inbox and stars are still absolutely unusable.

I resorted to turning them off in the overview to prevent me from trying to use them 😛 Until this is fixed, stars only happen in detail view.

This issue is still open and it's recognized as a problem.
Please use the forum for discussions. Your comments are generating notifications for a lot of people, but they're not adding relevant new information for fixing the issue.

This issue is still open and it's recognized as a problem.
Please use the forum for discussions. Your comments are generating notifications for a lot of people, but they're not adding relevant new information for fixing the issue.

Aye and on top 🔝 of that every comment gets emailed (at least to me) in plain text (insecure / not encrypted).
Use the setting in the Developer options "Show layout bounds" to see the scroll 📜 line that's hidden.

This should be less of an issue in K-9 Mail 6.400 and much better in K-9 Mail 6.509 and newer.

authors: Ollik27 Thorbur bhundven caugner cketti cocofifi dannysauer ddanesin dewi-ny-je edison23 fedcas fjl-london foxacid life777eternal marksblitz siouxchief skironDotNet torantal wwp


text:
Change ReplyToParser to prefer From over List-Post header

Behavior before: ReplyToParser preferred List-Post header over the From header which made the list to the default reply-to address.
Behavior after: ReplyToParser prefers the From header over the List-Post header since mailing list tools like mailman also set the Reply-To header to the mailing list in case the admin would like to have the mailing list as default return. This follows also the behavior that most desktop mail clients are using (like Thunderbird, Apple Mail and Outlook).
This PR doesn't contain a reference to an issue ID since I didn't create a bug report or feature request.

This changes the behavior which was initially implemented in https://github.com/k9mail/k-9/commit/2e33e0dd9492fe2ededf5eaf17495a5dd5ff6f67

Hmm, I would think replying to the list is the expected behavior in most cases, and replying to the original author is the exception. On the other hand, for non-list mails "reply" replies to the sender only unlike "Reply to all". I guess there is no truly natural behavior for a "reply" button, so maybe we should offer "Reply to list" and "Reply to sender" buttons?

Hi @Valodim,
those two buttons would make it actually clear.
The reason for my pull request was initially that I replied by accident to a mailing list instead of the sender only. Most of the time it is worse when you are sending the email to a large group of persons than to one specific person by accident. When you would like to reply to the list I would maybe also reply to the sender as well (he might not be on the list) so I would say there the "reply all" button is also a fit. Are there other email applications which are going for a "reply to list" as a default reply button?
Thank you for your feedback!
Valentin

Most of the time it is worse when you are sending the email to a large group of persons than to one specific person by accident

Agreed.

When you would like to reply to the list I would maybe also reply to the sender as well (he might not be on the list) so I would say there the "reply all" button is also a fit

Agreed.

Are there other email applications which are going for a "reply to list" as a default reply button?

I don't know :) I guess it also depends on the placement of the button - if there is a single big "reply" button and alternative ones a click away, it should clearly cover the common case, and I'm fairly sure that that's participating in the on-list discussion, rather than branching off to only the recipient.
I think we can be smart about those reply options, i.e. "reply" / "reply to all" for regular mails and "reply to sender" / "reply to list" for those with a list-post header. Would you want to take a shot at that? The info should be easily available in RecipientPresenter :)

I can give it a shot, but it might take some time since I pretty busy right now.

Thanks for taking the time to contribute to K-9 Mail by creating this PR! Sorry, we didn't include it. But I think it started an important discussion.
We'll stick with the current behavior for now and change once we've figured out how we want reply to behave in the future. See #3738.

Or what about just doing it? Internet standards are not written hastily. Things like this have been already discussed throughly. No point in implementing surprising, non-standard behaviour.

authors: Valodim ilmaisin vzickner


text:
Feature request: MySQL support

The title describe itself. It'd be great to also have MySQL support on the logger. Cheers!

@giovannipds
Apologies for the late response, I was out of town for a while.
As a matter of fact, I did implement MySQL support for a project of my own, but I haven't yet ported it to here. I'll aim to do this as soon as I can.

@giovannipds see release v1.1 which has a MySQL storage implementation.
You will need to provide it with a MySQL PDO connection, e.g.
$pdo = new \PDO("mysql:host=localhost;dbname=database", 'username', 'password');

// Create the storage strategy (standalone or collection dependent on your needs)
$storage = new \EventLogger\Storage\MySQLStorage($pdo);

// log events
.......

Hope this helps!

Suggest you use v1.1.1
;)

Nice @kabudu, I think it's a good improvement to the package. =)

authors: giovannipds kabudu

repo: kabudu/event-logger

license_source: bigquery


text:
Can I switch username with CLI arguments?

If I can  avoid hardcoding, it can be easy used in devcontainer and others.
https://github.com/kachick/dotfiles/blob/2a5d6f5a83ca3232a25f8dbfc9368fef253f5a64/flake.nix#L48-L62
https://github.com/kachick/dotfiles/blob/2a5d6f5a83ca3232a25f8dbfc9368fef253f5a64/home-manager/home.nix#L16
https://github.com/kachick/dotfiles/blob/2a5d6f5a83ca3232a25f8dbfc9368fef253f5a64/home-manager/git.nix#L9-L10

https://github.com/nix-community/home-manager/blob/0e0e9669547e45ea6cca2de4044c1a384fd0fe55/docs/manual/faq/multiple-users-machines.md?plain=1 🤔

repo: kachick/dotfiles

license: MIT


text:
created Singularity recipe and updated README.md

I created a quick Singularity recipe for those that do not have access to docker (such as users within shared systems). I did change around the README.md quite significantly, only because of the users that I support may be interested only in the singularity format. Of course it may make sense to integrate my README chanes with yours.

Codecov Report

Merging #218 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #218   +/-   ##
=======================================
  Coverage   81.25%   81.25%
=======================================
  Files          33       33
  Lines        1494     1494
  Branches      155      155
=======================================
  Hits         1214     1214
  Misses        206      206
  Partials       74       74

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 fb1b238...2bf06ab. Read the comment docs.

Hi @tjhendrickson - I will close this PR at the moment because I do not plan to include a Singularity definition for neurodocker. The prebuilt Docker images available at https://hub.docker.com/r/kaczmarj/neurodocker can be pulled as singularity containers.

authors: codecov-io kaczmarj tjhendrickson

repo: kaczmarj/neurodocker


text:
Add proper windows support.

Seems like we use some bash features. See: #145
We need to add some proper support for windows.
cc @mnmtanish

I think we can use shelljs to write scripts so it'll work on all platforms. Eg. prepublish.js instead of prepublish.sh.
I'm working on integrating Appetize.io to react-native-storybook these days. I'll get back to react-storybook as soon as it's ready.

@mnmtanish sounds like a good plan.

Its possible to fix that soon ?

It's working for me on Windows now. Thanks!

Fixed with #308

authors: arunoda mnmtanish szopenkrk wallslide

repo: kadirahq/react-storybook

license: mit


text:
Group instance ID support (group.instance.id) (static membership)

Hello!
It is possible to add group instance ID support for static membership. This allows in some cases reduce consumer rebalances.
Details: KIP-345

The underlying protocol library already supports it,
however we do not have the plan to support it in brod yet, not at the moment.
ref: https://github.com/kafka4beam/kafka_protocol/blob/7147d6e16652b9b1c39758250bdf93ee934ec706/src/kpro_schema.erl#L499-L517

@zmstone thanks for reply!
Correctly I understand that we should pass this to coordinators state and after to join_group and sync_group requests body?
https://github.com/kafka4beam/brod/blob/master/src/brod_group_coordinator.erl#L616
https://github.com/kafka4beam/brod/blob/master/src/brod_group_coordinator.erl#L652

Hi @anoskov
I'm afraid it's more than just adding the fields.
I had a quick look at KIP before, and just quickly revisited it,
It seems that "Client Behavior Changes" implies brod_group_coordinator should change in its rebalance behaviours.

authors: anoskov zmstone


text:
Getting IDE Fatal Errors

Description of the bug & expected behaviour (required)
After installing the plugin, I constantly get a notification in the bottom saying "IDE error occurred", which brings me to the page saying it caught an exception in your plugin.
the exception is in this link https://pastebin.com/qNn4BEzy
Environment Info (required)

OS: Windows 10 20H2
JetBrains Product: eg. IntelliJ Ultimate
JetBrains Product Version: eg. 2021.1.EAP
Plugin Version: eg. 1.4.2

Steps to reproduce (optional)
Install plugin, and do anything to bring up the progress bar
Additional context or information (optional)
eg. It only happens when it is raining

Interesting, this doesn't seem to happen with ≤ 2020.3, so likely something that they've changed/removed in 2021.1. I haven't played around with the EAP version at all yet; I'll try to see if I can pinpoint the issue & fix it this weekend.
Thanks for the bug report!

No worries, just wanted to bring it to your attention.

Thanks @ShadowChild :) This has been resolved in the upcoming 1.5.0 release!

authors: ShadowChild kagof

repo: kagof/intellij-pokemon-progress


text:
Accept kubernetes config style as input

cloud config and c3os blocks should be ideally configurable as standard kubernetes resources. To follow the same API-style, a configuration similar to kubernetes API is wanted for consistency, example taken from kind:
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
  - role: control-plane
    image: kindest/node:$KUBE_VERSION
    kubeadmConfigPatches:
      - |
        kind: InitConfiguration
        nodeRegistration:
          kubeletExtraArgs:
            node-labels: "ingress-ready=true"

maybe relates to #1023 ?

repo: kairos-io/kairos


text:
Domain Expired

When i try to go to the url (http://learn-swift.co), the domain has expired and site is no longer there.

Domain is now http://swiftbits.redalemeden.com. This can be closed.

authors: derek-skinner vitorgalvao

repo: kaishin/swiftbits


text:
Add state_class for 1wire sensors

Is your feature request related to a problem? Please describe.
I have five 1wire temperature sensors connected to Heishamon and I would like to utilize Home Assistant's long term statistics for them, however, since these sensors in HA don't have state_class attribute defined, they are not included in the long term statistics.
Describe the solution you'd like
Add state_class: measurement attribute to 1wire sensors
Describe alternatives you've considered
Using customize.yaml (as described here) but I believe this is a feature that would benefit lots of people and I would prefer not to add separate customizations where possible (easier to manage HA instance).
Additional context
Documentation
Similar to https://github.com/Egyras/HeishaMon/pull/292

https://github.com/kamaradclimber/heishamon-homeassistant/releases/tag/1.7.6 contains the patch

authors: Vallatu kamaradclimber

repo: kamaradclimber/heishamon-homeassistant


text:
email service unhealthy

ERROR: for emails  Container "1c315e14cd71" is unhealthy.

ERROR: for usage-ingestor  Container "88f815015dee" is unhealthy.
ERROR: Encountered errors while bringing up the project.

@sschneider-ihre-pvs can you please share more information?

Sure, what do you need? I ran the docker-compose.community.yaml in windows WSL2 and that was the result.

Sure, what do you need? I ran the docker-compose.community.yaml in windows WSL2 and that was the result.

Can you please share the docker logs and docker inspect output of that container? thank you!

authors: dotansimha sschneider-ihre-pvs

repo: kamilkisiela/graphql-hive


text:
bottom-left

Please add bottom-left

This is for positioning the pop-over?

I am new to contributing to an open source project. Any open issues in this project that is good for intermediate JS guy like me?

Yes for positioning the pop-over.

Okay. Will work on this issue then.

Hey, there is already left-bottom, please use that.

Got it. Shall I add the current positioning options into the Demo page? currently it only has left, top, bottom & right.

Also, i was thinking of a feature

While highlighting input boxes, allow Enter(key press) as an option to move to the next highlighted button. This will help in building forms that will highlight the current required field for every field.

@vishwanathovi if you want to update the demo page for that, go ahead.
Regarding the Enter key to move next, I don't think we should have that, it can easily be implemented by anyone who wants that using an event handler in their app.

authors: Muchwat kamranahmedse vishwanathovi


text:
How to intercept closing event?

onReset: () => null,              // When overlay is about to be cleared
I want to show additional info BEFORE closing a tour.

I don't understand

Onreset will be triggered when the mask is closed，
Is there a way to click close，
I need to close the entire driver when I click Close

We just released v1.0 of driver.js which has been rewritten from the ground up. There are more simplified hooks which give you more control over the popover and the whole lifecycle. You are probably looking at one of onClose, onDestroyStarted or onDestroyed. Please have a look at the docs and do let me know if you face any issues.


text:
Cannot download : triggerUncaughtException

[SPLIT CONTENT FROM OTHER ISSUE TO. ALREADY SOLVED.]
Doesn't work 😭 .
Input
Target category is Category:Lingua_Libre_pronunciation, exists, and contains sub-categories.
(Also tested with Category:Lingua_Libre_pronunciation-cmn, exists, and only contains files. Same results.)
The directory in which I want to store all those downloads is ./downloads and this directory exists.
Full code (base)
// PURPOSE: Given a root category, script list subcategories and download all files from them into dedicated repositories.
// Run: $node script.js
const Wikiapi= require('wikiapi');
const logins = require('./logins.js');

// Login credentials from .login*.js
var USER = logins.commons.user,
	PASS = logins.commons.pass,
	API  = logins.commons.api;

(async () => {
    // Connect
    var targetwiki = new Wikiapi;
    await targetwiki.login(USER, PASS, API);
    console.log(`Username ${USER.split('@')[0]} is connected !`);

    // CORE CODE
    await targetwiki.download(targetwiki.to_namespace('Lingua_Libre_pronunciation', 'Category'), { directory: './downloads' });

})();

Variations
Cannot download
{ directory: './downloads' }
    await targetwiki.download(targetwiki.to_namespace('Lingua_Libre_pronunciation', 'Category'), { directory: './downloads' });

yug@yug-k401ub:~/Documents/WikiapiJS-Eggs$ node wiki-category_tree-many.js
get_API_parameters: Cache commonswiki: path=query+siteinfo
Username ShufaBot is connected !
Cannot download Category:Lingua Libre pronunciation
node:internal/process/promises:246
          triggerUncaughtException(err, true /* fromPromise */);
          ^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "[object Array]".] {
  code: 'ERR_UNHANDLED_REJECTION'
}

Node.js v17.0.1

Variations within try { ... } catch (error) { ... }
Errors are similar for :

category of categories : Category:Lingua_Libre_pronunciation, exists, and contains sub-categories.
category of files: Category:Lingua_Libre_pronunciation-cmn, exists, and only contains files.

Cannot download
{ directory: './downloads' }
try {
   await targetwiki.download(targetwiki.to_namespace('Lingua_Libre_pronunciation', 'Category'), { directory: './downloads' });
} catch (error) { console.log(`Download error : ${JSON.stringify(error)}`) }

yug@yug-k401ub:~/Documents/WikiapiJS-Eggs$ node wiki-category_tree-many.js
get_API_parameters: Cache commonswiki: path=query+siteinfo
Username ShufaBot is connected !
Cannot download Category:Lingua Libre pronunciation
Download error : [{"pageid":69811642,"ns":14,"title":"Category:Lingua Libre pronunciation"}]

Pushed there https://github.com/hugolpz/WikiapiJS-Eggs/blob/main/wiki-download-many-category_tree_and_files.js .
Question : DOES THIS LINE OF CODE WORK ON YOUR PC ?

@kanasimi  answered:

It's strange that I successfully downloaded the files using the latest wiki-download-many-category_tree_and_files.js.
Do you move the CeJS-master directory to node_modules/cejs?
How about changing var targetwiki = new Wikiapi; to var targetwiki = new Wikiapi('commons');. For testing this issue, I did not login, just using var targetwiki = new Wikiapi('commons');, and it still works.

Same error messages. 😭

@kanasimi posted:

I still think it is caused by an old version. I make a new version 4.4.3.
You can run npm update to get it, and using console.log(CeL.version); to verify what version you are using.

Update
console.log(CeL.version); returns 4.4.2, yes.
npm uninstall cejs
npm update

console.log(CeL.version); returns 4.4.3, yes.
The WikiapiEgg now works !
Mini benchmark

Initial download:

760s/829 ⬇ = 0.9s/ ⬇

Update downloads:

~20s/829 🔉 / 20 ⬇ = ~0.02s/file comparison and ~1s/⬇

UPDATE IS DAMN FAST !
Thanks

repo: kanasimi/wikiapi


text:
Optionals with some?.that : 12 were treated for ternary space alignme…

…nt. Which produces bad code. This fixes that

fixes #4

repo: kandelvijaya/XcodeFormatter


text:
Transaction id mismatch

I occasionally run into errors when parsing raw transactions (returned from getrawtransaction), one such example is:
Calculated txid 51ade4ff7f403e4f8abe2fddbb03bd890a7e79f5345f78452c3f0cb49ebb41bb
Actual txid 434ebb1d15a184ea5d9b4be02ae6c99a6f4b3095b7c9601e5bad672bf326e157

TX mismatch! Raw tx:

010000000001010000000000000000000000000000000000000000000000000000000000000000ffffffff5103de940c184d696e656420627920536563506f6f6c29003b04003540adfabe6d6d95774a0bdc80e4c5864f6260f220fb71643351fbb46be5e71f4cabcd33245b2802000000000000000000601e4e000000ffffffff04220200000000000017a9144961d8e473caba262a450745c71c88204af3ff6987865a86290000000017a9146582f2551e2a47e1ae8b03fb666401ed7c4552ef870000000000000000266a24aa21a9ede553068307fd2fd504413d02ead44de3925912cfe12237e1eb85ed12293a45e100000000000000002b6a2952534b424c4f434b3a4fe216d3726a27ba0fb8b5ccc07717f7753464e51e9b0faac4ca4e1d005b0f4e0120000000000000000000000000000000000000000000000000000000000000000000000000

It seems just excluding coinbase transactions from my script avoids this problem.

Thanks for reporting. The structure of a coinbase is supposed to be the same but apparently I might have missed something. I will look into it when I find some time.

Found the issue and fixed it. Should be OK but let me know if you still have issues.

authors: CedarMist karask

repo: karask/python-bitcoin-utils


text:
V 1.3.1 - json data in Multipart/form-data in Multipart field or Multipart file is not working as a expected

Hi
I am using Karate version 1.3.1 for our projects. Currently we have a use case to test an API which is taking a file and a metadata as part of the request.
we are using multipart file and field to write our feature file, but it seems when we check the POsT call on report we don’t see the metadata which is a Json going as part of the request.
As per the suggestion in link: https://github.com/karatelabs/karate/issues/1710
we tried the other approach to use multipart file and value as a parameter but it did not work for us.
Is there any other way to implement this on karate?
note: postman is working without any issues and we get a response too
please help if anyone has faced or resolved this.
Below is my feature file:

def temp = { 'upload': ['name':'test', 'org':123, 'branch': 'xyz', 'amount': 100], 'info': 8900, 'id': 123}
Given url "http://11.111.1.111:1111"
And path "/api/v1/upload
header Content-Type = 'multipart/form-data'
multipart file file = {read: 'classpath:resources/file/file1.txt', filename: 'file1.txt'}
multipart file metadata = {value: '#(temp)}
And method POST
print response

Note: I also tried * multipart field metadata = temp (but no luck here)
Response:
content-disposition: form-data; name= file; filename="file1.txt"
content-type: text/plain; charset= UTF-8
content-length: 5300
Completed: true
IsInMemory: true
content-disposition: form-data; name= metadata; filename=""
content-type: application/json; charset= UTF-8
content-length: 100
Completed: true
IsInMemory: true

The issue is when I run the feature file on Karate the api returns me 200 with a blank response.
Response: { }
but when the same is executed from Postman it returns me response
Response from postman: {id:123, status: ‘Done’}
also I tried the same request with Java okhttpClient request and it worked fine and gave me the expected response.
Is there anything which I am missing while running from Karate?

closing as unable to replicate and there is a thread for this on stack overflow: https://stackoverflow.com/q/76546469/143475

repo: karatelabs/karate


text:
Karate change / by \ in the request body

When create a json body in js file like this
function fun() {
rut = rut[0] + "-" + rut[1];
let request =    {     "key":1,     "idExpediente":${expedienteId},     "rut":"${rut}",     "flujo":"solicitudes",     "id":null,     "tipoArchivos":{"id":${fileType.id}},     "etapa":"documentos",     "keyname":"document_auto.pdf",     "nombreDocumento":"document_auto.pdf",     "contentType": "application/pdf"   };
return JSON.parse(request)
}
When karate make the request in the show

POST https://qa.sagcom.cl/dev/api/msdocumento-repositorio/v1/solicitar-url
1 > Content-Type: application/json; charset=UTF-8
1 > Content-Length: 228
1 > Host: qa.sagcom.cl
1 > Connection: Keep-Alive
1 > User-Agent: Apache-HttpClient/4.5.13 (Java/1.8.0_292)
1 > Accept-Encoding: gzip,deflate
{"key":1,"idExpediente":6649,"rut":"18672798-3","flujo":"solicitudes","id":null,"tipoArchivos":{"id":1},"etapa":"documentos","keyname":"document_auto.pdf","nombreDocumento":"document_auto.pdf","contentType":"application\/pdf"}

@albertor03 please ask these kinds of questions on stack overflow in future. here karate is doing the right thing: https://stackoverflow.com/a/68411097/143475


text:
Logging Example does not run as a Service

So i just tested the example/logging/main.go, It runs, but only as a normal program. Its not running as a service, though it says it is.
Windows 10 64Bit

It is designed to run as a normal program if ran as a user. If you install it and start it with the service manager, it will run as a service.

How does one go about installing it, sc create?

Hi Daniel,
Sorry for bugging you.. after I installed it and started the same using - service GoServiceExampleLogging start
I am still not able to find it running -
ps -ef | grep GoServiceExampleLogging
root      60407  57808  0 15:19 pts/8    00:00:00 grep --color=auto GoServiceExampleLogging
Where can I check the logs for the same or confirm if its actually running?

authors: Groot221 SaturnsVoid imRohan kardianos

repo: kardianos/service

license: Zlib


text:
Fix bug that deletes model checkpoints

Changes:

Fix bug that deleted saved models when multiple processes are started concurrently
Fix logo in README.md

LGTM!

authors: Ashutosh-Adhikari achyudh

repo: karkaroff/hedwig


text:
Clean up dev dependencies

Electron doesn't need to be installed by default.  Clean up package.json and documentation so it is not installed via npm install

Fixed for 0.8.5

repo: karlcswanson/micboard


text:
Only retry Tire::Index#bulk_store on StandardError.

Otherwise bulk_store retries after receiving signals like INT or TERM, likely resulting in the process getting killing by the KILL signal (if being terminated automatically) without executing normal cleanup (e.g. ensure blocks).

Dylan, this would completely change the purpose/semantics of swallowing exceptions from HTTP client etc, wouldn't it?
I think the proper way how to handle this would be to rescue SystemExit; raise;...

The HTTP client shouldn't be throwing non StandardError exceptions.  If they are that should be fixed.

Yes, seems like you're right, eg. RestClient https://github.com/archiloque/rest-client/blob/master/lib/restclient/exceptions.rb#L82.
Could you try it with RestClient, Curb? Eg. shutdown ES and try the bulk?
Also, the patch will need tests...

Looked at the source code for rest-client and curb, and they both seem to use exceptions that inherit indirectly from StandardError.  I also tried catching the exceptions from Tire.index('').exists? when elasticsearch is down with Curb and RestClient, and the exceptions were caught.
Here are some of the inheritance chains:

Errno::ECONNREFUSED -> SystemCallError -> StandardError
RestClient::RequestTimeout -> RestClient::RequestFailed -> RestClient::ExceptionWithResponse -> RestClient::Exception -> RuntimeError -> StandardError
Curl::Err::ConnectionFailedError -> Curl::Err::CurlError -> RuntimeError -> StandardError
Interrupt -> SignalException -> Exception

I have also added tests to the pull request.

Dylan, I'm very sorry for the delay. The patch makes very much sense. Merged & pushed now, thanks!

authors: dylanahsmith karmi

repo: karmi/tire


text:
allow to "overwrite" tabs

Add function where user can open specified set of tabs closing all currently opened tabs.

added this functionality in commit 7304483eca7bc8c1f7734095ee00193ac8d0de01


text:
Adding requires_grad flag to Value class

I've added a requires_grad flag to the Value class that defaults to False, mimicking PyTorch's behavior.
The topological sort of the computational graph can then stop expanding nodes that don't require gradient propagation. E.g. in expressions such as x + 2 the conversion of the scalar 2 to Value(2) will no longer propagate the gradient for that node.
I've also incorporated these changes into the neural network where all parameters receive requires_grad=True. All unit tests continue to pass and the demo notebook finds the exact same loss after 99 iterations.
Note that I also did some other small refactorings such as the separation between local gradient computation and propagation. This made it easier to selectively propagate the gradient based on the requires_grad flags. I've renamed the internal _backward attribute to a constructor argument gradient_fn.
All in all, the engine.py module was reduced by 15 lines, and weighs in at less than 80 lines now.

Any update on this? Is this repo not taking PRs, or should I polish the PR a bit more?

Any update on this? Is this repo not taking PRs, or should I polish the PR a bit more?

@rhalbersma unfortunately this repo doesn't take PRs..

authors: fcakyon rhalbersma

repo: karpathy/micrograd


text:
Modified texts, alerts to acknowledge user about topic search

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change

[ ] Bug fix
[ ] New feature
[ ] Documentation update
[x] Other

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings or errors
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

fixes #69


text:
[Feature Request]: Adding preview of links shared to chat with click property

Fixes #119

📋 Description
The main problem is to make the links shared in the chat clickable and also preview them inside the chat like discord or LinkedIn, twitter, Instagram platform does.
🔨 Changes Made
This pull request introduces a new feature to extract and display link previews in messages. It includes changes to both the backend and frontend to support this functionality.
Backend Changes:

backend/controllers/messageControllers.js: Added logic to extract URLs from message content and fetch link previews using an external API. These previews are then included in the message object.
backend/models/messageModel.js: Updated the message schema to include a new field for storing link previews, which contain title, description, URL, and image.
backend/package.json: Added the node-fetch package to enable fetching link previews from an external API.

Frontend Changes:

frontend/src/components/ScrollableChat.js: Modified the ScrollableChat component to display link previews within messages. This includes rendering the previews with appropriate styling and ensuring the message content appears below the previews.
frontend/package.json: Added the stream-chat and stream-chat-react packages to support the new chat features.

Summary of Changes
Backend:

Updated sendMessage in messageControllers.js to extract URLs and fetch link previews.
Modified messageModel.js to include a linkPreviews field.

Frontend:

Updated the message rendering logic to display link previews.

#119

🔨 Screen Shots OR Short videos of working
talktrove-119.webm

✅ Checklist
Before submitting the PR, please make sure you have completed the following:

[X] My code follows the style guidelines of this project.
[X] Read Contributing.md

🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)

[ ] Bug fix (non-breaking change which fixes an issue) 🐛
[X] New feature (non-breaking change which adds functionality) ✨
[X] UI enhancement (non-breaking change which enhances UI) 🎨
[ ] Documentation update 📚

[!NOTE]
Make sure to replace YOUR_API_KEY with your actual API key for the link preview service from here
You may need to install node-fetch in your backend if it's not already included

@kartikay-bigsteps @Sibam-Paul Review this PR, and assign it to me

@Sibam-Paul there is an error in vercel deployment is there something wrong on my code ?

Wait seeing

@Sibam-Paul all changes pushed

closes - #119

authors: Sibam-Paul yashksaini-coder

repo: kartikayasijaa/talk-trove


text:
Refactor block struct

Created a MutableBlock struct which test consensus returns from build methods, and changed Block to have header through an Arc, making it immutable and easy to pass by cloning (w/o another Arc around). This also saves from a full header clone on header processor commit

Addressed some of the items in https://github.com/kaspanet/rusty-kaspa/issues/60

repo: kaspanet/rusty-kaspa

license: ISC


text:
TODO

This project is a small initial sample of VLC binding.
Initially the zig translate-c (c to zig) is not 100% yet, generating some inconsistencies in vlc.h. But libvlc.h is being translated in this example.
Issues

[x] fix translate-c on vlc.h - error: missing struct_a.
[x] fix sleep timeout
[ ] Tests
[x] #2

Examples

[x] CLI - player
[x] CLI - print version (libvlc, compiler)
[ ] #3
[ ] #5

Next steps

[ ] Build C and C++ examples w/ zig bindings
[ ] Refactor impl using comptime
[ ] Document zig binding.

cc: @tguillem

After I was able to run the example cli-player on Linux.
It is still necessary to investigate why std.time.sleep does not work as a timeout and requires using c.sleep from the system's native API.

After spending a few days trying to fix the CI/CD (Linux, MacOS), as for Windows, preferred to postpone it a little due to the interpretation complication (will review it more calmly later).
Now, refactoring the SDL_player example with OpenGL support.
Therefore, I take the opportunity to update Todo list for the next steps after merging the SDL2 example.

Windows CI (MinGW) issue has been fixed, and cli-player (zig version) example issue has been fixed and cli-player (c version) added. #11
The implementation of the SDL will be resumed. #6

repo: kassane/libvlc-zig


text:
action: Require PR porting labels

A PR now needs two labels to be applied before it can be merged. One
label must be a backport label from the list below and the other a
forward port label:

backport labels: needs-backport, no-backport-needed.
forward-port labels: needs-forward-port, no-forward-port-needed.

This is to make the maintainer think carefully before merging a PR and
hopefully maximise efficient porting.
Related: https://github.com/kata-containers/kata-containers/issues/634
Fixes: #1133.
Signed-off-by: James O. D. Hunt james.o.hunt@intel.com

Ping @c3d.

Ping @fidencio, @egernst - please tal so we can get this merged today.

/test

/AzurePipelines run

repo: kata-containers/packaging


text:
Kata deploy automation

simple script to update the Dockerfile for kata-deploy to a new version for a given branch.  based off of the update-repository-version script.
TODO:  add testing, similar to update-repository-version_test.sh

Your PR description contains a TODO so should this have a dnm tag? If not, please convert those TODO items into new issues.

Ping @egernst.

@egernst ping

thanks for the review @jodh-intel and the follow up @caoruidong .
I'm going to start working on this again now.

authors: caoruidong egernst jodh-intel


text:
Release 1.5.1

Fix issues found in Kata release 1.5.1
Note: The  ubuntu 16.04 failed on OBS, I confirm that golang 1.11 does not work with this ubuntu version.
https://github.com/kata-containers/packaging/issues/264

/test

Added dnm until we understand the retpoline changes more fully.
/cc @marcov.

If I understand correctly, @jcvenegas is trying to disable CONFIG_RETPOLINE on some distros because, if that is enabled, then you need at least gcc 7.3 to build the kernel, and that's not available on {SLES,Centos}.
I'd suggest to try update the OBS project metadata to include:

For SLE, <path project="SUSE:SLE-12-SP3:Update" repository="standard"/>
For CentOS, <path project="CentOS:CentOS-7" repository="update"/>

Sorry, in my previous comment I thought CentOS was failing, but it is RHEL instead.
Unluckily the RHEL-7 project does not have an update repository on OBS. I am not sure how to get an updated version of gcc then.

@marcov thanks for the suggestion, I added the repository for SLES , I think will keep that for RHEL, pushing again to OBS to see if the build goes well

@marcov I updated the repositories for SLES but still see the issue,
See:
https://build.opensuse.org/project/show/home:katacontainers:releases:x86_64:stable-1.5#
And
https://build.opensuse.org/projects/home:katacontainers:releases:x86_64:stable-1.5/meta
probably I am missing something else

@jcvenegas ok I see, let me try to see how can we force using gcc > 7.3 and I'll report

@jodh-intel @grahamwhaley @marcov  are you OK to merge as it is today, this was used to to the release 1.5.1

/test

/me leaves this to @jodh-intel @marcov - I will note you will need to drop the DNM before the merge..

I couldn't find an easy way to use a more recent gcc for SLES.
Actually, we should probably change the way the kernel is built. The Kata kernel is in no way linked to the OS we build on, as it is used inside a VM with a clearlinux os anyway.
So, probably we should just build the kernel with a reference machine and use the same package for all the different distros.
Let me think about this.
For the time being, we can waive the DNM.

I think this is @egernst / @gnawux's call. If you guys are happy to proceed, feel free to remove the dnm. Personally, I'd rather we find a proper solution here for RHEL.
I should point out that although we build packages for RHEL, nobody has yet found a way to actually allow us to test on RHEL :-((( See https://github.com/kata-containers/ci/issues/3. I think we were all hoping/expecting this problem would be very quick to resolve, but clearly it isn't.
I'm pretty sure we've asked before, but if @lsm5, @ttx or anyone else knows how we can make this happen, that would be excellent.
If we cannot test the RHEL packages, the question naturally arises as to whether we should be creating them at all...

We could probably leverage the CentOS nodes we have in Zuul to continuously test package build there... Testing on RHEL itself provides imho little additional value (packages produced by us would be excluded from RHEL support contract scope anyway).
But that's a lot of CI work while the only good final outcome there is to get Kata properly distro-packaged by Fedora and imported/supported in RHEL. And yes, creating our own untested packages in the mean time could be seen as a distraction reducing the priority of getting it properly distro-packaged...

@egernst, @gnawux, @ttx - in which case, until Kata is packaged by Redhat for RHEL (see table in https://github.com/kata-containers/packaging/issues/6#issuecomment-453940053), we seem to have the following options:

Stop building RHEL packages entirely, on the hope that Kata will be added to RHEL "Real soon now".

Continue to build packages for RHEL, but add a big fat warning to the Kata RHEL install guide along the lines of:

WARNING: The RHEL packages are provided as a convenience to users until native packages are available in RHEL but they are NOT currently tested so caution should be exercised. See https://github.com/kata-containers/ci/issues/3 for further details.

Since continuing to build the RHEL packages is essentially zero cost [*], how about just adding the warning?

[*] - That's not strictly true of course, particularly given our plans to start using packagecloud. But packagecloud may provide us with statistics on "number of RHEL downloads per month" for example which would make interesting reading and allow us to better assess the RHEL situation.

PR https://github.com/kata-containers/documentation/pull/397 raised to add a warning in the RHEL install guide stating we do not (cannot) test on RHEL.
@jcvenegas - since this code was used for the last release, as you say I think we're going to have to land it. I've raised #388 as a P2 to remove this RHEL-specific change but we could do with some help from Redhat by the sounds of it.
With that tracking issue open, I think we can get this PR landed.
wdyt @grahamwhaley, @egernst, @gnawux?

@kata-containers/architecture-committee could you take a look to this?, it is being 2 releases with this changes.

authors: grahamwhaley jcvenegas jodh-intel marcov ttx


text:
release: add script to bump repositories

Add script that will help to bump versions for all the projects.
Fixes: #49

@klynnrif  could you review  docs changes from this PR.

@egernst ping more release automation \o/

Hi @klynnrif, @intelkevinputnam - ptal.

@jodh-intel @klynnrif  PR updated.

Fixed docs
Added tests for new script

Test is failing:
Non existing repo should fail
/tmp/jenkins/workspace/kata-containers-packaging-ubuntu-16-04-PR/go/src/github.com/kata-containers/packaging/.ci/../Makefile:15: recipe for target 'test-release-tools' failed
make[1]: *** [test-release-tools] Error 1
make[1]: Leaving directory '/tmp/jenkins/workspace/kata-containers-packaging-ubuntu-16-04-PR/go/src/github.com/kata-containers/packaging'
Makefile:12: recipe for target 'test' failed
make: *** [test] Error 2

authors: jcvenegas jodh-intel


text:
Hello, my brother！I am from China

Hello, my brother！I am from China I saw your article on the Internet. Can I save wavesurfer.js data, I'm not a professional programmer. I don't know how to operate. Can you help me

How to save wave data, can you help me, I am not a programmer, do not know how to operate, hope the author can see can help me, thank you very much, hope to see can contact me, my email 285611750@qq.com

Loading songs is too laggy.

Load peak is needed to speed up loading

Hope to get your help

It's not ok to spam the project like this. Blocked @ytmsuhsff

authors: thijstriemstra ytmsuhsff


text:
symplegit won't work on linux

Runtime.getRuntime().exec("git");
this won't make it in linux, and this is too strictly validated in basicParamsCheks
typical resultions are with "/bin/sh -c" or allowing "/usr/bin/git"

Hi,
This will be fixed in 1.1 version.
The Maven would be available soon, we must ask to move our com.symplegit from old s01.oss.sonatype.org to Maven Central in order to build.
Meanwhile, you can use the final jar manually:
https://www.symplegit.com/download/symplegit-1.1.jar
(signature: https://www.symplegit.com/download/symplegit-1.1.jar.asc)
The new API is:
final Git sympleGit = SympleGit.custom()
    .setDirectory(repoDirectoryPath)
    .setGitExecutable("/usr/local/bin/git") // Specify the full path to the Git executable
    .build();

authors: janesser ndepomereu

repo: kawansoft/SympleGit-Java


text:
トップページで ipa と apk のプロジェクトを視覚的に区別する

りんごとドロイドくんを使うなど。

1プロジェクトで管理することになったので close

@m0t0k1ch1 逆に、appページでipaとapkのbundleを視覚的に区別する必要が出てきたので、別issue切りましょうかね。

@nobii
#22 に含んでるつもりだったけど、別 issue 化したほうがやりやすいなら切っちゃってくださいまし！

@m0t0k1ch1 りょ。作業始めた時のステータスにもよりますが、 #22 に含まれてるということでOKす。

repo: kayac/alphawing


text:
Document that to process a OCR-D workspace, one needs to use ocrd_fileformat

Internally we had some confusion around this - I think the README should state that a user should use ocrd_fileformat to process workspaces.

See also #21!

repo: kba/page-to-alto


text:
RE2022-83: Run match process in separate process

Pydantic models don't pickle in some cases - it appears to have something to do with the validation function. Required some refactoring.

Tests are failing due to codecov upload

repo: kbase/collections


text:
🛑 Portainer is down

In a64b10d, Portainer (https://portainer.byungchan.kim) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Portainer is back up in 4164696 after 1 day, 43 minutes.


text:
Added payment webhooks

Adds the structures for payment webhook support, as well as the documentation I could find on Square's api reference website.

The structs I made are missing the keyword pub :sweat_smile:

No worries! I should have caught that. I fixed it in the newest version


text:
Way to include different highlight.js (with more/different languages to highlight)?

Is there a way, or could there be added a way to import different variants of the highlight.pack.js file? The one included only supports the standard choice of languages I think and there are many more to choose from.

Never mind, importing highlight.pack.js in a script tag where ever code-sample is used does exactly what I want. Thanks and great element!

FYI. I’m going to include more languages in a future release using polymer 3.

repo: kcmr/code-sample