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
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
This issue has come up while packaging Sourcetrail for NixOS (NixOS/nixpkgs#95530). There seems to be a compatibility problem with recent commits of jedi (davidhalter/jedi@216f976) that prevents the SourcetrailPythonIndexer from resolving symbols from the Python standard library. Though not strictly a bug since we were obviously attempting to use an unsupported configuration, we thought it might be worth creating a issue to avoid problems when the next version of jedi is released.
Here's a screenshot with the errors:
The text was updated successfully, but these errors were encountered:
I get this error as well on Archlinux, and I suspect that #52 is of the same kind - what I experience is that occasionally symbols from the standard library are not resolved, and restarting the scan can help.
I wouldn't say that it is a brand new issue - I experience this kind of behavior already for a couple of months.
I wouldn't say that it is a brand new issue - I experience this kind of behavior already for a couple of months.
I think this is a separate issue because no amount of restarting helped. Since downgrading jedi did fix the issue however, I see it likely that it is a problem introduced by recent commits from jedi.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue has come up while packaging Sourcetrail for NixOS (NixOS/nixpkgs#95530). There seems to be a compatibility problem with recent commits of jedi (davidhalter/jedi@216f976) that prevents the SourcetrailPythonIndexer from resolving symbols from the Python standard library. Though not strictly a bug since we were obviously attempting to use an unsupported configuration, we thought it might be worth creating a issue to avoid problems when the next version of jedi is released.
Here's a screenshot with the errors:
The text was updated successfully, but these errors were encountered: