I saw the notification about 5.28 being released the other day so I updated it in my project. Code that had been working fine suddenly starting throwing random exceptions. It's still in development, so the data set being returned is VERY small (less than 10 nodes). It seems to have gone away after I downgraded back to 5.27.
This is the exception I got was:
fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1]
An unhandled exception has occurred while executing the request.
System.InvalidOperationException: The LinkedList node already belongs to a LinkedList.
at System.Collections.Generic.LinkedList`1.ValidateNewNode(LinkedListNode`1 node)
at System.Collections.Generic.LinkedList`1.AddFirst(LinkedListNode`1 node)
at Neo4j.Driver.Internal.HomeDbCaching.HomeDbCache.TryGetCached(HomeDbCacheKey key, String& value)
at Neo4j.Driver.Internal.Routing.LoadBalancer.AcquireConnectionAsync(AccessMode mode, String database, SessionConfig sessionConfig, Bookmarks bookmarks, Boolean forceAuth)
at Neo4j.Driver.Internal.Routing.LoadBalancer.AcquireAsync(AccessMode mode, String database, SessionConfig sessionConfig, Bookmarks bookmarks, Boolean forceAuth)
at Neo4j.Driver.Internal.AsyncSession.AcquireConnectionAndDbNameAsync(AccessMode mode, Boolean forceAuth)
at Neo4j.Driver.Internal.AsyncSession.<>c__DisplayClass40_0.<<RunAsync>b__0>d.MoveNext()
Not entirely sure if it is related to this, but since this morning, when I try to connect to my instance through Aura to query the DB, this error is displayed:
Failed to check Neo4j version.
Application supports Neo4j versions >= 4.4.0. Connecting to an unsupported version may lead to incompatibilities, reduced functionality, unexpected bugs, and other issues. Error: Executing procedure is not allowed for user '210d9cce-9ca8-44df-8c36-65e570195643' with roles [PUBLIC] overridden by READ.;
Hi Team, after jun 9 our team is unable to find the neo4j database in the instance and this seems an oerall issue even , when i created another instance i also got the same error
The error you have highlighted is not related to the bug in the .Net driver that was fixed in 5.28.1.
The relevant teams are aware of the issue you are seeing and it is being actively investigated. Apparently if you switch to the classic console experience you should not get it, which might work as a temporary workaround until everything is resolved.
Thanks Andy! Sorry for publishing in an unrelated old bug... a toast telling me to refresh the page appeared just now. After doing so, it connected to the database with no problem :)))
