Error Creating Region on Setup

[KM198912]

Steps to reproduce

1. Setup Standalone with Sqlite
   2.Create first region

Expected behaviour

Region should be created and "parked" with the estate default account

Actual behaviour

Mono Throws Error

Server configuration

Operating system: Debian 10 Buster

Web server: None

Database: SQLite

WhiteCore version: Latest Dev

Logs

Aug 08 09:44:10 - [EVENT MANAGER]: Delegate for TriggerIncomingLandDataFromStorage failed - continuing. System.ArgumentNullException: Value cannot be null.
Parameter name: source
at System.Linq.Enumerable.All[TSource] (System.Collections.Generic.IEnumerable1[T] source, System.Func2[T,TResult] predicate) [0x0000d] in :0
at WhiteCore.Modules.Land.ParcelManagementModule.EventManagerOnIncomingLandDataFromStorage (System.Collections.Generic.List1[T] data, OpenMetaverse.Vector2 parcelOffset) [0x00015] in <a5829a3b599b42e5a28b8b2f70295252>:0 at WhiteCore.Framework.SceneInfo.EventManager.TriggerIncomingLandDataFromStorage (System.Collections.Generic.List1[T] landData, OpenMetaverse.Vector2 parcelOffset) [0x00029] in :0 at System.Linq.Enumerable.All[TSource] (System.Collections.Generic.IEnumerable1[T] source, System.Func2[T,TResult] predicate) [0x0000d] in :0
at WhiteCore.Modules.Land.ParcelManagementModule.EventManagerOnIncomingLandDataFromStorage (System.Collections.Generic.List1[T] data, OpenMetaverse.Vector2 parcelOffset) [0x00015] in <a5829a3b599b42e5a28b8b2f70295252>:0 at WhiteCore.Framework.SceneInfo.EventManager.TriggerIncomingLandDataFromStorage (System.Collections.Generic.List1[T] landData, OpenMetaverse.Vector2 parcelOffset) [0x00029] in :0

[emperorstarfinder]

As I begin testing against Debian 10 (Buster), there are some noticeable changes in the Debian 10 operating system. This to some degree (to what extent I am not sure yet), could affect mono and in turn how virtual world architectures such as WhiteCoreSim works on Debian 10. As far as I am aware, none of the development teams have started testing against Debian 10 (i.e. OpenSim, WhiteCoreSim, ArribaSim, etc.).

I would recommend downgrading Debian back to Debian 9 (Stretch) and see if the issue persists on Debian 9. If the problem goes away at least then we can determine that Debian 10 compatibility will need to be reworked a bit in the architecture. However, this is more likely an issue with how the information is being obtained via storage.