← Back to issue list

Disambiguate artifacts type in case of multiple valid inspections

View original Github issue

Metadata

Project
fetch-service
Number
#304
Type
issue
State
open
Author
cmatsuoka
Labels
—
Created
Updated
Closed
—

Current evaluation

Fetch Service has no deterministic type when several craft inspectors approve; metadata is last-write-wins. A Sourcecraft header approach is under discussion, with a reproducer in #296.

Suggested action: keep open

Reason: Maintainer tigarmo said general disambiguation is difficult and proposed a Sourcecraft-specific Git header, while cmatsuoka linked #296 for examples and a reproducer. The inspected Sourcecraft inspector still approves whenever sourcecraft.yaml exists, and no resolving commit or PR was found, leaving a valid cross-component design problem open.

Evaluated by: mr-cal-bot

Impact: 55 Quick Win: 10 Complexity: 72 Confidence: 93 Actionability: 66

Issue body

### What needs to get done Decide an implement a strategy to select the file type for an artifact approved by multiple inspectors, e.g. a file project containing both charmcraft.yaml and rockcraft.yaml. ### Why it needs to get done Currently a rule for this situation is not specified and the last approved inspector run wins.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 55
Quick Win: 10
Complexity: 72
Confidence: 93
Actionability: 66
keep open Fetch Service has no deterministic type when several craft inspectors approve; metadata is last-write-wins. A Sourcecraft header approach is under discussion, with a reproducer in #296.
stealth/space-bunny-alpha
Impact: 62
Quick Win: 12
Complexity: 63
Confidence: 82
Actionability: 54
keep open Fetch Service selects artifact metadata from the last inspector to approve projects containing both charmcraft.yaml and rockcraft.yaml. A sourcecraft header was proposed, but the cross-project design remains unresolved.
stealth/space-bunny-alpha
Impact: 42
Quick Win: 6
Complexity: 78
Confidence: 88
Actionability: 64
keep open Artifact filename selection is undefined when one project is approved by multiple inspectors, such as one containing both charmcraft.yaml and rockcraft.yaml; currently the last approval wins.
qwen/qwen3.6-35b-a3b
Impact: 45
Quick Win: 20
Staleness: 75
Complexity: 55
Confidence: 65
Support Request: 15
needs triage Design decision needed for artifact type selection when multiple inspectors approve an artifact. Open for 646 days with no labels, assignee, or maintainer triage.

Update history

Date Change
created

Related work

  • Related To: fetch-service#296 (confidence 96%)

    Explicitly linked by the maintainer as providing more examples and a reproducer for the ambiguous CRAFT package type.

Related issues

No related issues found above the similarity threshold.