Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
Critical: Logic bug in existing package detection for URL packages.
Lines 138 and 140 have a mismatch that can cause incorrect version comparisons:
is_installed=true.next()These could reference different packages when multiple versions exist in the database. The query at lines 120-133 doesn't filter by
is_installedorversion, so it can return multiple package records (e.g., different versions where some are installed and others are not).Example scenario:
Query returns:
[PackageV1(is_installed=false), PackageV2(is_installed=true)]is_already_installed = true(because V2 is installed)existing_install = Some(PackageV1)(wrong package!)This will cause incorrect update/sync decisions and potential unwrap panics.
🔎 Proposed fix
This ensures
existing_installalways references the actually installed package (if any), making the subsequent logic correct.📝 Committable suggestion