Replies: 8 comments 20 replies
-
|
Can you make sure you are using the latest versions of Bref and the Laravel bridge? This should be the first version btw, not the second. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using: I've just tested again with this code: Then I've fetched the logs with |
Beta Was this translation helpful? Give feedback.
-
|
Does this information help? |
Beta Was this translation helpful? Give feedback.
-
|
All the problems above were solved after downgrading aws-sdk-php from |
Beta Was this translation helpful? Give feedback.
-
|
We are using PHP 7.3 and can't migrate to PHP 8 soon. The compatible versions for PHP 7.3 are As per the documentation, in serverless.yml, we have to provide below is my serverless.yml file provider: package: functions: constructs: plugins: What could be the issue? |
Beta Was this translation helpful? Give feedback.
-
|
@harshal-ringe you are using an older version of this package, you should follow the old versions of the documentation. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @mnapoli for your reply, I have migrated the project to the latest PHP and Bref versions and now the error has gone but the exceptions inside the workers are not getting logged on Cloudwatch. If there is any error worker, the job directly fails without logging the actual exception/error in Cloudwatch. It only logs |
Beta Was this translation helpful? Give feedback.
-
|
@dnl4 I am seeing the same issue migration from bref v1. to v2. How did downgrading the PHP SDK help here, the page you linked returns a 404. Thanks! Bref: 2.1.3 |
Beta Was this translation helpful? Give feedback.
-
|
It would appear that the laravel-bridge |
Beta Was this translation helpful? Give feedback.
-
|
@steverhoades thanks for investigating, any idea why that file is not loaded? That is weird, Composer should automatically load it 🤔 Could you try running |
Beta Was this translation helpful? Give feedback.
-
|
@mnapoli I'll look into this again ASAP. I will say that reverting back to my v1 configuration works (explicit handler files). |
Beta Was this translation helpful? Give feedback.
-
|
Revisiting this a year later and i'll be damned if i'm seeing the same error when trying to upgrade laravel bridge. Was there any further insight on how to debug this issue? |
Beta Was this translation helpful? Give feedback.
-
|
Disregard, I see the issue when upgrading to v2. The QueueHandler.php file should be used instead of the v1 LaravelSqsHandler. I'm unblocked. |
Beta Was this translation helpful? Give feedback.
-
|
I'm hitting this issue at the moment and it has completely stumped me. What's really strange is that I have SQS queues working fine on another project with the same setup, and very similar versions of laravel/bref and laravel-bridge. I've compared these projects, as far as doing diffs on files like serverless-state.json, and the config of the queues really appears the same. I can successfully put a job on to the queue, but then when it gets processed I see in the Cloudwatch logs:
I'm pretty sure bref-init.php is running, as the logs include before the error
The rest of the application in general is working fantastically in production. I'm doing this work on a staging copy, but the setup is pretty much identical (and the staging application works fine too, it's just the queue handling). I can't think what else to check/upgrade/compare. |
Beta Was this translation helpful? Give feedback.
-
|
Howdy Matthieu, I really appreciate your thoughts here!
That throws an error, whilst I can target other classes within Laravel Bridge without error.. (but I admit I'm not sure if it's supposed to work or not)
The only 'unusual' thing about this project I guess is that it's one I've worked on over quite some time, maybe a year and a half, and updated along the way. There must be some little override or config somewhere I've missed. Going to test this process on my other project next. |
Beta Was this translation helpful? Give feedback.
-
|
Just updated to serverless 3.36.0, no change. Also just tried a SQS queue on a new project, worked as expected! |
Beta Was this translation helpful? Give feedback.
-
|
Oh, that's good at least. Here is what the Laravel-Bref bridge is doing: $this->app->when(QueueHandler::class)
->needs('$connection')
->giveConfig('queue.default');Maybe try adding that into your own ServiceProvider? That's not ideal, but maybe it will be enough? Maybe the project is old enough that some automatic registration (service provider? service class?) that has been added in Laravel since isn't happening. Also I would indeed expect this to work in a controller, so there's definitely something wrong: $container = app();
$handler = $container->get( 'Bref\LaravelBridge\Queue\QueueHandler' ); |
Beta Was this translation helpful? Give feedback.
-
|
Well, I've got it working. And it's probably the most frustrating mistake I've made in the last year. It's almost comical. What made it hard to pick up was that the EntryNotFoundException exception is very misleading, it's more of a fall back exception, than something that's true. What I did was edit /laravel/framework/src/Illuminate/Container/Container.php, and adjust the When I did that, I got:
Spot the issue? In my severless.yml file, I accidentally set QUEUE_CONNECTION to 'ses', and not 'sqs'. So ONE letter mistake, has cost me a day or so's worth of debugging. Thanks again for the suggestions for debugging, I owe you another 🍺 @mnapoli ! The only issue now I'm hitting is that I doesn't look like I can set the default to the database connection, but send to the SQS queue. It looks like you have to set the SQS as the default for this to work. I may have to try it the other way around, where I specifically send jobs to the database queue. (or I rework that and just use SQS) |
Beta Was this translation helpful? Give feedback.
-
|
@Mesuva Don't worry, you are not the only careless developer out there.... I had made the same mistake and you saved me a lot of pain! Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
I had the same error message for another reason. So the problem in my case was my dockerfile was wrongly extending the Hope this will save some time to somebody else. |
Beta Was this translation helpful? Give feedback.
-
|
Would you mind sharing an example of your queue Dockerfile? I am trying to figure out how to get the QueueHandler to work in the container! |
Beta Was this translation helpful? Give feedback.
-
|
My configuration is the same as in the docs explained here. My dockerfile looks like this: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the info! So now I am getting the same error discussed in this thread: "message": "Bref\\LaravelBridge\\Queue\\QueueHandler",
"type": "Illuminate\\Container\\EntryNotFoundException",Here is my Dockerfile: FROM bref/php-83:2
COPY --from=bref/extra-pgsql-php-83:1 /opt /opt
COPY . /var/task
RUN echo "extension=pdo_pgsql.so" >> /opt/bref/etc/php/conf.d/bref.ini
CMD ["Bref\\LaravelBridge\\Queue\\QueueHandler"]
You have any idea what would cause this? Appreciate it! |
Beta Was this translation helpful? Give feedback.
-
|
Never mind, it's working now. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
@michaelaguiar do you mind to share how you able to make it work? |
Beta Was this translation helpful? Give feedback.
-
The docs example bellow give me an error:
Error:
Then I changed it to
Now I get the error:
Handler/var/task/Bref\LaravelBridge\Queue\QueueHandlerdoesn't existBeta Was this translation helpful? Give feedback.
All reactions