(Linux) 40P01: deadlock detected during a GET request for NPM package

It looks like there was a possible regression of the following issue:

https://inedo.myjetbrains.com/youtrack/issue/PG-1050

Using ProGet 5.1.6 running in docker on an Amazon EC2 instance we are getting the following error when doing an NPM install with the registry set as our ProGet server:

An error occurred processing a GET request to http://proget.mydomain.com/npm/npm/redux-thunk/-/redux-thunk-2.2.0.tgz: 40P01: deadlock detected

Npgsql.PostgresException (0x80004005): 40P01: deadlock detected
at Npgsql.NpgsqlConnector+<DoReadMessageAsync>d__6.MoveNext () [0x002d7] in <4985dea8374f4819bebb7847d95ad483>:0

Product: ProGet
Version: 5.1.6

We have the same issue, running on ubuntu linux docker-ce

I'm afraid we can't reproduce this on a fresh install; next time it happens, please provide a full stack trace so we can try to at least make a guess as to what's causing this.

Npgsql.PostgresException (0x80004005): 40P01: deadlock detected
at Npgsql.NpgsqlConnector+<DoReadMessageAsync>d__6.MoveNext () [0x002d7] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlConnector+<ReadMessageWithPrependedAsync>d__5.MoveNext () [0x001c3] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlDataReader+<NextResultInternalAsync>d__1.MoveNext () [0x007da] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlDataReader+<NextResultAsync>d__48.MoveNext () [0x0014a] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlCommand+<ExecuteAsync>d__0.MoveNext () [0x003d8] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlCommand+<ExecuteDbDataReaderInternalAsync>d__4.MoveNext () [0x000f1] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlCommand+<ExecuteDbDataReaderAsync>d__99.MoveNext () [0x000a7] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.Postgres.WrappedPgCommand+<ExecuteDbDataReaderAsync>d__41.MoveNext () [0x001db] in <23bd4f2f6a9f4322a9b22056dc381001>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.Data.DatabaseContext+DbResult+<CreateAsync>d__10.MoveNext () [0x00082] in <11d9d064da4a4db995155317f7ec47e4>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.Data.DatabaseContext+<ExecuteInternalAsync>d__33.MoveNext () [0x001fc] in <11d9d064da4a4db995155317f7ec47e4>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.Data.DatabaseContext+<ExecuteNonQueryAsync>d__31.MoveNext () [0x0007b] in <11d9d064da4a4db995155317f7ec47e4>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.ProGet.WebApplication.FeedEndpoints.Npm.NpmPackageDownloadHandler+<RecordPackageDownloadAsync>d__1.MoveNext () [0x000cc] in <57c6a09763914e368f30bc7b778ebe6e>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.ProGet.WebApplication.FeedEndpoints.Npm.NpmPackageDownloadHandler+<TryProcessRequestAsync>d__0.MoveNext () [0x0030f] in <57c6a09763914e368f30bc7b778ebe6e>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.ProGet.WebApplication.FeedEndpoints.Npm.NpmHandler+<ProcessRequestAsync>d__2.MoveNext () [0x0029b] in <57c6a09763914e368f30bc7b778ebe6e>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler+FeedRequestHandler+<ProcessRequestAsync>d__8.MoveNext () [0x000bf] in <57c6a09763914e368f30bc7b778ebe6e>:0

Also happens on latest version:

Npgsql.PostgresException (0x80004005): 40P01: deadlock detected
at Npgsql.NpgsqlConnector+<DoReadMessageAsync>d__6.MoveNext () [0x002d7] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlConnector+<ReadMessageWithPrependedAsync>d__5.MoveNext () [0x001c3] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlDataReader+<NextResultInternalAsync>d__1.MoveNext () [0x007da] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlDataReader+<NextResultAsync>d__48.MoveNext () [0x0014a] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlCommand+<ExecuteAsync>d__0.MoveNext () [0x003d8] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlCommand+<ExecuteDbDataReaderInternalAsync>d__4.MoveNext () [0x000f1] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Npgsql.NpgsqlCommand+<ExecuteDbDataReaderAsync>d__99.MoveNext () [0x000a7] in <4985dea8374f4819bebb7847d95ad483>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.Postgres.WrappedPgCommand+<ExecuteDbDataReaderAsync>d__41.MoveNext () [0x001db] in <23bd4f2f6a9f4322a9b22056dc381001>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.Data.DatabaseContext+DbResult+<CreateAsync>d__10.MoveNext () [0x00082] in <11d9d064da4a4db995155317f7ec47e4>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.Data.DatabaseContext+<ExecuteInternalAsync>d__33.MoveNext () [0x001fc] in <11d9d064da4a4db995155317f7ec47e4>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.Data.DatabaseContext+<ExecuteNonQueryAsync>d__31.MoveNext () [0x0007b] in <11d9d064da4a4db995155317f7ec47e4>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.ProGet.WebApplication.FeedEndpoints.Npm.NpmPackageDownloadHandler+<RecordPackageDownloadAsync>d__1.MoveNext () [0x000cc] in <282454a3c2a74b79b8c2f5f3bb705a10>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.ProGet.WebApplication.FeedEndpoints.Npm.NpmPackageDownloadHandler+<TryProcessRequestAsync>d__0.MoveNext () [0x0034a] in <282454a3c2a74b79b8c2f5f3bb705a10>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.ProGet.WebApplication.FeedEndpoints.Npm.NpmHandler+<ProcessRequestAsync>d__2.MoveNext () [0x0029b] in <282454a3c2a74b79b8c2f5f3bb705a10>:0
--- End of stack trace from previous location where exception was thrown ---
at Inedo.ProGet.WebApplication.FeedEndpoints.FeedEndpointHandler+FeedRequestHandler+<ProcessRequestAsync>d__8.MoveNext () [0x000bf] in <282454a3c2a74b79b8c2f5f3bb705a10>:0

We believe we have fixed this as PG-1377, which will be included in ProGet 5.1.11. Thank you!