-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
logging shows timestamp on each (control) character #2500
Comments
I think this may be related to our handling of control characters with logs, but not certain yet. |
Not control characters. We seem to print each character as it comes in, with full timestamp, when timestamps are requested. Probably an artifact of how we read from conmon? It doesn't help that there are seemingly no newlines being printed, either. |
Partial fix in #2513 - will greatly improve readability by ensuring that each timestamp is on a separate line. Does not deal with user input appearing one character at a time, a timestamp for each, though. |
@mheon Sorry for asking this, but could you right pad with zeros? See the hashtag
This might it even more readable, since the columns won't jump - or does this degrade performance too much? |
@tobwen Went ahead and fixed the actual issue (the entire line should now appear under a single timestamp), so we should be good |
@mheon But can you right-pad the timestamp please? I hate jumping columns :D |
Alternative question: why are some timestamps missing a digit? Is it omitting zeroes, or is there something else going on here? I'll take a look |
From the Go documentation: And that, there, explains our missing zeroes. |
#2522 with the final formatting fix |
Thanks |
/kind bug
Description
Warning about a not-wellformed tag when parsing language.
Steps to reproduce the issue:
1st window:
podman --log-level debug run -it --rm --read-only busybox sh
(returns af49b446cf34...)2nd window:
podman logs -ft af49b446cf34
Describe the results you received:
019-03-01T04:53:12.517290493Z / # 2019-03-01T04:53:33.565339544Z 2019-03-01T04:53:33.626659047Z 2019-03-01T04:53:33.687523235Z 2019-03-01T04:53:33.708198635Z 2019-03-01T04:53:33.767723803Z 2019-03-01T04:53:33.827842903Z 2019-03-01T04:53:33.8487504Z 2019-03-01T04:53:33.908428489Z 2019-03-01T04:53:33.967692938Z 2019-03-01T04:53:33.991472119Z 2019-03-01T04:53:34.051359604Z 2019-03-01T04:53:34.111670887Z 2019-03-01T04:53:34.132360549Z 2019-03-01T04:53:34.192956436Z 2019-03-01T04:53:34.252802312Z 2019-03-01T04:53:34.334168968Z 2019-03-01T04:53:34.393670188Z 2019-03-01T04:53:34.487301865Z 2019-03-01T04:53:34.546584874Z 2019-03-01T04:54:08.993315313Z 2019-03-01T04:54:12.025890929Z 2019-03-01T04:54:16.420445Z 2019-03-01T04:54:16.947456176Z 2019-03-01T04:54:17.006923129Z 2019-03-01T04:54:17.139674739Z 2019-03-01T04:54:17.668521897Z 2019-03-01T04:54:17.728321548Z 2019-03-01T04:54:17.788493409Z 2019-03-01T04:54:17.849062338Z 2019-03-01T04:54:17.909409104Z 2019-03-01T04:54:17.969603528Z 2019-03-01T04:54:18.028831379Z 2019-03-01T04:54:18.087902127Z 2019-03-01T04:54:18.147525757Z 2019-03-01T04:55:03.98441397Z
While typing interactively inside the container, a timestamp get pasted on each keystroke.
Describe the results you expected:
One timestamp at each new line.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Additional environment details (AWS, VirtualBox, physical, etc.):
VirtualBox 6 on Windows 10, running Debian 9 (stable)
The text was updated successfully, but these errors were encountered: