-
Notifications
You must be signed in to change notification settings - Fork 18
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
Show/hide solution buttons #80
Comments
i'll try to look into this next week sometime |
Thank you Will :) |
Hi there, Just got around to testing this. I can't reproduce. (I'm on ubuntu). When I try for instance on binder, it's fine. (This link ) Can you provide precise steps to reproduce? Thank you. |
hey will :) I just gave it a shot on binder as well. First it seemed that the problem did indeed show but it turned out that I had to wait a couple of seconds after creating the solution button: Screen.Recording.2021-05-16.at.21.24.40.movso at least I am not crazy :D I think I didnt wait the last time i tried it on binder ... I'll check with my collegues working on windows if that is their problem as well (but somehow I don't think so). Will let you know asap. Thanks for checking though! |
Aha yes, there's some lag as the code has to go through the backend of jupyter to write the file out. Locally, though, it should be fairly quick. But let me see if I can repro that raciness locally, maybe there's a fix for that. Separately, I'm going to try to get a new release out for you that will allow for alternative kernels. |
OK I tried to replicate the problem locally, and can't. If there's a race condition, I can't beat it yet. |
@4flixt I've release 1.0.1.19 which uses |
Dear @willkessler,
we have encountered a problem with the show/hide solution buttons in JupyterGraffiti (1.0.1.18).
It seems like the feature to create a solution box doesn't write a new file. If we want to display the solution, we obtain:
Note that the used kernel is "Python 3" (also visible in the figure). Interestingly, we are able to record and play voice recordings in the same setup.
We experienced the problem on various Windows machines and have also worked with Docker. Even with Docker the problem persists. On MacOSX everything works fine for some reason.
We currently work around the problem by using the "old" method of manually creating files and linking them to the solution button.
The text was updated successfully, but these errors were encountered: