An error occurs in the SubscriptionRegistry when sending a subscription event via Subscription::broadcast with Laravel Octane (Swoole) about lighthouse HOT 5 CLOSED

To fix this issue just add SubscriptionRegistry::class to octane config octane.warm.

Description of this configuration section.

    /*
    |--------------------------------------------------------------------------
    | Warm / Flush Bindings
    |--------------------------------------------------------------------------
    |
    | The bindings listed below will either be pre-warmed when a worker boots
    | or they will be flushed before every new request. Flushing a binding
    | will force the container to resolve that binding again when asked.
    |
    */

After adding this SubscriptionRegistry to the list of warms, the problem went away.

 'warm' => [
        ...Octane::defaultServicesToWarm(),
        Nuwave\Lighthouse\Subscriptions\SubscriptionRegistry::class,
    ],

It is worth updating the documentation and creating a section on how to configure lighthouse to work with laravel octane, or using internal methods to change the laravel octane configuration.

I'm still not entirely sure whether the decision is correct or whether there is some side effect from adding this class to the list of "warm".

from lighthouse.

I propose an addition to the docs in #2575, does this look right?

from lighthouse.

The error only appears when used together with laravel octane (swoole). There is no error when using php-fpm.

from lighthouse.

Add dump to constuctor of SubscriptionRegistry

dump('subscription registry new instance: ' . spl_object_hash($this));

Got 2 instances

subscription registry new instance: 00000000000054960000000000000000
subscription registry new instance: 00000000000007ea0000000000000000

First request i got

array:1 [ // $subscriptions dump
  0 => "scheduleUpdated"
]
spl_object_hash of SubscriptionRegistry: 00000000000007ea0000000000000000

Second and future requests

array:0 [] // $subscriptions dump
00000000000054960000000000000000

In the second and etc requests, subscription registration is not called...

from lighthouse.

Based on the explanations in this article, this appears to be a solution to the problem.

https://divinglaravel.com/laravel-octane-bootstrapping-the-application-and-handling-requests

Only singletons that are resolved during the application bootstrapping will persist between requests. Singletons that are resolved during request handling will be registered in the sandbox container, this container is destroyed after handling the request.
To persist singletons between requests, you can either resolve them in your service providers or add them to the warm array inside the Octane configuration file

But the explanations sound a little strange, here singleton is set in the service provider, which in theory should be a marker for laravel octane to keep it persistent...

from lighthouse.