Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you're interested in analyzing Go codebases in LGTM, talk to your support contact for details.

ProductDetails of changeReference
LGTM Enterprise

When exporting SARIF from either the command line or from LGTM the process could fail with an exception if one of the results to be exported included a path with a node without a location. This has been fixed for all supported SARIF export versions.J8101 - G34287
An issue where a Windows script, install-machine.bat, failed when run inside a folder containing a space, has been fixed.JL3552 - G34178
An issue where the LGTM web application could fill up your disk by crashing repeatedly has been fixed.JL3566 - G34019
In 1.22.0, LGTM services running on Ubuntu Bionic weren't always shut down correctly. This is fixed by upgrading to 1.22.1.JL3531 - G33862
An issue with file permissions when running the config generator as another user using sudo -u has been resolved.JL3563 - G33990

All components of the LGTM analysis system now correctly interpret LGTM_RAM where the value includes a unit (for example, LGTM_RAM = 8G). Previously, some components ignored the value when it included units, and reverted to the default value of LGTM_RAM. This was particularly noticeable in query evaluation.

JL3358 - G34310
The C# autobuilder now attempts to build all project or solution files it finds the same (shortest) depth from the root directory. Previously, if more than one file was detected it did not attempt to build any of them.GQ1944
The "attribution" and "issue-tracker-sync" jobs now use the amount of memory specified by LGTM_RAM.JL3571 - G34421
An issue where restarting the database connection prevented jobs from being processed has been fixed.G34352
QLWhen exporting SARIF from either the command line or from LGTM the process could fail with an exception if one of the results to be exported included a path with a node without a location. This has been fixed for all supported SARIF export versions.J8101 - G34287
Some builds using .NET components on macOS previously failed with the error Failed to resolve full path of the current executable. These errors have been resolved.J6830 - G34158
Some builds using the GCC and Clang command line option -fconstexpr-depth would fail to trace. This has been fixed.JC442 - G34347
Code using the Microsoft __try/__except language extensions with the clang-cl compiler could previously cause the extractor to enter an infinite loop. This has been fixed.G34244
The Export to GraphML command in the QL for Eclipse graph result viewer silently failed for certain graph/path-problem queries. This has now been fixed.JQ985 - G34420
The treatment of nested lambdas with captured variables by the data flow library has been corrected.GQ1943