Queued jobs trigger worker lambda, but jobs are not processed about laravel-bridge HOT 5 CLOSED

Hi, could you post the content of worker.php?

from laravel-bridge.

Hi, could you post the content of worker.php?

Yes, of course. Here you go:

<?php declare(strict_types=1);

use Bref\LaravelBridge\Queue\LaravelSqsHandler;
use Illuminate\Foundation\Application;

require __DIR__ . '/vendor/autoload.php';
/** @var Application $app */
$app = require __DIR__ . '/bootstrap/app.php';

/**
 * For Lumen, use:
 * $app->make(Laravel\Lumen\Console\Kernel::class);
 * $app->boot();
 */
$kernel = $app->make(Illuminate\Contracts\Console\Kernel::class);
$kernel->bootstrap();

Log::info('WORKER STARTED!');

return $app->makeWith(LaravelSqsHandler::class, [
    'connection' => 'sqs', // this is the Laravel Queue connection
    'queue' => getenv('SQS_QUEUE'),
]);

Edit: Versions I am using

• bref/bref: 1.4.1
• bref/laravel-bridge: 1.1.3
• laravel/framework: 8.77.0

from laravel-bridge.

OH I found it. It confused me so much 😅

In your CDK config you are adding the console layer, but it doesn't make sense here. The console layer is specifically for running CLI scripts or binaries.

Here you are using PHP code (files & classes) to handle the event, so you can remove it and give it another try.

I guess that nothing was displayed in the output because with the console layer your worker.php file was executed "as-is", and the only thing it does is boot Laravel and return a service, and then it would exit (with the console layer).

from laravel-bridge.

Oh man, that was really the problem! It only cost me like 1 week of debugging 😄 Thank you so much for your quick help!

from laravel-bridge.

Oh yeah I hate when that happens ^^

No problem!

from laravel-bridge.