Remove most pipeline compat and add a fetch call in testing #427
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.
Small PR ahead of PR to address #406 .
Informed by working on
compat
forEpiAware
, I noted that the compat requirements in the pipeline had drifted a bit (e.g. fixingADTypes
to 1.2). My current thinking is that as a project having compat requirements forEpiAwarePipeline
is not appropriate since the version of the packages used is fixed anyway.Also, I noted that the pipeline run tests were passing before running had finished. I realised that this was because the execution was not waiting for the
EagerThunk
to resolve before resolving the test outcome. I've added aDagger.fetch
call to force the process to wait (this didn't change test from pass to fail but might in the future).