-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Uncaught ReferenceError: spyder_terminal is not defined #327
Comments
Hey @mrclary, thanks for reporting. I noticed this too in the Github action logs, but I think this problem comes from one of the Javascript libraries that come as part of Spyder-terminal. Could you post a screenshot of how that message is shown in the internal console? |
Checking this as @mrclary says even with the plugin disabled in the preferences it is getting loaded. When disabling it the terminal pane is not visible but the plugin is still listed in the panes available. Checked this with the Windows installer. My guess is that the reference error messages are generated due to some qt to js/js to qt code that is trying to get some reference while the mainwindow is starting but the plugin is not yet fully up. Seems like after the mainwindow is visible it takes sometime for the terminal to start (I'm seeing the terminal as a white pane for a moment while starting): Also I'm seeing another message in the internal console - Seems like the messages stop being generated once the terminal is fully up |
Hi guys! This is happening in the installers or in your development environments? |
@steff456, this is happening in both the development environment (bootstrapping in conda environment) and in the standalone macOS application (PR builds and local builds, since 5.2.2 release did not have spyder-terminal). |
@steff456, for reference, I listed my conda environment in this comment. |
Checked again and this happens to me in a conda env with Spyder and Spyder terminal installed from conda-forge, running from |
This is kind of serious and we should try to address it before 5.3.0. Everyone else agree with that? Ok, this looks annoying but not so serious to me. They are probably warnings emitted while the spyder-terminal server has not started yet and some JS library is looking for it. |
I agree. I'll open a separate issue for it. |
I agree that this is annoying but may not be serious. |
Thanks @mrclary! |
Description
What steps will reproduce the problem?
Output from bootstrap --debug (or internal console if not debug) shows a long string of
Uncaught ReferenceError: spyder_terminal is not defined
.This occurs independent of whether the Terminal external plugin is enabled or disabled in Preferences.
Perhaps unrelated: disabling Terminal plugin in Preferences does not seem to have any effect; it is still loaded.
All the above manifested with clean config files.
Versions
Dependencies
Dependencies
The text was updated successfully, but these errors were encountered: