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
I think that the computer should resolve this upgrade issue automatically. I do not understand this "Auto Update LSP Sever on startup. My scenario appears to be normal and predictable and should not cause a failure. Next time I upgrade NetBeans it might happen again.
I think that the exception must not happen because it is confusing. Perhaps you can change something to make it go away.
From my perspective, I do NOT have any preferences or settings that I am expecting to be migrated, say from NetBeans 18 to NetBeans 19 in this case.
What I would expect to happen is as follows:
Let's look at the point after the import of userdir / preferences from a previous NetBeans version.
I do not necessary expect that NetBeans automatically upgrades my Python plugin. This would be a feature that i do not expect. I would be happy if the plugin was missing after the NetBeans upgrade.
However, I do expect that a fresh plugin installation (from a new version download) works as FRESH in this case.
That means that it should find its dependencies and that the installation should ONLY succeed if all dependencies could be installed. If not, then the installation should fail.
At present, the installation succeeds but all dependencies are missing. This is a defect.
If you implement the flow accordingly, then this might be easier and less work for you.
2 things:
I think that the computer should resolve this upgrade issue automatically. I do not understand this "Auto Update LSP Sever on startup. My scenario appears to be normal and predictable and should not cause a failure. Next time I upgrade NetBeans it might happen again.
I think that the exception must not happen because it is confusing. Perhaps you can change something to make it go away.
Originally posted by @bernard01 in #71 (comment)
The text was updated successfully, but these errors were encountered: