crash with sqlalchemy2 stubs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Crash Report
I can't understand log, so do you have any ideas where I can find a line for this report?
I am using VSCode, vscdoe gives me this error.
Traceback
Daemon crashed!
Traceback (most recent call last):
File "mypy/dmypy_server.py", line 229, in serve
File "mypy/dmypy_server.py", line 272, in run_command
File "mypy/dmypy_server.py", line 331, in cmd_run
File "mypy/dmypy_server.py", line 393, in check
File "mypy/dmypy_server.py", line 568, in fine_grained_increment_follow_imports
File "mypy/server/update.py", line 245, in update
File "mypy/server/update.py", line 328, in update_one
File "mypy/server/update.py", line 388, in update_module
File "mypy/server/astdiff.py", line 164, in snapshot_symbol_table
File "mypy/server/astdiff.py", line 224, in snapshot_definition
File "mypy/server/astdiff.py", line 160, in snapshot_symbol_table
TypeError: str object expected; got None
To Reproduce
(Write what you did to reproduce the crash. Full source code is
appreciated. We also very much appreciate it if you try to narrow the
source down to a small stand-alone example.)
Your Environment
- Mypy version used: 0.930
- Mypy command-line flags: ~/.venv/bin/python -m mypy.dmypy --status-file ~/.config/Code/User/workspaceStorage/2caf0291ecf6795a93085715a3e82615/matangover.mypy/dmypy-26b3c3104152348d4353e0e6c8df6fc0c43c532d.json run --log-file ~/.config/Code/User/workspaceStorage/2caf0291ecf6795a93085715a3e82615/matangover.mypy/dmypy-26b3c3104152348d4353e0e6c8df6fc0c43c532d.log -- . --show-column-numbers --no-error-summary --no-pretty --no-color-output --python-executable ~/.venv/bin/python
- Mypy configuration options from
mypy.ini(and other config files):
[mypy]
plugins = sqlalchemy.ext.mypy.plugin, pydantic.mypy
ignore_missing_imports = True
disallow_untyped_defs = True
- Python version used: 3.9.4
- Operating system and version: Ubuntu 20.04 LTS
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
Start with the traceback paths in mypy/dmypy_server.py, mypy/server/update.py, and mypy/server/astdiff.py, then try to reproduce the crash using mypy 0.930, Python 3.9.4, dmypy, and the reported plugins. A useful outcome requires a minimal reproducible example and a regression test showing that the daemon no longer crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlalchemy
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100