Added a command script, did not restart the octane service, resulting in the data read by config and the monolog log not being recorded

[clemask]

Octane Version

2.11.0

Laravel Version

10.48.29

PHP Version

8.2.5

What server type are you using?

Swoole

Server Version

5.1.1

Database Driver & Version

No response

Description

We verify client requests using the signature check middleware, which retrieves some of the signature information from the .env file via config. I recently added a command script, but I didn't restart Octane. After a while, all client requests were intercepted by the signature check middleware, and the link logs recorded in the middleware were no longer written to the logs and were completely lost. The logs are based on the Monolog buffer driver.

Steps To Reproduce

step1：
Synchronize the latest code for an already running service without restarting the service

[sy-records]

This is normal behavior. The resident process does not update files in real time; changes take effect only after a restart.

[clemask]

My description may not be clear. Before adding this script, the signature generated by the signature checking middleware is consistent with the client. However, after adding the script and not restarting the service, the signature checking middleware will intercept all requests. I guess it may be that the key that the signature checking middleware relies on cannot be obtained normally (this key is configured in env and loaded through config), causing the signature checking to fail.

[sy-records]

Provide detailed steps to reproduce your issue. If necessary, please provide a GitHub repository to demonstrate your issue using laravel new bug-report --github="--public".

[crynobone]

Hey there, thanks for reporting this issue.

We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here?

Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.

laravel new bug-report --github="--public"

Do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue.

Thanks!