Paths cannot have leading "/" character
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- backend, distributed-systems
Research direction
Start by locating the Zookeeper backend's path-normalization logic and any existing path-related tests. Reproduce the failure with a leading slash, then update the behavior so the issue's standard Zookeeper path form is accepted and add coverage confirming it.
Written by the indexing model from the issue text.
Description
Hello,
I was working with Traefik and I was having issues with it pulling configuration information from Zookeeper. I narrowed it down to this code (an older version) and discovered that if I had a leading "/" on the path, it would fail. The current code looks to be the same for the normalization of the paths, so the "bug" is still there.
Barring a good reason why this behaviour should remain, I'd like to suggest that the code be updated to allow for a leading "/" to be provided as, at least with zookeeper, is the standard way of referencing paths.
- Dominant language
- Go
- Stars
- 848
- Forks
- 204
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from docker/libkv
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AOSSIE-Org/DebateAI#611 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MHSanaei/3x-ui#6737 · 1 comment ·
Maintainers usually reply within 1 day
-
terraform-provider
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
ClickHouse/terraform-provider-clickhousedbops#281 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
open-telemetry/opentelemetry-go-compile-instrumentation#1450 ·
Maintainers usually reply within 2 days