Kepler: Issues 2010-07-21T19:59:44Z Ecoinformatics Redmine Redmine Bug #5100 (Resolved): Report Layout designed in a composite actor window is lost 2010-07-21T19:59:44Z Derik Barseghian <p>When you have a workflow with a composite actor, and you open the composite actor, its contents appear in a new kepler window. If you design a report layout in this window, and then close it, the parent workflow report designer does not show this layout. If you open the composite again, the report layout is not there either.</p> <p>If you leave the composite actor window open with a report layout, no instance is generated for it after execution.</p> <p>I'm not sure if or what the plan was for this scenario. Maybe switching to the Report Designer view should simply not be allowed when you're in a composite window. I think this would be a good first pass. An alternative is to keep the 2 (or N) report layout guis and objects for parent window and all opened composite actor windows in sync, and this will likely be more work.</p> Bug #5096 (Resolved): Reporting on a RecordToken fails 2010-07-15T00:49:16Z Derik Barseghian <p>I'm trying to report on a record token. I make a simple workflow with {{data = 1, timestamps = 2}} pasted in a Constant, and add Constant's output to my report design, but on execution get this error:</p> <p>(Location of error unknown) Error(Unknown location): fo:table-body is missing child elements. <br />Required Content Model: marker* (table-row+|table-cell+)</p> <p>and a popup error.</p> <p>I found someone w/ a similar error that garnered this response:<br /><a class="external" href=";m=120819139826155&#38;w=2">;m=120819139826155&#38;w=2</a></p> Bug #5094 (Resolved): reports do not display matrix or xml token data 2010-07-14T18:08:43Z Daniel Crawl <p>Reports do not display the contents of matrix tokens. I'm attaching an example kar.</p> Bug #5047 (Resolved): Rename the tagging docs tagging.pdf 2010-06-11T18:29:02Z debi staggs <p>The tagging docs (tagging-2.0 > docs) need to be named tagging.pdf instead of kepler-tagging-ui.pdf</p> <p>This is so that they can be displayed in the list of 'available documentation' for the modules.</p> Bug #5015 (Resolved): Export of runs contain different, and missing or extra reporting items now 2010-05-17T18:55:42Z Derik Barseghian <p>After the changes to roll ROML lsids with changes, the first export of a run kar contains less items than the second export of the same run. The first export no longer contains the RIOs, and the second export contains an extraneous ROML. An example export of a run from WRM:</p> <p>1st export:<br />derik_test_wf_with_report_ROML.xml<br /><br />WorkflowRun.1.xml</p> <p>2nd export:<br />derik_test_wf_with_report_ROML.xml<br />ROML.1.xml<br /><br />RIO.1.pdf<br />RIO.1.xml<br />WorkflowRun.1.xml</p> <p>I don't think either of these contains the right items -- it used to be that you only get 1 ROML, so the second kar contents minus a ROML would seem right to me.</p> Bug #5014 (Resolved): Add documentation to resources for the Workflow Run Manager module 2010-05-17T18:11:41Z debi staggs <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 #5013 (Resolved): Add documentation to resources for Tagging module 2010-05-17T18:10:18Z debi staggs <p>Add resources > documentation into svn, and then place the tagging documentation there. Documentation needs to be named the same as your module name, i.e. tagging .pdf. This is so that the Modules Documentation for the tagging module can be found by that menu action in Kepler.</p> Bug #4980 (Resolved): Tagging a run now creates two identical tags in the GUI 2010-05-06T00:44:54Z Derik Barseghian <p>Sean is able to replicate this at r24224. If you tag a run in the WRM, two gui tag labels show up instead of one.</p> Bug #4979 (Resolved): ROML has type of ReportInstance instead of ReportLayout in kar manifest 2010-05-05T02:11:35Z Derik Barseghian <p>E.g.:</p> <p>Name: Unnamed1_ROML.xml<br />dependsOnModule: reporting<br />handler: org.kepler.kar.handlers.ReportLayoutKAREntryHandler<br />lsid:<br />type:<br />dependsOn:</p> <p>I believe this is because calling reportLayout.getClass().getName() in ReportLayoutKAREntryHandler saveReportLayout sometimes returns ReportInstance. I'm not sure why yet.</p> Bug #4977 (Resolved): Can't associate multiple sets of reporting artifacts in one kar with differ... 2010-05-05T00:00:07Z Derik Barseghian <p>Reporting artifacts from imported runs are no longer being put into provenance since reporting attributes are no longer stored in the WorkflowRun. I'll change the code to instead look for and insert all items found in the kar manifest that use handlers ReportLayoutKAREntryHandler or ReportInstanceKAREntryHandler.</p> <p>Since reporting items dependOn the workflow and not the workflowRun, this is another tripping up point for multiple runs in one kar -- how will we know which reporting artifacts to associate with which run? I think putting multiple runs in one kar will require reporting artifacts dependOn the execution lsid.</p> Bug #4976 (Resolved): Importing run archive from a different namespace is broken 2010-05-04T21:13:27Z Derik Barseghian <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 #4973 (Resolved): Save Archive sometimes saves more or less than it should in WRP 2010-05-03T23:40:25Z Derik Barseghian <p>When running the WRP suite, if you create a workflow and a report design(roml), File => Save Archive should save the workflow and the roml, whether or not you've run the workflow.</p> <p>However sometimes only the workflow is saved. Other times the workflow, the roml, the rios, and the workflowRun are saved. I'll try to post replication procedures if I can figure them out. This is in trunk wrp at r24154.</p> Bug #4972 (Resolved): Write documentation for workflow-run-manager module 2010-05-03T20:18:13Z Derik Barseghian <p>Debi will try to fwd Sean and I documentation outlines to fill in.</p> Bug #4971 (Resolved): Write documentation for tagging module 2010-05-03T20:15:31Z Sean Riddle <p>n/t</p> Bug #4970 (Resolved): Make non-instantiable items in local KARs not draggable 2010-05-03T20:14:05Z Sean Riddle <p>Items in KARs that are not instantiable should not be draggable. The tree model needs to be constructed with these NamedObjs having the _notDraggable attribute set.</p>