Metaserver query code cannot handle fragmented response

[Al Riddoch]

When the metaserver is queried for a list of servers, the results are fragmented into multiple packets if the list is too long for a single packet. Recently we have for the first time seen a number of servers online which exceeds the threshold for this, and the Eris metaquery tool is giving the following errors even though the testclient included in the metaserver codebase is working fine:

[byron@impulse eris]$ ./test/metaquery
querying metaserver.worldforge.org
metaserver knows about 151 servers.
ERIS: Incorrectly got duplicate metaserver list response. This is unexpected.
got info for server: sd-19255/88.190.11.44
.......
got info for server: jml03/38.117.193.198
got query failure: Connection to the meta-server timed out
querying meta server at metaserver.worldforge.org failed

[Al Riddoch (alriddoch)]

This is a placeholder for me. I plan to fix this asap.

[Al Riddoch (alriddoch)]

I have started work on this issue, and removed the lines which cause Eris to abort when it gets additional server list packets. Sadly the metaserver not longer has enough servers for me to test this code more, so finishing the fix will happen soon.