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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binder not working in a sub-directory #1338

Closed
HarshCasper opened this issue Jul 17, 2021 · 2 comments
Closed

Binder not working in a sub-directory #1338

HarshCasper opened this issue Jul 17, 2021 · 2 comments
Labels

Comments

@HarshCasper
Copy link

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 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.

How to reproduce

  • Start the Binder instance here.
  • Go to the examples sub-directory and try executing a notebook.
  • Kernel starting, please wait would be shown.
@welcome
Copy link

welcome bot commented Jul 17, 2021

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.
welcome
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! 馃憢

Welcome to the Jupyter community! 馃帀

@manics
Copy link
Member

manics commented Aug 24, 2021

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 馃榾.

@manics manics closed this as completed Aug 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants