The way it is currently fixed means that matches can still overflow
in the web interface because JavaScript has a 2^53 number limit.
However, this fix is in line with how earlier cases have been fixed.
This fixes issue #5054.
{"order", (int)a->order},
{"pools", pools},
{"latency", (int)(a->latencyUsec/1000.0)},
- {"queries", (int)a->queries}};
+ {"queries", (double)a->queries}};
/* sending a latency for a DOWN server doesn't make sense */
if (a->availability == DownstreamState::Availability::Down) {