Open mrclary opened 2 years ago
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?
Also, @steff456, are you seeing the same problem with Spyder started from bootstrap
?
@dalthviz, are you seeing the same error with the Windows installer?
Both things will let us know if this is exclusive to the Mac app or not.
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 - Uncaught TypeError: Cannot read property 'fit' of undefined
:
Seems like the messages stop being generated once the terminal is fully up
From bootstrap with --safe-mode
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). I have not tested previous versions of spyder-terminal, only the latest 1.2.1.
@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 bootstrap.py
and with the Windows installer with Spyder terminal bundled (installer available from spyder-ide/spyder#17247)
Checking this as @mrclary says even with the plugin disabled in the preferences it is getting loaded
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.
Checking this as @mrclary says even with the plugin disabled in the preferences it is getting loaded
This is kind of serious and we should try to address it before 5.3.0. Everyone else agree with that?
I agree. I'll open a separate issue for it.
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 that this is annoying but may not be serious.
I agree. I'll open a separate issue for it.
Thanks @mrclary!
Just in case, regarding the plugin enabled state seems like that is caused since the validation done to check if the plugin is enable in Spyder is giving a No option 'enable' in section: 'terminal'
. I checked with the spyder-boilerplate plugin used with the slow tests and seems like this also happens there so probably something is missing when mapping external plugins options or using the CONF manager to get those options
Great detective work @dalthviz! Then the solution should be simple: adding enable
to the default options in Spyder-terminal.
Most internal plugins have it:
so we should add it to external ones as well in order to totally disable them with the new teardown mechanism.
@steff456, could you take care of that?
@steff456, could you take care of that?
Sure, I can take care of that.
Just for context, I did add the option to not be able to disable the terminal plugin as seen here: https://github.com/spyder-ide/spyder-terminal/blob/703cfdd92ab42ce21730eef9565adefbfa88df10/spyder_terminal/terminalplugin.py#L48
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
``` # Mandatory: applaunchservices >=0.1.7 : 0.2.1 (OK) atomicwrites >=1.2.0 : 1.4.0 (OK) chardet >=2.0.0 : 4.0.0 (OK) cloudpickle >=0.5.0 : 2.0.0 (OK) cookiecutter >=1.6.0 : 1.7.3 (OK) diff_match_patch >=20181111 : 20200713 (OK) intervaltree >=3.0.2 : 3.0.2 (OK) IPython >=7.31.1;<8.0.0 : 7.32.0 (OK) jedi >=0.17.2;<0.19.0 : 0.18.1 (OK) jellyfish >=0.7 : 0.9.0 (OK) jsonschema >=3.2.0 : 4.4.0 (OK) keyring >=17.0.0 : 23.4.0 (OK) nbconvert >=4.0 : 6.4.2 (OK) numpydoc >=0.6.0 : 1.2 (OK) parso >=0.7.0;<0.9.0 : 0.8.3 (OK) pexpect >=4.4.0 : 4.8.0 (OK) pickleshare >=0.4 : 0.7.5 (OK) psutil >=5.3 : 5.9.0 (OK) pygments >=2.0 : 2.11.2 (OK) pylint >=2.5.0 : 2.12.2 (OK) pyls_spyder >=0.4.0 : 0.4.0 (OK) pylsp >=1.3.2;<1.4.0 : 1.3.2 (OK) pylsp_black >=1.0.0 : 1.1.0 (OK) qdarkstyle =3.0.2 : 3.0.2 (OK) qstylizer >=0.1.10 : 0.2.1 (OK) qtawesome >=1.0.2 : 1.1.1 (OK) qtconsole >=5.2.1;<5.3.0 : 5.2.2 (OK) qtpy >=1.5.0 : 2.0.1 (OK) rtree >=0.9.7 : 0.9.7 (OK) setuptools >=49.6.0 : 60.9.3 (OK) sphinx >=0.6.6 : 3.5.4 (OK) spyder_kernels >=2.2.1;<2.3.0 : 2.3.0.dev0 (OK) textdistance >=4.2.0 : 4.2.2 (OK) three_merge >=0.1.1 : 0.1.1 (OK) watchdog >=0.10.3 : 2.1.6 (OK) zmq >=17 : 22.3.0 (OK) # Optional: cython >=0.21 : 0.29.28 (OK) matplotlib >=2.0.0 : 3.5.1 (OK) numpy >=1.7 : 1.22.2 (OK) pandas >=1.1.1 : 1.4.1 (OK) scipy >=0.17.0 : 1.8.0 (OK) sympy >=0.7.3 : 1.9 (OK) # Spyder plugins: spyder_terminal.terminalplugin 1.2.1 : 1.2.1 (OK) ```