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

Verbose output is no longer well formatted (since v2.1.0) #280

Open
sirockin opened this issue Sep 4, 2024 · 3 comments
Open

Verbose output is no longer well formatted (since v2.1.0) #280

sirockin opened this issue Sep 4, 2024 · 3 comments
Assignees

Comments

@sirockin
Copy link

sirockin commented Sep 4, 2024

When tests are run with the -v flag, results are no longer formatted as a table and there is no colouring.

This appears to have happened since the v2.1.0 re-write.

@nvloff-f3
Copy link
Contributor

nvloff-f3 commented Sep 9, 2024

Hi @sirockin ,

Yes, there has been a behavior change as part of #260

The aim of the change was to allow for the f1 output to be parsed by log collection systems with the introduction of structured logging.

As the verbose option would interweave structured logs (from the log file) and interactive messages, we found that difficult to handle for log parsers, so we made it that in case the verbose option was enabled all the output was structured logs. More details and rationale is available in the PR: #260

Can you describe your use case please? I'm happy to make adjustments to support, but I need a better understanding of that.

(in the meantime a workaround would be to use json format for the logs and use jq templating to achieve the exact formatting you're looking for)

@nvloff-f3 nvloff-f3 self-assigned this Sep 9, 2024
@sirockin
Copy link
Author

sirockin commented Sep 9, 2024

Hi @nvloff-f3 no specific use cases but we did find the previous -v output format useful and readable whereas the new one isn't.

Happy for you to mark it as wontfix.

@nvloff-f3
Copy link
Contributor

Alright, I think what's missing here is an option to force interactive mode. That, with a combination of providing a custom logger should restore the previous behavior.

We'll keep the defaults as they are, as we want to streamline f1 for unattended use, which I think should be the most common use case.

I'll see what that looks like, not sure exactly when I'll get to it, but I'll keep this open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants