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.

Sign up for GitHub

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

Jump to bottom

Do not annotate content database at upgrade #5541

Open

benjaoming opened this issue Nov 13, 2017 · 0 comments

Labels

bug

Contributor

benjaoming commented Nov 13, 2017 •

edited

Loading

Summary

An upgrade may bundle a new preseeded content pack, and thus when it is installed, it should also result in content db annotation.

However, when no new content pack is installed, we shouldn't annotate the whole content database again, it can take quite a long time (hours on RPi)

System information

Operating system: *
Version: 0.17.x
Browser: *

benjaoming added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment