during testing of #4943 i also found that the server doesn't check if the size of numbers matches the expected bit size. i had 2 u32 and 1 u64 and changed it on the client to 1 u32 and 2 u64 and besides it reading the wrong value, it didn't notice that it had 32 bits left over and just ran the reducer with the wrong values. i could even change one of them to a string and send "hello this is an invalid arg" as string and the server would just ignore that the arg size is way too big.
from my testing the error message only appears if the args length is too small.
i made this issue separate so that it is easier to track.
during testing of #4943 i also found that the server doesn't check if the size of numbers matches the expected bit size. i had 2 u32 and 1 u64 and changed it on the client to 1 u32 and 2 u64 and besides it reading the wrong value, it didn't notice that it had 32 bits left over and just ran the reducer with the wrong values. i could even change one of them to a string and send "hello this is an invalid arg" as string and the server would just ignore that the arg size is way too big.
from my testing the error message only appears if the args length is too small.
i made this issue separate so that it is easier to track.