CommandSchedulerBundle
CommandSchedulerBundle copied to clipboard
j-guyon
Is this project still being maintained?
Is this project still being maintained? Or should we fork it? I can see a lot of open PR and issue.
what about. the current version does not work correctly i have the same problem #176. is there a corrective version planned
I hope @j-guyon is still maintaining it.
After i opened the issue about Php8 #188 i started to add it in my fork. https://github.com/Chris53897/CommandSchedulerBundle I fixed, refactored and added more functions over the last month. (see feature section)
**My main goal is to integrate these changes in a version 4 of this repo together with @j-guyon ** I did not have the backwards compatibility in mind.
If this project in unmaintaned we could maybe work with my Fork as a replacement, until we have a statement from @j-guyon
There is some work todo, before there could be a switch. https://github.com/Chris53897/CommandSchedulerBundle/issues
The main focus should be to fix issues in 3.x and allow PHP 8 https://github.com/Chris53897/CommandSchedulerBundle/issues/10
Could need some help with this. See "Help wanted" Labels ;)
@Chris53897 have you published your fork on packagist ? I really need to fixe this bugs on my current project. Maybe should i try this one : https://github.com/Guikingone/SchedulerBundle
Hi. I created an organization https://github.com/Dukecity/CommandSchedulerBundle and released it. I merged the pull request to fix the bug. But i have not reproduced the error, and so i could say nothing if the pull request fix the error.
I took a lot of time to work in my fork. If someone wants to help, your welcome.
V3 with mostly Bugfixes only V4 with more Features
@Chris53897 thanks, i will test this. Does the version v3.0.2 solve the problem of multiple entries #176 ?
@jvancoillie I have integrated the pull request. But i did not recreate the behaviour and tested it. https://github.com/j-guyon/CommandSchedulerBundle/commit/61fc1f340c72b3eeaaea7f990e8b2a62da9fce94
If you are on symfony 4.4 i suggest to use v3.0.9 or v4.0.2. In v.4.0.2 i made the Command Name unique. The best way is to test it on an dev environment, before you deploy it. https://github.com/Dukecity/CommandSchedulerBundle/blob/master/Entity/ScheduledCommand.php
I hope my pull request for symfony recipe will be approved soon. That will make things easier.
Thank you guys for your answers. That's a Pitty @j-guyon do not answer. It seems he is not very active this last months.