-
-
Notifications
You must be signed in to change notification settings - Fork 15
Conversation
Bumps [tar](https://github.com/npm/node-tar) from 4.4.13 to 4.4.15. - [Release notes](https://github.com/npm/node-tar/releases) - [Changelog](https://github.com/npm/node-tar/blob/main/CHANGELOG.md) - [Commits](isaacs/node-tar@v4.4.13...v4.4.15) --- updated-dependencies: - dependency-name: tar dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> adding maxWait command line flag adding maxWait flag adding maxWait flag
Thanks for submitting your first pull request! You are awesome! 🤗 |
Thanks @dharmaquark! Galata has been moved into the core JupyterLab repository: jupyterlab/jupyterlab#10796. And we are in the process of archiving the However it looks like we could get this change in here, and cut a new What do you think @fcollonval @mbektas? |
that would be great! Also happy to port this PR over to the JupyterLab repo if that ends up being easier for everyone! |
FYI in the code ported to core, this is happening there. And there is no timeout on the action (except the global test timeout). |
Thanks @dharmaquark! @jtpio yes, sounds good to me. Lets merge this and publish a new version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
FYI @dharmaquark, Thanks @mbektas for the release! |
Description of change
This PR introduces a new optional command line flag
max-wait
to support customizable timeouts (implementing suggestion made in #80 to handle use case of an instance of JupyterLab taking longer than the current 5000 ms default before thewindow.jupyterlab
object is available)