[Pypes-developer] [ pypes-Bugs-2947547 ] 2nd InputPort not connected correctly to 2nd OutputPort

[SourceForge.net <no...@so...>]

Bugs item #2947547, was opened at 2010-02-07 13:33
Message generated for change (Tracker Item Submitted) made by mattrweber
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1155513&aid=2947547&group_id=271766

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interface
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Matt Weber (mattrweber)
Assigned to: Eric Gaumer (egaumer)
Summary: 2nd InputPort not connected correctly to 2nd OutputPort

Initial Comment:
When you have a pipeline with a component that has 2 output ports followed by a component with 2 input ports, the 2nd output port does not get connected to the 2nd output port correctly.  To reproduce:

1. Start pypes with empty pipeline
2. Create the following pipeline TextReader -> Split -> Collate -> Debug.
3.  Send any text file though the pipeline

Take a look at the debug output and you will see that only one document has been output.  If you take a look at the component inputs dictionary (Component._inputs) you will see the 2nd input contains a None object:

{'in2': [None, 'Second Input Port'], 'in': [<pypes.pype.Pype object at 0x9f6c76c>, 'Default input port']}

Now, if you break the connection between the 2 output ports, everything works just fine.  For example put a copy field between the 2nd output port and the 2nd input port and you will now see the expected behavior.

This leads me to believe that the UI code that connects the ports has a bug connecting components with multiple ports.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1155513&aid=2947547&group_id=271766