Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362013-01-30T16:12:23ZEcoinformatics Redmine
Redmine Bug #5834 (New): Fix Kepler Javadoc warningshttps://projects.ecoinformatics.org/ecoinfo/issues/58342013-01-30T16:12:23ZChristopher Brookscxh@eecs.berkeley.edu
<p>Running "ant javadoc" produces warnings about javadoc problems.<br />The Kepler nightly build at Berkeley now reports these warnings, see<br /><a class="external" href="http://sisyphus:8079/hudson/job/kepler/warnings31">http://sisyphus:8079/hudson/job/kepler/warnings31</a></p>
<p>It would be good to fix these warnings.</p> Bug #5724 (New): Display actor's suppressBlankLines parameter not workinghttps://projects.ecoinformatics.org/ecoinfo/issues/57242012-10-23T00:24:41ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>This happens in vergil too.</p>
<p>If I create and run an SDF workflow w/ String Constant => Display, w/ Display's suppressBlankLines option turned on, and String Constant's value set to:<br />--------<br />line1</p>
<p>line3 after blank line2<br />--------<br />the resulting display includes the blank line.</p> Bug #5721 (New): Add ModelRepaintController to the Kepler libraryhttps://projects.ecoinformatics.org/ecoinfo/issues/57212012-10-01T22:48:19ZSean Riddleswriddle@gmail.com
<p>This is a bug split off of 4903. ModelRepaintController is not in the Kepler actor library and should be added.</p> Bug #5697 (New): Workflow Run Manager can fail to Force Open a run kar that Kepler canhttps://projects.ecoinformatics.org/ecoinfo/issues/56972012-08-24T19:41:25ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>After connecting the Workflow Run Manager (2.3.0) to the kepler library and using it to download the attached run kar, it will fail to Force Open it. Nothing seems to happen (I can't see the logs on Mtn Lion-- need to check for errors). Yet if you manually download the run kar from the web, and open it from Kepler's File-> Open, the workflow opens, though the run does not get imported into the WRM as it should.</p>
<p>Note we should delete kars like this from the non-dev 'official' library (so things are 'clean' for users), since it was made with an unreleased, unversioned module in the mix:</p>
<p>reporting-2.3;keplerio;ssh-2.1;workflow-run-manager-2.3;provenance-2.3;tagging-2.3;workflow-scheduler-gui-1.0;kepler-2.3;outreach-2.2;r-2.3;loader-2.2;actors-2.3;directors-2.0;opendap-2.0;dataturbine-2.2;ecogrid-2.3;authentication-gui-2.2;gui-2.3;module-manager-gui-2.3;authentication-2.3;repository-2.3;job-2.1;io-2.0;data-handling-2.1;sms-2.2;component-library-2.2;util-2.1;event-state-2.1;core-2.3;common-2.3;module-manager-2.3;configuration-manager-2.3;kepler-tasks-2.3;ptolemy-kepler-2.3</p> Bug #5695 (New): more automatic module update process.https://projects.ecoinformatics.org/ecoinfo/issues/56952012-08-24T17:18:27Zjianwu jianwujianwu@sdsc.edu
<p>As discussed for bug 5398, We should discuss the usability perspective of module upgrade management. Some of the process can be automated.</p>
<p>Close 5398 for 2.4 and open this one for future release.</p> Bug #5693 (New): decide on issuing patches so older versions of kepler can upload accessible item...https://projects.ecoinformatics.org/ecoinfo/issues/56932012-08-23T19:41:12ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Do we want older versions of Kepler to be able to upload easily accessible items to Metacat >2.0 repositories? If so we need to patch these versions of Kepler.<br /><a class="external" href="http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5621#c1">http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5621#c1</a></p> Bug #5692 (New): Values not committed to actorshttps://projects.ecoinformatics.org/ecoinfo/issues/56922012-08-22T00:41:36ZIan Ianian.szarka@anu.edu.au
<p>Values not committed to actors</p>
<p>Open new Kepler workflow<br />Drag RExpression from Components tree<br />double click RExpression icon<br />Change test in "R function or script:" field<br />Press commit button <br />Double click on the same RExpression icon from above<br />- Any changes have been lost</p>
<p>This occurs on other actors and is not limited to the RExpression.</p> Bug #5690 (New): problems with updateActorDocshttps://projects.ecoinformatics.org/ecoinfo/issues/56902012-08-18T08:14:59ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>I ran into a few issues updating EcogridWriter documentation using:<br />./kepler.sh -updateActorDocs actors/resources/kar/CoreActors/EcogridWriter.xml</p>
<p>1) the actor LSID revision wasn't incremented (and the corresponding entry in CoreActor's manifest). Maybe simply a warning should be printed.<br />2) port documentation didn't show up in kepler, because the variable names for the ports were used, instead of the assigned names. Using the variable (default) names like this is probably the best though, since port names can be dynamically created, as can ports themselves. But the target should probably print out a warning that the developer should check/fix port doc by hand.<br />3) special chars were inserted for linebreaks (not that line breaks seem to get displayed anyways)</p>
<p>Bonus enhancement request:<br />4)It would be cool if the resulting xml were run through a 'pretty print'.</p> Bug #5674 (New): The patch downloader dialog can fail to automatically restart Keplerhttps://projects.ecoinformatics.org/ecoinfo/issues/56742012-08-10T23:48:09ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>In pre-release sensor-view-0.9 testing on os X 10.8, I found Kepler-2.3's patch downloader gui can fail to automatically restart kepler. It quits, the kepler icon bounces and then disappears. Subsequent start of Kepler from the Kepler icon works.<br />I think we've had this problem in the past, search for related bugs.</p> Bug #5673 (New): if user has newer version of module than exists in repository, old version will ...https://projects.ecoinformatics.org/ecoinfo/issues/56732012-08-10T23:44:37ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Summary: We should probably fix the logic here -- don't download an older version of a module a user already has.</p>
<p>Background:<br />Doing some sensor-view pre-release testing I:<br />started Kepler-2.3<br />switched to reporting-2.3<br />quit kepler<br />hacked kepler's module manager configuration.xml to use the test-releases area<br />restarted kepler<br />accepted test-releases patches<br />restarted kepler manually (patch downloader can apparently still fail to restart kepler successfully)<br />changed to sensor-view-0.9</p>
<p>And at this point, apple-extensions-2.1.0 got downloaded into KeplerData/kepler.modules. This is because the test area didn't have apple-extension-2.1.1. Unless this is something special to do w/ apple-extensions, this means it's possible MM will download old unnecessary modules when the user has a newer version. Except for testing like this, this seems an unlikely problem scenario currently, but there are likely problems lurking should we try using suites composed of modules on different repositories.</p> Bug #5672 (New): java -jar sensorview-utils-1.0.jar should invoke a simple java app that prints helphttps://projects.ecoinformatics.org/ecoinfo/issues/56722012-08-10T22:53:13ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>It would be nice if the sensorview-utils-1.0.jar had a default main class target that was a simple java app that printed some simple help, showing how to invoke all contained util (we do have this explained in the sensor-view module doc):</p>
<p>java -cp sensorview-utils-1.0.jar util.SpanToDT -h<br />java -cp sensorview-utils-1.0.jar util.MirrorDT –h<br />java -cp sensorview-utils-1.0.jar org.kepler.sensor.span.SpanSim -h</p> Bug #5671 (New): Workflow Run Manager tries to connect to keplerDevRepository as a database inste...https://projects.ecoinformatics.org/ecoinfo/issues/56712012-08-10T20:18:16ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>If you enable kepler dev in your local trunk repository and authentication configuration.xml files, the Workflow Run Manager tries to treat it as an sql provenance store, instead of a remote kar repository. When you change to keplerDevRepository w/ the workflow run manager, you can get the error below when it tries to connect to the database, which it shouldn't try to do. I suspect something minor, as it can still connect to the keplerRepository (as a remote kar repository, not database) fine.</p>
<p>Also, to 2.3 can connect to keplerDevRepository (if you configure it to include it) fine.</p>
<p>ProvenanceStore constructor. type:EcogridRepository for keplerDevRepository<br />java.sql.SQLException: S1000 General error java.lang.RuntimeException: remote open not allowed<br />ERROR in WorkflowRunManagerPanel reconnect() unable to connect.<br /> at org.hsqldb.jdbc.Util.sqlException(Unknown Source)<br /> at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)<br /> at org.hsqldb.jdbcDriver.getConnection(Unknown Source)<br /> at org.hsqldb.jdbcDriver.connect(Unknown Source)<br /> at java.sql.DriverManager.getConnection(DriverManager.java:582)<br /> at java.sql.DriverManager.getConnection(DriverManager.java:185)<br /> at org.kepler.util.sql.HSQL._getConnection(HSQL.java:478)<br /> at org.kepler.util.sql.DatabaseType.connect(DatabaseType.java:141)<br /> at org.kepler.util.sql.DatabaseFactory.getConnectedDatabaseType(DatabaseFactory.java:309)<br /> at org.kepler.provenance.sql.SQLQueryV8.<init>(SQLQueryV8.java:77)<br /> at org.kepler.workflowrunmanager.WorkflowRunManager.connect(WorkflowRunManager.java:156)<br /> at org.kepler.workflowrunmanager.gui.WorkflowRunManagerPanel.reconnect(WorkflowRunManagerPanel.java:965)<br /> at org.kepler.workflowrunmanager.gui.WorkflowRunManagerPanel.resetProvenanceInfo(WorkflowRunManagerPanel.java:937)<br /> at org.kepler.workflowrunmanager.gui.WorkflowRunManagerPanel.access$5(WorkflowRunManagerPanel.java:921)<br /> at org.kepler.workflowrunmanager.gui.WorkflowRunManagerPanel$ComboBoxAction.changeProvenanceStore(WorkflowRunManagerPanel.java:1802)<br /> at org.kepler.workflowrunmanager.gui.WorkflowRunManagerPanel$ComboBoxAction.access$0(WorkflowRunManagerPanel.java:1791)<br /> at org.kepler.workflowrunmanager.gui.WorkflowRunManagerPanel$ComboBoxAction$1.run(WorkflowRunManagerPanel.java:1781)<br /> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)<br /> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)<br /> at java.lang.Thread.run(Thread.java:680)</p> Bug #5670 (New): see if runtimemonitor module can be deleted, contains duplicate codehttps://projects.ecoinformatics.org/ecoinfo/issues/56702012-08-10T01:45:49ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>The runtimemonitor module contains these classes:</p>
<p>./runtimemonitor/FigureUpdater.java<br />./runtimemonitor/MonitorAttribute.java<br />./runtimemonitor/MonitoredStatus.java<br />./runtimemonitor/MonitorIcon.java<br />./runtimemonitor/ProcessCentral.java<br />./runtimemonitor/ProcessCentralWindow.java<br />./runtimemonitor/RuntimeMonitor.java<br />./runtimemonitor/TableData.java</p>
<p>Everything but ProcessCentral, ProcessCentralWindow, and TableData are near duplicates of code now in gui.</p>
<p>fsaresh worked on this. Is this code used? Should the module be removed? I don't know if anything is using it anymore. Sensor-view and vanilla don't, so this bug isn't high priority.</p>
<p>I also see at r17463 dzinn also checked in duplicates of these classes to the pws module, which I don't know anything about.</p> Bug #5667 (New): reevaluate how opening kars vs. XML should work from actor library.https://projects.ecoinformatics.org/ecoinfo/issues/56672012-08-07T23:03:26Zjianwu jianwujianwu@sdsc.edu
<p>currently, opening kar is different from opening xml from actor library (see bug 5348). One more difference is that one kar could have multiple xmls.</p>
<p>We should reevaluate how opening kars vs. XML should work from actor library.</p> Bug #5639 (New): ant update ptolemy -Drev=stable doesn't update you to latest "stable"https://projects.ecoinformatics.org/ecoinfo/issues/56392012-07-16T19:59:51ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>If you run ant update ptolemy -Drev=stable, ptolemy/module-info/revision.txt isn't updated first, so ptolemy is simply updated to the revision listed in your local copy of revision.txt.</p>