Skip to content

dagger.#Nop: work around bugs in the DAG resolver#1790

Merged
aluzzardi merged 1 commit intodagger:mainfrom
shykes:nop
Mar 16, 2022
Merged

dagger.#Nop: work around bugs in the DAG resolver#1790
aluzzardi merged 1 commit intodagger:mainfrom
shykes:nop

Conversation

@shykes
Copy link
Copy Markdown
Contributor

@shykes shykes commented Mar 12, 2022

This does not fix #1789, but it does allow working around it. A pure cue action can wrap its output in dagger.#Nop, which will trigger client filesystem writes.

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 12, 2022

@shykes shykes requested a review from aluzzardi March 16, 2022 20:27
@shykes
Copy link
Copy Markdown
Contributor Author

shykes commented Mar 16, 2022

Merging this before next auto-release would be appreciated, it unblocks my use case but I can't use it directly in dagger-for-github, because it can only run released versions of dagger.

@aluzzardi aluzzardi merged commit 8b7e591 into dagger:main Mar 16, 2022
@aluzzardi aluzzardi deleted the nop branch March 16, 2022 20:40
@shykes
Copy link
Copy Markdown
Contributor Author

shykes commented Mar 16, 2022

Thank you!

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.

Actions with no core buildkit actions don't trigger filesystem write

2 participants