jfrog / jfrog/jfrog-cli-security
Audit/Scan - Logs are interfering with the output table
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
Describe the bug
On commands that produce a table output, in some cases logs are print in the middle of the table, which breaks its structure.
This probably happens due to the fact that the logs are printed to stdErr and the table to stdOut.
To Reproduce
Currently easily reproduced on Azure Devops with the build-scan / audit tasks.
Expected behavior
All logs are print before or after the table.
Screenshots
Versions
- JFrog CLI version: 2.9.0
- JFrog CLI operating system: macOS
- Latest version of both of the Azure DevOps Artifactory/JFrog Extensions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the build-scan and audit commands, reproducing the issue in Azure DevOps with the JFrog CLI and Artifactory/Azure DevOps extensions. Inspect how logs use stderr while table output uses stdout; done means logs appear entirely before or after the table without breaking its structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100