Repository navigation
Tags: GrahamDumpleton/jupyterlab-workshop
Tags
Never put a removed workshop back by writing to it late: the progress… … save and the environment files are both written on a debounce, so a write could land after the workshop's directory had gone, removed from another window or by the clean-up between tests, and ensureDirectory would then create the state directory with its missing parents, leaving an empty shell of the workshop in the way of the next install, which is what failed the browser suite on main once; both writers now go through ensureDirectoryWithin, which creates the state directory only while the workshop directory is still there and otherwise writes nothing, and a browser test that removes an open workshop, turns the page and sets a variable, and checks nothing comes back
PreviousNext