Skip to main content

Diagnostics

Problems with library management are displayed as diagnostic notifications. The notifications are located in two places. During the resolve and the restore processes, notifications are displayed to indicate the progress and any problems which may have occurred. During a compile process, the Libraries.lock.json lockfile is checked and every detected problem is reported. This test step is called precompile. Changes to the affected files are monitored and the notifications are updated accordingly. These notifications are divided into three levels: errors, warnings, and notices.

Errors

An error prevents a successful compile. The following errors are reported when the Libraries.lock.json file is processed.

  • The Libraries.lock.json file is missing.

  • The Libraries.lock.json file is corrupt and cannot be read.

  • A library is not located at the specified relative path. 

  • An input/output error occurs when accessing a library. 

  • The project information is incorrect. 

  • A compiled library cannot be read. 

  • A SHA384 checksum does not match the contents of the file.

Warnings

A warning indicates a suspicious condition. However, a compile is not prevented.

  • The sources section of the Libraries.lock.json file no longer matches the actual sources.

Notices

A notice suggests a possible improvement. A compile is not prevented.

  • A newer, matching version is available for a library. Resolving it again would resolve the library to the new version.