kernel_ready.Kernel triggered twice when creating a new notebook about notebook HOT 5 CLOSED

@neilzimmerman commented

This is happening because 'kernel_ready.Kernel' is triggered in kernel.js on line 960 when the new kernel is starting and on line 411 after connecting. Does it need to be triggered the first time? is it really ready if it is not yet connected?

from notebook.

@minrk commented

The first one is probably triggered inappropriately.

from notebook.

@takluyver commented

I still see the two trigger calls in the code, but I only get one kernel_ready event when I create a new notebook. Can someone dig into the code a bit?

from notebook.

@Carreau commented

Need to be migrated to Notebook repo.

from notebook.

I can't reproduce this anymore. I tried adding the following to my custom.js and I only got 1 log:

events.on('kernel_ready.Kernel', function(event){ 
    console.log('kernel_ready.Kernel', event);
});

from notebook.