Moved opcache clearing to before bootWorker

[LauJosefsen]

Moved opcached clearing to before bootWorker method to enable hot reloading for Swoole and OpenSwoole when Opcache is enabled.

More information about the issue this solves can be seen in #546 .

Closes #546

[michael-rubel]

Looks like it's related to this issue: #432

[LauJosefsen]

Looks like it's related to this issue: #432

It sure does seem like that. Also the issues linked from that issue. (funny how i didn't find those by searching for issues with "--watch" 🤔)

I believe the change I propose is both safe and fixes the issue completely.

[binaryfire]

Sorry to bump an old thread, but is anyone still having this issue? I'm using Swoole and reloading workers (either automatically via --watch / Chokidar or manually via php artisan octane:reload) doesn't reflect certain changes. The only way to get it fully working is via php artisan octane:stop.

If anyone has a workaround they could share it would be much appreciated. I'm using Docker but I don't think that should make a difference, since everything is run in the container.

[LauJosefsen]

@binaryfire Are you using file opcache by chance? Maybe link your php.ini file? We do not have any problems anymore, also using Swoole on our deployments.

[binaryfire]

@LauJosefsen Hi Lau, thanks for the reply. Yeah I'm using opcache. Here's the link to the PHP config I'm using in the container: https://gist.github.com/binaryfire/ed1ec34f8333117aa7e494192f807aa2

It's identical to Sail: PHP 8.2 from the Ondrej PPA on Ubuntu 22.04, stock php.ini with the same custom config in conf.d folder. Not sure what's going on! I've considered implementing a custom listener or file watcher to fully stop and start Octane on file changes, but I'm hoping there's a more elegant solution.