-
Notifications
You must be signed in to change notification settings - Fork 11.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scheduler no longer runs commands in background #12628
Comments
Thanks for the report. |
Thanks in particular for the link to the commit. That's very helpful. :) |
Unfortunately, this seems to still be an issue on Windows. I have a command registered as below:
When letting the scheduled Windows task run (which in turn runs If there are more details I can provide, I'd be more than happy to. Thanks |
@GrahamCampbell when i use command * * * * * php path/artisan schedule:run > /dev/null 2>&1 then its not working. but when i use php path/artisan schedule:run > /dev/null 2>&1 then it works but only for once. could you please guid me? |
I think this has some unfortunate underpinnings in the Syfmony process component. I played around with trying to get a Symfony process to run in the background on Windows and wasn't having much luck. I'll try again to see if I have some luck that I can transfer over to this project |
@StevenBock I wonder if you have any updates regarding this? |
Closing for lack of activity. |
@StevenBock - did you have any progress on this? I've just had a similar issue.... |
@StevenBock @laurencei same issue here. Any fix for that? |
Did you have any progress on this? I've just had a similar issue.... |
Removal of the check and function that checks whether a scheduled task should be executed in background causes issues with long tasks.
After the removal of runCommandInBackground each scheduled task waits for the previous one to finish before it can start.
Is there another way to force it to run as a Background process?
issue is caused by the change in commit
9147bf7
The text was updated successfully, but these errors were encountered: