Remi Rampin
Remi Rampin
Ok, I did my best on `invalid-pipeline-hides-package-errors`, please review that this makes sense. The fact that `handle_invalid_pipeline()` might first enable packages and then perform upgrades in a second call is...
`invalid-pipeline-hides-package-errors_/loops` loops, waiting for a test case.
(still on branch `invalid-pipeline-hides-package-errors_/loops`) Alright, I added a test to the `TestUpgradePackageRemap`: `test_looping_pipeline_fix`. It doesn't pass. Issues: - How do I add an available package without enabling it? (so that...
Yes, it looked like the correct way to do this, however it doesn't add the package to the available list either.
But it doesn't accept the `prefix=` argument. Actually I remember fixing that one on branch `pkg-as-setuptools-plugins`, which is probably worth merging in.
Reading the code, I stumbled into another issue: if the upgrades don't lead to a valid pipeline, they will be ignored and a new upgrade will be attempted from the...
Alright, I made the change in 463d3eab. `TestMashupApp#test_load_mashup()` now fails, this might be because the latest version in the file is invalid (it gets selected by the `api.open_vistrail_from_file()`, although the...
I merged `invalid-pipeline-hides-package-errors` into v2.2. I'm attaching the looping version to this issue.
It would seem that loading an abstraction which contains an out-of-date abstraction fails. Or something similar.
I really think 2.1 should display some kind of readable message when an abstraction can't be loaded... even if the revamp dakoop mentions may be farther away.