Increase size of response message buffer#12
Open
towo wants to merge 1 commit into
Open
Conversation
We were experiencing a lack of function due to an overly long 'output' element coupled with quite a few overlay mounts, which lead to the buffer not even containing the network section. A simple doubling in buffer size fixes this problem, but since the container information can be arbitrarily long, this is just a jury-rigged fix.
|
Duplicate of #10 |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We were experiencing a lack of function due to an overly long 'output' element coupled with quite a few overlay mounts, which lead to the buffer not even containing the network section.
A simple doubling in buffer size fixes this problem, but since the container information can be arbitrarily long, this is just a jury-rigged fix.
My C isn't good enough to formulate a better plan for this (some kind of response paging, maybe even properly parsing the JSON?) and rewriting it as a search over all networks seems a bit overkill.