Suppressing GOMAXPROCS in info log

[thezim]

Is there any way to suppress the Leaving GOMAXPROCS=16: CPU quota undefined from info logs. Even if you define a value for GOMAXPROCS it gets logged with an indication that is inheriting/respecting the set value. Large logs are a pain to look at.

20:49:06 [Info] [Thread 0] Indexing file: packages/microsoft.win32.systemevents/6.0.0/microsoft.win32.systemevents.6.0.0.nupkg
20:49:07 [Info] Waiting for scan to complete on JFrog Xray...
20:49:07 [Info] Waiting for scan to complete on JFrog Xray...
20:49:10 [Info] 2024/06/06 20:49:04 maxprocs: Leaving GOMAXPROCS=16: CPU quota undefined

20:49:10 [Info] [Thread 2] Indexing file: packages/mono.texttemplating/2.2.1/mono.texttemplating.2.2.1.nupkg
20:49:11 [Info] Waiting for scan to complete on JFrog Xray...
20:49:12 [Info] 2024/06/06 20:49:06 maxprocs: Leaving GOMAXPROCS=16: CPU quota undefined

20:49:12 [Info] [Thread 1] Indexing file: packages/mstest.testadapter/3.1.1/mstest.testadapter.3.1.1.nupkg
20:49:13 [Info] Waiting for scan to complete on JFrog Xray...
20:49:16 [Info] 2024/06/06 20:49:10 maxprocs: Leaving GOMAXPROCS=16: CPU quota undefined

20:49:16 [Info] [Thread 2] Indexing file: packages/mstest.testframework/3.1.1/mstest.testframework.3.1.1.nupkg
20:49:17 [Info] Waiting for scan to complete on JFrog Xray...
20:49:17 [Info] 2024/06/06 20:49:06 maxprocs: Leaving GOMAXPROCS=16: CPU quota undefined

[eyalbe4]

@thezim, Will you be able to a open a new issue, but this time choose the "Audit and Scan" option, so that the issue receives visibility by the relevant team? You can then close this issue.

[thezim]

Issue submitted here.

https://github.com/jfrog/jfrog-cli-security/issues/80

Closing this issue.