ViperHttpServer did not call start() on ViperCoreServer and instead directly called start(active_jobs) on VerificationServer. This resulted in an uninitialized cache and thus in an exception whenever ViperServer tries to store a verification result in the cache after a verification.
This PR fixes #111 by making ViperHttpServer call ViperCoreServer.start() and slightly changing the inheritance such that VerificationServerHttp can still configure the server startup (i.e. to bind the HTTP server).
ViperHttpServer
did not callstart()
onViperCoreServer
and instead directly calledstart(active_jobs)
onVerificationServer
. This resulted in an uninitialized cache and thus in an exception whenever ViperServer tries to store a verification result in the cache after a verification. This PR fixes #111 by makingViperHttpServer
callViperCoreServer.start()
and slightly changing the inheritance such thatVerificationServerHttp
can still configure the server startup (i.e. to bind the HTTP server).