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

Incorrect Null evaluation of file #38

Closed
drjrm3 opened this issue Nov 11, 2018 · 1 comment
Closed

Incorrect Null evaluation of file #38

drjrm3 opened this issue Nov 11, 2018 · 1 comment

Comments

@drjrm3
Copy link

drjrm3 commented Nov 11, 2018

#37 seems to be resolved now with my minimal example but when I ran my larger workflow again it still failed. After dissecting each piece I found that an unrelated parameter seems to be causing this same error.

When I change the example CLT / WF from #37 and allow the CLT to have an optional boolean and then edit the WF to interpret the boolean as z: {valueFrom: $(true)} I get the same std error I did in #37. However, the new z parameter is (I think) completely unrelated to the parameter involved with the std error.

UndefinedVariableError2.5.tar.gz

@drjrm3 drjrm3 changed the title Incorrect Nul evaluation of file Incorrect Null evaluation of file Nov 11, 2018
skeeey pushed a commit that referenced this issue Nov 14, 2018
skeeey pushed a commit that referenced this issue Nov 14, 2018
@skeeey
Copy link
Collaborator

skeeey commented Nov 14, 2018

This is because I evaluate the stdout/stderr at a wrong phase, I should evaluate them after the inputs were handled

@skeeey skeeey closed this as completed Nov 14, 2018
@drjrm3 drjrm3 mentioned this issue Nov 20, 2018
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

No branches or pull requests

2 participants