You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are seeing strange, somewhat non-deterministic errors in pyright. I say "somewhat non-deterministic" because we don't always see the error, but when we do, it usually complains about the same erroneous thing.
For example, we often get this error:
path/to/util.py:8:8 - error: Import "urllib.parse" is not accessed (reportUnusedImport)
Despite the fact that is IS actually accessed in the module:
We are running pyright 1.1.405 in CI, and we are getting the erroneous pyright errors quite frequently. I tell my developers to just rerun the job and it will probably pass in the 2nd attempt... but this is not ideal. What's going on?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We are seeing strange, somewhat non-deterministic errors in pyright. I say "somewhat non-deterministic" because we don't always see the error, but when we do, it usually complains about the same erroneous thing.
For example, we often get this error:
Despite the fact that is IS actually accessed in the module:
We are running pyright 1.1.405 in CI, and we are getting the erroneous pyright errors quite frequently. I tell my developers to just rerun the job and it will probably pass in the 2nd attempt... but this is not ideal. What's going on?
Beta Was this translation helpful? Give feedback.
All reactions