Error getting npm package versions: The JSON value could not be converted to System.DateTime ...

jeff.peirson_4344

I'm getting this error for my private npm feed:

JsonException: The JSON value could not be converted to System.DateTime. Path: $.time.unpublished | LineNumber: 0 | BytePositionInLine: 2874.

It's only happening for a specific package, and only for specific versions of that package. I also can't use the web UI to list package versions via /feeds/myfeed/mypackage/versions, since it also shows this error. I also get the same error when I try to download the package directly using curl https://host/npm/myfeed/mypackage/-/mypackage-version.tgz.

I don't know what the JSON path $.time.unpublished refers to, I'm guessing something internal to ProGet?

Any ideas?

rhessinger

Hi @jeff-peirson_4344,

This is a known issue that we will have fixed in tomorrow's release of ProGet, 2024.23. We are tracking the fix in ticket PG-2860.

Thanks,
Rich

jeff.peirson_4344

I've upgraded to ProGet 2024.24, and I still get an error, although a different one now:

JSON deserialization for type 'Inedo.ProGet.Feeds.Npm.NpmPackageResponse' was missing required properties, including the following: versions

Is there any kind of re-index or repair or something I'm supposed to do?

jeff.peirson_4344

and I can log this in the upack github repo instead, but the upack command line tool now fails to push packages against ProGet v2024.24:

The JSON value could not be converted to Inedo.ProGet.Feeds.Universal.JsonModels.UPackManifest. Path: $.createdDate | LineNumber: 14 | BytePositionInLine: 39.

For now, since the regression to upack push is a showstopper for us, I've rolled back to 2024.22 but then of course I get the originally posted JSON error.

rhessinger

Hi @jeff-peirson_4344,

Can you please share the npm package you are having issues with?

Thanks,
Rich

rhessinger

Hi @jeff-peirson_4344 ,

For the issue with upack, can you please submit a new forums post for that? So far this post has been about npm and I don't want this issue to get lost.

Thanks,
Rich

jeff.peirson_4344

@rhessinger There are only two versions of the problematic package that I'm able to download from ProGet. It's a private package, not one pulled via a connector. This is the actual package.json (some string replacements made) for one:

{
  "name": "volante",
  "description": "SNIP",
  "version": "6.9.0",
  "author": "USER <USER>",
  "url": "https://github.com/USER/volante",
  "repository": "USER/volante.git",
  "main": "./src",
  "keywords": [
    "hub",
    "spoke",
    "framework",
    "wheel",
    "configuration",
    "events"
  ],
  "devDependencies": {
    "volante-console": "^3.3.1"
  }
}

And for one of the versions I can't get to in ProGet, I'm able to see in the NpmPackageVersions db table a similiar looking entry under PackageJson_Bytes:

{
  "description": "SNIP",
  "author": "USER <USER>",
  "url": "https://github.com/USER/volante",
  "repository": "USER/volante.git",
  "main": "./src",
  "keywords": ["hub", "spoke", "framework", "wheel", "configuration", "events"],
  "devDependencies": {
    "volante-console": "^3.3.1"
  },
  "readme": "SNIP"
}

Also, can you confirm the actual latest ProGet docker image version? Through the dashboard, it describes an upgrade to 2024.23. I use docker compose to pull the latest 24.0 image, and the latest currently points to 2024.24.

rhessinger

Hi @jeff-peirson_4344,

Thanks for sending these over. Let me do some investigation on these and I'll get back to you soon.

As for the latest version of the image, we are now on 2024.24. We ran into a replication issue with universal packages in 2024.23 and had to release 2024.24 on Monday.

Thanks,
Rich

rhessinger

Hi @jeff-peirson_4344,

I have been able to recreate the issue and created a ticket, PG-2870, to track the fix. We expect this to release in ProGet 2024.25 on January 24, 2025. This looks to be related to the package name existing on npmjs.org with all versions being unlisted. If you need a fix sooner, we can provide a pre-release version of ProGet 2024.25 that includes the fix.

Thanks,
Rich