You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on developing a Jupyter Wrapper Kernel for the MetaCall Core library. We have a Dockerfile specified here that allows us to spin a Binder where we can try out the examples.
Unfortunately, this doesn't work with the sub-directories like examples where we host all of our example notebooks. It just displays Kernel starting.. and asks us to wait. This leads to a bad UX since most users would employ the use of example notebooks to try out the kernel.
Expected behaviour
The notebooks in the examples sub-directory should work and execute the code.
Actual behaviour
The notebooks in the examples sub-directory do not work and do not execute the code.
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 馃
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 馃憢
Sorry for the slow response. Have you tried reproducing the error locally with repo2docker?
This sounds like a problem specific to your kernel rather than a bug in binder or repo2docker, but if you can demonstrate a bug please open a new issue with specific details.
If you need more help would you mind posting on the community forum where more people hang out, and the rest of the community can benefit from these discussions 馃榾.
Bug description
Hi 馃憢
I am working on developing a Jupyter Wrapper Kernel for the MetaCall Core library. We have a Dockerfile specified here that allows us to spin a Binder where we can try out the examples.
Unfortunately, this doesn't work with the sub-directories like
examples
where we host all of our example notebooks. It just displaysKernel starting..
and asks us to wait. This leads to a bad UX since most users would employ the use of example notebooks to try out the kernel.Expected behaviour
The notebooks in the examples sub-directory should work and execute the code.
Actual behaviour
The notebooks in the examples sub-directory do not work and do not execute the code.
How to reproduce
Kernel starting, please wait
would be shown.The text was updated successfully, but these errors were encountered: