Error -> Type requires a JSON object to deserialize correctly

[max-ieremenko]

Error -> Type requires a JSON object to deserialize correctly

[max-ieremenko]

It looks like an index.json file of one of the packages is corrupted.

For example, the expected content should be

{
  "License": {...},
  "UsedBy": [...],
  "Licenses": [...]
}

but for some reason (e.g. manual editing) according to the exception details the content looks something like this

[
{
  "License": {...},
  "UsedBy": [...],
  "Licenses": [...]
}
]

To resolve the issue, the contents of index.json should be fixed manually, or alternatively, remove the package folder with index.json from the repository and run the update again.

Especially for this ticket I release version 3.4.1, where the exception should contain the full package name with an invalid index.json

Failed to deserialize contents of index.json of package npmjs.com/bootstrap/4.6.1. System.InvalidOperationException: Failed to deserialize contents of index.json of package npmjs.com/bootstrap/4.6.1. ---> Newtonsoft.Json.JsonSerializationException: Cannot deserialize the current JSON array (e.g. [1,2,3]) into type 'ThirdPartyLibraries.Repository.Template.LibraryIndexJson' because the type requires a JSON object (e.g. {"name":"value"}) to deserialize correctly.

[stunney]

This error occurs after a large output of
Valid reference **** from *****
and then a few
The nuget.org ******* VVVV has been completely removed from the repository

[stunney]

Turns out it was:

Failed to deserialize contents of index.json of package npmjs.com/babel-jest/22.4.4/node_modules/spdx-exceptions.

the index.json files I see are just a strict array of package names, no other meta is mentioned in them for this specific library

example

[
  "389-exception",
  "Autoconf-exception-2.0",
  "Autoconf-exception-3.0",
  "Bison-exception-2.2",
  "Bootloader-exception",
  "Classpath-exception-2.0",
  "CLISP-exception-2.0",
  "DigiRule-FOSS-exception",
  "eCos-exception-2.0",
  "Fawkes-Runtime-exception",
  "FLTK-exception",
  "Font-exception-2.0",
  "freertos-exception-2.0",
  "GCC-exception-2.0",
  "GCC-exception-3.1",
  "gnu-javamail-exception",
  "GPL-3.0-linking-exception",
  "GPL-3.0-linking-source-exception",
  "GPL-CC-1.0",
  "i2p-gpl-java-exception",
  "Libtool-exception",
  "Linux-syscall-note",
  "LLVM-exception",
  "LZMA-exception",
  "mif-exception",
  "Nokia-Qt-exception-1.1",
  "OCaml-LGPL-linking-exception",
  "OCCT-exception-1.0",
  "OpenJDK-assembly-exception-1.0",
  "openvpn-openssl-exception",
  "PS-or-PDF-font-exception-20170817",
  "Qt-GPL-exception-1.0",
  "Qt-LGPL-exception-1.1",
  "Qwt-exception-1.0",
  "Swift-exception",
  "u-boot-exception-2.0",
  "Universal-FOSS-exception-1.0",
  "WxWindows-exception-3.1"
]

[max-ieremenko]

npmjs.com/babel-jest/22.4.4/node_modules/spdx-exceptions

node_modules in the path looks strange. ThirdPartyLibraries can only create package folders in their repository, such as npmjs.com/babel-jest/22.4.4.

Where did the sub-folder node_modules/spdx-exceptions come from?

[stunney]

npm install && npm dedupe command is a likely culprit

[max-ieremenko]

I recommend having 2 separate folders for the source code and the ThirdPartyLibraries repository like in this repo:

/path/sources
-- ...
-- babel-jest # structure under the control of npm
---- 22.4.4
------ index.json # npm index file
------ node_modules
-------- ...
			 
/path/third-party-libraries # structure under the control of ThirdPartyLibraries 
-- configuration
-- licenses
-- packages
---- npmjs.com
------ babel-jest
-------- 22.4.4
---------- index.json # tpl index file

ThirdPartyLibraries expects the repository folder to be under its complete control.