Thread history

Fragment of a discussion from Talk:Gilgalad
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
No results

Well, I think my uploaders use to be (and probably still are) culprits. But I did not do any tweaking or modification of stock client. I was also under suspicion that even with mine, some of my machines were doing the correct size report and other were not. But they all have identical configs and java distributions.

The only thing which might be of importance: I run everything on OpenJDK, may be it has a different way to evaluate the code size.

Nevertheless, I stopped uploading for a week, so new wrong entries are due to new uploaders. May be we should look for correlation, and see what is the possible reason for the size misreporting.

Beaming (talk)16:29, 31 August 2014

Hi all. Apparently all we need to do is to report bugs to developers :) I did so and Fnl fixed it within a day.

I suggest everyone to upgrade to 1.9.2.2 and kindly ask Rednaxela to tune rumble server to accept client with this version and above.

Beaming (talk)00:24, 4 September 2014

It would be Skilgannon that runs the rumble server, not I. ;)

Rednaxela (talk)14:16, 4 September 2014

Shame on me, I keep doing this mistake over and over :(

Beaming (talk)16:24, 4 September 2014

No worries =) The rumble is updated, and only accepting contributions from 1.9.2.2

Skilgannon (talk)18:18, 4 September 2014

Beaming, it seems your new client is still uploading megabots to the minirumble :-/

Edit: never mind, it now seems to be removing them. Maybe they were left over from the old install?

Edit2: it seems you have two clients running, one is removing and one adding.

Skilgannon (talk)08:19, 5 September 2014