Remote kernel does not work after updating to Hydrogen 2.16.1
See original GitHub issuemacOS Big Sur 11.2.3 Atom 1.56.0 x64 Hydrogen 2.16.1
#2094 has been addressed and updated to Hydrogen 2.16.1.
I found a bug where the connection to the remote kernel did not work properly after the update.
Rolled back Hydrogen to 2.15.3 with apm
, and confirmed that it works correctly.
I will try not to update until the issue is resolved.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Hydrogen can't start kernel and remote kernel doesn't work
When I try to start a kernel for the first time after starting Atom a message that the Python3 Kernel is updated pops...
Read more >Troubleshooting Guide · Hydrogen - nteract
Hydrogen stopped working after updating Atom. Whenever your Atom is upgraded, the Hydrogen package needs to be rebuilt. Atom should prompt you to...
Read more >hydrogen - Bountysource
When I open Atom and try to run any code for the first time, Hydrogen show me the Kernels are updated, but immediately...
Read more >Release 7.11.1 The IPython Development Team
To connect to a specific kernel once you have several kernels running, ... IPython is made to run arbitrary code anyway) it is...
Read more >Hydrogen successfully installed but can't execute on Atom
Versions: Python 3.10.2; macOS Monterey; Atom 1.59; Hydrogen 2.16.3. Additional details: { "kernelspecs" ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is fixed in the latest version. Hydrogen now prompts for authentication in case it could not find a session.
I see. I will check if the token entered in the UI is not transferred to the server correctly!