On Fri, Jul 22, 2011 at 06:25:39PM -0700, Ian Smith-Heisters wrote: > On Fri, Jul 22, 2011 at 4:28 PM, John Mettraux <[email protected]> wrote: > > Instead, we did this, which seems to fix the problem: > https://gist.github.com/1100812 That is, only move the sub_wfid to the > subid the first time through. > > > Are there other issues coming up ? > > Yes, now we're hitting a problem where ParticipantList#instantiate > expects pinfo to be an array. We verified that newly created processes > store the participant in the format it expects, eg. > > ["FooParticipant", {}] > > While our legacy processes store it as a simple string > ("FooParticipant"). Here's the monkey patch that seems to have fixed > that for the moment: https://gist.github.com/1100818 . > > Do you have feedback on the patches?
Hello Ian, tell Greg I'm sorry for IRC, I was out gardening. The first patch I integrated it as https://github.com/jmettraux/ruote/commit/02846f556853823590393807050de51f8300997e For the second patch (ParticipantList), I would suggest cleaning the participant list in the storage (type 'configuration') and re-registering the participants. I'd go https://gist.github.com/1100883 > Are there other data migration issues we should be looking out for? > Is there an easy way to get all our legacy data into a schema that > Ruote 2.2.0 will play nicely with? Sorry again, I thought I got covered with the sub_wfid conversion code I had in place. The participant list issue is a bit more delicate. http://groups.google.com/group/openwferu-users/browse_thread/thread/5cb41f958d91308b Most of the installs I have re-register participants on startup (and are mono-worker)so the issue was not visible to me. Best regards, -- John Mettraux - http://jmettraux.wordpress.com -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
