-
Notifications
You must be signed in to change notification settings - Fork 591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.x client doesn't throw proper exception when input is too long for shortstr #907
Comments
I just checked the behavior of this with 6.2.0-rc.1, and it seems somewhat improved:
But this is thrown from the internal guts of the framework:
This means the client is still not checking the length directly before trying to write it. The exceptions being thrown in 6.1.0 and 6.2.0 are not clear at all, and I wouldn't expect anyone using the client to understand what the problem is. |
11 tasks
Fixed by #908 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like there's been a change/break in behavior around what the client does when encountering a value that is too large to fit into a
shortstr
.Given the following code:
With version 5.2.0 and earlier you get the following exception thrown immediately:
With version 6.1.0, it appears to be hitting some timeout value:
The stack trace of that exception:
Looking at the network traffic, the client never sends anything when running into this on 6.1.0.
We should definitely be detecting if the input is too long to be written and throwing a more informative error, like it used to.
The text was updated successfully, but these errors were encountered: