Skip to content
This repository was archived by the owner on Sep 21, 2019. It is now read-only.

Conversation

ktonga
Copy link
Contributor

@ktonga ktonga commented Nov 14, 2016

It's a work in progress only shared to get some early feedback, not ready to be merged yet. Still trying to fix a problem that prevents it to work properly.

There's a few logging lines to debug the problem, please ignore them by now.

New command to restart ensime servers without leaving the Vim session
Copy link
Contributor

@jvican jvican left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! Have you tested these changes locally?

@ktonga
Copy link
Contributor Author

ktonga commented Dec 30, 2016

@jvican, yes, i did, sadly it's not working. Something related to the threading system is not working as I expected, as a result it doesn't execute the shutdown sequence of steps in the order the should be executed. That's why I tagged this PR as a WIP.
Was hoping any of the refractors @ches is working on could make the things work.

@jvican
Copy link
Contributor

jvican commented Jan 1, 2017

Cool, hope to see this feature soon. In my opinion, it's one of the most important ones. Spurious errors happen in the communication between client and servers and being able to restart the connection is a huge improvement in UX. We also need to figure out what's going on under the hood with the connection. Stability and predictability should be a primer concern for us 🥇 I don't know whether you guys agree on this.

@jvican jvican mentioned this pull request Jan 1, 2017
@ches ches added this to the Server Lifecycle Control milestone Jan 2, 2017
ches referenced this pull request in ches/ensime-vim Jan 7, 2017
Killing the server doesn't completely lead to everything restarting yet,
but it's almost there. Might leave the rest to @ktonga on #350. 

Generally it's supposed to be an invariant that if client's
self.connected is true, then self.ws should be set--so use that
everywhere instead of having a mix that's confusing.
ches referenced this pull request in ches/ensime-vim Jan 13, 2017
Killing the server doesn't completely lead to everything restarting yet,
but it's almost there. Might leave the rest to @ktonga on #350. 

Generally it's supposed to be an invariant that if client's
self.connected is true, then self.ws should be set--so use that
everywhere instead of having a mix that's confusing.
ches referenced this pull request in ches/ensime-vim Aug 26, 2017
Killing the server doesn't completely lead to everything restarting yet,
but it's almost there. Might leave the rest to @ktonga on #350. 

Generally it's supposed to be an invariant that if client's
self.connected is true, then self.ws should be set--so use that
everywhere instead of having a mix that's confusing.
ches referenced this pull request in ches/ensime-vim Aug 26, 2017
Killing the server doesn't completely lead to everything restarting yet,
but it's almost there. Might leave the rest to @ktonga on #350.

Generally it's supposed to be an invariant that if client's
self.connected is true, then self.ws should be set--so use that
everywhere instead of having a mix that's confusing.
ches referenced this pull request in ches/ensime-vim Aug 27, 2017
Killing the server doesn't completely lead to everything restarting yet,
but it's almost there. Might leave the rest to @ktonga on #350.

Generally it's supposed to be an invariant that if client's
self.connected is true, then self.ws should be set--so use that
everywhere instead of having a mix that's confusing.
@ktonga ktonga closed this Jun 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants