Looking into binlog attached to the issue, I could see the cause of this error was a skipping target for GenerateSplash, and I fixed that for wasm on #241, so my guess is that we should remove all these Inputs from other targets as well. That should fix everything and missed during our refactoring, since VS behaves in a very unpredictable way.
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfills the following requirements:
Fixes: #244
PR Type
Looking into binlog attached to the issue, I could see the cause of this error was a skipping target for
GenerateSplash
, and I fixed that for wasm on #241, so my guess is that we should remove all these Inputs from other targets as well. That should fix everything and missed during our refactoring, since VS behaves in a very unpredictable way.What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Run
results.Other information
Internal Issue (If applicable):
This is an automatic backport of pull request #246 done by Mergify.