-
Notifications
You must be signed in to change notification settings - Fork 335
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
upgraded to atom 1.2.0, hydrogen now failing - Failed to activate the Hydrogen package #135
Comments
I am having the same issue |
Me too! |
[Enter steps to reproduce below:]
Atom Version: 1.2.0 Stack TraceFailed to activate the Hydrogen package
Commands
Config{
"core": {
"disabledPackages": [
"about",
"metrics",
"timecop",
"package-generator",
"welcome",
"linter-eslint",
"minimap"
],
"themes": [
"atom-dark-ui",
"one-dark-syntax"
]
}
} Installed Packages# User
color-picker, v2.0.13
git-log, v0.4.1
Hydrogen, v0.6.5
linter, v1.11.1
linter-csslint, v1.1.0
linter-less, v2.2.0
linter-lesshint, v1.2.0
linter-xo, v0.9.0
minimap-find-and-replace, v4.3.2
minimap-git-diff, v4.1.8
minimap-highlight-selected, v4.3.1
minimap-linter, v1.0.0
minimap-selection, v4.3.1
# Dev
No dev packages |
Sorry I haven't looked at this yet, I'm super slammed today. I'll dig into this tomorrow if nobody has written a PR to fix it before then. |
The problem seems to be in the The next thing I would investigate is why this behaviour has changed in Atom v1.2.0. |
Should be related to the upgrade from node v3.1 to v4.1.1, as described in the announcement for Atom 1.2. |
It looks like Atom has made |
Hi Will, Thanks for your great efforts. On 16/11/2015 21:05, Will Whitney wrote:
|
@JeremyCavanagh thanks for the support! I'm working on getting this fixed. @n-riesco we may have to think about a new ZMQ solution for @rgbkrk any suggestions? |
@willwhitney My understanding is that the installation problem in Atom v1.2.0 is caused by the I don't see a quick solution to replacing |
Dear all, has this issue been resolved? |
Is anyone aware of a way to revert to an old version of atom in order to work around this problem? I really need Hydrogen to record some screencasts. |
If you'd rather connect to the notebook server from a websocket instead of zmq, we're in the midst of building npm packages for the web API provided by that application. You can try jupyter-js-services, which is the most basic part of it, but it only just became relatively complete and probably isn't super stable yet. It doesn't make much sense to provide the zmq-websocket bridge itself as an npm package, since it's all Python. |
I revert to Atom 1.1 just download the source code zip of the release you want: this case 1.1 cd to download folder of atom 1.1 and run on Mac:
Note: name the app and final directory as you wich. Check code for build in other OS. More info in build in https://github.com/atom/atom/tree/master/docs/build-instructions Had to download the source zip, as using git and chekout kept me building version 1.4. |
@n-riesco thanks for your work on this! Switching over to jupyter-js-services or something similar (maintained by Jupyter, with a stable API, etc) is probably the long-term answer, but hopefully we can get the issue with Atom resolved. It sounds like a change Atom made has been causing issues for others as well. It looks like for the moment reverting is the only workaround, but I expect to have a better answer shortly. |
@minrk I tried sub-ing jupyter-js-services in for jupyter-kernel-launcher for this package and atom-notebook and I am running into a CORS issue. jupyter notebook:
jupyter-js-services: This seems like an issue specific to Atom as the requests are originating from Node and not the browser. Is it possible to use jupyter-js-services within Atom? Would the package need to run a server in order to communicate with the notebook server? See my fork of atom-notebook: gnestor/atom-notebook@86445b3 There seems to be some relevant discussion here: https://github.com/jupyter-incubator/kernel_gateway/wiki/notebook_kernel_gateway |
@willwhitney @n-riesco I've mostly migrated(1) atom-notebook from jupyter-kernel-launcher to jupyter-js-services. That means that it no longer depends on jmp, zmq, bindings, etc. It works fine in Atom >=1.2. @minrk I was able to fix the CORS issue (by following the docs and adding XMLHttpRequest and ws to globals...can you explain how that works?) so now atom-notebook is successfully communicating with jupyter notebook and jupyter kernelgateway. However, I'm only receiving "execute_input" and "status" messages (no "execute_result"). Any idea why that may be?
|
Now that you've got atom notebook working with the js packages, feel free to submit a PR and I'll happily merge it on in and add you to the repo. |
@rgbkrk @willwhitney 2 things before I submit a PR:
// Inside main.activate
let spawn = require('child_process').spawn;
this.kernelGateway = spawn('jupyter kernelgateway');
this.kernelGateway.on('exit', function (code) {
console.log('kernelGateway.exit '+code);
});
this.kernelGateway.stdout.on('data', function (data) {
console.log('kernelGateway.stdout ' + data);
});
this.kernelGateway.stderr.on('data', function (data) {
console.log('kernelGateway.stderr ' + data);
});
this.kernelGateway.on('close', function (code) {
console.log('kernelGateway.close ' + code);
});
// Inside main.deactivate
this.kernelGateway.stdin.pause();
this.kernelGateway.kill(); |
BTW, it looks like @n-riesco was able to get the bindings issue in Atom >=1.2 patched, so the next Atom release should fix this issue for hydrogen and atom-notebook: atom/atom#9660 (comment) |
Last build from source, with Atom 1.4dev already works! |
@themiguelamador Where did you get 1.4, if the last version is 1.3beta? Am I loosing something? |
1.4dev is the version if you build from Source. On a mac, just do this, and it will create the Atom app in your Applications folder.
Note: name the app and final directory as you wich. Check code for build in other OS in https://github.com/atom/atom/tree/master/docs/build-instructions |
I tried to build and run 1.4.0-dev and encountered the following issue (which seems like it may be related to this patch): atom/atom#9860 |
No error at least on running some code in Julia Kernel. Build version 1.4.0-dev-f2155fa yesterday. 1.3 should be more stable when they release the version with the patch mentioned above. I have it above how to build from a previous version, since you have to download the source zip from the release (at least checkout did not work with me to move to a different tag). |
atom-notebook is now fully working using jupyter-js-services and jupyter-kernel-gateway. You can see details on how to migrate in the jupyter-js-services branch of my fork: https://github.com/gnestor/atom-notebook/tree/jupyter-js-services I was also able to fix the path issue that requires Atom to be launched from the command line: gnestor/atom-notebook@419174f @rgbkrk I've submitted a PR. |
Confirmed that Hydrogen is working again on Atom 1.4.0-dev-c0bc38a (current master branch). |
Atom Version: 1.2.0
System: Mac OS X 10.10.5
Thrown From: Hydrogen package, v0.6.5
Stack Trace
Failed to activate the Hydrogen package
Commands
Config
Installed Packages
I tried
apm rm hydrogen; apm install hydrogen
but no luck.The text was updated successfully, but these errors were encountered: