Frédéric Collonval

Thanks for the test @kiansahafi For what I saw, yarn is using a workers pool to handle the fetched packages. This is consistent with your finding that each dependency gives...

> does this build log answer your question? if not, please tell me how i can see that. Actually what I'm interested in, is what happen if you execute within...

Hey @kiansahafi thanks for keeping testing. I made a short demo of what I would like you to test - I guess it will be easier than explaining: https://github.com/jupyterlab/jupyterlab/assets/8435071/6e6b50a9-56d9-4350-a5c9-6eb4d8f410ec >...

Thanks again for the test @kiansahafi The appearance of the error in the dev container is at least consistent (the dev container is actually not running the last part of...

Last idea, in the docker, could you report the defined environment variables ? You should get that list by executing `export`. > [!important] > Check that there are no sensitive...

Thanks @kiansahafi Unfortunately nothing out of the ordinary there.

What do you get when executing: ``` npm config ls -l | egrep node-options ``` for reference I got `node-options = null`

@Rajhans858188 could you provide more background on the purpose for this PR?

Yep, from a quick discussion with the authors, increasing the Python version support is unlikely: https://github.com/scientific-python/cookie/discussions/435 I just hope that the policy [SPEC0](https://scientific-python.org/specs/spec-0000/) and [NEP29](https://numpy.org/neps/nep-0029-deprecation_policy.html) won't bite us in the...

An alternative approach would be to test if switching to `actualOnClick` would work to solve this: https://github.com/jupyterlab/jupyterlab/blob/6143d29918d0d3686646e22716293f288c659667/packages/ui-components/src/components/toolbar.tsx#L805