Go to http://knb.ecoinformatics.org/software/metacat/metacat.html
Then click on the 'Open Bugs' link to go to Kepler/Bugzilla Dan Higgins NCEAS Felipe Albrecht wrote: > Hi, > I also noticed this bug and another minors bugs on save/load processes. > Kepler has a bug manager, like bugzilla, or a todo page? > Some bugs look easy to solve, but I dont know if other person are working on > it. > > Thanks > > Felipe Albrecht > > On 5/7/07, Efrat Frank <efrat at sdsc.edu> wrote: > >> Hi Vinicius, >> >> We are aware of this problem and came up a while back with several >> solution ideas such as caching the metadata or storing it in a local/ >> remote repository. Changing the schema format, though, also requires >> changes in the query builder. Due to tight schedules and higher >> priorities we never had the time/man power to get to it. We always >> look forward to new Kepler contributors and would be happy if someone >> could dig into it. >> >> Cheers, >> Efrat >> >> On May 6, 2007, at 2:35 PM, Vinicius Von Held wrote: >> >> >>> Hi, >>> >>> I?ve just begun to use kepler and I guess I?ve found a bug with the >>> databases components. I use 'open database connection' and >>> 'database query' to access a postgres database. The connection >>> works well and I can run queries normally. The problem happens when >>> I try to save the kepler model. I figured out that it happens >>> because of the size of the component 'database query', which it?s >>> big, due to the fact that it contains ALL the database schema in >>> it, written in XML format. The database schema is pretty large >>> ( the script file worn to generate the bank had more than 200 Mb). >>> I would expect that saving this file would take a while due the >>> component?s (big) size, but actually it takes forever: the >>> processor begins to run at 100% and the busy memory raises >>> continously, till I kill the java process (ctrl+alt +del the click >>> on 'terminate process' button). So, I can build a workflow and even >>> execute it, but I cannot save it. >>> >>> Have anyone noticed this bug? Is there any way to solve it? Or >>> maybe another component to take place the database query component? >>> >>> Regards, >>> Vinicius Von Held >>> >>> >>> >>> _______________________________________________ >>> Kepler-users mailing list >>> Kepler-users at ecoinformatics.org >>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/ >>> kepler-users >>> >> _______________________________________________ >> Kepler-users mailing list >> Kepler-users at ecoinformatics.org >> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users >> >> > _______________________________________________ > Kepler-users mailing list > Kepler-users at ecoinformatics.org > http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users > -- ******************************************************************* Dan Higgins higgins at nceas.ucsb.edu http://www.nceas.ucsb.edu/ Ph: 805-893-5127 National Center for Ecological Analysis and Synthesis (NCEAS) Marine Science Building - Room 3405 Santa Barbara, CA 93195 *******************************************************************
