Skip to content

@RedhawkDeployer RedhawkDeployer released this Apr 8, 2021


The effort in REDHAWK 2.2.8 focused on:

  • EOS condition is reported correctly for all connections when an incoming stream receives an EOS flag.
  • Rate in header for zero-rate SDDS headers is ignored
  • Resolved issue when adding a new stream to an attachable port that would cause a program to segfault.
  • Exiting a python sandbox session will now properly terminate a resource's processes started during the session that threw initialization exceptions.

Fixes

The following fixes were completed in REDHAWK 2.2.8:

Core Framework Fixes

  • The application object updates the property on the correct component when one component's name is a substring of another component
  • Slow-startup devices no longer cause issues for the Python sandbox
  • Removed vendor check for Java

IDE Fixes

  • Null pointer fixed and doesn't occur any longer

Special Resolution

The following previously reported Known Issues have been closed in REDHAWK 2.2.8 with the following resolutions:

IDE Special Resolutions

  • This has been fixed. The behavior no longer exists as stated in defect.
  • OBE
Assets 16

@RedhawkDeployer RedhawkDeployer released this Mar 18, 2021


The effort in REDHAWK 2.3.0 focused on:

  • Added methods to C++ ThreadedComponent API, that allow developers to determine if stop was called or if the resource internally reached an finished state.
  • Added Python iterator support to limit the number of entries that are returned from a servant's iterator interface.
  • Fixed connection rate check for rh.MSDD during device startup when the MSDD radio supports multiple network interfaces.
  • rh.MSDD correctly enables the tuner's output module for successful allocations The rh.MSDD property advanced::max_nic_percentage will now track the total output rate from the radio's network interface against this threshold to disallow allocations that oversubscribe the interface.
  • Resolving issue to correctly set the time-of-day in ONEPPS mode.
    Added properties msdd_status::tod_host_delta (gives the time-of-day offset between the host and the MSDD's TOD module while in ONEPPS mode) and msdd_status::ntp_running (shows whether ntp is running on the host while in ONEPPS mode).
  • Added JAVA Bulk IO Stream API support to bulkio.jar
  • EOS condition is reported correctly for all connections when an incoming stream receives an EOS flag.
  • An application's external property maps to the correct component when the component's name is a substring of another component.
  • Fixed issue where timecodes values were not properly adjusted during filter operations.
  • rh.fastfilter adds a bybass mode property. When bypass mode is enabled, any input stream data bypasses all filter operations and passed directly to any output connections.
  • rh.psd component properly handles values above 2.4 GHz for SRI keywords CHAN_RF and COL_RF.
  • Resolved issue when adding a new stream to an attachable port that would cause a program to segfault.
  • Exiting a python sandbox session will now properly terminate a resource's processes started during the session that threw initialization exceptions.

New Features

The following features were added in REDHAWK 2.3.0:

Core Framework Features

  • Added Bulkio Stream support in Java

Documentation Features

  • Added support for Java Bulk IO stream API

Fixes

The following fixes were completed in REDHAWK 2.3.0:

Core Framework Fixes

  • Changed setup and teardown code to prepare the state of /dev/shm to allow the test to operate properly.
  • For JAVA BulkIO ports, disconnectPort will throw CF.InvalidPort for unknown connection identifiers.
  • Device_impl::updateUsageState is now a virtual method to allow for specialization.
  • The application object updates the property on the correct component when one component's name is a substring of another component
  • Removed vendor check for Java
  • Do not remove PushConsumers if a timeout occurs during a push operation.

IDE Fixes

  • Null pointer fixed and doesn't occur any longer

Documentation Fixes

  • Updated the format of headings in the REDHAWK Manual.
  • Updated the REDHAWK ICD to indicate that dataChar is deprecated and dataOctet should be used in favor of dataChar.
  • Added an example using the connectionId argument when making sandbox connections.
  • Updated glossary links to display the first time glossary terms are displayed on a page. Acronym terms and the corresponding acronym were updated to display the first time the terms are displayed on a page. After this first occurrence, only acronyms are displayed.
  • All images in the manual now have a caption displayed under the image.
  • Added GPS interface information to the FrontEnd Interfaces appendix.
  • Added NavData interface information to the FrontEnd Interfaces appendix.
  • Added RFInfo interface information to the FrontEnd Interfaces appendix.
  • In Optimization -> Configuring omniORB, fixed a typo that referenced IORs.
  • In Frontend Interfaces -> Types of Tuners -> CHANNELIZER Tuner, fixed a typo that referenced DDC.
  • Updated the cleanomni script to include CentOS 7 information, and rearranged the omni information in the Troubleshooting appendix .
  • In Troubleshooting -> Setting Omni Log Levels, updated the omniORB User's Guide links for CentOS 7.
  • In the Logging Configuration Plugin section, fixed a typo that referenced --useloglib.
  • Updated tables in the manual to auto adjust in size so the contents wraps correctly within the cells.
  • Removed UHD dependencies from those provided in REDHAWK and added them to the External Dependencies appendix.
  • In Managing and Defining Properties, fixed a typo in the utctime description.
  • Fixed grammatical errors in the REDHAWK ICD and in the SCA Domain Profile.
  • In the Waveform Editor -> Components Tab section, removed the reference to Component ID and modified the text to match the new Components Tab image.
  • In the Waveform Editor and in the Distributed Computing and RF Devices sections, updated missing and incorrect links.
  • In the Connecting to a Running Domain section, fixed minor typographical errors.
  • In the REDHAWK ICD, corrected section numbers.
  • In the REDHAWK ICD and in the SCA Specification, fixed minor typographical errors in the Logging Description section.
  • In the Logging Within a Resource section, fixed minor typographical errors.
  • In the Waveform Editor, in the Components Tab section, added the Components Tab image.
  • In References for Application Developers, corrected the Sandbox link to point to the Sandbox section.
  • In Creating a New Node, corrected the Exploring the Running Node link to point to the Exploring the Running Node section.
  • In Creating a Waveform Service Configuration Using the rhadmin Script, corrected the Waveform Configuration File link to point to the Waveform Configuration File page.
  • Fixed error of DMD file reference to be DCD file in Creating a Node section.
  • Removed a sentence from the Workbench topic.
  • Corrected expanded term information for JDT (Java Development Tools) and CDT (C/C++ Development Tools) acronyms.
  • Removed the following glossary terms: Editor, System, Ethernet, Linux, and Local Area Network.
  • Updated the Installing the Framework from Source and the Device and Service Affinity sections to reflect affinity disable build options.
  • Updated the Persistence Store and the Installing the Framework from Source sections to reflect that the default build now enables the sqlite backend.
  • Updated custom.css to fix table formatting issue.
  • Removed references to 32-bit OS versions that are no longer supported.
  • Removed Standalone EPEL information from the REDHAWK External Dependencies appendix.
Assets 18

@RedhawkDeployer RedhawkDeployer released this Nov 6, 2020


The effort in REDHAWK 2.2.7 focused on:

  • Plugin infrastructure created for GPP to track custom system metrics
  • Queue flush reported on all affected streams in the incoming queue
  • When reading Bulk IO streams, allow the consume size to be greater than the read size (equivalent to read+skip)
  • Resolving an issue with intermittent failures in omniEvents when writing to syslog running on CentOS 7.
  • Components generate from command line with applications like createBinaryComponent generate the correct header on the SCD and PRF files
  • Java message ports are consistent with Python and C++ message ports. When the message fails, it tries again in subsequent messages
  • Python helper pythonComplexListToBulkioComplex converts numpy.float to Python native float

Fixes

The following fixes were completed in REDHAWK 2.2.7:

Core Framework Fixes

  • Resolved an issue with device allocations. If the device's state is BUSY, the device allocation always returns False.
  • Resolved an issue with ports generated from custom IDL. The ports now use the hierarchical logger to log errors.
  • RH_SOFTPKG_CXX version checks are honored when minimum and maximum versions are given for the dependency
  • Resolved an issue with custom interfaces returning a data structure with variable-length fields. The generated code now returns the correct type.
  • Resolved an issue with the DeviceManager. It now sets the process group id for all services and devices that it launches.
  • Resolved issue with attachable ports (like dataSDDS and dataVITA49) failing silently. They now report a failure to attach with an exception.
  • Resolved an issue with code generators. They no longer fail when the wavedev file is missing.
  • Appropriate XML headers are created for SCD and PRF files when creating a project from command line
  • Python helper pythonComplexListToBulkioComplex converts numpy.float to Python native float
  • When invoking resource.getPOA, if a name is provided, the named POA is returned
  • When using Bulk IO streams, the amount of data consumed (pointer pushed forward) can exceed the amount of data read
  • Java output message ports can recover from CORBA.COMM_FAILURE errors

Documentation Fixes

  • Updated custom.css to fix table formatting issue.
  • Removed Standalone EPEL information from the REDHAWK External Dependencies appendix.

Special Resolution

The following previously reported Known Issues have been closed in REDHAWK 2.2.7 with the following resolutions:

Core Framework Special Resolutions

  • popen in spawnnodebooter needs a nb.wait() to make sure that a return code is received - Cannot Reproduce - This bug could not be reproduced against REDHAWK 2.2.6. (The test framework already has a wait on the popen.)
  • Out scan control ports are missing from FEI library - Duplicate of Output scanning tuner ports are missing the template, and this feature was resolved in REDHAWK 2.2.6.
  • Sandbox generates an unnecessary error when cleaning up - Fixed by Other Issue - Fixed by update in REDHAWK 2.2.3 release: When the Python sandbox exits and it has a reference to a Device Manager, the deactivation of the object no longer raises an exception if the object no longer exists.
  • Cannot call connectPort on a bidirectional MessageEvent port - Won't Fix - This is the expected behavior. A bidirectional message port is a message consumer port. Connecting a message consumer port to another message consumer port is invalid.
Assets 23

@RedhawkDeployer RedhawkDeployer released this May 6, 2020


The effort in REDHAWK 2.2.6 focused on:

  • Resolving an exception that occurred when calling theAllocationManager's listAllocations method with no arguments.
  • Adding developer documentation to explain how to enable JacORB for Java components.
  • Fixing typos in component sample code comments.
  • Implementing fixes to properly initialize the persona device logger.
  • Changing _bindir to _libdir in the generated .spec file for generated C++ components.
  • Adding a return code to cleanomni to indicate when one of the steps failed. In the event of an error, cleanomni still attempts each step of the cleanup process before exiting with a non-zero status.
  • Modifying Device Manager behavior to no longer hang on shutdown when non-DCD devices/services remain registered.
  • Resolving an issue with the DeviceManager exiting during device and service registrations due to unhandled exceptions.
  • Updating the behavior of the GPP's memory threshold monitoring to more accurately reflect real world usage. The available memory is calculated using MemAvailable, which provides the best estimate per the Linux kernel and does not include swap memory. The default value for the free memory threshold is now the lesser of 20% of total memory, or 6GB.
  • Resolving a dead lock issue that occurred during the omniEvents check point operation.
  • Preventing the file system from crashing when files are removed while list() is invoked.
  • Resolving handling of process lifecycle by the GPP when process identifiers are reused on a busy system. Adding safeguard against the GPP terminating processes when the process identifier and process group identifier are not the same.

Fixes

The following fixes were completed in REDHAWK 2.2.6:

Core Framework Fixes

  • Fixed display of property.api() for Python sandbox components.
  • Added DigitalScanningTuner interface to C++ and OutDigitalScanningTunerPort to Java.
  • Updated the Python output in the Custom Transport Technical Notes.
  • Added comparison of sri.blocking to comparison of two SRIs.

IDE Fixes

  • Removed the Help button from the Properties tab of the Softpkg Editor in the IDE.
  • Increased the thread.sleep value in order to let all processes completely stop.
  • Resolved issue with Browse Properties dialog to display all matching criteria for the filtered text.

Documentation Fixes

  • Updated the formatting in all REDHAWK Specifications and fixed inconsistencies and errors in cross references and text.
  • Corrected capitalization of Event Service.
  • Corrected inconsistent capitalization and incorrect glossary references of the term, sandbox.
  • Removed the term, role, from the subscriber and publisher implementation information in the Working with Events page of the REDHAWK Manual.
  • Revised and reorganized the BulkIO data transfer and Stream API information and added the Attachable Streams page to the REDHAWK Manual.
  • Updated the Overview Tab information in the SoftPkg Editor page of the REDHAWK Manual.
  • Updated text and graphics in the Waveform Editor page of the REDHAWK Manual.
  • Added REDHAWK asset README.md files, REDHAWK asset release notes, and the updates repository information to the main website page.
  • Updated screen captures in the Creating a REDHAWK Shared Library Project page, the Plot Settings Dialog page, and the Using the Octave Wizard page of the REDHAWK Manual.
  • Updated STDOUT references in the log configuration information and stdout references in the code examples in the Configuring Logger Settings page of the REDHAWK Manual.
  • Updated property access information in the Managing and Defining Properties page of the REDHAWK Manual.
  • Added a section, IDE and Code Generation Support, to explain how to create a programmable device and a persona device using the IDE and code generators.
  • Added instructions for using the REDHAWK Updates repository.
  • Removed 2.1.x beta information from the website.

Special Resolution

The following previously reported Known Issues have been closed in REDHAWK 2.2.6 with the following resolutions:

IDE Special Resolutions

  • Deleting project does not close all related open editors - Cannot Reproduce - This bug could not be reproduced against REDHAWK 2.2.5.
  • IllegalArgumentException when cancelling FindBy Wizards - Cannot Reproduce - This bug could not be reproduced against REDHAWK 2.2.5.
  • CI RCPTT test fails for red x on testDomainConnectionLoss - Fixed by Other Issue - Fixed by update in 2.2.3 release: Improved the robustness of Domain Manager refresh in the Explorer view so that it is less likely to require a manual refresh when the Domain Manager is unexpectedly terminated and restarted.

Documentation Special Resolutions

  • TOC disappears in the left frame of the Manual upon subheading selection - Cannot Reproduce - This bug could not be reproduced against REDHAWK 2.2.5.
  • Typo in REDHAWK ICD - Fixed by Other Issue - Fixed by update in REDHAWK 2.2.4 release: Updating the REDHAWK SCA Specification and the REDHAWK ICD Specification with the application launch sequence that includes initializeProperties.
Assets 23

@RedhawkDeployer RedhawkDeployer released this Dec 30, 2019


The effort in REDHAWK 2.2.5 focused on:

  • Resolving an issue that occurred when creating an event channel with an empty string name. In this case, an exception is now thrown and documentation was added explaining valid content for event channel names.

Fixes

The following fixes were completed in REDHAWK 2.2.5:

Core Framework Fixes

  • Corrected misspellings in loghelpers.cpp.
  • The generated SAD xml excludes components such as StreamSource, StreamSink, etc.

IDE Fixes

  • Consolidated graphical and graphical-runtime tests to both use the installed REDHAWK components.
  • Removed synchronous call when closing the Signal Related Information (SRI) view because a port disappeared.
Assets 23

@RedhawkDeployer RedhawkDeployer released this Sep 13, 2019


The effort in REDHAWK 2.2.4 focused on:

  • Enabling the SCA File Manager to return hidden files when requesting a directory listing from the FileSystem or theFileManager.
  • Improving support when adding RFInfo, GPS, and NavData ports to a component. The generated implementation now supports the delegation pattern with the component rather than empty methods that require developer implementations.
  • Documenting how to overload BulkIO ports to implement out-of-band communications (for example, between components implemented on FPGA). Developer documentation is available at https://github.com/RedhawkSDR/core-framework/tree/2.2.4/docs/custom-transport.
  • Updating SoundSink to detect and use the correct version of gstreamer to enableSoundSink to work on both CentOS 6 and 7; and updating the External Dependencies in the REDHAWK Manual to include the appropriate gstreamerdependencies.
  • Correcting the blocking behavior when using an infinite queue size.
  • Improving the shared memory subsystem to reduce total memory use and provide additional controls to system deployers.
    • Modified behavior such that when BulkIO connections use shared memory for the transport, virtual memory mappings are reused across input connections to reduce the growth of the process' memory space.
    • Changed the default behavior of the shared memory allocator to increase the reuse of shared memory and reduce the growth of heap files.
    • Added runtime metrics to the shared memory allocator for observing and tuning the usage of shared memory on a system. Shared memory allocator metrics are disabled by default. Developer documentation is available at https://github.com/RedhawkSDR/core-framework/tree/2.2.4/docs/shared-memory/metrics.md.
    • Added configurable settings to the shared memory allocator that are managed via environment variables. These options allow system deployers to tune the shared memory allocator for higher concurrency or lower memory footprint, depending on the expected usage. Developer documentation is available at https://github.com/RedhawkSDR/core-framework/tree/2.2.4/shared-memory/tuning.md.
  • Updating cleanes to clean the appropriate log location based on the version of omniEvents.
  • Resolving issue with Python sandbox plotting of complex data.
  • Modifying how the Device Manager deploys SharedLibrary devices. It no longer attempts to launch SharedLibrary devices as if they are Executable devices. An error message is displayed and the device is not launched.
  • Updating the REDHAWK SCA Specification and the REDHAWK ICD Specification with the application launch sequence that includes initializeProperties.
  • Fixing a condition in which C++ BulkIO input ports could cause a crash during frequent SRI updates.
  • Modifying behavior in EventChannelManager registerConsumer and registerPubslisher methods. If the event channel in the registration request does not exist, the event channel is created to satisfy the request.
  • Resolving issue with Python components that use both the generic and specific message callbacks. These components no longer have values overwritten in the generic message callback invocation. When associating both a specific message callback and a generic message callback to a message input port, the generic message callback is populated with an id/value pair, where the value is of type any.
  • Adding Boost header includes to some files to allow building with later versions of Boost.
  • Modifying the code generators to only allow persona devices to be created as SharedLibrary (not Executable). When attempting to generate code for a persona device with its xml code type set to Executable, the code generators display an error.

Fixes

The following fixes were completed in REDHAWK 2.2.4:

Core Framework Fixes

  • Updated bluefile.py to the latest version.
  • Updated BulkIO unit tests by replacing DataSource and DataSink with StreamSource and StreamSink except in cases where DataSource or DataSink itself was being tested. In such cases, the deprecation warnings were silenced.
  • NodeBooter bash completion is installed in the Runtime install whereas previously, it was installed in the Devel rpm.
  • Fixed issue when configuring properties and assigning non-boolean values in Java. The value defaults to false rather than throwing an exception.
  • Fixed issue when using the same stream ID for multiple back-to-back streams into a single port; the SRI no longer gets corrupted.
  • Fixed an issue with multi-domain allocations where the AllocationManager would attempt to allocate all of the original requests on subsequent remote domains, as opposed to only the requests that have not been satisfied.
  • Resolved event channel connection issues when the Domain Manager and omniEvents reside on different hosts and the channel already exists.
  • Fixed issue with Python stream API to properly handle back-to-back streams.
  • Resolved synchronization issues for FrontendTunerDevice's allocateCapacity and deallocateCapacity.

IDE Fixes

  • Fixed the Event Channel processing to use persistent server connections.

Documentation Fixes

  • Corrected parameter definition for sandbox Valgrind in Working with Components, Devices, and Services section of the REDHAWK Manual.
  • Added rh.MSDD to the Basic Devices Section of the Core Assets release notes page and reordered the waveform information.

Special Resolution

The following previously reported Known Issues have been closed in REDHAWK 2.2.4 with the following resolutions:

Core Framework Special Resolutions

  • testExecute in GPP can fail depending on num cpus - Cannot Reproduce

Documentation Special Resolutions

  • Incorrect section numbers and page numbers in REDHAWK SCA Specification and ICD pdfs - Won't Fix - This issue was caused by the unoconv PDF conversion tool. The conversion tool is no longer being used.
Assets 23

@RedhawkDeployer RedhawkDeployer released this Jun 17, 2019


The effort in REDHAWK 2.2.3 focused on:

  • Adding a note in the REDHAWK Manual about compiling REDHAWK with newer versions of GCC that default to the C++11 standard.
  • Adding code to DomainEventReader to recognize and handle object-removed events.
  • Adding the Querying and Configuring Components and Devices section in the REDHAWK Manual to include instructions on how to interact with properties from programs in C++, Java, or Python.
  • Resolving a missing symbol issue for C++ bulkio::SampleDataBlock::copy() methods.
  • Improving how gpp_setup responds to the host processor. If the processor cannot be determined, user input is requested.
    Adding the section, Setting Host Architecture/Computer Processor Name, to the Troubleshooting appendix of the REDHAWK Manual.
  • Correcting the Domain Manager's behavior when a DCD has an improperly-defined connection (for example, an incorrect port name) between a device and a service. The Domain Manager now correctly completes all other valid connections defined in the DCD.
  • Correcting the Device Manager's behavior to successfully reconnect with the Domain Manager in the event that the Domain Manager has to be reset.
  • Modifying the getPacket function in Java to limit logging, which allows garbage collection to keep up when the argument in getPacket is set to zero.
  • Resolving the following issues related to shared memory transport:
  • Rapidly stopping and restarting components with BulkIO shared memory connections could lead to crashes or aborts.
  • Incorrect display of owner PID for shared memory heaps in redhawk-shminfo.
  • Resolving issue within the ProcessThread base class in C++ to take into account an updated delay value.
  • Providing the following updates related to generating a component using createOctaveComponent:
  • The contents of the SCD file are generated by inspecting the ports to list the interfaces.
  • The contents of the SoftPkg ID is based on a DCE:<uuid> instead of the m-file.
  • Correcting behavior when an allocation of an FEI device fails. The frontend_tuner_status is not updated with the failed allocation's values.

Improvements

The following improvements were added in REDHAWK 2.2.3:

Documentation Improvements

  • Added documentation regarding object creation and garbage collection in Java components' and devices' serviceFunction.

Fixes

The following fixes were completed in REDHAWK 2.2.3:

Core Framework Fixes

  • Resolved issue ensuring --useloglib tab complete now works with nodeBooter.
  • Added a helpful error message that is displayed when Naming Service is not running.
  • Provided the correct commit hash and build timestamp in RPM header.
  • Updated test to override methods in unittest.TestProgram, for Python versions < 2.7, to skip tests related to Non-Uniform Memory Access (NUMA) when the host does not support NUMA.
  • Lowered NIC thresholds for Core Framework (CF) regression testing.
  • Changed setup and teardown code to prepare the state of /dev/shm to allow the test to operate properly.
  • Increased wait time in testBusyLoadAvg test to allow CPU load average to settle.
  • Updated code to properly identify CPUs on virtual machines.
  • Fixed failures with unit test test_04_ApplicationFactory.py test_ExecParamToConstruct_py.
  • Fixed intermittent failures for unit test test_01_DeviceManager.py test_DeviceBadOverload.
  • Resolved issue for GPP to correctly identify CPU affinity for network interfaces that support RX/TX queues.
  • Changed wait conditions in the test script so that test_01_DeviceManager.py DevCppPyJavaDeps no longer fails intermittently.
  • When the Python sandbox exits and it has a reference to a Device Manager, the deactivation of the object no longer raises an exception if the object no longer exists.
  • Updated test_13_RedhawkModule.py test_API_remap to account for new versions of omniORBpy.
  • Added better regression testing checks to deal with slower CI infrastructure.
  • Added device checks throughout Core Framework tests to reduce false errors.
  • Added smarter check to test_MessageMarshalJava to support slower continuous integration.
  • When a property is configured, if the new value is the same as the old value, the property change callback in the component/device is not triggered.
  • Using getPacket(0) no longer leads to large memory growth in Java components.

IDE Fixes

  • Corrected a resource leak in the command-line plotter.
  • Addressed code quality issues.
  • Corrected an issue with the JavaFileFileImplTest.close() unit test.
  • Fixed an error in configuring dataBit plots.
  • Improved the robustness of Domain Manager refresh in the Explorer view so that it is less likely to require a manual refresh when the Domain Manager is unexpectedly terminated and restarted.
  • Added a very short duration cache of metadata for SCA filesystem objects to reduce network traffic.
  • Corrected the FrontEndDataProvider to now only listen to the data provider preference to enable/disable the FrontEnd tuners shown in the REDHAWK Explorer view.

Documentation Fixes

  • Modified a reference to Allocating a FrontEnd Tuner.
  • Corrected capitalization on the REDHAWK Core Assets page.
  • Corrected an incomplete sentence in the Manually Including External Libraries section of the REDHAWK Manual.
  • Updated references to the node definition file to use dcd.xmlrather than DCD.
  • Fixed typos in the REDHAWK Manual.
  • Improved information in the Message Producer and Message Consumer sections of the REDHAWK Manual.
  • Revised RF Allocation information in the Distributed Computing and RF Devices section of the REDHAWK Manual.
  • Corrected capitalization of terms and references to interfaces in the REDHAWK Manual.
  • Corrected the term "Linux domain sockets" with "Unix domain sockets" in the Getting Started with REDHAWK Guide and in the REDHAWK Manual.
  • Corrected capitalization of the acronyms, "TCP" and "GIOP" in the Optimization appendix.
  • Removed bash from code blocks in the Logging Configuration Plugin appendix.
  • Updated the documentation repository releases file to enable the manuals to display in release version during development.
  • Fixed capitalization inconsistencies.
  • Corrected inconsistency of terms in the REDHAWK Manual.
  • Removed bash from code blocks in the Configuring Logger Settings and Adjusting Logging at Runtime sections of the REDHAWK Manual.
  • Updated the New Domain Manager dialog and revised text in Connecting to a Running Domain section.
  • Removed references to 1.8 version of REDHAWK in the External Dependencies appendix.
  • Fixed improper sub-section headings in the REDHAWK Manual.
  • Fixed a missing reference and corrected an example class name in the Writing Your Own Event Consumer section of the REDHAWK Manual.
  • Removed references to 32-bit OS versions that are no longer supported.
  • Updated the REDHAWK Manual to include introductory sentences after section headings and before tables to describe the information being presented.
  • Updated REDHAWK runtime dependency information to include bash-completion, which enables tab completion when running the nodeBooter command.
  • Updated the GitHub link on the manuals website pages.

Special Resolution

The following previously reported Known Issues have been closed in REDHAWK 2.2.3 with the following resolutions:

IDE Special Resolutions

Assets 23

@RedhawkDeployer RedhawkDeployer released this Mar 15, 2019


The effort in REDHAWK 2.2.2 focused on:

  • Updating the redhawk.attach() call to not cache domains anymore. Instead, the last connected CORBA ORB is cached and subsequent calls make sure the ORB is still valid.
  • Fixing refresh and NPE issues in the REDHAWK Explorer view. Event channels are now properly connected on Domain Manager restarts. ClientMessageReceptor threads no longer grow unbounded.

Fixes

The following fixes were completed in REDHAWK 2.2.2:

Core Framework Fixes

  • Rebinded domain event channels to their domain context name and not their fully qualified name used in the Event Service.
  • Restored ODM and IDM channels when the persistence database file is present.
  • Resolved issue with creating IDM_Channel when DeviceManager does not unregister properly due to failed execution.

Documentation Fixes

  • Removed references to 32-bit OS versions that are no longer supported.

Special Resolution

The following previously reported Known Issues have been closed in REDHAWK 2.2.2 with the following resolutions:

Core Framework Special Resolutions

  • GPP NIC affinity blacklist test is using the wrong CPU list - Cannot Reproduce - This bug could not be reproduced against REDHAWK 2.2.2.
  • test_GPP.py testForceOverride can't grab 2nd socket in vm with one socket - Won't fix - This behavior only affects the REDHAWK 2.0.x series.
Assets 23

@RedhawkDeployer RedhawkDeployer released this Mar 15, 2019


The effort in REDHAWK 2.2.1 focused on:

  • Improving how the MessageSupplier port's sendMessages() method handles bulk message failures when the size exceeds the maximum CORBA transfer size. On failure, messages are now sent individually.
  • Fixing the Octet output format for the bluefile FileSink.
  • Changing the output for the "number of samples pushed" when data for a BulkIO stream is generated spanning multiple timestamps. The output changed from being the "number of samples spanning the timestamp packets" to being the "number of samples that was requested".
  • Resolving an issue for BulkIO input ports to hold multiple back-to-back streams with the same stream ID in a pending, independent state.
  • Ensuring that the Python Publisher and Subscriber classes disconnect from their event channels before unregistering from the Event Channel Manager.
  • Ensuring that calling stop on a component no longer causes an exception from a timeout if the NOOP sleep time in C++ components is too long.
  • Enabling waveforms to successfully run when the useScreen property is set to true on the GPP in a Device Manager.
  • Correctly resolving @@@WAVEFORM.INSTANCE@@@ and @@@DEVICE_MANAGER.NAME@@@ in log files for components and devices, respectively.
  • Fixing an issue with loadSADFile and generateSADXML. When using loadSADFile, all connections in the XML file are appropriately created in the Python sandbox, and when using generateSADXML, connections in the sandbox are included in the resulting XML.
  • Preserving EOS and sriChanged flags on a per-stream basis when a BulkIO input port queue is flushed. As a result, when a queue flush occurs, any stream that has an EOS in the queue will receive an empty packet with EOS set.
  • Preventing duplicate service name registration in the REDHAWK domain. When a Device Manager attempts to register a service with a name that is already in use, the Domain Manager throws an exception and the Device Manager terminates the service's process.
  • Generating a unique identifier for NIC allocations from host-collocated components in a waveform.
  • Supporting NIC allocations for host-collocated components in a waveform.
  • Fixing a memory leak in BulkIO input ports when using getPacket() to fetch data.
  • Fixing an issue to allow files to be truncated when component host logging is enabled on the GPP.
  • Enabling persistence at runtime (persistence is compiled into the Core Framework by default) by providing a backend database to store the configuration when launching a Domain Manager using the nodeBooter argument --dburl.
    The persistence options to nodeBooter are handled more strictly:
    • If --dburl is given when launching a Domain Manager, and the database file location cannot be accessed, an error is reported and the Domain Manager is not launched.
    • If --dburl is given when launching only a Device Manager, an error is reported and the Device Manager is not launched.
    • The --nopersist argument to nodeBooter is deprecated and has no effect.
  • Enabling Non-Uniform Memory Access (NUMA) affinity processing by default in the GPP. Prior releases required a source code rebuild to enable this feature.
  • Resolving an issue to allow for the use of a connection ID in each control port's getter methods, FrontEnd Interfaces, or custom IDL when a value is being returned.
  • Resolving an issue with increased application launch times identified during endurance testing.
  • Correcting the handling of shared library SoftPkg dependencies for loadable devices to properly add Java and Python dependencies to the environment prior to running components.

Fixes

The following fixes were completed in REDHAWK 2.2.1:

Core Framework Fixes

  • Fixed a code generator's issue involving Python and Java component implementations with numeric values specified as hexadecimal numbers in the component's properties file (prf.xml).
  • When a component running in the Python sandbox crashes, if it allocated any shared memory heap (/dev/shm), it is cleaned up by the sandbox.
  • Improved comments describing the GPSInfo data structure.
  • The attribute, _instanceName, for Device Managers shown in the Python sandbox resolves correctly.
  • Updated the GPP to check if the Non-Uniform Memory Access (NUMA) library is supported by the running host before making NUMA affinity requests.
  • Fixed issue to allow command-line properties with empty string values to be passed into the initializeProperties method.
  • Resolved unhandled exceptions that occur when a component process exits or fails during registration with the Domain Manager. Resolved memory loss issues when components register with the Domain Manager.
  • Fixed issue to handle all exceptions that can occur between a registering component and the Domain Manager.
  • BulkIO shared memory connections detect when the input side terminates unexpectedly without disconnecting, avoiding an error state in which the output side becomes unresponsive and consumes an entire CPU.
  • When quitting a Python session after attaching to a REDHAWK domain, the CORBA ORB will be shutdown.
  • Fixed issue so when using ulimit -u before starting the GPP, the GPP properly interprets the thread limits as either a number or the string 'unlimited'.
  • Event channels created through the event channel logging appender (RH_LogEventAppender) register with the Event Channel Manager if available.
  • Unregistering a property change listener no longer causes a race condition to occur.
  • Matched the Python API to the C++ API in FEI, and added an optional connection ID to the output FEI control port.
  • Fixed intermittent test failures due to low available memory in container.
  • Fixed intermittent test failures due to a test occurring before the Device Manager terminates.
  • Fixed application metrics test intermittent failure.

IDE Fixes

  • Resolved issue so data from BulkIO dataOctet ports is now plotted correctly.
  • Improved the efficiency of the REDHAWK Explorer view's auto-refresh.
  • Improved the efficiency of refreshing event channels in the REDHAWK Explorer view.
  • Corrected an issue so event channel information for a domain is appropriately retrieved.
  • Resolved issue to ensure CORBA objects used by the IDE's models are always released.
  • Corrected an NPE that may occur while releasing a resource in the sandbox.
  • Improved UI responsiveness for large domains.
  • Corrected the icons for ports and connections in the Port Monitor view.
  • Updated the default port type when creating an FEI device to now be dataShort.
  • Resolved an issue to prevent a possible NPE when interacting with context menus on ports.
  • Addressed a code quality issue regarding unused project natures.
  • Addressed a code quality issue to correct errors in xcore model files.
  • Addressed a code quality issue to correct the use of deprecated BulkIO classes.
  • Corrected a concurrency issue that occurred while accessing XML profiles.
  • Corrected a graphical issue so the text for a highlighted selection is displayed when selecting a new log level in the SAD editor.
  • Corrected issues with the workflow for connecting to a new Domain Manager.
  • Corrected an issue that prevented launching devices with a SoftPkg dependency from context menus.
  • Ensured that two services cannot be registered with the same name in the sandbox.
  • Waveforms with a componentinstantation ID that does not match the usagename now launch properly in the IDE sandbox.

Documentation Fixes

  • Updated the format of headings in the REDHAWK Manual.
  • Updated the REDHAWK ICD to indicate that dataChar is deprecated and dataOctet should be used in favor of dataChar.
  • Added an example using the connectionId argument when making sandbox connections.
  • Updated glossary links to display the first time glossary terms are displayed on a page. Acronym terms and the corresponding acronym were updated to display the first time the terms are displayed on a page. After this first occurrence, only acronyms are displayed.
  • All images in the manual now have a caption displayed under the image.
  • Added GPS interface information to the FrontEnd Interfaces appendix.
  • Added NavData interface information to the FrontEnd Interfaces appendix.
  • Added RFInfo interface information to the FrontEnd Interfaces appendix.
  • In Optimization -> Configuring omniORB, fixed a typo that referenced IORs.
  • In Frontend Interfaces -> Types of Tuners -> CHANNELIZER Tuner, fixed a typo that referenced DDC.
  • Updated the cleanomni script to include CentOS 7 information, and rearranged the omni information in the Troubleshooting appendix .
  • In Troubleshooting -> Setting Omni Log Levels, updated the omniORB User's Guide links for CentOS 7.
  • In the Logging Configuration Plugin section, fixed a typo that referenced --useloglib.
  • Updated code blocks to include a pinned "Copy to clipboard" icon on the right side.
  • Updated tables in the manual to auto adjust in size so the contents wraps correctly within the cells.
  • Removed UHD dependencies from those provided in REDHAWK and added them to the External Dependencies appendix.
  • In Managing and Defining Properties, fixed a typo in the utctime description.
  • In the Waveform Editor -> Components Tab section, removed the reference to Component ID and modified the text to match the new Components Tab image.
  • In the Waveform Editor and in the Distributed Computing and RF Devices sections, updated missing and incorrect links.
  • In the Connecting to a Running Domain section, fixed minor typographical errors.
  • In the REDHAWK ICD, corrected section numbers.
  • In the REDHAWK ICD and in the SCA Specification, fixed minor typographical errors in the Logging Description section.
  • In the Logging Within a Resource section, fixed minor typographical errors.
  • Changed the "Documentation" button for the website and the manuals to a house icon with the text "Home". Changed the REDHAWK icon and "REDHAWK" text to also link to the main website page.
  • Added instructions (README.md file) on how to use the new documentation repository.
  • In the Waveform Editor, in the Components Tab section, added the Components Tab image.
  • Updated documentation repos to pull from the local copy of the docdock theme.
  • In References for Application Developers, corrected the Sandbox link to point to the Sandbox section.
  • In Creating a New Node, corrected the Exploring the Running Node link to point to the Exploring the Running Node section.
  • In Creating a Waveform Service Configuration Using the rhadmin Script, corrected the Waveform Configuration File link to point to the Waveform Configuration File page.
  • Fixed error of DMD file reference to be DCD file in Creating a Node section.
  • Removed a sentence from the Workbench topic.
  • Corrected expanded term information for JDT (Java Development Tools) and CDT (C/C++ Development Tools) acronyms.
  • Removed the following glossary terms: Editor, System, Ethernet, Linux, and Local Area Network.
  • Updated the Installing the Framework from Source and the Device and Service Affinity sections to reflect affinity disable build options.
  • Removed REDHAWK Core Asset version numbers from tables in REDHAWK Core Assets section.
  • Updated the Persistence Store and the Installing the Framework from Source sections to reflect that the default build now enables the sqlite backend.
  • Added information about control port connection management.

Special Resolution

The following previously reported Known Issues have been closed in REDHAWK 2.2.1 with the following resolutions:

Core Framework Special Resolutions

  • Component loggers do not honor DEBUG_LEVEL exec param - Fixed by Other Issue - Fixed by update in REDHAWK 2.1.3 release: Changing log_level on the Domain Manager now affects all classes in the Domain Manager process space.
  • waveform.instanceName returns assembly controller instance name - Cannot Reproduce - This bug could not be reproduced against REDHAWK 2.0.8 or 2.2.0.
  • Error when running daughterboard tests - Fixed by Other Issue - Fixed by resolving issue to allow for the use of a connection ID in each control port's getter methods, FrontEnd Interfaces, or custom IDL, when a value is being returned.

IDE Special Resolutions

  • Duplicate of Generated XML files from the Python sandbox cannot be loaded correctly on the Chalkboard (fixed in REDHAWK 2.2.1) and IDE sends incorrect properties during sandbox launch (fixed in REDHAWK 2.0.4).
  • Drag selection in diagrams uses white dotted lines for the selection rectangle - Won't Fix - This behavior only affects CentOS 6/GTK 2.

Documentation Special Resolutions

  • custom/static/css/custom.css on branch 'docs-829' generates errors using csslint - Won't Fix - The CSS issues are artifacts of the docdock theme and cannot be changed.
Assets 23

@shmahon shmahon released this Sep 7, 2018

REDHAWK Release Notes, Version 2.2.0

The REDHAWK 2.2.0 release is a culmination of all the 2.1.x beta releases into the next Long Term Supported (LTS) product release of REDHAWK.

In summary, REDHAWK 2.2.0 focused on:

  • Adding support for Components to be deployed on a specific GPP, and conversely allowing the GPP to restrict deployments through a matching set of id/value pairs. These id/value pairs are defined in the Software Assembly Descriptor and Device Configuration Definition files respectively. Users may refer to this feature as the "special snowflake" deployment Property.
  • Adding the API for a new type of tuner, a scanning Device.
  • Shared address space Components: Significant enhancement of Component model and BulkIO to support high performance I/O. Developer documentation is available at https://github.com/RedhawkSDR/core-framework/tree/develop-2.2/docs/shared-address.
  • Adding support for a new type of Property, utctime, extending the list that includes types such as short or string. This timestamp Property is used in PropertyChangeEvents and can be queried from Components/Devices with the id QUERY_TIMESTAMP, which is useful when synchronizing the state of the system. utctime can be used by Component/Device developers as an additional type of Property.
  • Adding cacheDirectory and workingDirectory Properties to the GPP. These properties provide the deployer with control over where Components are stored (cacheDirectory) and the directory from which Components are executed (workingDirectory).
  • Redesigning the IDE's Event Viewer to improve the ability to monitor event channels.
  • Adding functionality for capacity to be reserved for an entire host collocation on the SAD file. The reservation is a capacity floor for the Components in the host collocation, where the amount of capacity utilized by the aggregate set of Components is this reservation or actual, whichever is higher. This reservation is allocated against the target GPP running this Application, allowing the GPP to verify that the request can be satisfied, reducing the likelihood of over-subscription.
  • Waveform Metrics support: Application objects now contain a "metrics" function that returns GPP usage metrics for individual Components as well as overall for the Application. Metrics are viewable in the Properties view of the IDE.
  • Adding support for DCD files to have a startorder attribute, which functions similarly to the SAD file's startorder. On startup, "start" is automatically called on Devices and Services (when possible), and on shutdown, reverse-order "stop" is called. The IDE's tooling for DCD files has been updated to display and edit startorder.
  • Adding snapshot capability of network data and performing SDDS packet analysis on the captured data.
  • Ending support of Command-line interactive mode (-i) on Components, Services, and Devices. Terminal prompt interactions should be through the Python Sandbox.
  • Improving Python tooling to help manage REDHAWK systems. For example, these improvements include more intuitive event monitoring as well as new EventChannelManager, AllocationManager, and ConnectionManager helpers.
  • Adding functionality to allow Components that have a usesdevice dependency to now be launched on the same host (Device Manager/Node) as the Device satisfying the usesdevice requirement. This functionality is provided through an extension of the componentplacement hostcollocation.
  • Improving recovery of a REDHAWK Domain after a catastrophic failure. The Device Manager reboots all associated Devices/Services when it detects a reset Domain Manager after a catastrophic failure in the Domain Manager. This reboot only happens if (1) persistence is enabled and (2) the name service log, event service log, and persistence database are emptied.
  • Adding functionality within the code generators so they create C++, Java, or Python constants for enumerated values defined in the PRF.
  • Adding support for debugger options in the Python sandbox for C++ (Valgrind or gdb), Python (pdb), or Java (jdb) Components, Services, or Devices.
  • Adding scripts and configuration files that allow REDHAWK core services to run as system services. In addition to these services, integrators can define REDHAWK waveforms that are deployed during the system boot process.
  • Adding the Components tab to the Waveform editor in the IDE to allow editing of Component instantiation details, including logging configuration. This information will be used to resolve the LOGGING_CONFIG_URI parameter during Component deployment.
  • Improving the New Project Wizard to warn users if the project location selected already contains files that will become part of the project. Increase user awareness of files that may be moved, deleted, or packaged with a project.
  • Updating the IDE to use the latest available Eclipse tooling, Eclipse Neon. For more information about Eclipse Neon, refer to http://www.eclipse.org/neon/noteworthy.
  • Adding a Libraries chapter in the REDHAWK Manual to explain how to use shared libraries.
  • Documenting available affinity processing directives when deploying Devices, Services, and Components.
  • Extending the tool, rh_net_diag, to provide read/write/execute permissions checks on directories important for running a REDHAWK system.
  • Creating a new MSDD device released with bug fixes and enhancements and regenerated for REDHAWK 2.1.
  • Changing the default logging directory for omniEvents service to reside in /var/log/omniEvents.
  • Adding support for the REDHAWK Core Framework, IDE, assets, and new REDHAWK projects to now compile against and run on Java 8.
  • Improving nodeBooter so it does not deploy if --user or --group are set while --daemon is not, and if the command-line arguments to nodeBooter are malformed, deployment fails.
  • Changing FrontEnd Interfaces (FEI) property definitions:
  • For devices, the FRONTEND::tuner_allocation and FRONTEND::listener_allocation allocation properties are now writeonly instead of readwrite. Because the properties are now created as writeonly, they can no longer be queried. This change was made to prevent confusion with the actual state of the FrontEnd device, which is reported by the FRONTEND::tuner_status property. Existing Core Asset FEI devices have been updated with this change. New FrontEnd devices created with the IDE will automatically have this change.
  • Improving the user experience when locating and connecting to existing REDHAWK Domains.
  • Providing users with the option to copy Properties from other projects in their workspace or choose from pre-defined REDHAWK Properties when developing a Component or Device.
  • Displaying a REDHAWK editor when double-clicking on SCD XML files.
  • Showing IDL details when Ports are selected in the REDHAWK Explorer view.
  • Adding a notification that is now displayed after exporting projects to the Target SDR.
  • Providing better support for adding and editing Services in a DCD file.
  • Adding a Connection Callbacks section to the REDHAWK Manual.
  • Extending DeviceManager to call configure() on Services at the time they register. This enables users to implement custom Property handling if so desired.
  • Providing functionality to add custom headers to project files when generating code.
  • Removing some obsolete options from the Core Framework and BulkIO configure scripts.
  • Adding support for the state of the Connection Manager and Event Channel Manager to be restored when persistence is enabled.
  • Updating the IDE to use the latest available Eclipse tooling, Eclipse Oxygen.
  • Improving Python Sandbox tooling for new Domain features and resources. Specifically, extended DataSource to provide access to all the available SRI and the data timestamp.
  • Adding reservation schema graph in the documentation to enhance the text describing capacity allocation reservation for the GPP.
  • Adding functionality to the IDE so when users edit a property's name, the IDE automatically supplies an appropriate ID for the property based on REDHAWK's naming convention.
  • Providing validation of Property references in SAD and DCD files and flagging invalid Property references as errors.
  • Adding the ability to terminate services in the Sandbox via the hover pad or the delete key and making the terminate icon more distinct throughout the IDE.
  • Adding the stop timeout control to the Application. Options, like the stop timeout, can be configured when designing Waveforms in the IDE.
  • Adding functionality in the IDE to install the diagram layout when installing a SAD/DCD file (either by drag-drop or via its RPM .spec file). At runtime, the IDE checks for the diagram layout and if present, preserves the developer's layout.
  • Adding an option to enable the Domain Manager's logging level to be dynamically changed.
  • Adding a new packed bit data port type and data format for BulkIO:
    • Port API for component developers is fully implemented in C++, Python, and Java.
    • Plotting, monitoring, and interacting with data are supported in the IDE and Python Sandbox.
    • For C++ and Python, a new bitbuffer class provides high-level access to packed bit data.
    • In Python, all BulkIO ports now support a stream-based API that is consistent with C++.
  • Correcting issue in the Python Sandbox so now when the BulkIO queue is full, the Python Sandbox no longer locks up when trying to release stopped Components.
  • Providing Generate Waveform and Generate Node buttons in the IDE editors to initiate file generation. This ensures that Waveform and Node project spec files are created or modified only when requested by the user.
  • Adjusting the default tuner type for the Python Sandbox tuner allocation. It is now RX_DIGITIZER rather than DDC, matching the default tuner for a generated FEI Device.
  • Adding CF base class support and IDE tooling to allow users to create, implement, and test a FrontEnd scanner device.
  • Adding extensible hierarchical name structure support for loggers.
  • Correcting behavior for structures that have a default value that is mixed simple values and sequences; if the sequence is empty, it is not treated as nil.
  • Adding support for working with multi-out ports.
  • Adding Allocation Manager functionality in the IDE:
  • Viewing current allocations and allocation details for each allocation is supported.
  • Searching for devices used for an allocation and Device Managers referenced by an allocation is supported.
  • Allocations can be deallocated.
  • Adding context-sensitive property views in the REDHAWK IDE for the following:
    • Waveform and node properties are displayed when selecting the respective runtime editor. Runtime connection details are also displayed (read-only) when selecting a connection in a diagram editor.
    • SoftwareAssembly and DeviceConfiguration properties are displayed when selecting the respective design-time editor. Design-time connection properties are displayed when selecting a connection in a diagram editor.
  • Providing better context-specific icons throughout the IDE, and updating images and text in the REDHAWK Manual to reflect these new icons.
  • Providing new functionality for interacting with event channels and message event ports.
  • Adding Connection Manager functionality in the IDE:
  • Viewing current connections and connection details for each connection is supported.
  • Searching for the source or target of a connection is supported.
  • Connections can be disconnected.
  • Adding validation for mistyped property refs.
  • Adding support to custom IDL and FEI control ports so they now accept a connection id argument to specify the connection to use and throw exceptions if the port call is exercised and no connection exists or a connection is specified that does not exist.

Caution: This functionality was added to all FEI ports, including the RFInfo port. As a result, if an RFInfo port is configured as a uses port and there are no connections, an exception will occur and must be caught to prevent a disruption to the operation of the device or component. This behavior will be corrected in a future release.

  • Fixing an issue so when unhandled exceptions occur in Python and Java components, the components terminate rather than remain in a defunct state. If termination was not requested, the GPP now sends a message to the IDM channel when a component exits with a non-zero status.
  • Updating the FEI specification to require a device to only partially support a requested signal range rather than the whole signal to return a valid request. The validateRequest function in the frontendInterfaces support package checks that a partial overlap of the requested band succeeds rather than requiring full coverage of the requested range.
  • Updating the IDE on CentOS 7 to use the latest available Eclipse tooling, Eclipse Photon.
  • Correcting a bad XML file in the SDRROOT that caused loading of the SDRROOT to stop and report an error.
  • Updating rh.VITA49 to adhere to the approved version of V49.2 Standard (August 2017).
  • Adding an option for MessageSupplierPort to send messages to a specific connection.
  • Deprecating REDHAWK Enterprise Integration and removing all references to it within the documentation.
  • Providing the ability to generate configuration files for waveforms and nodes for use by the REDHAWK admin service.
  • Changing the redhawk user's home directory. When installing REDHAWK, the home directory is now /var/redhawk. When upgrading, the existing redhawk user home directory is updated to /var/redhawk if it is currently set to /home/redhawk.
  • Refactoring IO redirection to use epoll system call to handle redirection of component output to a single file and direct IO redirection when configured for one output file per component process.
  • Correcting behavior so when a component has a struct property with an element that is a complex sequence, the value can be overloaded correctly on a waveform.

Fixes

The following fixes were completed in REDHAWK 2.2.0:

Core Framework Fixes

  • When a property has the element action as <action/> rather than <action type=external/>, it is now correctly processed as external.

IDE Fixes

  • Ensured that kind and configurationkind elements in PRF XML files default to configure if not specified.
  • Corrected an issue that prevented struct sequence properties without any values from having their values adjusted.

Special Resolution

The following previously reported Known Issues have been closed in REDHAWK 2.2.0 with the following resolutions:

Core Framework Special Resolutions

  • Sandbox DataSource.push() slow - Won't Fix - In REDHAWK 2.1.3, the new StreamSource sandbox helper provides better performance than the legacy DataSource helper when pushing real sample data. DataSource.push() will not be updated in the 2.0.x series to address this performance concern.
  • Struct_from_props fails during allocate_capacity in python device - Won't Fix - This behavior is not an error.

IDE Special Resolutions

  • Uses FEI Device wizard overwrites existing allocation ID - Duplicate of FEI uses device wizard doesn't preserve existing XML values.
  • SAD editor properties tab allows setting external IDs on struct / struct seq members - Cannot Reproduce
Assets 18