This repository was archived by the owner on Mar 4, 2025. It is now read-only.
Fixed potential array out of bounds exception, issue #14 #16#1
Merged
Conversation
…would not read the entire server response
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This should likely fix reported issue solita#14
Because we do the write-call before checking the read response, we might try to write with -1 as the array index
Additionally, I'm not entirely sure of the purpose of the is.available() call. We presumably want to exhaust and read everything until end of stream anyway? This is where I might be wrong though.