-
Notifications
You must be signed in to change notification settings - Fork 90
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
streaming podman metrics breaks with ~ 14 containers active #1025
Labels
bug
Something isn't working
Comments
marusak
added a commit
to marusak/cockpit-podman
that referenced
this issue
Jul 11, 2022
It is not given that one reply comes in one piece. It might come n multiple messages and we need to connect them before trying to parse them. Fixes cockpit-project#1025
marusak
added a commit
to marusak/cockpit-podman
that referenced
this issue
Jul 11, 2022
It is not given that one reply comes in one piece. It might come n multiple messages and we need to connect them before trying to parse them. Fixes cockpit-project#1025
marusak
added a commit
to marusak/cockpit-podman
that referenced
this issue
Jul 11, 2022
Maximum length on one message is 4096 characters. When the reply is longer than that it will come in multiple messages. In such case we need to connect them before trying to parse such message. This for example happens when there are multiple containers and `Stats` often are split into multiple messages. Fixes cockpit-project#1025
marusak
added a commit
to marusak/cockpit-podman
that referenced
this issue
Jul 11, 2022
Maximum length on one message is 4096 characters. When the reply is longer than that it will come in multiple messages. In such case we need to connect them before trying to parse such message. This for example happens when there are multiple containers and `Stats` often are split into multiple messages. Fixes cockpit-project#1025
marusak
added a commit
to marusak/cockpit-podman
that referenced
this issue
Jul 11, 2022
Maximum length on one message is 4096 characters. When the reply is longer than that it will come in multiple messages. In such case we need to connect them before trying to parse such message. This for example happens when there are multiple containers and `Stats` often are split into multiple messages. Fixes cockpit-project#1025
marusak
added a commit
to marusak/cockpit-podman
that referenced
this issue
Jul 12, 2022
Maximum length on one message is 4096 characters. When the reply is longer than that it will come in multiple messages. In such case we need to connect them before trying to parse such message. This for example happens when there are multiple containers and `Stats` often are split into multiple messages. Fixes cockpit-project#1025
martinpitt
pushed a commit
that referenced
this issue
Jul 12, 2022
Maximum length on one message is 4096 characters. When the reply is longer than that it will come in multiple messages. In such case we need to connect them before trying to parse such message. This for example happens when there are multiple containers and `Stats` often are split into multiple messages. Fixes #1025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cockpit-podman version: 0cb9c37
Podman version: 4.1.1
When having ~ 14 containers active I noticed the page was running slow and the console is full of errors.
The json we try to parse is streamed with `cockpit.http().request().stream()
The data we try to parse is not complete, is that a bug in cockpit.http or our podman implementation.
The text was updated successfully, but these errors were encountered: