[kepler-dev] [Bug 4228] New: - Not all tokens seem to be written when running WF from commandline

[bugzilla-daemon at ecoinformatics.org]

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

           Summary: Not all tokens seem to be written when running WF from
                    commandline
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: P2
         Component: provenance
        AssignedTo: crawl at sdsc.edu
        ReportedBy: leinfelder at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org


I'm still trying to isolate the problem, but I'm finding that a RecordToken is
not "fully" being written to provenance.
When I run in the GUI I see that the token has two port_event rows: one with a
write_event_id=-1 and another with a write_event_id that corresponds to the
previous row.
When running from the commandline I only see the write_event_id = -1 row and
nothing else.

The recordToken is being passed to a display actor - perhaps the non-GUI filter
is removing that connection and the port firing is modified? That's my only
lead so far...

I will try to make a simpler workflow to isolate it.