Skip to content
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

Fix reconnecting after hibernation on Windows #11739

Merged
merged 4 commits into from
Dec 3, 2024

Conversation

farmaazon
Copy link
Contributor

Pull Request Description

Fixes #11716

The previoud implementation of restoring execution context assumed, that any synchronization in progress on connection close will fail - but actually if the synchronization just waited for executionContext/create, it might be successfull and effective after reconnecting.

Also, show "Language Server connection lost" when the actual language server connection is lost, and dismiss the message on reconnect.

Important Notes

The hibernation still does not work properly - connection to Project Manager is not restored.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

  • The documentation has been updated, if necessary.
  • [ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
  • All code follows the
    Scala,
    Java,
    TypeScript,
    and
    Rust
    style guides. In case you are using a language not listed above, follow the Rust style guide.
  • [ ] Unit tests have been written where possible.
  • [ ] If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
    or the Snowflake database integration, a run of the Extra Tests has been scheduled.
    • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

@farmaazon farmaazon added CI: No changelog needed Do not require a changelog entry for this PR. -gui labels Dec 3, 2024
@farmaazon farmaazon self-assigned this Dec 3, 2024
Copy link

github-actions bot commented Dec 3, 2024

🧪 Storybook is successfully deployed!

📊 Dashboard:

@farmaazon
Copy link
Contributor Author

I still need to test it: let nobody attach "Ready to merge" label too eagerly!

@farmaazon
Copy link
Contributor Author

Tested: the fix works fine.

@farmaazon farmaazon added the CI: Ready to merge This PR is eligible for automatic merge label Dec 3, 2024
@mergify mergify bot merged commit 7a3f34d into develop Dec 3, 2024
49 of 50 checks passed
@mergify mergify bot deleted the wip/farmaazon/fix-reconnecting branch December 3, 2024 16:08
jdunkerley pushed a commit that referenced this pull request Dec 3, 2024
Fixes #11716

The previoud implementation of restoring execution context assumed, that any synchronization in progress on connection close will fail - but actually if the synchronization just waited for executionContext/create, it might be successfull and effective after reconnecting.

Also, show "Language Server connection lost" when the actual language server connection is lost, and dismiss the message on reconnect.

# Important Notes
The hibernation still does not work properly - connection to Project Manager is not restored.

(cherry picked from commit 7a3f34d)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-gui CI: No changelog needed Do not require a changelog entry for this PR. CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Duplicate context creation on re-connection
2 participants