Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362013-01-14T20:30:34ZEcoinformatics Redmine
Redmine Bug #5778 (Resolved): Force Open doesn't (always?) currently work with Workflow Run Managerhttps://projects.ecoinformatics.org/ecoinfo/issues/57782013-01-14T20:30:34ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>There's currently at least one scenario where if a run's workflow's module dependencies are not satisfied, Force Open doesn't work (nothing appears to happen). I've started tracking it down, should be fixed soon.</p> Bug #5014 (Resolved): Add documentation to resources for the Workflow Run Manager modulehttps://projects.ecoinformatics.org/ecoinfo/issues/50142010-05-17T18:11:41Zdebi staggsstaggs@nceas.ucsb.edu
<p>Add resources > documentation into svn, and then place the workflow-run-manager documentation there. Documentation needs to be named the same as your module name, i.e. workflow-run-manager .pdf. This is so that the Modules Documentation for the tagging module can be found by that menu action in Kepler.</p> Bug #4976 (Resolved): Importing run archive from a different namespace is brokenhttps://projects.ecoinformatics.org/ecoinfo/issues/49762010-05-04T21:13:27ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>When you import a run, the run's execId is set to the next available execId, and we attempt to increment the run's revision. Subsequent tag events on this run also increment the revision. However, if this run comes from a different namespace, it gets an entirely new lsid. There are a few problems with this at the moment:<br />- a subsequent export of this imported run will not contain the derivedFrom lsid. This is not currently stored in provenance. We can't tell who originally created the run.<br />- opening the kar again during a subsequent kepler session will again import the run with a different lsid even though it's already been imported, because the lookup to avoid this is based on the original lsid. So you end up with two runs that are the same in all ways but run lsid. This bug doesn't happen during the same kepler session.</p>
<p>I think the solution to these issues is to make sure WorkflowRuns are getting and storing referral list, and to then store and utilize the referral list in provenance.</p> Bug #4954 (Resolved): Duration value on imported runs is incorrecthttps://projects.ecoinformatics.org/ecoinfo/issues/49542010-04-21T01:06:28ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>If you export a run, then import it, the end_time for the run inserted into provenance is wrong, and hence so is the duration.</p> Bug #4927 (Resolved): Don't allow export, upload, delete of executing run in WRMhttps://projects.ecoinformatics.org/ecoinfo/issues/49272010-04-03T00:39:09ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>The workflow run manager shouldn't allow the export, upload or delete of an executing run.</p> Bug #4895 (Resolved): Exporting multiple runs gives duplicate entry errorshttps://projects.ecoinformatics.org/ecoinfo/issues/48952010-03-19T23:10:25ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Exporting multiple runs from the Workflow Run Manager gui sometimes gives a series of duplicate entry error messages from KARBuilder writeKARFile like:</p>
<p>ERROR (org.kepler.kar.KARBuilder:writeKARFile:598) Tried to write Duplicate Entry to kar WorkflowRun.9.xml urn:lsid:kepler-project.org/ns/:129:66:1<br />java.util.zip.ZipException: duplicate entry: 01-SimpleAddition.urn.lsid.kepler-project.org.ns..129.62.1.xml</p>
<p>To reproduce:<br />Open a workflow<br />Run it 3 times<br />Export all 3 runs</p>
<p>A subsequent export of these 3 runs will not give the errors.</p> Bug #4800 (Resolved): CacheManager can not insert WorkflowRun into cachehttps://projects.ecoinformatics.org/ecoinfo/issues/48002010-02-17T20:41:12ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>When you export a run, CacheManager's insertObject cannot insert WorkflowRun entries into cache. This is because the call to serializeObjectInFile fails, caused by:</p>
<p>Caused by: java.io.NotSerializableException: java.lang.ref.WeakReference<br /> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)<br /> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)</p> Bug #4689 (Resolved): Export run creates duplicate WorkflowRun files. Exporting it again gives none.https://projects.ecoinformatics.org/ecoinfo/issues/46892010-01-21T21:59:53ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Oliver and I both have this problem after the big KAR change. <br />Aaron, I think you mentioned being aware of the duplication issue, take over this bug if you want it.</p>
<p>If you export a run, you get two WorkflowRun files with identical contents:<br />WorkflowRun.1.xml<br />WorkflowRun1.1.xml</p>
<p>If you export the run again, you get no WorkflowRun files.</p> Bug #4671 (Resolved): cannot export workflow runs when workflow has actors with <> in the nameshttps://projects.ecoinformatics.org/ecoinfo/issues/46712010-01-15T01:25:58ZOliver Soongsoong@nceas.ucsb.edu
<p>Title says it all. This is at r22494.</p> Bug #4652 (Resolved): clicking rows in the wrm no longer updates the report designer/viewerhttps://projects.ecoinformatics.org/ecoinfo/issues/46522010-01-08T00:55:38ZOliver Soongsoong@nceas.ucsb.edu
<p>If I have multiple entries in the wrm and I click on different rows, the report designer and viewer no longer automatically update their views. This is at r22407 under linux.</p> Bug #4618 (Resolved): First export of a run doesn't yield KAR with ROMLhttps://projects.ecoinformatics.org/ecoinfo/issues/46182009-12-09T23:44:10ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>I've introduce a bug in r22148:</p>
<p>For the case where no report is made: the first export of a run doesn't put a ROML in the kar, and subsequent exports get a ROML and a RIO. For this scenario you previously got ROMLs and no RIOs each time (which seems right).</p> Bug #4580 (Resolved): Error saving/opening KAR that has a workflow with a PortParameterhttps://projects.ecoinformatics.org/ecoinfo/issues/45802009-11-25T01:02:02ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Opening a past run where the workflow contained a PortParameter is giving a ptolemy.kernel.util.NameDuplicationException</p> Bug #4555 (Resolved): error exporting etc >1 run with same name but different wfhttps://projects.ecoinformatics.org/ecoinfo/issues/45552009-11-17T01:12:54ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>If you export or open more than one run where the workflow names are the same but the workflows are different, you get an error:<br />ptolemy.kernel.util.IllegalActionException: Error building the KAR file: duplicate entry: 00-StatisticalSummary.xml<br /> at org.kepler.kar.KARBuilder.generateKAR(KARBuilder.java:236)</p> Bug #4479 (Resolved): Error messages are not imported during run importhttps://projects.ecoinformatics.org/ecoinfo/issues/44792009-10-16T23:11:33ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>When importing a WorkfowRun that contains error messages into provenance (creating a 'husk run'), the error messages are lost. I forgot to inject these.</p>
<p>A related problem is that I'm not parsing the error messages from the serialized string form of a Map into a real Map (which I'll need to use). Though it's probably better to find a better way to serialize this map; the string form of the map is hard to parse since error messages can contain "=" and ",".</p> Bug #4473 (Resolved): Add WRM to bottom of report viewer for navigationhttps://projects.ecoinformatics.org/ecoinfo/issues/44732009-10-16T19:06:56Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Still need to design exactly how this will work out.</p>