-
Notifications
You must be signed in to change notification settings - Fork 26
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
Catch all exceptions during migration #1893
Catch all exceptions during migration #1893
Conversation
@r-peschke did you mean to approve this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's about the yml changes. Please write an issue if you change there.
For the migration part: I miss the reason why you do this and/or a test.
It's a simple version upgrade, I don't think a separate issue is needed here. If you wish, I could extract it into its own PR, but I think that's overkill. We should think about adding a
This was not tested before and is really hard to test, so I didn't add a test. The reason why I did this is linked earlier in this thread. |
* commit '343326a220f149fb06e91d96df85bfb339b59113': Use get_all instead of filter for migration 46 (#1910) Fixed readding point of order speaker (#1909) I1906 migrations 0045, 0046 replace get-all by filter (#1908) Support point of order speakers in re-add-speaker (#1894) (#1905) Remove all topic.tag_ids from database (#1901) update all new fields (#1900) Catch all exceptions during migration (#1893)
If exceptions other than
MigrationException
happen during a migration, they are currently not logged anywhere. They should instead be logged.