test: failing reproducer - snap developer-id not asserted
Metadata
Current evaluation
PR claims to fix #445 by parsing developer-id from snap-revision assertions, but the fix (commit 5df1922) does not exist in the codebase and the issue remains open.
Suggested action: close stale
Reason: The PR claims to be 'Fixed in 5df1922' but that commit does not exist in the repository and the described changes (parsing developer-id from snap-revision assertions) are not present in the current codebase. Issue #445 remains open with no maintainer engagement since November 2023, and the PR has been inactive for 136 days without any actual mergeable changes.
Impact:
45
Quick Win:
33.75
Staleness:
85
Complexity:
25
Confidence:
70
Issue body
## Reproducer for #445
When a snap changes ownership (e.g. transferred from a personal account to an org), the `snap-revision` assertion contains a `developer-id` that differs from the current publisher. The current code only asserts the publisher's account, not the developer's, causing `snap ack` to fail with:
```
error: cannot assert: assert failed: cannot resolve prerequisite assertion: account (<developer-id>)
```
### Root cause
`_get_assertions_file()` in `snap_installer.py` always queries `account-id=<publisher_id>` but never reads the `developer-id` field from the snap-revision assertion bytes to also fetch `account-id=<developer-id>`.
### Fix
Parse the snap-revision assertion to extract `developer-id`. If it differs from the publisher-id, also fetch `["account", "account-id=<developer-id>"]` and include it in the assertion file.
Closes #445
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
45
Quick Win:
33.75
Staleness:
85
Complexity:
25
Confidence:
70
|
close stale | PR claims to fix #445 by parsing developer-id from snap-revision assertions, but the fix (commit 5df1922) does not exist in the codebase and the issue remains open. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
55
Complexity:
20
Confidence:
65
|
needs review | Proposed fix for snap developer-id assertion issue #445. Adds a reproducer test and modifies the assertions file function to fetch developer account assertions. Currently pending review with no maintainer feedback for 91 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
70
Complexity:
15
Confidence:
90
|
close stale | Reproducer test for snap developer-id assertion failure. The underlying issue is already resolved in commit 5df1922. PR has been inactive for 79 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
65
Complexity:
20
Confidence:
90
|
close stale | Reproducer for snap developer-id assertion failure. Fix already applied in commit 5df1922, which parses snap-revision bytes and fetches the developer account. PR is resolved and inactive. |
Update history
| Date | Change |
|---|---|
| updated | |
| updated |
Related work
-
Related To:
canonical/craft-providers#445
(confidence 95%)
This PR claims to fix issue #445, but the fix was never actually applied to the codebase.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #445 `developer-id` of the `snap-revision` is not asserted | craft-providers | open | Valid bug: craft-providers fails to assert developer-id when it differs from publisher-id, causing snap injection to fail for snaps like rockcraft revision 1194. Issue is 1032 days old with no maintainer comments. |