Closed PROFeNoM closed 1 month ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 80.91%. Comparing base (
3f3547d
) to head (73c12ff
). Report is 1 commits behind head on master.
Benchmark execution time: 2024-10-17 09:11:58
Comparing candidate commit 73c12ffb2b7b51158c3f61bd172a4e84415d7a73 in PR branch alex/AIDM-358_laravel-queue-mitigation
with baseline commit 3f3547dc7d60b86a6f7dcccc46f5173b6edc8cd7 in branch master
.
Found 0 performance improvements and 2 performance regressions! Performance is the same for 176 metrics, 0 unstable metrics.
execution_time
[+7.847µs; +12.569µs] or [+4.354%; +6.973%]execution_time
[+1000.000ns; +1000.000ns] or [+100.000%; +100.000%]
Description
A customer reported hitting the hook limit from
laravel.queue.action
hook installs.While their issue disappears when removing these three lines (CallQueueHandler::call being called before the job handler), this is by no means a fix. For legacy, doing
method_exists
on the hooked $class::$method was returningtrue
for them, and we have had confirmation that this method was indeed being called; yet, the hook wasn't invoked.This PR acts as a mitigation by preventing hooks from stacking up by removing them during the post-hook of the surrounding
fire
operation. It doesn't fix the issue.Reviewer checklist