B11a socket errors

Do you need help? Ask here!

Bug reporting belongs here: http://developer.wz2100.net/newticket
BunkerBlaster
Trained
Trained
Posts: 268
Joined: 21 Feb 2010, 09:56

B11a socket errors

Post by BunkerBlaster »

I was going to submit a ticket but Im a little confused on whether r10004 is closed or not.
([10010]: Handle socket clean up, then player cleanup, and then re-init the player)

changelog states "Fix: On player quit, close things down and cleanup correctly (r10004)"

But when I search the issue tracker r10004 is not crossed out like the ones that are closed.
Does this mean you are aware there is still a problem or is it that you wait until a certain amount of time to close it?

The reason I ask is the socket cleanup is also closing connected sockets causing all players to exit from lobby. When a player exits the game and warzone reports it as color leaving, the very next player that joins the game will cause all players to exit. The last player does not show on screen, only in error log. I verified the connection actually happens by creating a pop up that shows every time a connection is recieved. I have 3 error logs that close all active connections during the socket cleanup.([NETclose] Closing connected_bsocket[2], 02712BA0).
User avatar
Zarel
Elite
Elite
Posts: 5770
Joined: 03 Jan 2008, 23:35
Location: Minnesota, USA

Re: B11a socket errors

Post by Zarel »

BunkerBlaster wrote:But when I search the issue tracker r10004 is not crossed out like the ones that are closed.
Does this mean you are aware there is still a problem or is it that you wait until a certain amount of time to close it?
r10004 is a changeset (the "r" stands for revision), not an issue ticket. A ticket looks like this: #1671.

The difference between tickets and changesets, are that each ticket is a discussion topic talking about the code, while each changeset is a change to the code itself. Some changesets are the result of a ticket (and committing the changeset closes the ticket), and some aren't.

Only tickets are opened or closed. Changesets are just committed.
User avatar
Buginator
Professional
Professional
Posts: 3285
Joined: 04 Nov 2007, 02:20

Re: B11a socket errors

Post by Buginator »

Not socket errors...it was a bug, which is hopefully fixed now.
and it ends here.