redshiftzero

Nope we still need more tests for pagination

I think the following duplicate job scenario would describe the behavior: 1. Sync starts, jobs corresponding to source A added to queue. They start processing but won't finish since there...

I agree, I think it is worthwhile, we don't have a way to cancel a job yet but I think that'd be a nice architectural improvement after #975

> if a source is deleted client-side, we already prevent any new jobs on that source true, but since any client-triggered deletion jobs will run _before_ any already enqueued message...

Two possibilities (there may be more) to what's causing these test failures: 1. We're calling `QApplication.exit` somewhere, causing subsequent tests to fail: https://github.com/pytest-dev/pytest-qt/issues/37 2. The pytest-qt docs [recommend](https://pytest-qt.readthedocs.io/en/latest/tutorial.html) registering widgets...

Just a note: while the current behavior on the JI is searching only by codename (since everything else is encrypted), since we added the `content` field to the database in...

for SecureDrop's journalist interface (a Flask webapp) we support both HOTP (I agree with @dismantl that I don't think we need to support HOTP for OpenOversight) and TOTP using the...

Welcome @pinkgladiator :) Yep, this is a good choice for first ticket. I recommend starting by sorting the lists of classifications and identifications on a user's profile by `id` such...

Good question - it's b. So with the current logic the application won't allow the upload of duplicate photos. Preventing the upload of duplicate photos is actually the right thing...

Yep I agree with dumping the dropdown. That's similar to one of the feedback points we got in our [heuristic UX analysis](https://github.com/lucyparsons/OpenOversight/issues/252#issue-226799014) - check that out for a little screenshot...