Data Library and Electronic Updates
The following are known issues related to the Code Insight data library and the Electronic Update, which keeps Code Insight systems up to date with the latest data-library information.
SCA-43625: Server shutdowns when simultaneous custom-component indexing and searching occur
As of 2022 R4, Code Insight starts the background process of indexing a custom component in the Code Insight data library as soon as the component is created or updated. Even though indexing takes only a half minute or less per component, a server shutdown can occur if you attempt to perform a component search against the data library while multiple components are being simultaneously indexed.
Workaround: Wait until the indexing process is finished for all components before you use the Global Component & License Lookup feature or the Component Search REST API to search components in the data library.
SCA-43568: Sequential creation of multiple custom components with similar names resulting in incorrect component search counts and pagination
As of 2022 R4, Code Insight starts the background process of indexing a custom component in the Code Insight data library as soon as the component is created or updated. If multiple custom components with similar names are sequentially created/updated and indexed in the background, the search results for these components might show incorrect search counts and pagination.
Workaround: After the custom-component updates are indexed, run an Electronic Update to fix the indexes.
SCA-40194: Duplicate inventory issues for MIT-related components
The Code Insight MIT data-library update does not fix inventory items with names that include multiple licenses separated by commas (instead of ORs), as shown in this example:
jquery (MIT, MIT License)
On a rescan, duplicates can be created for such inventory items:
jquery (MIT, MIT License)
jquery (MIT)
Two possible workarounds are available.
Workaround 1: Before starting the rescan, select the option On data import or rescan, delete inventory with no associated files on the Manage Project > Edit Project > General tab accessed from the project’s Summary tab. This option deletes the original inventory item as long as it is system-generated.
Workaround 2: Manually delete the original inventory item in the Analysis Workbench by right clicking the item and selecting Delete inventory. You must repeat this step for each such inventory item.
SCA-31562: Component license remapping issues from MIT-Style to MIT for inventories
Remapping Issues have occurred once the latest Electronic Update (available from Code Insight 2021 R4 and later) has been run. These issues involve the remapping of licenses from MIT-Style to MIT for inventories. The following is an example.
Before running the Electronic Update available at the release of Code Insight 2021 R4 and later:
The following inventory mapping existed in inventory:
concurrent-ruby 1.1.9 (MIT License)
This component was mapped with License id 744.
After running the Electronic Update available at the release of Code Insight 2021 R4 and later:
The inventory item was remapped as follows:
concurrent-ruby 1.1.9 (MIT-Style)
The license short name had been changed (in this example, from MIT License to MIT-Style). However, the mapped license ID remained 744.
Ideally this component should be remapped to MIT, which is License id 7.
Workaround: Follow these steps:
1. | Click Inventory on the main Code Insight window to open the Inventory view, showing inventory across projects. |
2. | Switch from My Projects to All Projects. |
3. | Search for the inventories containing the string (MIT-Style). |
4. | Locate the Possible Licenses value for a given inventory. If this value is MIT (Id 7) and the term MIT-Style is in the inventory name or is the value of Selected License, then an incorrect license remapping has been performed for this specific inventory item. One incorrect license remapping is a possible indicator of other incorrect remappings. |
5. | Run the Code Insight cleanup SQL script to correct the license mappings for the inventory in your Code Insight system. (To obtain this script, download the codeinsight-MITCleanupPackage archive from the Product and Licensing Center, and extract the script and its instructions.) |