Basset Fresh might not work 100% of the time

[tabacitu]

I've noticed this in our online demo. But the issue happens on my local too. After I've already run php artisan basset:fresh... subsequent calls DO NOT seem to actually do a fresh. They are just too fast.

• first php artisan basset:fresh call - 4s to internalize everything
• second php artisan basset:fresh call - 0.08s 👀 fishy
• third php artisan basset:fresh call - 0.04s 👀 fishy again
• manually calling php artisan basset:clear && php artisan basset:internalize (which should be the same thing as php artisan basset:fresh - 4-8s (normal)

Soo... what's happening here? 👀 Any idea @promatik ?

[pxpm]

Me and @tabacitu had debugged this a little bit further.

We suspect the issue may be that the artisan calls (in basset:fresh command) are made asynchronously, so the second one does not wait for the first to finish.

Instead of directly calling artisan we may need to use Symfony Process class, that we can wait until we get a "all good" output from the first command.

@promatik

[promatik]

Fix provided by https://github.com/Laravel-Backpack/basset/pull/73 👌