[Bug] safeline-chaos fails update with the following issue server.go:83
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 22.6k
- Forks
- 1.5k
- Avg merge
- 4h 30m
- Merged PRs (30d)
- 11
Description
What happened?
panic: runtime error: invalid memory address or nil pointer dereference
goroutine ... running:
git.in.chaitin.net/safeline-ce/challenge/server.(*APIServer).Shutdown(0xc000... )
/app/server/server.go:83 +0xdb
main.gracefulShutdown(...)
How we reproduce?
- ...attempt container update this error is produced each time
- ...
- ...
Expected behavior
No response
Error log
panic: runtime error: invalid memory address or nil pointer dereference
goroutine ... running:
git.in.chaitin.net/safeline-ce/challenge/server.(*APIServer).Shutdown(0xc000... )
/app/server/server.go:83 +0xdb
main.gracefulShutdown(...)
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
Start by reading server/server.go around line 83 and trace APIServer.Shutdown during the container-update path. Reproduce the failure during an update and identify the nil value behind the panic; done means the update no longer produces the reported shutdown panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100