Fixes a bug in the watch priority sorting algorithm.

[mpforce1]

Description

Fixes a regression introduced in the last update (sorry 🙏 ).

Fixes #748 (again)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

I stripped out just the sorting part and ran some local tests to find the issue. Once fixed, I reran the tests and found it sorted as expected.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented on my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (README.md)
• My changes generate no new warnings
• Any dependent changes have been updated in requirements.txt

[saabia]

@rdavydov its working again 👍

[DanzoGit]

Is it working well right now?

[mpforce1]

Is it working well right now?

It's been a while since I looked at this branch specifically but I believe it was working as of December.

FYI, I've been working on a revamped version of the priority system that's easier to test over on my fork. @saabia's been helping me test it and we seem to be in a good place now. This is on my merged branch which has got all of my pending PR improvements from this repo (excluding the prediction system changes) plus this extra work on the priority system.