-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Python test extension discovery of tests broken #24292
Comments
@shane99a Is there any particular reason why you have set |
I opted out for But I figured out through a lot of debugging, that there was an import to an external library that is triggering the extension issue. I unfortunately cannot change anything regarding the external library there as I'm not sure where to even debug that code. But here's where I'm a little confused because when I run the extension command in the terminal then it seems to run just fine:
There is a json payload outputted which I assume is what the extension is using for display. I have hidden some of the json fields due to source code details but you get the idea. Also I ran I don't think the DeprecationWarning is the issue. What I really would like is some useful stack trace errors or debug logs that could help point to the exact issue in the test extension. I would appreciate some help here @karthiknadig . |
Ok I figured it out. It turns out I had to then clear cache and reload window after opting into: |
Sorry for the delay! The work around is very interesting- didn't expect that to be the issue! We will me moving off the experiment (and making that the default) so hopefully that will avoid it in the future. |
going to close this as it seems resolved |
What is
swigvarlink
?Additional info
The text was updated successfully, but these errors were encountered: