Add error code to Keychain failure logs

RESOLVED FIXED in Camino2.0

Status

Camino Graveyard
OS Integration
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: Stuart Morgan, Assigned: Stuart Morgan)

Tracking

({fixed1.8.1.15})

unspecified
Camino2.0
x86
Mac OS X
fixed1.8.1.15

Details

Attachments

(1 attachment)

fix
11.01 KB, patch
Jeff Dlouhy
: review+
Mike Pinkerton (not reading bugmail)
: superreview+
Details | Diff | Splinter Review
(Assignee)

Description

10 years ago
The keychain error messages are almost completely useless, we've had a couple of cases now where we needed the error codes to find out what was going on. We should always log the code in the failure message to make debugging easier.
(Assignee)

Comment 1

10 years ago
Created attachment 316939 [details] [diff] [review]
fix
Attachment #316939 - Flags: review?(Jeff.Dlouhy)

Comment 2

10 years ago
Comment on attachment 316939 [details] [diff] [review]
fix

r=jeff
Attachment #316939 - Flags: review?(Jeff.Dlouhy) → review+
(Assignee)

Updated

10 years ago
Attachment #316939 - Flags: superreview?(mikepinkerton)
Comment on attachment 316939 [details] [diff] [review]
fix

sr=pink
Attachment #316939 - Flags: superreview?(mikepinkerton) → superreview+
Given the Keychain-related problems in 1.6, we should take this there.
Flags: camino1.6.1+
(Assignee)

Comment 5

10 years ago
Landed on trunk and MOZILLA_1_8_BRANCH.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Keywords: fixed1.8.1.15
Resolution: --- → FIXED
Target Milestone: --- → Camino2.0
You need to log in before you can comment on or make changes to this bug.