Re: workflow runner error

2017-07-13 Thread DeWayne Filppi
+1 On Thu, Jul 13, 2017 at 12:51 AM, Tal Liron wrote: > I wonder if we should provide a better upgrade path here. Perhaps we need > to add a file with some meta information about the version of the database. > We don't necessarily have to provide an automatic upgrade to a

Re: workflow runner error

2017-07-13 Thread Ran Ziv
I think upgrade paths is not really a topic that should be discussed at the moment - we're at a 0.x.y release with no backward compatibility guarantees, plus, the version that was used prior to the current version in this case was an unreleased version, so an upgrade path wouldnt have been viable

Re: workflow runner error

2017-07-13 Thread Tal Liron
I wonder if we should provide a better upgrade path here. Perhaps we need to add a file with some meta information about the version of the database. We don't necessarily have to provide an automatic upgrade to a new database format, but least we can tell the user that the database is out of date

Re: workflow runner error

2017-07-12 Thread DeWayne Filppi
Yes, that absolutely could be the case. I'll try a reset. On Wed, Jul 12, 2017 at 3:40 PM, Ran Ziv wrote: > Could it be that you first used an older, non-release version of ARIA, and > then used 0.1.0 without first resetting your ARIA working directory (e.g. > "aria reset

Re: workflow runner error

2017-07-12 Thread Ran Ziv
Could it be that you first used an older, non-release version of ARIA, and then used 0.1.0 without first resetting your ARIA working directory (e.g. "aria reset -f")? The task table should indeed have the said column, as can be seen here:

workflow runner error

2017-07-12 Thread DeWayne Filppi
When executing this: runner = WorkflowRunner(model_storage, resource_storage, plugin_manager, service_id = service_id, workflow_name = workflow_name, inputs = inputs, executor = executor,