Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No linter output #9550

Closed
demattia opened this issue Jan 11, 2020 · 4 comments
Closed

No linter output #9550

demattia opened this issue Jan 11, 2020 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@demattia
Copy link

After updating the extension to 2020.1.57204 all files show no warnings or highlighted errors anymore. I have no linter output from flake8 and it seems that also output from the python language server is not shown. Reverting to 2019.11.50794 fixes the issue. My custom settings are:

{
    "workbench.iconTheme": "vscode-icons",
    "python.linting.flake8Args": [
        "--max-line-length=88"
    ],
    "python.linting.flake8Enabled": true,
    "[python]": {
        "editor.rulers": [
            88,
        ]
    },
    "terminal.integrated.inheritEnv": false,
    "window.zoomLevel": -1,
    "vsicons.dontShowNewVersionMessage": true,
    "python.dataScience.sendSelectionToInteractiveWindow": true,
    "todohighlight.isEnable": true,
    "todo-tree.highlights.enabled": true,
    "python.jediEnabled": false
}

Any other checks I may perform to help identifying the root cause?

@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Jan 11, 2020
@ghost
Copy link

ghost commented Jan 12, 2020

Linting is no longer working in latest version of this extension. You have to downgrade it until it is fixed.

@RuneDominik
Copy link

At least pylint seems to work under 2020.1.57204 while flake8 does not.

@karthiknadig karthiknadig added triage bug Issue identified by VS Code Team member as probable bug labels Jan 13, 2020
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jan 13, 2020
@kimadeline
Copy link

Hi @demattia 👋 Thank you for reaching out.

In terms of other checks, one helpful thing would be to fill our issue template.

We introduced the use of conda run in version 2020.1.57204 of the extension, however this caused issues, so the work has been reverted (#9490). If you are using conda please download the latest version of the extension (2020.1.58038) to check if your linting problem still persists.

Note: Probably a duplicate of #9481.

@kimadeline kimadeline added the info-needed Issue requires more information from poster label Jan 13, 2020
@demattia
Copy link
Author

demattia commented Jan 15, 2020

Hi @kimadeline, after updating to 2020.1.58038 linter output is back. Looks like #9481 and possibly #9598 are already tracking the potential root cause so I am closing this. I will follow the issue template for any possible future submission. Thank you very much for your help!

@ghost ghost removed the triage label Jan 15, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Jan 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

4 participants