← Back to issue list

when a validation already exists, the error message is not nice and is displayed after entering the password

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1636981
Type
issue
State
open
Author
~elopio
Labels
store
Created
Updated
Closed
—

Current evaluation

Duplicate validation still prompts for a passphrase before the store returns a raw 409; current code signs before posting and needs a preflight error.

Suggested action: keep open

Reason: The report provides an exact reproduction, and the current command lists validations, signs the assertion, and only then calls post_validation without rejecting a duplicate, preserving the reported ordering problem. The store-labeled report was filed by a maintainer, and the later workaround comments explicitly belong to LP #1912332 rather than resolving this issue.

Evaluated by: mr-cal-bot

Impact: 32 Quick Win: 17 Complexity: 38 Confidence: 94 Actionability: 88

Issue body

I tried to create the same validation twice. The second time it fails displaying an error; but this error is shown after I entered my password. I think the error should be shown before signing the validation. $ snapcraft validate u1test20161026 ubuntu-core=3 Getting details for ubuntu-core Signing validation ubuntu-core=3 You need a passphrase to unlock the secret key for user: "default" 4096-bit RSA key, ID D017FEB3, created 2016-01-01 Received error 409: 'There is already a validation assertion stored for snap-id y8gqFXGKAfN5NoZtNRZHqWhB1C4jt3Gi in this context.' In addition to that, the error is not for humans. It shows the error code, the snap-id, and it's not nicely formatted.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 32
Quick Win: 17
Complexity: 38
Confidence: 94
Actionability: 88
keep open Duplicate validation still prompts for a passphrase before the store returns a raw 409; current code signs before posting and needs a preflight error.
stealth/space-bunny-alpha
Impact: 30
Quick Win: 19
Complexity: 28
Confidence: 84
Actionability: 88
close resolved Duplicate validate requests previously prompted for signing before exposing a raw 409; the current code preloads validations and advances assertion revisions, avoiding that conflict path.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 22
Complexity: 10
Confidence: 80
Actionability: 80
keep open The `snapcraft validate` command prompts for a GPG passphrase before checking if a validation assertion already exists, then shows a raw 409 error with internal snap-id. The duplicate check should happen before signing.
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18
Staleness: 90
Complexity: 40
Confidence: 45
Support Request: 10
close stale snapcraft validate shows a raw 409 error (with snap-id) only after the user enters their GPG passphrase when a validation already exists; the error should appear before signing and be human-readable. No comments, no activity for ~5.6 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 85
Support Request: 10
needs triage snapcraft validate displays a cryptic 409 API error with internal snap-IDs after prompting for a GPG passphrase. The error should appear before signing and be human-readable. No maintainer response in over 5 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 85
Support Request: 10
close stale Duplicate validation assertion error displays after password prompt and shows raw internal details instead of a user-friendly message. Issue is over 9 years old with no activity.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 15
Confidence: 80
Support Request: 5
close stale Duplicate validation assertions trigger a raw 409 API error with internal snap-IDs after GPG passphrase entry, lacking pre-validation checks and human-readable formatting. No maintainer response in over 5 years.

Update history

Date Change
created

Related work

  • Related To: snapcraft (launchpad)#1912332 (confidence 95%)

    A commenter explicitly stated that the revocation workaround documentation should have been added to LP #1912332 instead.

Related issues

No related issues found above the similarity threshold.