Skip to content
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

how to jump to the failed cell? #4323

Open
stas00 opened this issue Jan 7, 2019 · 2 comments
Open

how to jump to the failed cell? #4323

stas00 opened this issue Jan 7, 2019 · 2 comments

Comments

@stas00
Copy link

stas00 commented Jan 7, 2019

Often when a large notebook is run, and some cell fails there is no way to navigate straight to it, one has to scroll (a lot at times) to find for the failed cell.

Is it possible to add a facility to be able to navigate to the failed cell in one click?

For example, I've been using the following to jump to the currently running cell - a similar functionality to what I'm requesting:

Jupyter.keyboard_manager.command_shortcuts.add_shortcut('Alt-I', {
    help : 'Go to Running cell',
    help_index : 'zz',
    handler : function (event) {
        setTimeout(function() {
            // Find running cell and click the first one
            if ($('.running').length > 0) {
                //alert("found running cell");
                $('.running')[0].scrollIntoView();
            }}, 250);
        return false;
    }
});

But there doesn't seem to be an '.error' JS state.

Of course, while there can be only one '.running' cell, there could be more than one '.error' cell at the same time. But, perhaps, only the last one needs to be tracked.

And when the facility is in place, then there can be a configuration option for the notebook to automatically refocus to the failed cell any time an error happens. But that's a bigger ask, I'd be happy to have a way to jump to it quickly.

Thanks.

@cpoptic
Copy link

cpoptic commented Dec 18, 2019

  • 1 to this. It would save many a developer countless hours of scrolling through a notebook that has hundreds of cells in a script-type of format trying to find the one cell that failed.

@Ruibin-Liu
Copy link

Hard to believe there has been no response for years.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants