Project-MONAI / Project-MONAI/MONAI
pylint v3.0 false alarm
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 8.7k
- Forks
- 1.6k
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 20
Description
...
Traceback (most recent call last):
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/pylint/__main__.py", line 10, in <module>
pylint.run_pylint()
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/pylint/__init__.py", line 34, in run_pylint
PylintRun(argv or sys.argv[1:])
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/pylint/lint/run.py", line 211, in __init__
linter.check(args)
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/pylint/lint/pylinter.py", line 679, in check
check_parallel(
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/site-packages/pylint/lint/parallel.py", line 153, in check_parallel
for (
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/concurrent/futures/process.py", line 484, in _chain_from_iterable_of_lists
for element in iterable:
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/concurrent/futures/_base.py", line 619, in result_iterator
yield fs.pop().result()
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/concurrent/futures/_base.py", line 444, in result
return self.__get_result()
File "/opt/hostedtoolcache/Python/3.8.18/x64/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.
Check failed!
Please run auto style fixes: ./runtests.sh --autofix
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
The report only provides a traceback through pylint/lint/pylinter.py and pylint/lint/parallel.py, plus the command ./runtests.sh --autofix. Start by reproducing the failure with the reported Python 3.8 and pylint v3.0 setup, then inspect the parallel-check path. Done means identifying the false alarm's cause and making the reported style workflow complete successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100