Example from cmd/server does not work as expected
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 539
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
I run
go run cmd/server/main.go
server starts, outputs
Running...
Then I run
curl 'localhost:8081/set?key=a&value=1'
server outputs
Set: [a]1
then I run
curl 'localhost:8081/cache?key=a'
server outputs
Fetching value for key 'a'
curl hangs for a while then outputs
context deadline exceeded
I expect server will output the value 1 set for the key a
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Reproduce the issue with cmd/server/main.go and the /set and /cache curl requests described in the report. Trace those handlers to determine why the value for key a is not returned; done means the cache request returns 1 instead of timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100