Load WASM module dependencies if non-WASM input data is specified #3747
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was previously a bug where if a user specified a job spec which uses the WASM module dependency feature to load in WASM from multiple modules, it would fail if there was more than a single dependent module or if the WASM module to load is not specified first in the input sources list.
This commit adds tests of this feature and ensures that WASM module dependencies are loaded by examining the Alias of the InputSources.
Resolves #3746.