Skip to content

fix: update always reports "failed" even when it succeeded - #7

Merged
pQu4k3r merged 1 commit into
mainfrom
develop
Sep 14, 2026
Merged

pQu4k3r merged 1 commit into
mainfrom
develop

Conversation

@pQu4k3r

@pQu4k3r pQu4k3r commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

lsConsole.runFinished() called self.finishedCallback() with no arguments, but both real callers (_update_finished and myCallback in plugin.py) declare it as finishedCallback(self, result=None) and branch on that result to decide success vs failure. Since it was never passed anything, result was always None (falsy), so _update_finished always took the "Update failed!" branch regardless of the actual outcome - even though the wget|sh install/update itself had completed fine.

Pass the same success flag already computed for self.callback (not self.errorOcurred), matching the line right above it.

lsConsole.runFinished() called self.finishedCallback() with no
arguments, but both real callers (_update_finished and myCallback in
plugin.py) declare it as finishedCallback(self, result=None) and
branch on that result to decide success vs failure. Since it was
never passed anything, result was always None (falsy), so
_update_finished always took the "Update failed!" branch regardless
of the actual outcome - even though the wget|sh install/update itself
had completed fine.

Pass the same success flag already computed for self.callback
(not self.errorOcurred), matching the line right above it.
@pQu4k3r
pQu4k3r merged commit f4c1ea8 into main Sep 14, 2026
12 checks passed
Sign up for free to 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.

1 participant