Hi @kadern0. Thanks for your PR.

I'm waiting for a stackrox member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

/ok-to-test

Images are ready for the commit at e7f892a.

To use with deploy scripts, first export MAIN_IMAGE_TAG=3.72.x-426-ge7f892a67c.

Hi @kadern0. Thank you for addressing this! Now, please help us to fix the G103 alerts:

pkg/concurrency/error_signal.go:117:51: G103: Use of unsafe calls should be audited (gosec)
	if !atomic.CompareAndSwapPointer(&s.errPtr, nil, unsafe.Pointer(&err)) {
	                                                 ^
pkg/concurrency/error_signal.go:132:12: G103: Use of unsafe calls should be audited (gosec)
		errPtr:  unsafe.Pointer(&[]error{nil}[0]),
		         ^
pkg/concurrency/error_signal.go:147:13: G103: Use of unsafe calls should be audited (gosec)
		statePtr: unsafe.Pointer(newErrorSignalState()),
		          ^

@kadern0 pkg/concurrency/error_signal.go has some issues

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>