linkify report format from crash-reports

RESOLVED FIXED

Status

()

RESOLVED FIXED
11 years ago
7 years ago

People

(Reporter: timeless, Assigned: reed)

Tracking

Details

(Reporter)

Description

11 years ago
if a user pastes an incident id, it will be of this form:
bp-de11b4fd-f3e6-11dc-8b25-001a4bd43ed6 

if an analyst copies a portion of the report from the server it will be of this form:
UUID    de11b4fd-f3e6-11dc-8b25-001a4bd43ed6

bugzilla has always linkified both equivalents for talkback :(
Fortunately, talkback reports were uniquely identifiable because they were a specific format (specific number of letters on each end with digits in the middle, always a certain length).  Breakpad IDs, without the bp- in front, are not only not uniquely identifiable as breakpad IDs, but there are other known uses for identifier number in the exact same format:

  Extension IDs within Firefox
  Registry keys in Windows
  Device UUID identifiers in Linux

And thats just a few...
(Reporter)

Comment 2

11 years ago
i meant that the form should be:
/^UUID\s+:uuid:$/

not just /:uuid:/
(Assignee)

Updated

11 years ago
Assignee: justdave → reed
OS: Windows XP → All
Hardware: PC → All
(Assignee)

Comment 3

11 years ago
Changed to: \b(?:UUID\t|bp\-)([a-f0-9]{8}\-[a-f0-9]{4}\-[a-f0-9]{4}\-[a-f0-9]{4}\-[a-f0-9]{12})\b

Will go live during next update from prodpatches.
Status: NEW → ASSIGNED
(Reporter)

Comment 4

11 years ago
fwiw, copying w/ ie8b1 on my laptop yields this:
UUID de11b4fd-f3e6-11dc-8b25-001a4bd43ed6 

the paste in c0 (which has 4 spacs) was from the same incident id, you'll need to use:
\s+ instead of \t, sorry.

note that talkback has two formats:
TB41575058X
Incident ID: 41575058
The latter is the lesser known format but is the one similar to the UUID format that I was asking to have linkified.
(Assignee)

Comment 5

11 years ago
My change went live. It's \t still, but if we start to see reports where \s+ would be better, I'll change it.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.