Hi,
I noticed this morning that a component didn’t work anymore. Upon opening it, I noticed a connection got severed without any change made by me.
Best
Mike
5.3 totally screwed up my workflow and quite frankly, I am not amused. This has been the worst rollout ever!
PS: @Vernalis I am trying to reconstruct what has been severed and I happen to notice all severed connections are related to the configurable i/case switch if the port type is flow variable (my best guess).
Here is a reconstructed portion shown above in it’s broken state:
Here another example …
Broken
Fixed
image|690x338
What I can imagine is that at some point, either during community hacking days or during 5.3. roll out, the Vernalis nodes were unavailable. Then, upon becoming available, were reintroduced but the config, switch from data to flow variable ports, got lost / reset.
But then there is this section which only can have a flow variable port pointing towards a more generic issue of all Vernalis nodes became unavailable (I believe during 5.3 community hacking days), I opened and saved the workflow resulting in connections getting permanently severed and now have to deal with the consequences.
@armingrudd would it be possible for the next community hacking days to ensure we can test:
- All 3rd party extensions like NodePit
- The regular update process of Knime testing what a user would do upon release
Hi Mike,
The Vernalis community contribution is I think a few patch versions behind the latest in the current 5.3 update site, which might have caused this problem, although in the testing we have done we have not seen this. This is due to a combination of the original email from the KNIME community team getting swallowed by mail filters somewhere along the way, and despite a lot of effort on release day when we became aware of the situation we were unable to complete the update as we have dependencies on other community contributions which were also not ready. I will chase that up to see what the latest situation is there.
You should be able to install the latest version from the nightly build community update site, but I think that once a workflow has been saved with mysteriously-disappeared nodes/connections they’ve gone. In general, I would advise not switching a production workspace to a new version without backing it up fully or testing by importing key workflows into a new vanilla workspace with the new version.
Unfortunately we were unable to attend the hacking days, but again it’s difficult to get our update into those due to inter-dependencies with other projects.
Steve
Hi Steve,
no worries. I hope you didn’t took my “worst rollout ever!” personally as I did anticipate, like it happened for Selenium too, that you struggled to keep up for various reasons.
I have already made the proposal to improve upon that for the next Community Hacking days. Anyways, thanks for taking the time to reply 
Cheers
A beloved Vernalis Nodes Fanboy
1 Like
Hi Mike,
No worries. Much as I like KNIME, the 5.x series has presented a seemingly endless series of problems. I’m still trying to migrate up from 4.7 internally…
Steve
Glad to read I am not alone with my gut feeling 
1 Like