You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a zip archive with the pipeline files directly in it;
a zip archive with a directory in it that contains the pipeline files.
The latter case is handled by moving the files outside of the directory and then deleting the directory.
Unfortunately, the behavior of shutil.move when the destination already exists consists in moving the source within the destination (ie. as cp does on unices), meaning that if a zip archive contains name/name, then the subdirectory is “moved” into the directory (hence not actually moving). The result is 1) files left in a subdirectory 2) the removal failing because os.rmdir can't remove directories that are not empty.
The text was updated successfully, but these errors were encountered:
To be honest, I'd rather see a single valid way of packaging pipelines, and that would be without a top directory as it doesn't provide any benefit (the first thing we do when it exists is to remove it). See jar files in Java: there's a single valid place where a manifest can be.
But if we really want to handle that, I guess a sound approach would be to start by renaming the top directory to some name that doesn't exist in it. Something like:
The pipeline import code can handle both:
The latter case is handled by moving the files outside of the directory and then deleting the directory.
Unfortunately, the behavior of shutil.move when the destination already exists consists in moving the source within the destination (ie. as
cp
does on unices), meaning that if a zip archive containsname/name
, then the subdirectory is “moved” into the directory (hence not actually moving). The result is 1) files left in a subdirectory 2) the removal failing because os.rmdir can't remove directories that are not empty.The text was updated successfully, but these errors were encountered: