Closed martinRenou closed 1 year ago
@meeseeksdev please backport to 0.4.x
@meeseeksdev please backport to 0.3.x
Given that you're reverting a solution to this issue: https://github.com/voila-dashboards/voila/issues/896, don't we think it's gonna come back?
It's possible that self.executor.kc.stop_channels
may still be needed for #896 and not harmful in the case of using a kernel provisionner. Can you confirm on your setup @davidbrochart ?
I checked that self.executor.kc.stop_channels
is not harmful for kernel provisioners. It just disconnects the kernel client, but the kernel is kept alive.
It makes sense, cleaning up the kernel client in the Voila executor will help reducing the number of threads opened. We don't need the kernel client after execution because we won't execute more code
I'm working on getting the 0.3.x branch to build, then will release a new patch for 0.3.x and 0.4.x. Will continue this PR after that.
The execution time (in milliseconds) are grouped by test file, test type and browser. For each case, the following values are computed: min <- [1st quartile - median - 3rd quartile] -> max.
Question about the channels. Will the self.executor.kc.stop_channels
affect the ability of the widgets to communicate with the kernel? If not, what channels are these that we need to force close?
Also, I'm guessing y'all are planning on releasing a patch for 0.3.x and 0.4.x after the build is complete?
Will the
self.executor.kc.stop_channels
affect the ability of the widgets to communicate with the kernel? If not, what channels are these that we need to force close?
With Voila there are basically two clients that communicate with the kernel:
self.executor.kc
). This happens when you see the Voila loading spinner.So what we are cleaning here is the first one. After the notebook execution we don't need the executor anymore, so we close its communication channel. This is why it helped solving https://github.com/voila-dashboards/voila/issues/896 in the first place.
Also, I'm guessing y'all are planning on releasing a patch for 0.3.x and 0.4.x after the build is complete?
0.3.7 and 0.4.1 are out with this change already :)
Trigger CI
Revert https://github.com/voila-dashboards/voila/pull/969
This should never have been merged. The client still needs the kernel and channels running after execution !
When using a kernel provisionner, this would simply kill the kernel