lichess-org / lichess-org/external-engine
limited depth?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 94
- Forks
- 29
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 2
Description
it seems like I can only get analysis to depth 28, I hacked a `self.send("go depth 40")` and even then it closes the connection early:
> DEBUG:root:45973 >> info depth 16 seldepth 21 multipv 5 score cp 11 nodes 3102148 nps 3858393 hashfull 30 tbhits 0 time 804 pv d1c2 f8b4 e2e3 c7c5 d4c5 b6c5 c1d2 e8h8 f1e2 d7d6 e1h1 b8d7 c3b5 d8e7 f1d1 b4d2 c2d2 f6e4
> DEBUG:root:45973 >> bestmove e2e3 ponder f8b4
> INFO:root:Connection closed while streaming analysis
> DEBUG:urllib3.connectionpool:https://engine.lichess.ovh:443 "POST /api/external-engine/work HTTP/1.1" 204 0
is there maybe a timeout somewhere I've missed? ideally I would like a `go infinite` and handle the `stop` signal then
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 with the /api/external-engine/work request and the analysis streaming path; compare the handling of `go depth 40` with the requested `go infinite` and `stop` flow. Trace where the connection closes and identify the timeout or lifecycle condition, then verify that indefinite analysis stops cleanly without an early disconnect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100