Need a way to get to different 5.0 beta and release reports



7 years ago
6 years ago


(Reporter: Robert Kaiser, Assigned: brandon)


Firefox Tracking Flags

(Not tracked)



(1 attachment, 1 obsolete attachment)



7 years ago
In the new model, a final release like 5.0 should have both a beta and a release report for TCBS and graphs, but currently I get only one "5.0" entry in the version selection on stage. We need some way to get to the two different reports there.

Comment 1

7 years ago
Can we retroactively extend our sql changes backwards to include this?


7 years ago
Target Milestone: --- → 2.2

Comment 2

7 years ago
We can invent some label there for the "final release on beta" entry, like for example "5.0 (beta)" or something, as long as there's a way for us as users to know what it means.

Comment 3

7 years ago
OK.  Josh wrote a new stored procedure to try and find these in the data.  It's deployed on staging.  There's a lot of junk data, so there will likely be a few crashes aggregated that don't fit into the right bucket.

You will now see these showing up in the UI (as 6.0 (beta), 5.0 (beta), but the links are busted.  Will take a look at those next.


7 years ago
Assignee: nobody → bsavage

Comment 4

7 years ago
Over to Brandon to fix the UI.

If you're not using the version_string to retrieve these, then make sure you match on:
- product
- version
- release channel.

Comment 5

7 years ago
Created attachment 552667 [details] [diff] [review]
Patch for the UI

This patch fixes the 404 by correcting the regular expression that determines the proper URL. The rest of the data loads properly but the graphs are returning a 404.
Attachment #552667 - Flags: review?(chris.lonnen)

Comment 6

7 years ago
Chris, there is a patch to fix the URL issues in the bug. However, the middleware is returning an error on all requests for this, probably because "6.0 (beta)" is a string it can't understand. Here is the traceback:

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/", line 242, in process
    return self.handle()
  File "/usr/lib/python2.6/site-packages/", line 233, in handle
    return self._delegate(fn, self.fvars, args)
  File "/usr/lib/python2.6/site-packages/", line 396, in _delegate
    return handle_class(f)
  File "/usr/lib/python2.6/site-packages/", line 387, in handle_class
    return tocall(*args)
  File "/home/bsavage/trunk/socorro/webapi/", line 60, in GET
    raise Exception(stringLogger.getMessages())
Exception: ERROR Caught Error: <type 'exceptions.KeyError'>
ERROR ('Firefox', '6.0+(beta)')
ERROR trace back follows:
ERROR Traceback (most recent call last):
ERROR File "/home/bsavage/trunk/socorro/webapi/", line 46, in GET
    result = self.get(*args)
ERROR File "/home/bsavage/trunk/socorro/services/", line 86, in get
    return impl[table_type].twoPeriodTopCrasherComparison(cursor, parameters)
ERROR File "/home/bsavage/trunk/socorro/services/tcbs/", line 198, in twoPeriodTopCrasherComparison
ERROR File "/home/bsavage/trunk/socorro/lib/", line 47, in getId
    raise KeyError((product, version))
ERROR KeyError: ('Firefox', '6.0+(beta)')

When you resolve this, please combine it with my patch so that there is only one patch for this bug.
Assignee: bsavage → chris.lonnen

Comment 7

7 years ago
The space in the name is getting encoded, and decoding is a bit of a headache. It seems much simpler to prohibit the space in the version name. Is that possible?


7 years ago
Assignee: chris.lonnen → josh
Severity: normal → blocker

Comment 8

7 years ago
Josh: so basically instead of calling these "6.0 (beta)" we should call them "6.0(beta)" (no space).  Actions are therefore:
1.  modify the stored proc
2. rerun the backfill

Then you can kick this back over to lonnen for testing.
Actually, eliminating the space is a lot easier than that.

breakpad=# update product_versions set version_string = '5.0(beta)' where version_string = '5.0 (beta)';
breakpad=# update product_versions set version_string = '6.0(beta)' where version_string = '6.0 (beta)';

Done.  Fixing the SP and checking it in now.
Checked in. I'm done, back to brandon/lonnen.


7 years ago
Assignee: josh → chris.lonnen
Comment on attachment 552667 [details] [diff] [review]
Patch for the UI

It looks like this patch is already in 2.2 branch.

Do we need a corresponding mware fix per comment 6, or should this be backed out per comment 7? Sounds like the latter...
Backed out please.
(In reply to Laura Thomson :laura from comment #12)
> Backed out please.

With or without this patch, it still doesn't work.
Chris can you take a look? If not please kick it over to rhelmer or myself.

Comment 15

7 years ago
Created attachment 552884 [details] [diff] [review]
Correct patch for the webui

This is the correct patch for the UI bug that we're seeing here. For some reason, the wrong patch was uploaded and this was not previously caught.
Attachment #552667 - Attachment is obsolete: true
Attachment #552667 - Flags: review?(chris.lonnen)
Attachment #552884 - Flags: review?(rhelmer)
Comment on attachment 552884 [details] [diff] [review]
Correct patch for the webui

Yes this fixes the 404 on my dev instance
Attachment #552884 - Flags: review?(rhelmer) → review+

Comment 17

7 years ago
Applying the correct patch, along with Josh's changes to remove the space, solve this bug.
Assignee: chris.lonnen → bsavage
Last Resolved: 7 years ago
Resolution: --- → FIXED


7 years ago
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.