File dispute not working

Metadata

Project: snapcraft (launchpad)
Number: #1771767
Type: issue
State: open
Author: ~cprov
Labels: —
Created: 2018-05-17 08:28 AM UTC
Updated: 2020-08-03 09:55 PM UTC
Closed: —

Current evaluation

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.

Suggested action: close stale

Reason: The issue is ~8.3 years old with zero comments, no labels, and no maintainer interaction (last activity ~6 years ago), and the reported behavior concerns the store API's error code for the dispute flow, which is server-side and not fixable in this client repo. The snapcraft store integration has since been substantially restructured (modern snapcraft/store module and the separate craft-store library), so the original reproduction against the old /dev/api/register-name/ endpoint is no longer applicable. Confidence is moderate because repo tools had no pinned SHA, so I could not verify whether the dispute flow still exhibits the same error code.

Impact: 25 Quick Win: 15.0 Staleness: 95 Complexity: 40 Confidence: 60 Support Request: 10

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
2026-09-01 08:18 AM UTC	qwen/qwen3.8-27b	Impact: 25 Quick Win: 15.0 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.
2026-07-23 11:56 AM UTC	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.
2026-07-22 12:20 PM UTC	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.
2026-07-09 11:53 PM UTC	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.
2026-06-21 02:05 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 95 Complexity: 20 Confidence: 85 Support Request: 10	close stale	Dispute filing returns incorrect 409 error instead of expected already_claimed response. Issue remains open with zero maintainer comments after over 8 years.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.