I'm using execute_reply to cleanup execute calls that don't send any output.
This works fine if excute_reply always comes after output. However, it randomly comes in afterwards. AFAIK, it should come in after but apparently it's not guaranteed.
Oddly, it seems like the iopub idle event always comes in after data. Not sure why.
Could be that the fake browser is getting the data afterwards because i'm sending large json. so maybe node.js is getting it in the right order, but due to some processing it's not coming in the right order. Doubtful about that though.
perhaps check against iopub.idle?
Either way, i'd be nice to change the callback into a registry that can keep track of what the current deferred is.
I'm using execute_reply to cleanup execute calls that don't send any output.
This works fine if excute_reply always comes after output. However, it randomly comes in afterwards. AFAIK, it should come in after but apparently it's not guaranteed.
Oddly, it seems like the iopub idle event always comes in after data. Not sure why.
Could be that the fake browser is getting the data afterwards because i'm sending large json. so maybe node.js is getting it in the right order, but due to some processing it's not coming in the right order. Doubtful about that though.
perhaps check against iopub.idle?
Either way, i'd be nice to change the callback into a registry that can keep track of what the current deferred is.