[kepler-dev] [Bug 4462] Component search in remote repositories not working

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Sat Feb 6 10:29:47 PST 2010


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4462

--- Comment #8 from ben leinfelder <leinfelder at nceas.ucsb.edu> 2010-02-06 10:29:46 PST ---
In regard to replicating problematic components on Kepler-dev, I sent this
email to Sean:
----
If I was correct about what they contained, a "safe" version would be to search
for a dataset in Kepler ("Datos Meteorologicos" is a good clean test data set)
and you just drag that onto the canvas.
Save that "workflow" to the Kepler-dev repository you'll have a testbed that
hopefully won't cripple KNB when you search Kepler-dev for that workflow
component. wilrwind
To clarify - I don't think there are any "damaged metacat records" - but there
are certainly "problematic moml" files that reference lots of data on the KNB
and bring it to a grinding halt when Kepler parses them in a whirlwind of new
Threads.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the Kepler-dev mailing list