-
Notifications
You must be signed in to change notification settings - Fork 70
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
HTTP 400 : Bad Request #64
Comments
Hi, I am running into the same issue now. |
It seems that for some reason jupyter notebook does not have permission to write hidden files anymore. As a workaround you can start the notebook with |
To follow on erobiquee's excellent advice for a workaround, you can find an example config file 'jupyter_notebook_config.py' here that allows appmode to work in mybinder again. Note that if you are using a The showing the hidden files isn't too much of an issue if you are working in the appmode mode. My example didn't involve interacting with files in the session and so maybe that aspect is messier than usual. |
Hi, I have tried @fomightez's workaround but I think it is broken again. The launch here now returns "500 : Internal Server Error". I have a repo that used to launch into appmode using this url, but now I get "404 : Not Found You are requesting a page that does not exist!" Any suggestions would be greatly appreciated! |
Yes, sorry @olivertlord . MyBinder announced a sort of big update like a week after I got the workaround working and I think changing the default server broke it. That's my guess anyways. It was definitely working well with the workaround just a few days before that. (I noted it seemed broken again already here, but since I just had it working again, I was too discouraged to look into it much at the time. I couldn't quite remember where I had posted the related issue on GitHub and so I missed linking this.) Based on here, I'm wondering if going over into an available terminal by using the URL to switch over to either the JupyterLab or classic interface and running |
No need to apologize @fomightez. I have pasted the log below. I am new here. Do you think I should post this at the Jupyter Community Discourse? I don't know hpw to interpret it. Launching jupyter-lab |
Had that run included trying to open in the appmode mode? It may be enough to just tag the post announcing MyBinder switching the server over with a link to your post above and saying Appmode had been working via launches from MyBinder after a setting the config to show hidden files. And then it broke again around the time of this announcement. Then say see this thread for more details. |
Sorry - now I understand. The log does not include me attempting to launch in appmode. I will create a new one, and then I will tag the announcement and try and explain things. Thanks for your help. |
See reply here and the note over at binder-examples/appmode needs workaround to enable appmode to work for now #275. Promising. |
Yes, I saw that. Thanks for pointing me in the right direction! |
Have you found a solution for this problem? I noticed that the “Try it live” binder launcher is still failing with the above-mentioned error. I have an application that depends on Appmode and this is an important issue for me. When you find a solution, please update the example, so I can update my repository as well. Thank you. |
Fixed in release v0.9.0. |
Thanks @oschuett! I will give it a try. |
Yeah, I'm very sorry for the long silence. I hope this resolved the issue. I also tried testing with mybinder, but they seem overloaded at the moment. |
@oschuett Presumably related to this: https://blog.jupyter.org/mybinder-org-reducing-capacity-c93ccfc6413f |
@oschuett
When I launch the "Try it live" AppMode example and I receive the error:
400 : Bad Request
The error was: Cannot create file or directory '/home/jovyan/... .ipynb'
The reason for trying this is because my MyBinder repos are also now returning the same error when launching AppMode.
Is there a new dependency that you are aware of?
Any ideas/suggestions would be much appreciated!
The text was updated successfully, but these errors were encountered: