We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I found this problem recently, If the exception occurs during flush on the following line https://github.com/j-guyon/CommandSchedulerBundle/blob/1.2/Command/ExecuteCommand.php#L223 the command stays locked forever, untill unless you unlock it manually.
Symfony can throw exception here \Doctrine\ORM\OptimisticLockException Please add try catch here. So that code don't break.
The text was updated successfully, but these errors were encountered:
I have the same issue. Did you find some workaround for this @muhammadumair-coeus ?
Sorry, something went wrong.
No branches or pull requests
I found this problem recently, If the exception occurs during flush on the following line https://github.com/j-guyon/CommandSchedulerBundle/blob/1.2/Command/ExecuteCommand.php#L223 the command stays locked forever, untill unless you unlock it manually.
Symfony can throw exception here \Doctrine\ORM\OptimisticLockException
Please add try catch here. So that code don't break.
The text was updated successfully, but these errors were encountered: