Roman Zipp
Roman Zipp
I haven't worked with Lumen yet. Feel free to send a PR regarding this
As I've said before, feel free to create a PR for Lumen support
Actually I have never seen a job being emitted as failed **and** processed. Did you implement the `failed` method in your job class? A small code excerpt would be helpful...
Laravel does not include include any functionality like this out of the box. I've already implemented a similar functionality by storing the process ID in the queue data. ```php public...
I'm currently using this package in a production system with distributed queue workers and did observe any issues like this. Although the fix might work, it's looks like a workaround...
Could you try adding the following method to the job: ```php public function failed(Throwable $e) { parent::failed($e); throw $e; } ```
Thanks! Could you rebase your contributions to remove the merge commit?
Nice, Thanks! Looks like there are some merge conflicts. Could you squash those commits? I'd only like to enable rebase merges
You've posted an exception stacktrace in your first edit of this issue `Symfony\Component\ErrorHandler\Error\FatalError: Declaration of App\Http\Controllers\EventSubController::handleNotification` I don't see this in the current version, is it still correct or was...
Honestly I haven't ever used Octane and I'm not planning on doing so. Could you try calling the [`clearStructs()`](https://github.com/romanzipp/Laravel-SEO/blob/master/src/Services/SeoService.php#L159) in your AppServiceProvider or somewhere else before adding additional tags?