You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But I'm having issues running the docker image; on particular, the event_machine_projection service keeps failing to start. The logs show the following:
event_machine_projection_1 | Fatal error: Uncaught Error: Call to a member function run() on null in /app/vendor/proophsoftware/event-machine/src/Projecting/ProjectionRunner.php:93
event_machine_projection_1 | Stack trace:
event_machine_projection_1 | #0 /app/vendor/proophsoftware/event-machine/src/EventMachine.php(617): Prooph\EventMachine\Projecting\ProjectionRunner->run(false, NULL)
event_machine_projection_1 | #1 /app/bin/event_machine_projection.php(21): Prooph\EventMachine\EventMachine->runProjections(false)
event_machine_projection_1 | #2 {main}
event_machine_projection_1 | thrown in /app/vendor/proophsoftware/event-machine/src/Projecting/ProjectionRunner.php on line 93
I've checked the code, and seems like EventMachine.php is trying to create a projection runner, but the projection manager in the service container is null.
Just add a first aggregate and activate an AggregateProjection like described in the tutorial. The projection container should start to work then. Anyway, a better error handling would be a good idea here. Thx for reporting
yeah, I realized that we need a better error reporting here for the devs who want to start with a fully working system right away ;) I keep the issue open as a reminder.
@codeliner was trying to create prototype suggested here: proophsoftware/es-emergency-call#8
But I'm having issues running the docker image; on particular, the event_machine_projection service keeps failing to start. The logs show the following:
I've checked the code, and seems like EventMachine.php is trying to create a projection runner, but the projection manager in the service container is null.
Any ideas why this could be happening? Have you heard this issue before?
Thanks
The text was updated successfully, but these errors were encountered: