Closed JSmith-Aura closed 2 weeks ago
As discussed, this only happens when a new cracked hash has been added to the list. Only becomes distracting on very very large sets of hashes where the results are coming in quite quickly.
The solution would be to sort the DB query, first in terms of if its cracked, second in terms of ID. However, I'd need to performance test this for sets of hashes (i.e. 10k+) to evaluate any perf concerns, and I can't be bothered doing that quite yet. Might revisit in future
Each time that
api/v1/hashlist/<hashlist_id>
is queried the frontend hashlist shuffles to a new random ordering which is quite distracting when a job is running.I believe this is happening because the Preload doesnt have an order specified, e.g: