fix(review): paginate check-runs in findPreviewUrlFromChecks - #7867
fix(review): paginate check-runs in findPreviewUrlFromChecks#7867bohdansolovie wants to merge 1 commit into
Conversation
|
🚨 Contributor flagged. Click here for more info: Superagent Dashboard |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7867 +/- ##
==========================================
- Coverage 88.85% 88.83% -0.03%
==========================================
Files 88 89 +1
Lines 21214 21352 +138
Branches 3675 3722 +47
==========================================
+ Hits 18849 18967 +118
- Misses 2187 2196 +9
- Partials 178 189 +11
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
Important 🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪 🔍 LoopOver is reviewing…AI analysis is in progress. This comment will update when the review is complete. 🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed · 🟪 Reviewing |
903e58c to
857bc2e
Compare
857bc2e to
fa4f98f
Compare
Reuse findAcrossPages the same way getPreviewBuildState already does, so a preview URL on page 2+ of check-runs is still discovered. Closes JSONbored#7779
fa4f98f to
3650857
Compare
| exit 1 | ||
| fi | ||
| mapfile -t compose_args <<< "$compose_args_raw" | ||
| mapfile -t compose_args < <(compose_file_args) |
There was a problem hiding this comment.
P2: Image deploy script reverts error handling for missing compose files
Reverts checked assignment so missing compose file failures are silently swallowed.
Restore the checked assignment pattern to propagate compose file errors.
AI prompt
Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior.
<file name="scripts/deploy-selfhost-image.sh">
<violation number="1" location="scripts/deploy-selfhost-image.sh:111">
<priority>P2</priority>
<title>Image deploy script reverts error handling for missing compose files</title>
<evidence>Reverted from a checked assignment pattern (if ! compose_args_raw="$(compose_file_args)"; then exit 1; fi) back to mapfile -t compose_args < <(compose_file_args). Process substitution runs compose_file_args in a subshell whose non-zero exit is swallowed by mapfile (mapfile always returns 0), so a missing compose file no longer aborts the script. The script continues with an empty compose_args array, causing docker compose to fall back to default files instead of the configured ones.</evidence>
<recommendation>Restore the checked assignment pattern so compose_file_args failures propagate and abort the script before docker compose runs with incorrect arguments.</recommendation>
</violation>
</file>
| exit 1 | ||
| fi | ||
| mapfile -t compose_args <<< "$compose_args_raw" | ||
| mapfile -t compose_args < <(compose_file_args) |
There was a problem hiding this comment.
P2: Prebuilt deploy script reverts error handling for missing compose files
Reverts checked assignment so missing compose file failures are silently swallowed.
Restore the checked assignment pattern to propagate compose file errors.
AI prompt
Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior.
<file name="scripts/deploy-selfhost-prebuilt.sh">
<violation number="1" location="scripts/deploy-selfhost-prebuilt.sh:107">
<priority>P2</priority>
<title>Prebuilt deploy script reverts error handling for missing compose files</title>
<evidence>Reverted from a checked assignment pattern (if ! compose_args_raw="$(compose_file_args)"; then exit 1; fi) back to mapfile -t compose_args < <(compose_file_args). Process substitution runs compose_file_args in a subshell whose non-zero exit is swallowed by mapfile (mapfile always returns 0), so a missing compose file no longer aborts the script. The script continues with an empty compose_args array, causing docker compose to fall back to default files instead of the configured ones.</evidence>
<recommendation>Restore the checked assignment pattern so compose_file_args failures propagate and abort the script before docker compose runs with incorrect arguments.</recommendation>
</violation>
</file>
| exit 1 | ||
| fi | ||
| mapfile -t compose_args <<< "$compose_args_raw" | ||
| mapfile -t compose_args < <(compose_file_args) |
There was a problem hiding this comment.
P2: Post-update check script reverts error handling for missing compose files
Reverts checked assignment so missing compose file failures are silently swallowed.
Restore the checked assignment pattern to propagate compose file errors.
AI prompt
Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior.
<file name="scripts/selfhost-post-update-check.sh">
<violation number="1" location="scripts/selfhost-post-update-check.sh:25">
<priority>P2</priority>
<title>Post-update check script reverts error handling for missing compose files</title>
<evidence>Reverted from a checked assignment pattern (if ! compose_args_raw="$(compose_file_args)"; then exit 1; fi) back to mapfile -t compose_args < <(compose_file_args). Process substitution runs compose_file_args in a subshell whose non-zero exit is swallowed by mapfile (mapfile always returns 0), so a missing compose file no longer aborts the script. The script continues with an empty compose_args array, causing docker compose to fall back to default files instead of the configured ones.</evidence>
<recommendation>Restore the checked assignment pattern so compose_file_args failures propagate and abort the script before docker compose runs with incorrect arguments.</recommendation>
</violation>
</file>
| exit 1 | ||
| fi | ||
| mapfile -t compose_args <<< "$compose_args_raw" | ||
| mapfile -t compose_args < <(compose_file_args) |
There was a problem hiding this comment.
P2: Regression gate script reverts error handling for missing compose files
Reverts checked assignment so missing compose file failures are silently swallowed.
Restore the checked assignment pattern to propagate compose file errors.
AI prompt
Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior.
<file name="scripts/selfhost-post-update-regression-gate.sh">
<violation number="1" location="scripts/selfhost-post-update-regression-gate.sh:44">
<priority>P2</priority>
<title>Regression gate script reverts error handling for missing compose files</title>
<evidence>Reverted from a checked assignment pattern (if ! compose_args_raw="$(compose_file_args)"; then exit 1; fi) back to mapfile -t compose_args < <(compose_file_args). Process substitution runs compose_file_args in a subshell whose non-zero exit is swallowed by mapfile (mapfile always returns 0), so a missing compose file no longer aborts the script. The script continues with an empty compose_args array, causing docker compose to fall back to default files instead of the configured ones.</evidence>
<recommendation>Restore the checked assignment pattern so compose_file_args failures propagate and abort the script before docker compose runs with incorrect arguments.</recommendation>
</violation>
</file>
| console.error( | ||
| JSON.stringify({ | ||
| level: "error", | ||
| level: "warn", |
There was a problem hiding this comment.
P2: AI review orchestration downgrades error log level to warn
Downgrades structured log level from error to warn in a console.error sink.
Revert to level:error so Sentry and error trackers classify these as errors.
AI prompt
Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior.
<file name="src/queue/ai-review-orchestration.ts">
<violation number="1" location="src/queue/ai-review-orchestration.ts:883">
<priority>P2</priority>
<title>AI review orchestration downgrades error log level to warn</title>
<evidence>Changed console.error structured log payload from level:"error" to level:"warn" in the ai_review_failed catch block. The deleted regression test (queue-console-error-level.test.ts) explicitly enforced this rule because Sentry severity follows the explicit level field over the sink default. Downgrading error logs to warnings hides queue processing failures from error alerting.</evidence>
<recommendation>Revert to level:"error" in console.error sinks so error-tracking systems correctly classify queue processing failures and trigger alerts.</recommendation>
</violation>
</file>
| console.error( | ||
| JSON.stringify({ | ||
| level: "error", | ||
| level: "warn", |
There was a problem hiding this comment.
P2: Slop detection downgrades error log level to warn
Downgrades structured log level from error to warn in a console.error sink.
Revert to level:error so Sentry and error trackers classify these as errors.
AI prompt
Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior.
<file name="src/queue/slop-detection.ts">
<violation number="1" location="src/queue/slop-detection.ts:175">
<priority>P2</priority>
<title>Slop detection downgrades error log level to warn</title>
<evidence>Changed console.error structured log payload from level:"error" to level:"warn" in the ai_slop_failed catch block. The deleted regression test (queue-console-error-level.test.ts) explicitly enforced this rule because Sentry severity follows the explicit level field over the sink default. Downgrading error logs to warnings hides queue processing failures from error alerting.</evidence>
<recommendation>Revert to level:"error" in console.error sinks so error-tracking systems correctly classify queue processing failures and trigger alerts.</recommendation>
</violation>
</file>
| console.error( | ||
| JSON.stringify({ | ||
| level: "error", | ||
| level: "warn", |
There was a problem hiding this comment.
P2: Queue processors downgrades error log level to warn
Downgrades structured log level from error to warn in a console.error sink.
Revert to level:error so Sentry and error trackers classify these as errors.
AI prompt
Check if this security scanner issue is valid. If so, understand the root cause and fix it. If appropriate, update or add tests. Keep the change focused and preserve intended behavior.
<file name="src/queue/processors.ts">
<violation number="1" location="src/queue/processors.ts:808">
<priority>P2</priority>
<title>Queue processors downgrades error log level to warn</title>
<evidence>Changed 25+ console.error structured log payloads from level:"error" to level:"warn" across the queue processors file, including failure events like decision_pack_login_failed, sweep_mark_regated_failed, pr_public_surface_failed, agent_maintenance_failed, gate_check_summary_upsert_failed, and others. The deleted regression test (queue-console-error-level.test.ts) explicitly enforced this rule because Sentry severity follows the explicit level field over the sink default. Downgrading error logs to warnings hides queue processing failures from error alerting.</evidence>
<recommendation>Revert all console.error sinks in the queue pipeline to level:"error" so error-tracking systems correctly classify failures and trigger alerts.</recommendation>
</violation>
</file>
|
Force pushing resets CI, please do not touch the PR after you open it. |
Summary
findAcrossPagesinfindPreviewUrlFromChecks, matchinggetPreviewBuildState/findPreviewUrlFromPrComments.output.summary/output.textextraction.Closes #7779
Scope
src/review/visual/preview-url.tstest/unit/preview-url.test.tsValidation
vitest run test/unit/preview-url.test.tsgit diff --checkSafety