Resolved Issues

The following issues are resolved in this release.

Issue

Resolution Notes

SCA-13558

When an inventory item is associated with 4000 or more files, SQL Server no longer throws an exception when users attempt to add and view the files for the item.

SCA-40410

Global component searches through the Code Insight UI and REST API are now fetching information about new and updated custom components. Previously, users had to wait until an Electronic Update to fetch this information. See Immediate Indexing of Custom Components in Data Library.

SCA-41692

The Component Lookup search by URL was previously producing different results when the user tried various combinations of upper and lower case in the same search string. The URL search is now case-insensitive. No matter what case is provided in the search string, the results include all components containing the string.

SCA-42991

The core.update.log file no longer erroneously includes additional information from core.log.

SCA-43141

All audit records for a deleted inventory item are now deleted from the Code Insight database.

SCA-43238

The maximum length for project names is now 256 characters. Previously, SQL Server would not accept more than 60 characters for the name. Both SQL Server and MySQL now support this new maximum.

SCA-43145

Previously, associating or disassociating a file for an inventory item was creating an audit record. (No audit record should be created for this event.)

SCA-43256

Previously in Go modules, projects were not detected as top-level inventory, resulting in their first-level dependencies not being reported. As a fix, the scan now creates an unpublished ‘Work in Progress” inventory item for any project in these modules, enabling its first-level dependencies to be reported.

SCA-43346

When the PyPI analyzer searched dependencies in the requirements.txt file, those dependencies that contained an inline comment (along with a version) were reported without versions in the scan results. This issue is now fixed so that versions are reported.

SCA-44158

Previously during a Project Copy, symbolic links in a codebase caused issues, such as recursive behavior that consumed the hard drive. The Project Copy process now ignores symbolic links.