Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] Resume: print cache invalidation reason to console #4894

Open
ewels opened this issue Apr 8, 2024 · 1 comment · May be fixed by #4214
Open

[feature] Resume: print cache invalidation reason to console #4894

ewels opened this issue Apr 8, 2024 · 1 comment · May be fixed by #4214

Comments

@ewels
Copy link
Member

ewels commented Apr 8, 2024

Idea for making broken -resume caches less frustrating: get Nextflow to identify the change that caused an invalidated cache, then print to the console. Give immediate feedback, rather than forcing the end user to dig into hashes etc to try to figure this out.

Related to #4214

@bentsherman
Copy link
Member

bentsherman commented Apr 15, 2024

See also: #4369 (comment)

I originally imagined having a nextflow diff command where you specify two runs and it compares them. Doing this during the resumed run is much better UX but requires you to determine which task to compare from the previous run. Probably the task the same name e.g. FASTQC (1) and from the same session id..

If such a task isn't found then we must fall back to a simple message like "this task looks new" which isn't as helpful but better than nothing.

@bentsherman bentsherman linked a pull request Apr 22, 2024 that will close this issue
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 a pull request may close this issue.

2 participants