Github user agoodm commented on the issue:
https://github.com/apache/zeppelin/pull/1534
@felixcheung
In that case, I think that should be fine. Will do shortly.
@Leemoonsoo
The latest commit should fix the issue I just mentioned. Two other
important things to mention:
1) Any print statements made prior to printing the `%html` or `%angular`
won't show up in the results. This means that when `close=False` and when any
plots are open, print statements won't display since the output type magic will
always come after user entered print-statements. This can be fixed for the
matplotlib backend specifically by adding a pre-execute hook that prints the
magic of the currently open plot, but it's not really ideal.
2) Earlier we both had issues loading the tutorial notebook. As it turns
out, the reason appears to be due the angular display system. This happens
whenever I stop Zeppelin whenever variables are still bound to the angular
display system. If I make sure to unbind everything first, then I can safely
start Zeppelin again. I am pretty sure this issue was introduced in more recent
commits since I didn't have this problem when I first made the tutorial
notebook. It was not until after I rebased my branch to reproduce the problem
when you initially discovered it. This is actually a serious issue, and in this
case it would be bad to leave it unaddressed with this PR since that would mean
anyone that runs the last example in the tutorial notebook without calling
`plt.close()` at the end will brick their zeppelin installation until removing
the notebook.
How do you think we should proceed?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
