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

add test for broken conversationsdb #93

Open

elliefm opened this issue Aug 21, 2020 · 1 comment

Contributor

elliefm commented Aug 21, 2020

bron:

I ran fixaccount for user with the issue, so we don't have a testcase as such for this. It looks like you need a broken conversations.db for the error to come up. The specific brokenness is "mailbox got deleted, but a record for it didn't get removed from conversations.db for some reason" - so there's a G record with a folder number which is a broken pointer.

ellie:

Could we reproduce this from Cassandane by just having cyr_dbtool inject a bad G record into the cassandane account's conversations.db? Or does the bad record need to be bad in a particular way that's hard to anticipate?

bron:

I think we could - either by injecting a bad record, or by messing with $FOLDER_NAMES.

Putting this here so we don't completely forget it forever

Contributor Author

elliefm commented Aug 21, 2020

Forgot some context: the crash this caused is already fixed by cyrusimap/cyrus-imapd@63c6caf, but we don't have a regression test for it.

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