nextByte: insufficient buffer (24 of 23)

[darrensapalo]

Summary

I'm receiving the error below when parsing newer DotA 2 match replays.

nextByte: insufficient buffer (24 of 23)

Hypothesis

This might be related to patch changes affecting the packet rules/version, because attempting to patch it using older matches works successfully. These parsing errors appear to occur for matches beyond December 2022. This is based on an estimate and imprecise testing. My replays before November 2022 are able to be parsed properly.

Example demo match replay Match ID: 6955604251

Unfortunately, GitHub doesn't allow .dem uploads.

Screenshots

Debugger shows the following error is thrown, but I've tried googling what library (standard?) is throwing it but I'm unable to find it.

[darrensapalo]

This is likely related to protobuf definitions changing. I tried to use an alternative parser (i.e. clarity) but then it also encountered parsing issues.

I hypothesize that it must be the same- the low level parser owners need to update their protobuf definitions given the steam update sometime September/December 2022.

[brunal]

I've tried googling what library (standard?) is throwing it but I'm unable to find it.

It's from reader.go. Either here or there.

It's trying to read more bytes than are available.

The issue is that by being a panic and not a simple error, we cannot get the chain of explanations that brought the program to this situation.

You can, however, use the runtime/debug package to recover from the panic to write its stack trace: https://stackoverflow.com/a/52106370.

Can you share it? That should help. The alternative would be to make nextByte return an error & handle that, but it's more toil dev-wise.