Psalm hangs/slows down when analyzing Laravel Durable Activities
Description
Psalm analysis becomes extremely slow when analyzing Laravel Durable classes.
The issue appears mainly for Activities, rarely workflows, but could be due to less code in them.
I'm lead to believe that trees most likely have lots of nested relations and creates deep trees, yet psalm does not cache vendor files.
Running debug mode returns many Queueable trait parses
Analyzing /var/www/html/Modules/Services/app/Workflows/SlotPublishWorkflow.php
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Parsing /var/www/html/vendor/laravel-workflow/laravel-workflow/src/Workflow.php because we cannot use cache
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Parsing /var/www/html/vendor/laravel-workflow/laravel-workflow/src/Workflow.php because we cannot use cache
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Parsing /var/www/html/vendor/laravel/framework/src/Illuminate/Bus/Queueable.php because we cannot use cache
Has anyone faced this issue and possibly has a solution?
Psalm hangs/slows down when analyzing Laravel Durable Activities
Description
Psalm analysis becomes extremely slow when analyzing Laravel Durable classes.
The issue appears mainly for Activities, rarely workflows, but could be due to less code in them.
I'm lead to believe that trees most likely have lots of nested relations and creates deep trees, yet psalm does not cache vendor files.
Running debug mode returns many Queueable trait parses
Has anyone faced this issue and possibly has a solution?