Skip to content

fix(PLU-326): stop treating failed analyses as complete in status poller - #29

Merged
akashb95 merged 1 commit into
mainfrom
plu-326-binary-ninja-analysis-always-fails-with-ghidra-binary
Aug 26, 2026
Merged

fix(PLU-326): stop treating failed analyses as complete in status poller#29
akashb95 merged 1 commit into
mainfrom
plu-326-binary-ninja-analysis-always-fails-with-ghidra-binary

Conversation

@akashb95

@akashb95akashb95 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Context:
PeriodicChecker._worker, the analysis-status poller, treated any status other than Queued/Processing as a completed, successful analysis — including Error. That caused it to persist the failed analysis as attached and then crash on a downstream 422, since the backend has no function map to return for a failed analysis.

**Context:**
`PeriodicChecker._worker` treated any status other than `Queued`/`Processing` as a
completed, successful analysis, including `Error`. That persisted the failed analysis
as attached and then crashed on a downstream 422, since the backend has no function map
to return for a failed analysis.
**This diff:**
- Branches on the real `revengai.StatusInput` enum: in-progress statuses (`Uploaded`/`Queued`/`Processing`) reschedule as before, `Complete` runs the existing success path, and anything else (`Error`, or unrecognised) is now a terminal failure that is logged via `log_error` with no callback, sync, or persistence.
- Rewords the two `except` blocks' log messages, which wrap the whole worker rather than just the status check and previously mislabeled failures as "during status check".
- Removes the dead, never-emitted `update_text_signal`/`_update_text_slot` Qt signal copy-pasted from an unrelated class.
@akashb95
akashb95 marked this pull request as ready for review August 26, 2026 09:22
@akashb95
akashb95 requested a review from a teamAugust 26, 2026 09:22
@akashb95
akashb95 merged commit 86e4735 into mainAug 26, 2026
2 checks passed
@akashb95
akashb95 deleted the plu-326-binary-ninja-analysis-always-fails-with-ghidra-binary branch August 26, 2026 10:11
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@akashb95@vgoat21