-
Notifications
You must be signed in to change notification settings - Fork 5k
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
New interface in 7.0.0 breaks basic functionality #6976
Comments
If anyone else ends up here, horrified that upstream would trash a core tool in your workflow as the default option, |
Noted; the screenshots are from the lab interface (much frantic clicking trying to find an option to revert got me there) but I experienced the same issues with lack of output and consistency in reporting running status in the notebook interface. After some reading, I understand these now share a backend, so it makes some sense that both interfaces have issues. The notebook doesn't even change the page icon when cells are running in the same tab they are launched from... |
This will be fixed in #6980. Please open separate issues so it's easier to keep track of feature requests and bug fixes, thanks! |
@BenLand100 I'm sorry to hear that your experience upgrading to 7.0.0 included regressions. We will continue to maintain Notebook 6, which you can install at your option, until Notebook 8 becomes available. We had a beta and release candidate process specifically intended to suss out regressions like the ones that you've observed, and we have weekly calls to discuss the project. If you'd like to participate in future release processes to help improve their quality, we'd welcome your constructive feedback. This is a community-built project, made better by the positive contributions of our users, developers, and administrators. |
I'm ignoring the template intentionally. My system updated to Jupyter Notebook 7.0.0, which has brought me to a standstill.
How did something this basic slip past quality control for a major release?
The text was updated successfully, but these errors were encountered: