hovering over flake8 errors no longer shows error
See original GitHub issueEnvironment data
- VS Code version: Version: 1.62.0-insider (Universal) Commit: ff1e16eebb93af79fd6d7af1356c4003a120c563 Date: 2021-10-29T05:14:09.436Z Electron: 13.5.1 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Darwin x64 20.6.0
- Extension version (available under the Extensions sidebar): v2021.10.1365161279
- OS and version: MacOS 11.6
- Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.2 via pyenv
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): poetry
- Relevant/affected Python packages and their versions: flake8 3.9.2
- Relevant/affected Python-related VS Code extensions and their versions: ❯ flake8 --version 3.9.2 (aaa: 0.12.0, flake8-bandit: 2.1.2, flake8-broken-line: 0.3.0, flake8-bugbear: 21.9.2, flake8-comprehensions: 3.7.0, flake8-darglint: 1.8.0, flake8-debugger: 4.0.0, flake8-docstrings: 1.6.0, pydocstyle: 6.1.1, flake8-eradicate: 1.1.0, flake8-string-format: 0.3.0, flake8_2020: 1.6.0, flake8_commas: 2.1.0, flake8_isort: 4.0.0, flake8_quotes: 3.3.0, mccabe: 0.6.1, naming: 0.11.1, pycodestyle: 2.7.0, pyflakes: 2.3.1, rst-docstrings: 0.2.3, wemake_python_styleguide: 0.15.3) CPython 3.7.2 on Darwin
- Value of the
python.languageServer
setting: Default
Expected behaviour
flake8 messages when hovering. This is VSCode 1.61:
Note the flake8 output on the first line
Actual behaviour
wiggly underlines are only 1 character wide, not the whole word.
pop up only includes base information and not flake8 messages
problems tab shows flake8 messages as expected
Steps to reproduce:
simple program with flake8 errors
x = "hi"
if x == "hello" or x == "hi":
print("G'day")
❯ flake8 --select=B,B9,C,D,E,F,S,W,W504 --ignore=C812,C813,C815,C816,E203,E501,S101,W503,WPS111,WPS237,WPS301,WPS305,WPS306,WPS323,WPS336,WPS421,WPS465 --inline-quotes='"' --max-complexity=18 --max-imports=15 --max-line-complexity=18 --max-line-length=88 --max-local-variables=15 --max-module-members=15 --per-file-ignores="test_*:D102,DAR101,WPS110,WPS211,WPS226,WPS317,WPS432,WPS442,WPS450" --doctests --format="%(row)d,%(col)d,%(code).1s,%(code)s:%(text)s" crap.py
1,1,D,D100:Missing docstring in public module
3,4,W,WPS514:Found implicit `in` condition
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Logs
Output for Python
in the Output
panel (View
→Output
, change the drop-down the upper-right of the Output
panel to Python
)
XXX
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:18
Top Results From Across the Web
hovering over flake8 errors no longer shows error #135990
i have linting enabled and this code has flake8 warnings; hover over the coloured wiggly underline but nothing happens. In 1.61 it shows...
Read more >How can I make flake8 only detect errors? - Stack Overflow
I want flake8 to ignore all warning, but I can't find any option to detect error-only after searching flake8 documentation.
Read more >Linting Python in Visual Studio Code
Issues are shown in the Problems panel and as wavy underlines in the code editor. Hovering over an underlined issue displays the details:....
Read more >Selecting and Ignoring Violations — flake8 6.0.0 documentation
Extending the Default Ignore List. This tells Flake8 to ignore any error codes starting with E1 and E23 , in addition the default...
Read more >Use black, mypy, and pylint to make your Python code more ...
You can press F8 or CTRL K+CTRL I (first press CTRL K then CTRL I) to show the hints. The shortcuts are helpful...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The hitbox issue has been fixed in the main branch of
vscode
. I guess it will be included in1.63.0
Yes, it’s the same problem. I have tried and can confirm it.