Remi Rampin

I seem to have been running into [this bug](https://bugs.webkit.org/show_bug.cgi?id=35656). Maybe it should be fixed on WebViewCell directly, making it add the .html extension when missing?

Of course after #1046 you don't see that unless you uncheck "don't show upgrade nodes" in preferences/advanced.

This is more serious than I thought, since with the way the `__upgrade__` annotation works, we can only store a link to one upgrade from each version. They have to...

Relevant code: [do_version_switch()](https://github.com/VisTrails/VisTrails/blob/86324e95a8335eb5b1528cd9342f0f336f097131/vistrails/core/vistrail/controller.py#L3776)

Should be fixed by #901

``` add_module(0) add_module(1) INFO:VisLog:/home/remram/Documents/programming/dat/vistrails/vistrails/core/vistrail/controller.py, line 3185 Processing upgrades in package "org.vistrails.vistrails.basic" MissingPackageVersion: Missing version 2.1 of package org.vistrails.vistrails.basic MissingPackageVersion: Missing version 2.1 of package org.vistrails.vistrails.basic Traceback (most recent call last):...

Adding tag _gui_ because this is caused by the signal-sending override of `set_changed()`

The problem I see is that perform_action() changes the current_version without validating, and do_version_switch() doesn't validate when changing to the current version. So noone validates anything when performing an action,...

The problem is not catching potential errors, it is that without calling `validate()`, the pipeline is marked as invalid in the pipeline view. We thus have to call `change_selected_version()` although...

I created the branch `pipeline-validation`. Replying to comment 4 @rexissimus: > - Could we set a do_validate flag on the controller so that we can turn it off when needed...