-
Notifications
You must be signed in to change notification settings - Fork 1.3k
fix: resolve race condition in NSQ scaler test #6843
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
Conversation
0715e74 to
2c7dd9c
Compare
|
Semgrep found 7
Detected 'io.WriteString()' writing directly to 'http.ResponseWriter'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package to render data to users. |
2c7dd9c to
141a445
Compare
95be662 to
b6b5dcf
Compare
…ter usage Signed-off-by: Rick Brouwer <[email protected]>
b6b5dcf to
d97ae73
Compare
|
/skip-e2e |
zroubalik
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT, thanks!
…ter usage (kedacore#6843) Signed-off-by: Rick Brouwer <[email protected]> Signed-off-by: kmoonwright <[email protected]>
…ter usage (kedacore#6843) Signed-off-by: Rick Brouwer <[email protected]> Signed-off-by: kmoonwright <[email protected]>
…ter usage (kedacore#6843) Signed-off-by: Rick Brouwer <[email protected]> Signed-off-by: David Pochopsky <[email protected]>
The
TestNSQAggregateDepthandTestNSQGetTopicProducerstests were failing intermittently due to a race condition in the mock HTTP server setup. The tests were usingatomic.NewInt32(-1)followed bycallCount.Inc()and multiplecallCount.Load()calls, which could result in inconsistent values when accessed concurrently.This happens in de amd64 test in PR #6834 and #6546
Checklist