-
Notifications
You must be signed in to change notification settings - Fork 188
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
Migration to v. 2.2.0 failed #381
Comments
That doesn't sound good. Please provide more information:
|
Both. I suspected that it could be the reason and therefore tried to create a new jobs. They were also ignored. I hope I did follow.
I've tried both wit my current 7.0.2.3 and with the latest 7.0.3.1. Same result.
I've tried only the two versions I mentioned.
It seems to be the link to my issue. I did not find any other one that could fit.
If I've dropped the tables, will Que.migrate!(version: 0) recreate them?
I did not check anything else. What is in the list to investigate?
Now it is empty, as I have rolled back to dima4p@738bbf9 and finished them all. |
My current version of
que
is 3b7fccc with one fix for ruby 3.The migration is
All works until I've updated and migrated. After that no job is being executed.
What is the problem?
The text was updated successfully, but these errors were encountered: