You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating !PortSpecItems (e.g. via a !PortSpec constructor call), the ids for the !PortSpecItems are set to -1 and are never assigned to proper values. The issue is that the !PortSpecItem creation is done inside the !PortSpec construction which means that we don't have a central place to assign ids except in the constructor. We either need to check all !PortSpec constructions or modify the constructor to grab ids from the controller.
The text was updated successfully, but these errors were encountered:
<ticket>#693</ticket>
Because PortSpecItems are created as part of PortSpec construction, they were not being assigned correct ids (from the IdScope objects). This commit fixes this by spinning through the list of created PortSpecItems and assigning them ids from the corresponding IdScope. Note that this is not a big deal except for those PortSpecs that may be persisted.
vistrails/core/modules/module_descriptor.py:
- ModuleDescriptor.new_port_spec: **removed**
- ModuleDescriptor.add_input_port: **removed**
- ModuleDescriptor.add_output_port: **removed**
vistrails/core/modules/module_registry.py:
- ModuleRegistry.create_port_spec: set PortSpecItem ids
vistrails/core/vistrail/controller.py:
- VistrailController.create_port_spec_static: set PortSpecItem ids
- VistrailController.add_module_port: set PortSpecItem ids
vistrails/tests/utils.py:
- execute: assign PortSpecItem ids
When creating !PortSpecItems (e.g. via a !PortSpec constructor call), the ids for the !PortSpecItems are set to -1 and are never assigned to proper values. The issue is that the !PortSpecItem creation is done inside the !PortSpec construction which means that we don't have a central place to assign ids except in the constructor. We either need to check all !PortSpec constructions or modify the constructor to grab ids from the controller.
The text was updated successfully, but these errors were encountered: