-
Notifications
You must be signed in to change notification settings - Fork 42
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
Crash when sending reply [Nov 14 nightly / SF instance] #622
Comments
(This is reproducible, independent of which source is selected, on the SF instance.) |
we need #381 to help catch bugs like this pre-merge |
ok so this bug was a result of our 'no rebase before final merge' policy, read on for the details. When #605 was in the PR stage, #578 was merged introducing the use of the Next, we merged #605 removing the If we'd have rebased prior to final merge and re-tested everything (or had functional tests that would have then failed), we'd have discovered this bug. I think going forward we should be careful to rebase/retest other pending changes after a big PR lands, but I don't want to do this across the board until we see another defect introduced due to this cause (thoughts welcome though). Anyway for resolving the bug updating the reference from |
When sending reply in client, client crashes. Log in
.securedrop_client
sayeth:The text was updated successfully, but these errors were encountered: