Skip to content

Plugin registry silently omits a rejected shared fallback package #2209

Closed

Description

@giswqs

A registry entry can declare both its shared package/sha256 and platform-specific packages. In crates/plugins/src/registry.rs::parse_noting, invalid platform packages increment skipped, but an invalid shared package sets whole = false without adding an omission when another platform package keeps the entry present. Users can therefore see a plugin missing its fallback package with no indication that one was rejected.

Original review. Source confirmed during the release sweep. Duplicate search checked registry/package issues and #2008; this concerns shared fallback accounting, separate from the total registry cap and skipped-entry notice fixes in #2196.

Count a shared package that was actually advertised but rejected, distinguish an absent fallback, and report one bounded notice with the plugin id and cause. Add invalid-address/hash cases beside a valid platform package, plus a clean absent-fallback control. No runtime reproduction is claimed here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions