search

IzyPro / WatchDog

WatchDog is a Realtime Message, Event, HTTP (Request & Response) and Exception logger and viewer for ASP.Net Core Web Apps and APIs. It allows developers log and view messages, events, http requests made to their web application and also exception caught during runtime in their web applications, all in Realtime.
MIT License
783 stars 117 forks source link

Recursive read lock acquisitions not allowed in this mode. #137

Closed VictorioBerra closed 7 months ago

VictorioBerra commented 9 months ago

Description

   at System.Threading.ReaderWriterLockSlim.TryEnterReadLockCore(TimeoutTracker timeout)
   at System.Threading.ReaderWriterLockSlim.TryEnterReadLock(TimeSpan timeout)
   at LiteDB.Engine.LockService.EnterTransaction()
   at LiteDB.Engine.TransactionMonitor.GetTransaction(Boolean create, Boolean queryOnly, Boolean& isNew)
   at LiteDB.Engine.LiteEngine.AutoTransaction[T](Func`2 fn)
   at LiteDB.Engine.LiteEngine.Insert(String collection, IEnumerable`1 docs, BsonAutoId autoId)
   at LiteDB.LiteCollection`1.Insert(T entity)
   at WatchDog.src.Helpers.LiteDBHelper.InsertWatchLog(WatchLog log)
   at WatchDog.src.Managers.DynamicDBManager.InsertWatchLog(WatchLog log)
   at WatchDog.src.WatchDog.InvokeAsync(HttpContext context)
   at Serilog.AspNetCore.RequestLoggingMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
   at WatchDog.src.WatchDogExceptionLogger.InvokeAsync(HttpContext context)

To Reproduce I started a new .NET 8 project and added WatchDog and I get these errors everywhere.

Expected behavior No LiteDB errors?

Screenshots If applicable, add screenshots to help explain your problem.

Details (please complete the following information):

Additional context Add any other context about the problem here.

github-actions[bot] commented 8 months ago

This issue is stale because it has been open for 30 days with no activity.

VictorioBerra commented 8 months ago

Bump.

github-actions[bot] commented 7 months ago

This issue is stale because it has been open for 30 days with no activity.

VictorioBerra commented 7 months ago

Bump

Khelechy commented 7 months ago

Hi @VictorioBerra , This is currently an open issue with the LiteDB dependency and we are following up with it. However, a potential workaround has been released with the new version (v1.4.11). Do let us know if the issue still persists.