Skip to content

Prevent TaskPath leakage from typed record outputs#7090

Open
stekaz wants to merge 1 commit intonextflow-io:masterfrom
stekaz:outputs
Open

Prevent TaskPath leakage from typed record outputs#7090
stekaz wants to merge 1 commit intonextflow-io:masterfrom
stekaz:outputs

Conversation

@stekaz
Copy link
Copy Markdown
Contributor

@stekaz stekaz commented Apr 30, 2026

Fixes #7032

This change fixes the output-side problem where a process can emit a record containing TaskPath values. These TaskPath values are only meaningful inside the upstream task, so downstream processes can fail during hashing/staging or see invalid relative paths. The fix is to normalize the process output values before binding them to output channels.

#7083 makes nested record paths become TaskPaths when entering a task
This PR makes nested TaskPath values become durable paths when leaving a task

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 30, 2026

Deploy Preview for nextflow-docs-staging canceled.

Name Link
🔨 Latest commit 0624e5a
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-docs-staging/deploys/69f3619716ead80008aa7135

Signed-off-by: Stephen Kazakoff <sh.kazakoff@gmail.com>
@stekaz stekaz marked this pull request as ready for review May 1, 2026 01:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unused files in process inputs are of nextflow.processor.TaskPath type which makes invalid input paths for other processes

1 participant