Fixed logic for test to handle cases when input exceeds wsDefaultReadLimit

[arnabnandikgp]

Fixes #32232

[MariusVanDerWijden]

I don't understand this fix, could you elaborate why this fixes the issue? Thanks for picking this up!

[fjl]

The fix disables the overLimit case for any input > 32MB. To be fair, the test is confusing. I'll find a better way to fix this.

[arnabnandikgp]

The fix disables the overLimit case for any input > 32MB. To be fair, the test is confusing. I'll find a better way to fix this.

yup that is what I tried to assert through this test...earlier the function testLimit was checking if the message size limit was basically equal to the the default limit but rather I guess the essence of the test was to check on cases that have message size not only equal to the limit but also higher than that as we see here:

go-ethereum/rpc/websocket_test.go

Lines 173 to 174 in f96f82b

	testLimit(ptr(wsDefaultReadLimit * 2))
	}