Tim Stack

Which of these patterns were you expecting to match these logs? https://github.com/tstack/lnav/blob/f21517b56c8a1b6a4a709bce4cd90dd80621e5c4/src/formats/java_log.json#L7-L50 If I add the first line of your logs as a sample, I get this output: ``` =...

I've pushed a change that adds the following pattern that matches your logs: https://github.com/tstack/lnav/blob/8b12222a2007b62f9e02cf9ee178d38e6a92de0b/src/formats/java_log.json#L50-L52 However, I'm not totally sure about all the fields. For the 3rd column with the number...

> Please note, that some of the fields are optional. They're not shown by default. Ah, yes, I've made the correlation ID optional in this commit: 4d624f565557c10884aaa1c7ec27833bfce835e6 I'd need some...

> They were working some time ago, but currently they crash lnav. I'll update them and if they still crash it, I'll open an issue for that. Ah, sorry, what...

The I2P logs you sent seem to already match the `java_log` format for the most part. Can we modify that instead of adding a separate format?

Also, the virtiofsd log seems to be recognized by the Rust `env_logger_log` that was added to the top-of-tree.

@xuyangyuio can you provide some more details. Things seem to work for me and others, so it's hard to know what the issue might be.

The top-of-tree has switched from ncurses to notcurses for input handling. Pressing `ESC` in prompts seems to do the right thing now.

Updated the bins workflow to do a build on the github M1 machines.

@cw1nte > 0.12.4 I notice something similar. I have found a bug introduced in v0.12.4 that might be the cause of your problem. A fix is available in the top-of-tree....