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

Skipped Task unexpectedly evaluate both output.as and export.as #481

Closed
cdavernas opened this issue Jan 22, 2025 · 0 comments · Fixed by #482
Closed

Skipped Task unexpectedly evaluate both output.as and export.as #481

cdavernas opened this issue Jan 22, 2025 · 0 comments · Fixed by #482
Assignees
Labels
app: runner Concerns the Runner priority: high Indicates a high priority issue type: bug Something isn't working weight: 2 An issue with a low development impact
Milestone

Comments

@cdavernas
Copy link
Member

I tried this:

Run a task that defines an unmatched if clause

This happened:

Both output.as and export.as in the task were evaluated. Moreover, export.as ended up applying to the entire context instead of the task's output, causing the context to become invalid.

I expected this:

output.as and export.as to be ignored for a skipped task

Is there a workaround?

No response

Anything else?

No response

Platform(s)

No response

Community Notes

  • Please vote by adding a 👍 reaction to the issue to help us prioritize.
  • If you are interested to work on this issue, please leave a comment.name: Bug Report 🐞
@cdavernas cdavernas added app: runner Concerns the Runner priority: high Indicates a high priority issue type: bug Something isn't working weight: 2 An issue with a low development impact labels Jan 22, 2025
@cdavernas cdavernas added this to the v1.0.0 milestone Jan 22, 2025
@cdavernas cdavernas self-assigned this Jan 22, 2025
cdavernas added a commit that referenced this issue Jan 22, 2025
…`export.as` clauses for skipped tasks

Fixes #481

Signed-off-by: Charles d'Avernas <[email protected]>
@github-project-automation github-project-automation bot moved this from Backlog to Done in Progress Tracker Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app: runner Concerns the Runner priority: high Indicates a high priority issue type: bug Something isn't working weight: 2 An issue with a low development impact
Projects
Status: Done
1 participant