Peter Tiedemann

@jjcollinge After messing around a bit with ACME, we found that in fact there are more critical problems than rate limiting. We cannot use the HTTP challenge as the challenge...

@jjcollinge As you know, we remain interested in this. In fact, if it gets some traction i think we will use it to replace our usage of APIM in production....

Just wanted to add a "me too" here. Hit the exact same thing.

With 5.0.17, I get "LiteDB ENSURE: page type must be collection page" from our test suite. With 5.0.19 Maximum number of transactions reached :( We have been stuck on v4...

Just want to confirm that this is a *major* pain for library authors. Installing analyzers into hundreds of projects and then having to set them all to Error severity just...

@sharwell Can you enlighten us on how vs-threading resolves this (it seems to be focused on applications, and i am doing libraries that can be used in any context)?

I am seeing the same with 5.0.20 (just FYI)

I have a similar problem when upgrading (using 5.0.20): ``` LiteDB.LiteException: Cannot insert duplicate key in unique index '_id'. The duplicate value is '"59803E0EF693557459A7BCA047C118F998256C06E4BF7A1C4880012FF97E47B2"'. at LiteDB.Engine.IndexService.AddNode(CollectionIndex index, BsonValue key, PageAddress...

We are having a similar problem, just with even more artifacts.