`--threads=0` leads to an assertion violation
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Prerequisites
Please put an X between the brackets as you perform the following steps:
- Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues - Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries. - Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
Description
As of Lean 4.9.0, --threads=0 gives an assertion violation.
Steps to Reproduce
- Run
lean --threads=0 <(echo "example : True := by simp")
Expected behavior: Either silent, or complains that threads=0 is illegal
Actual behavior:
LEAN ASSERTION VIOLATION
File: /home/runner/work/lean4/lean4/src/runtime/object.cpp
Line: 1053
g_task_manager
'unreachable' code was reached
from
Versions
v4.9.0 onwards
Additional Information
[Additional information, configuration or data that might be necessary to reproduce the issue]
Impact
Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.
Contributor guide
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 failure with lean --threads=0 <(echo "example : True := by simp"), then start at src/runtime/object.cpp around line 1052. Trace how the thread count reaches the task manager and ensure the command either completes silently or reports that zero threads is invalid, without an assertion violation.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 75/100