You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If a container's command contains newlines, they are interpreted and spill over to the other sections of the display. I noticed this when running a VSCode devcontainer and checking glances.
Further testing showed that a Windows newline (\r\n) clears the container's line, effectivly hiding it.
To Reproduce
Steps to reproduce the behavior:
Start Glances with the default settings
Start a VSCode devcontainer or the sample I provided below
See error
Sample Dockerfile
FROM python:latest
# Test UNIX newline. Substitute \r\n to demonstrate hiding behaiviour
CMD ["/bin/sh", "-c", "echo Running\nwhile true; do sleep 1; done"]
Expected behavior
The newline should be converted to a whitespace. It should not spill over and should not hide the container's existance,
Describe the bug
If a container's command contains newlines, they are interpreted and spill over to the other sections of the display. I noticed this when running a VSCode devcontainer and checking glances.
Further testing showed that a Windows newline (
\r\n
) clears the container's line, effectivly hiding it.To Reproduce
Steps to reproduce the behavior:
Sample Dockerfile
Expected behavior
The newline should be converted to a whitespace. It should not spill over and should not hide the container's existance,
Screenshots
Running the devcontainer (has command
echo Container started\ntrap "exit 0" 15\n\nexec "$@"\nwhile sleep 1 & wait $!; do :; done', '-
):Running the sample docker container with windows newline:
Environement (please complete the following information)
Manjaro Linux 23.1.4
Glances v3.4.0.3 with PsUtil v5.9.8
AUR
Glances test (only available with Glances 3.1.7 or higher):
Additional Information
Same issue in process table: #2337
Tab (
\t
) is interpreted as well. Just adds a bit of space.The text was updated successfully, but these errors were encountered: