We’ve had a lot of reports of NoSuchElementExceptions thrown by SequenceEncoder.Decoder.nextToken(). For example:
sourceforge.net/tracker/?func=d … tid=594231
sourceforge.net/tracker/?func=d … tid=594231
sourceforge.net/tracker/?func=d … tid=594231
sourceforge.net/tracker/?func=d … tid=594231
sourceforge.net/tracker/?func=d … tid=594231
sourceforge.net/tracker/?func=d … tid=594231
sourceforge.net/tracker/?func=d … tid=594231
I understand what’s happening in these at the “bottom” of the stack trace: Something is expecting there to be more decodable tokens then there actually are. What I don’t understand is why this is the case. I’m fairly certain that SequenceEncoder.Decoder is not at fault here. The problem is either that more tokens should have been written, or fewer tokens should have been been requested.
This might also not be a VASSAL bug, but rather a module bug. If this isn’t a VASSAL bug, then I’d like to suggest that there is a VASSAL bug here anyway, namely that the user should be told what’s wrong and we should not be seeing these as bug reports.
Does anyone have any insight into this problem? I’d like to get these resolved, as this is the most frequent kind of bug report I see which isn’t obviously attributable to a JRE bug.