-
Notifications
You must be signed in to change notification settings - Fork 201
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
Plugin crash crashes whole diagnostic #153
Comments
Hey @Richardk2n, thanks for reporting. Could you post a traceback when that happens? I don't know how easy it could be to catch those errors and log them, but we could give it a try. |
By the way, what do you think about migrating your plugin to our organization? In the future we'd like to officially integrate it with Spyder, so it'd be nice having it here. Also, if you have some free time, you could give us a hand to add MyPy linting to Spyder for version 6 (we could guide you on how to do that). |
I added an assert 0 == 1 to simulate an error. If an error occurs in the startup code (pylsp_settings), spyder informs we (with the internal issue accured popup) about an issue with the following traceback:
Spyder hands at "LSP Python: starting" and no linting ever happens. When the issue is in the actual lint code spyder does not notice (at least it does not report an error)
Also no linting accurs, but spyder is totaly oblivious to it. Looking at those tracebacks and reading a little into the files, I guess, that it could be somewhat solved within pylsp, but the abstraction makes it difficult to handle without modifying Pluggy. |
Moving it to the organization would be something I would be willing to do, given that I can still work on it and given that I have a say in major changes. Furthermore, it would be nice if you could help with correct handling of the license, because I am not very sure if the current state of my license is correct. As long as I get credit, it does not matter too much for me, where I do the work. I do not really have a lot of free time, but I would really like to see it added to spyder in the long term. I would gladly invest some evenings and most weekends into that. |
Ok, it seems we need to catch any error when loading plugins, and just log them, so the server doesn't crash. I'll try to take a look at for our next version (1.4.0). |
Great! I'll send you an invite and give you the right permissions so you can do the migration. These are the docs about it: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
Sure, we can help you with that. Just open an issue after you migrate the repo and we'll take a look at it.
No worries, Spyder 6 will probably be released at the end of the year, or the beginning of the next one, so there's ample time for that. Also, we plan to do developer meetings to start discussing about Spyder development in the coming months, so that'll be a great way for us to tell you how to get started a give you a hand when you're stuck. |
While writing pylsp-mypy (and using it life in spyder), I noticed, that whenever one plugin crashes, the whole diagnostic stops. When the issue is in the startup code spyder tells me the server is starting indefinitely. The reason behind that is likely, that there are no guards to catch crashes. Please correct me if this is wrong. For the plugins you maintain this is somewhat reasonable, but with 3rd party plugins, I think some error handling would be nice.
Please treat this as a feature request rather than a bug.
The text was updated successfully, but these errors were encountered: