Report errors during parsing stage

Open

#22 opened on Mar 5, 2025 0 comments 0 reactions 1 assignee View on GitHub

@Emyrk is already working on this.

Since Mar 5, 2025.

Assessment

This issue has not been assessed yet.

Parsing errors are logged via slog.Logger

This needs to be corrected to not use the global logger. These warnings/errors should be silenced at worst, and reported at best via diagnostics.

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.

[GEP-28] `gardenadm restore`: Add developer docs for the local setup Open

area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement

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

gardener/gardener#15788 · Opened Sep 23, 2026
Codex skills: `git rev-parse --verify --` rejects every explicit ref Open

Difficulty 1/5 Under an hour Newbie friendliness 85/100

kenn-io/roborev#1229 · Opened Sep 23, 2026
download_media returns a relative path that breaks when the bridge and MCP server run from different working directories Open

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

FelixIsaac/whatsapp-mcp-extended#85 · Opened Sep 23, 2026
`docker logout docker.io` does not remove Docker Hub credentials Open

kind/bug status/0-triage

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

docker/cli#7326 · Opened Sep 23, 2026
Truncation of tekton task names causes conflict even though names are different Open

🤔 refinement needed

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

equinor/radix-operator#1979 · Opened Sep 23, 2026