LeelaChessZero / LeelaChessZero/lczero-client
Unexpected exit from client
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 74
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Client exiting unexpectedly when timed out.
2018/08/07 08:55:21 lc0_main.go:403: Bestmove has timed out, aborting match
2018/08/07 08:55:21 lc0_main.go:336: Waiting for candidate to exit.
2018/08/07 08:55:21 lc0_main.go:326: Waiting for baseline to exit.
2018/08/07 08:55:21 lc0_main.go:552: playMatch: timeout
Suggestion is trying to reconnect or restart client after aborting.
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 in lc0_main.go around the timeout and process-waiting paths referenced in the logs, especially lines 326, 336, 403, and 552. Trace what happens after a best-move timeout and determine how client recovery should work. Done means an aborted match does not leave the client exiting unexpectedly and the client can reconnect or restart as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100