Spline won't initialize on 0.5.2

[DaimonPl]

Ok so after upgrading to 0.5.2 and clearing database it's not possible for spline to initialize again :( here's what i'm getting:

spline_1    | Exception in thread "main" java.util.concurrent.ExecutionException: com.arangodb.ArangoDBException: Response: 404, Error: 1228 - database not found
spline_1    | 	at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
spline_1    | 	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
spline_1    | 	at za.co.absa.spline.persistence.ArangoDatabaseFacade$.workAroundArangoAsyncBug(ArangoDatabaseFacade.scala:90)
spline_1    | 	at za.co.absa.spline.persistence.ArangoDatabaseFacade.<init>(ArangoDatabaseFacade.scala:56)
spline_1    | 	at za.co.absa.spline.persistence.ArangoManager$.execute(ArangoManager.scala:81)
spline_1    | 	at za.co.absa.spline.persistence.ArangoManager$.initialize(ArangoManager.scala:49)
spline_1    | 	at za.co.absa.spline.admin.AdminCLI.exec(AdminCLI.scala:102)
spline_1    | 	at za.co.absa.spline.admin.AdminCLI$.delayedEndpoint$za$co$absa$spline$admin$AdminCLI$1(AdminCLI.scala:34)
spline_1    | 	at za.co.absa.spline.admin.AdminCLI$delayedInit$body.apply(AdminCLI.scala:30)
spline_1    | 	at scala.Function0.apply$mcV$sp(Function0.scala:39)
spline_1    | 	at scala.Function0.apply$mcV$sp$(Function0.scala:39)
spline_1    | 	at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:17)
spline_1    | 	at scala.App.$anonfun$main$1$adapted(App.scala:80)
spline_1    | 	at scala.collection.immutable.List.foreach(List.scala:392)
spline_1    | 	at scala.App.main(App.scala:80)
spline_1    | 	at scala.App.main$(App.scala:78)
spline_1    | 	at za.co.absa.spline.admin.AdminCLI$.main(AdminCLI.scala:30)
spline_1    | 	at za.co.absa.spline.admin.AdminCLI.main(AdminCLI.scala)
spline_1    | Caused by: com.arangodb.ArangoDBException: Response: 404, Error: 1228 - database not found
spline_1    | 	at com.arangodb.async.internal.velocystream.VstCommunicationAsync.lambda$execute$0(VstCommunicationAsync.java:66)
spline_1    | 	at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)
spline_1    | 	at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750)
spline_1    | 	at java.util.concurrent.CompletableFuture.uniWhenCompleteStage(CompletableFuture.java:795)
spline_1    | 	at java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:2153)
spline_1    | 	at com.arangodb.async.internal.velocystream.VstCommunicationAsync.execute(VstCommunicationAsync.java:59)
spline_1    | 	at com.arangodb.async.internal.velocystream.VstCommunicationAsync.execute(VstCommunicationAsync.java:44)
spline_1    | 	at com.arangodb.internal.velocystream.VstCommunication.execute(VstCommunication.java:124)
spline_1    | 	at com.arangodb.async.internal.ArangoExecutorAsync.lambda$execute$2(ArangoExecutorAsync.java:69)
spline_1    | 	at java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:966)
spline_1    | 	at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:940)
spline_1    | 	at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:456)
spline_1    | 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
spline_1    | 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
spline_1    | 	at java.lang.Thread.run(Thread.java:748)

[DaimonPl]

It happens with db-init -s when database does not exist in arangodb

[wajda]

Bug is a workaround for another bug. Nice.