Closed Bug 1513485 Opened 6 years ago Closed 6 years ago

Cannot manually create alerts

Categories

(Tree Management :: Perfherder, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: igoldan, Assigned: igoldan)

References

Details

Attachments

(3 files)

When trying to manually create alerts from Graphs view, the "Creating alert..." spinner is running forever and no alert is generated. I'm pretty sure this worked fine until the last deploy.
(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #0) > I'm pretty sure this worked fine until the last deploy. The last deploy was for https://github.com/mozilla/treeherder/compare/8ac1515494a8...6c3f8982873c , which includes both bug 1506671 and bug 1506553.
(In reply to Ed Morley [:emorley] from comment #1) > (In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #0) > > I'm pretty sure this worked fine until the last deploy. > > The last deploy was for > https://github.com/mozilla/treeherder/compare/8ac1515494a8...6c3f8982873c , > which includes both bug 1506671 and bug 1506553. I started debugging this. So far, it looks like bug 1506553 caused this issue. The createAlert() function from treeherder/ui/perfherder/helpers.js incorrectly used the create() function treeherder/ui/helpers/https.js
Assignee: nobody → igoldan
Blocks: 1506553
No longer blocks: 1450044
Status: NEW → ASSIGNED
Comment on attachment 9030751 [details] [review] Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/4367 Review of attachment 9030751 [details] [review]: ----------------------------------------------------------------- I made a push which re enables the create alert functionality. Bad thing now is the console dumps some errors I'm not yet sure how to follow. From the looks of it, Angular watches a function call expression. One of its parameters is somehow mutated during a digest cycle, causing an attribute access error. In case you're used with such peculiarities, please share your thoughts. Otherwise, I'll just resume the investigation tomorrow.
Attachment #9030751 - Attachment is patch: true
Attachment #9030751 - Attachment mime type: text/x-github-pull-request → text/plain
Attachment #9030751 - Flags: feedback?(sclements)
Attachment #9030751 - Attachment is patch: false
Attachment #9030751 - Attachment mime type: text/plain → text/x-github-pull-request
To clarify, the dependency tree change is since this regression bug was caused by bug 1506553 (comment 2), and we typically mark the regression bug as blocking the one that caused it. See bug 1513483 comment 4 for more details on this workflow :-)
Comment on attachment 9030751 [details] [review] Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/4367 :igoldan, can you give me the STR since I'm not that familiar with this part of the App? Does it require sheriff privileges to trigger an alert (if so, is there a way to work around that requirement for development purposes)? If you could paste the console message that would be helpful. One thing I noticed by looking at the `CreateAlert` method is that it's not catching errors so adding that and console.logging within that catch method and those nested `.then()`s might give more insight.
Attachment #9030751 - Flags: feedback?(sclements)
The STR are these: simply go to any graph, select a data point and from the black popup that shows up, click the "create" hyperlink.
I'm not sure about the privileges. I have to look that up in the source code.
Ok, so I see "No alert (log in as a a sheriff to create)" rather than "create hyperlink" on the tooltip. If you still need help debugging, please post a screen shot with the errors or paste them here.
(In reply to Sarah Clements [:sclements] from comment #6) > Does it require sheriff privileges to trigger an alert (if so, > is there a way to work around that requirement for development purposes)? I've set `is_staff` to 1 on stage+prod for your account (couldn't do prototype, since the user doesn't exist yet) - thought you had access already, but perhaps that was for your gmail? :-)
I do seem to have access now when logging in - thanks Ed!
(In reply to Sarah Clements [:sclements] from comment #9) > Ok, so I see "No alert (log in as a a sheriff to create)" rather than > "create hyperlink" on the tooltip. If you still need help debugging, please > post a screen shot with the errors or paste them here. Yes, I could use your help on this one. I've attached a screenshot with the errors.
I'm not seeing those errors when testing out your local commit and creating an alert (against stage). It seems to be generating Alerts properly. I did leave some comments on your pull request.
(In reply to Sarah Clements [:sclements] - away until 12/26 from comment #14) > I'm not seeing those errors when testing out your local commit and creating > an alert (against stage). It seems to be generating Alerts properly. I did > leave some comments on your pull request. Yes, I managed the fix the errors by tweaking the graphsctrl.html file.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: