Fabian Emilius

I only experienced it on WAX but we mainly run WAX nodes, so there we dont have anything to compare. The only way to reproduce this issue is to connect...

No its not related to that issue

A: Yes it runs https://github.com/cc32d9/wax2.0 but there are barely any modifications and no new types / ABI changes so I dont see why this should affect the deserialization B: It...

Here is a diff of the ship data: https://www.diffchecker.com/gIi3EDof visually prepared

Thanks for the answer. That error happened not on my node but apparenty debug mode was not enabled. I dont have an own parser but use eosjs so if both...

Yes makes sense. I will open it again once it happens again

Not sure which version I used back then (issue is 11 months old) but I can still reproduce this with eosjs 22.1.0 using the data provided in the initial message...

Ok nevermind. I did some more debugging and it actually is related to my code because the deserialization does not consume all data (see last condition). I know this can...