This leads to the following error when applying the input hack of #18:
Traceback (most recent call last):
File "/home/nsbg/venv/lib/python3.11/site-packages/doit/action.py", line 461, in execute
returned_value = self.py_callable(*self.args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/nsbg/quangis-workflow/dodo.py", line 377, in action
solution = repo.input_permutation_hack(orig)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/nsbg/quangis-workflow/quangis/tools/repo.py", line 354, in input_permutation_hack
raise RuntimeError(
RuntimeError: Number of inputs doesn't correspond for abstr:GenerateNearTable
This makes sense, because abstr:GenerateNearTable has two inputs, not one. This is indeed reflected in the tools.json file that's handed to APE:
Almost certainly because the two inputs are the same type, and so APE just reuses the same type. I will make it even more hacky and just duplicate the inputs.
APE generates the following workflow:
This leads to the following error when applying the input hack of #18:
This makes sense, because
abstr:GenerateNearTable
has two inputs, not one. This is indeed reflected in thetools.json
file that's handed to APE:This could be either an issue in the interface with APE at
ape.py
, or an issue with APE itself.Note also that the issue is not always reproducible because there's a nondeterministic aspect to it --- multiple workflows fit the bill.