explore
Explore
door-enter
Log in
menu
announcement

Spectrum is now read-only. Learn more about the decision in our official announcement.

Theia

Eclipse Theia - Cloud & Desktop IDE

link
https://theia-ide.org
Channels
# All channels
view-forward
# General
Team
Akos Kitta
@kittaakos
Anatoliy Bazko
@abazko
Sven Efftinge
@svenefftinge
Paul Maréchal
@marechal-p
Anton Kosyakov
@anton-kosyakov
Casey Flynn
@caseyflynn
Florent BENOIT
@florentbenoit
Jan Bicker
@jbicker
Artem Zatsarynnyi
@artem-z
Simon Marchi
@simark
Liang
@elaihau
Gorkem Ercan
@gercan
Jacques Bouthillier
@jacques-bouthillier
Rob Moran
@thegecko
Miro Spönemann
@spoenemann
Alex Tugarev
@alex-tugarev
Marc Dumais
@marc-dumais
Vince Fugnitto
@vince-fugnitto

Restarting Theia Programmatically

April 29, 2019 at 12:22pm
Thomas Mäder
@tsmaeder

Restarting Theia Programmatically

April 29, 2019 at 12:22pm
I'm trying to implement the VS Code "workbench.action.reloadWindow" command. For example, vscode-java uses it to restart VS Code and thereby itself. I'm a bit confused as to what "restart" would mean for Theia, though. I am thinking that we would have to restart any backend services and in particular all plugins (as they would need to reinitialize). Does anyone have ideas on how to best approach this problem?
April 29, 2019 at 1:15pm
Team
1:15pm
sounds like the same problem that solved when we developed the theia-extension runtime installer. We have a main process that (re)starts a secondary process containing the application. How does VS Code do it?
1:24pm
As I understand it, they shut down all contributions and then restart.
1:24pm
But I don't see a clear lifecycle in Theia.
1:24pm
What's the theia-extension runtime installer?
1:49pm
Restart the application, not the process, that is.
1:51pm
Anyway, Since our plugin system is open for extension (think running plugins in Che sidecar containers), we'd likely have to introduce some restart logic into a protocol somewhere in order to have a clean restart.
Team
2:41pm
We might have to restart the whole application to clean up any side-effects the extensions made? I.e. registration of commands, etc?
April 30, 2019 at 9:55am
Team
9:55am
When you reload the page all vs code extensions are reloaded from scratch as well as user session, would not it be enough?
Edited
9:56am
We've removed cluster module recently and i'm not keen on retroducing it. It was causing complexity in electron app with different dev/prod setups and additional indirection.
May 2, 2019 at 8:19am
8:19am
Because a new plugin host process is started? But what of the old plugins? How are they properly shut down? And I haven't got a clue how we would do that in the case of Che, where the plugin host processes are not started by theia itself.
Team
12:00pm
in pure Theia old host process is shutdown with all plugins and a new is started
12:03pm
it could be done without reload i guess, if there is a programmatic way to ask the host process to reload and it ensures that unloaded plugins properly remove all contributions from main process.
12:06pm
I don't see such capabilities in HostedPluginSupport, it only can load more plugins, not unload existing
12:07pm
We will need it later if we want to support uninstall plugin UI without page reload as well.
12:11pm
I wonder how multiple windows per a workspace are supporetd in Che if a new host process is not started for each window.
May 3, 2019 at 9:10am
9:10am
I dont' think multiple windows will work in Che.
May 13, 2019 at 9:00am
9:00am
Actually, after reading through a ton of code, I've convinced myself that all the plugin stuff (even in Che) is properly connection scoped, so a simple window reload should do the trick.