Fix invalid detection of hierarchical namespace stub blobs as files #4046
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using Azure Batch executor with storage account enabling hierarchical namespaces have problems publishing directories.
The problem is that for each directory azure will create an empty "stub blob" with a metadata field:
"hdi_isfolder": "true"
Nextflow currently detects these as files and will create a download request for that stub blob using a directory path which will cause a BlobStorageException (Status code 400: InvalidInput)
This PR adds a simple to check to detect such blobs and mark those as directories.
Fixes: #4016, #2557