-
Notifications
You must be signed in to change notification settings - Fork 0
fix: skip closed/fixed issues during migration (#133) #141
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,7 +7,7 @@ export function handleApiError(error, baseURL) { | |
| if (error.response) { | ||
| const { status, data, config } = error.response; | ||
| if (status === 401 || status === 403) { | ||
| throw new AuthenticationError(`Authentication failed for SonarQube: ${data.errors?.[0]?.msg || 'Invalid credentials'}`, 'SonarQube'); | ||
| throw new AuthenticationError(`Authentication failed for SonarQube: DATA = ${data} - ${data.errors?.[0]?.msg || 'Invalid credentials I believe'}`, 'SonarQube'); | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Debug text in authentication error messageMedium Severity The authentication error message was changed to include debug artifacts: raw Reviewed by Cursor Bugbot for commit 397bab4. Configure here. |
||
| } | ||
| const message = data.errors?.[0]?.msg || data.message || error.message; | ||
| throw new SonarQubeAPIError(`SonarQube API error (${status}): ${message}`, status, config.url); | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| /** | ||
| * Returns true if the issue is closed or fixed and should be excluded from migration. | ||
| * Covers all lifecycle variants: | ||
| * - Modern lifecycle: explicit CLOSED or FIXED status | ||
| * - Classic lifecycle: RESOLVED status with resolution=FIXED | ||
| */ | ||
| export function isClosedOrFixed(issue) { | ||
| if (issue.status === 'CLOSED' || issue.status === 'FIXED') return true; | ||
| if (issue.status === 'RESOLVED' && issue.resolution === 'FIXED') return true; | ||
| return false; | ||
| } |


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.
Debug log leaks authentication token to logs
High Severity
An accidentally committed debug statement logs the SonarQube authentication token in plaintext via
logger.info. The"OKO"prefix is a clear debug marker. This exposes sensitive credentials in application logs, which could end up in log aggregation systems, CI output, or shared log files.Reviewed by Cursor Bugbot for commit 397bab4. Configure here.