-
Notifications
You must be signed in to change notification settings - Fork 142
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
Unable to obtain truncated responses using --max-print-bytes #291
Comments
Hello @LeeZBug! I'm here to help you with any bugs, questions, or contributions you have. Let's work together to resolve this issue. The If you're experiencing issues where the parameter doesn't seem to take effect, consider the following possibilities:
Since the parameter should allow for larger content display, and it's not working as expected, it might be worth checking the kyanos documentation or code comments for any additional insights or reaching out to the maintainers for further assistance. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other | Bug Report |
I use '--max-print-bytes=anynumber'(like 3600,10240,20480), but the response is still incomplete. response is always truncate at same line |
I'll take some time to work on it. |
Hi, @hengyoush The problem is not related to the TUI, and it actually originates from |
Hi, @LeeZBug Could you provide your response header ? |
Describe the bug
I use 'kyanos watch http --path /site/list' to capture data, it says "truncated, total: 2351bytes"
But when I use "kyanos watch http --path /site/list --max-print-bytes=5120", it not says "truncated, total: 2351bytes", but the response is still incomplete.
To Reproduce
everytime
Expected behavior
It seems that the '--max-print-bytes=5120' parameter is not taking effect.
Screenshots
like above
Information (please complete the following information):
Linux test 3.10.0-1160.95.1.el7.x86_64 #1 SMP Mon Jul 24 13:59:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: