You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the error is happening in the test_no_outputs test. Upon execution, this is how the notebook looks like:
there's a clear error here since the first cell x = 1 should not produce any outputs; yet, it displays a plot. Seems like with the new matplotlib release, we need to do some "matplotlib state cleaning" when destroying the shell object, so when creating a new one, we don't share state from previous notebook runs. My guess is that we're missing something here
It's still unclear what changed in matplotlib 3.7 so more investigation is needed. for the time being, I pinned matplotlib so our tests pass.
The text was updated successfully, but these errors were encountered:
Our tests started failing with matplotlib 3.7, I tracked down the error locally:
the error is happening in the
test_no_outputs
test. Upon execution, this is how the notebook looks like:there's a clear error here since the first cell
x = 1
should not produce any outputs; yet, it displays a plot. Seems like with the new matplotlib release, we need to do some "matplotlib state cleaning" when destroying the shell object, so when creating a new one, we don't share state from previous notebook runs. My guess is that we're missing something hereIt's still unclear what changed in matplotlib 3.7 so more investigation is needed. for the time being, I pinned matplotlib so our tests pass.
The text was updated successfully, but these errors were encountered: