File dispute not working
Metadata
Current evaluation
Name-dispute registration moved from the API to the Store web UI; users confirmed the unified page succeeds only after two submits, and the remaining dashboard defect lacks resolution.
Suggested action: keep open
Reason: The reporter confirmed the maintainer's reproduction that the first submission returns already_registered and only the second succeeds. The original registrant_comment API path was intentionally removed, but the remaining Store/dashboard double-submit defect is valid and clearly scoped; long inactivity alone does not justify closure.
Evaluated by: mr-cal-bot
Impact:
40
Quick Win:
12
Complexity:
62
Confidence:
87
Actionability:
78
Issue body
# Summary
When registering a snap name that already exists filing a dispute is not working.
# Steps to reproduce
## On API
- Register a snap that already exists
/dev/api/register-name/
{
"snap_name": "toto"
}
Response:
409 Conflict
{
"error_list": [{'message': "'toto' is already registered.", 'code': 'already_registered'}]
}
- File a dispute
/dev/api/register-name/
{
"snap_name": "toto",
"registrant_comment": "I want this awesome snap name"
}
Response:
409 Conflict
{
"error_list": [{'message': "'toto' is already registered.", 'code': 'already_registered'}]
}
# Expected behaviour
## On API
- Register a snap that already exists
/dev/api/register-name/
{
"snap_name": "toto"
}
Response:
409 Conflict
{
"error_list": [{'message': "'toto' is already registered.", 'code': 'already_registered'}]
}
- File a dispute
/dev/api/register-name/
{
"snap_name": "toto",
"registrant_comment": "I want this awesome snap name"
}
Response:
409 Conflict
{
"error_list": [{'message': "You already registered a claim for 'toto'.", 'code': 'already_claimed'}]
}
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
12
Complexity:
62
Confidence:
87
Actionability:
78
|
keep open | Name-dispute registration moved from the API to the Store web UI; users confirmed the unified page succeeds only after two submits, and the remaining dashboard defect lacks resolution. | |
| stealth/space-bunny-alpha |
Impact:
43
Quick Win:
18
Complexity:
48
Confidence:
82
Actionability:
79
|
keep open | Confirmed name-dispute form requires two submissions through the API-provided register-snap URL; a working direct dispute URL exists, but the returned URL remains broken. | |
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
26
Complexity:
20
Confidence:
88
Actionability:
82
|
close resolved | Snap-name dispute registration returned already_registered instead of already_claimed; the legacy dispute workflow was later removed after register and dispute URLs were consolidated. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
15
Staleness:
95
Complexity:
40
Confidence:
60
Support Request:
10
|
close stale | 2017 report that filing a snap-name dispute via the register-name API returns an already_registered error instead of already_claimed. No labels, no comments, no maintainer activity for ~6 years; store integration has since been rewritten. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
5
|
close stale | API endpoint for filing snap name disputes returns incorrect 409 error instead of expected claim conflict response. Issue is unlabelled, has zero comments, and is over eight years old with no maintainer engagement. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
5
|
close stale | Dispute filing for registered snap names returns 409 already_registered instead of expected already_claimed. Unlabeled, 0 comments, inactive for ~6 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
|
needs triage | API dispute filing for existing snap names returns "already_registered" instead of expected "already_claimed". Unlabelled, zero maintainer comments, inactive for nearly six years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1613609
(confidence 92%)
PR #732 and commit fea4dfff4 replaced an obsolete dispute URL with the unified page, but do not establish that the later double-submit defect was fixed.
Related issues
No related issues found above the similarity threshold.