-
Notifications
You must be signed in to change notification settings - Fork 391
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
Notebooks become 'not trusted' when code cells are modified in the paired file #203
Comments
@stefanuddenberg, do you think the above explains the issue you reported at #12? |
The above issue would be solved if we decide to trust notebook for which outputs are either empty (updated or new code cell), or trusted (code cell with unchanged output). This seems to be consistent with the jupyter security model. |
My problem is a little different; the notebooks are becoming un-trusted even when no changes have been made to any representation of the notebooks at all. But fixing this issue sounds like it might end up fixing mine in the process. |
I see. I think we should specifically address your issue then. Do you happen to have this issue with every notebook? Could you please test a notebook with just one cell with javascript output, say,
Thanks! |
Consider the following notebook made of two cells:
The notebook may become 'not trusted' when we modify the associated text representation (e.g. the associated
py:light
script).Precisely,
3,
and2
, then the plot is preserved and the notebook remains trustedpy:light
script, or if I modify the plot other than by adding spaces, then the notebook becomes not trusted.The text was updated successfully, but these errors were encountered: