-
Notifications
You must be signed in to change notification settings - Fork 187
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
traceloop show fails with message larger than max
#2868
Comments
Hi! When you open a bug report issue, GitHub auto-fills the description with the following text:
This is not for the sake to add burden on people reporting bugs, but rather to help us to diagnostic the problem. For the problem itself, the error message is not printed by traceloop but by the trace and Best regards. |
I suspect we need to change this line:
in this way: -trace.Status.OperationError = fmt.Sprintf("failed to unmarshal output: %s", err)
+trace.Status.OperationError = fmt.Sprintf("failed to unmarshal output %q: %s", t.trace.Status.Output, err) This would be consistent with what was done in https://github.com/inspektor-gadget/inspektor-gadget/pull/714/files |
kubectl gadget traceloop show 33e588d70d7fdf6c837d727f4d1c6e067aaf7bdd03f96db26449a26a747c8411
CPU PID COMM SYSCALL PARAMS RET
Error: unmarshaling output: invalid character '\x1b' looking for beginning of value
Error: failed to receive stream on node "ip-10-11-85-0.ec2.internal": command terminated with exit code 1d message larger than max (12984636 vs. 4194304)
The text was updated successfully, but these errors were encountered: