Skip to content
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

stdin and adb logcat -v time issues #1262

Closed
A-Au opened this issue May 8, 2024 · 3 comments
Closed

stdin and adb logcat -v time issues #1262

A-Au opened this issue May 8, 2024 · 3 comments
Labels

Comments

@A-Au
Copy link

A-Au commented May 8, 2024

lnav version
v0.12.2

Describe the bug
Since updating to the latest version of lnav, I have had two issues that have been bugging me
1. adb logcat -v time | lnav -t prepends each log line with the current timestamp
Screenshot 2024-05-08 at 4 36 36 PM

  1. lnav -e 'adb logcat -v time' parses the output as a binary file input
    Screenshot 2024-05-08 at 4 35 27 PM

To Reproduce

Steps to reproduce the behavior:
Run either of the above commands with an android device plugged in or emulator running.
adb logcat -v time | lnav -t
lnav -e 'adb logcat -v time'

@A-Au A-Au added the bug label May 8, 2024
@tstack
Copy link
Owner

tstack commented May 9, 2024

lnav version
v0.11.2

I think you mean "v0.12.2" ?

  1. adb logcat -v time | lnav -t prepends each log line with the current timestamp

I'm not sure I understand, the -t option has always prepended the input with the timestamp. How is this different?

  1. lnav -e 'adb logcat -v time' parses the output as a binary file input

That's odd, what's shown there is the header for the internal file format for captured output. The file should've been recognized and handled. Does this always happen or is it sporadic?

@A-Au
Copy link
Author

A-Au commented May 9, 2024

Yes, typo "Version: lnav 0.12.2"

Oh wait ignore 1, I checked my previous commands and I didn't use the -t flag consistently. But 2 always happens for me.

@tstack
Copy link
Owner

tstack commented May 9, 2024

Ah, I think I know what is happening in case #2. I'll work on fixing it, thanks for the report.

@tstack tstack closed this as completed in 74a01bb May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants