-
Notifications
You must be signed in to change notification settings - Fork 29
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
The problem found by mypy do not shown in PROBLEMS #206
Comments
This looks like a bug. I will need to look into this. The following settings are deprecated:
|
Can some one running into this issue provide logs with actual file names? it seems like the file name computation is going wrong somehow. |
These are the mypy logs from clicking on the problem
Other clues:
|
Please note that this is two bugs. "extra files opened when in Reporting Scope is 'workplace'" and "no problems shown when Reporting Scope is 'file'" |
Has there been any progress on this issue? I’m experiencing the same problem. |
@iCasture can you share your full logs from Output > mypy type checker? |
@karthiknadig Sorry for the delayed response. Below is the complete log:
From the log, we can see that mypy detected errors, but there is no output from the mypy extension in the |
In OUTPUT-Mypy Type Checker I can see mypy really runs and finds some problem in my file, but there are not shown in PROBLEMS
The OUTPUT-Mypy Type Checker ouput:
When I set Reporting Scope as workspace, it actually show all problems in PROBLEMS, but when I click the problem, it open a new file named

path/to/file/ks.py
but not jump to the corresponding line in current opened file (ks.py
). Actually,path/to/file/ks.py
andks.py
are same file.If this behavior is by design, how could I set the extention to make it as previous. By "previous", I mean when we use
to use mypy. In that time, all found problems will be shown in PROBLEMS, when I click the reported preblems, it just jump to the corresponding line in current file.
The text was updated successfully, but these errors were encountered: