will we actually log any less for a PusherConfigException than for a TypeError or whatever it was?
Woops, I missed a code path where it wasn't handled.
I'm not entirely convinced by this. it's the only thing that gets logged during minutes of cpu-spinning, and it's not massively high-volume.
I could make it so it logs in batches the progress?
fair enough. let's see how it looks.
Merging #4716 into develop will decrease coverage by 0.11%.
The diff coverage is 33.33%.
Err, we know the type since we're only catching the one PusherConfigException exception?