[Question][Help req] bunch of runc threads, high cpu load

Open

#2,055 opened on May 14, 2019 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 15/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: docker, go
Domain: backend, cli

Research direction

No repository files or tests are named. Start by examining the repeated forkstat events for the runc state command and its associated containerd-shim process, then reproduce the behavior with the reported runtime and collect enough system and container details to establish an actionable cause.

Written by the indexing model from the issue text.

Description

Hey!

Im trying to debug high load on servers and somehow it lead me to runc.

So the problem is that when i run forkstat command on server i see a lot of following output and it does not stop:

Time     Event   PID Info   Duration Process
13:58:16 clone 19966 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19970 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19970      0    0.028 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19968      0    0.029 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19967      0    0.029 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19969      0    0.029 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19966      0    0.036 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 fork  27527 parent          containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053 -address /run/containerd/containerd.sock -containerd-binary /usr/bin/containerd -runtime-root /var/run/docker/runtime-runc
13:58:16 fork  19971  child          containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053 -address /run/containerd/containerd.sock -containerd-binary /usr/bin/containerd -runtime-root /var/run/docker/runtime-runc
13:58:16 exec  19971                 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19971 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19972 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19971 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19973 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19971 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19974 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19971 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19975 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19971 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19976 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19974      0    0.027 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19975      0    0.027 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19973      0    0.028 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19971      0    0.035 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19972      0    0.028 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19976      0    0.006 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 fork  27527 parent          containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053 -address /run/containerd/containerd.sock -containerd-binary /usr/bin/containerd -runtime-root /var/run/docker/runtime-runc
13:58:16 fork  19977  child          containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053 -address /run/containerd/containerd.sock -containerd-binary /usr/bin/containerd -runtime-root /var/run/docker/runtime-runc
13:58:16 exec  19977                 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19977 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19978 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19977 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19979 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19977 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19980 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19977 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19981 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19977 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19982 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19977      0    0.031 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19981      0    0.025 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19979      0    0.026 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19980      0    0.026 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19978      0    0.026 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19982      0    0.008 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 fork  27527 parent          containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053 -address /run/containerd/containerd.sock -containerd-binary /usr/bin/containerd -runtime-root /var/run/docker/runtime-runc
13:58:16 fork  19983  child          containerd-shim -namespace moby -workdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053 -address /run/containerd/containerd.sock -containerd-binary /usr/bin/containerd -runtime-root /var/run/docker/runtime-runc
13:58:16 exec  19983                 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19983 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19984 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19983 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19985 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19983 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19986 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19983 parent          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 clone 19987 thread          runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19986      0    0.028 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19987      0    0.028 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19985      0    0.028 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19984      0    0.028 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053
13:58:16 exit  19983      0    0.036 runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v1.linux/moby/4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053/log.json --log-format json state 4a2ad302bce4fd2d41665d6ab76c380c803b94ee40bf444d904783e46eeba053

Could someone give some insights what this means or how to read, interpret it? Like something in containers are forking a lot?

The whole story is helm redis-ha chart related, when i deploy redis-ha to kubernetes cluster.

Dominant language: Go
Stars: 13.5k
Forks: 2.3k
Avg merge: 2d 8h
Merged PRs (30d): 30

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[optimization:agents-md-curator] AGENTS.md: compress duplicated Debugging & Logging section and merge redundant autopilot rules Open

optimization optimization:agents-md-curator

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

githubnext/gh-aw-cao#13143 · Opened Sep 20, 2026
fix(ui/spend): normalize mnemonic before keystore reattach comparison Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

blinklabs-io/bursa#904 · Opened Sep 20, 2026
docs(parser): clarify State callback lifecycle Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

yanet-platform/ipfw-go#129 · Opened Sep 20, 2026
[confmap/provider/googlesecretmanagerprovider] Missing URI format validation for Google Secret Manager resource paths Open

bug confmap/provider/googlesecretmanagerprovider needs triage

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments · Opened Sep 20, 2026
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 90/100

coder/coder#29623 · 1 comment · Opened Sep 20, 2026

More Go issues