The data/processing.py script was using subdomain_name instead of name to index reports when sanity-checking them during processing. The subdomain_name variable would have referred to the result of unrelated use prior.
It seems to have been practically harmless (the sanity checking was just out of an abundance of caution), and this change doesn't affect the calculated numbers (or create/remove any new warning or exceptions) during data processing at all. It's good to fix it though, since it could have been the cause of new unexpected bugs if the subdomain_name value had ever changed, or if another change would have made the sanity-checking necessary or useful.
The
data/processing.pyscript was usingsubdomain_nameinstead ofnameto index reports when sanity-checking them during processing. Thesubdomain_namevariable would have referred to the result of unrelated use prior.It seems to have been practically harmless (the sanity checking was just out of an abundance of caution), and this change doesn't affect the calculated numbers (or create/remove any new warning or exceptions) during data processing at all. It's good to fix it though, since it could have been the cause of new unexpected bugs if the
subdomain_namevalue had ever changed, or if another change would have made the sanity-checking necessary or useful.