[MB-5275] Poor man's alerts can be 'prematurely eaten' sometimes Created: 09/May/12  Updated: 20/Jun/12  Resolved: 10/May/12

Status: Resolved
Project: Couchbase Server
Component/s: ns_server
Affects Version/s: 1.8.0
Fix Version/s: 1.8.1
Security Level: Public

Type: Bug Priority: Blocker
Reporter: Aleksey Kondratenko Assignee: Aleksey Kondratenko
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Anything that calls menelaus_alerts_srv:fetch_alerts will reset current list of alerts.

Particularly it was possible for some other smart client or moxi to 'eat' alerts. Which would incorrectly mark them as shown to user and not effectively shown to user.

Comment by Thuan Nguyen [ 10/May/12 ]
Integrated in github-ns-server-2-0 #349 (See [http://qa.hq.northscale.net/job/github-ns-server-2-0/349/])
    explicitly consume poor man's alerts. MB-5275 (Revision 2cfb9473a69bfff634698893d54eab673ada09a3)

     Result = SUCCESS
Aliaksey Kandratsenka :
Files :
* src/menelaus_web.erl
* priv/public/js/hooks.js
* src/menelaus_web_alerts_srv.erl
* priv/public/js/app.js
Comment by Aleksey Kondratenko [ 10/May/12 ]
Comment by Aleksey Kondratenko [ 20/Jun/12 ]
I disagree _a lot_ with recent subject change. We really had problems with moxi 'eating' alerts. And causing them to not be shown to user.
Comment by Farshid Ghods (Inactive) [ 20/Jun/12 ]
thanks. can you please help in modifying the subject to make it easier to end user understand what was fixed. ( what alerts were not displayed and under what circumstances )
IMHP "poor man alert" is not descriptive enough for our end user
Comment by Aleksey Kondratenko [ 20/Jun/12 ]
Any alerts were could be potentially eaten. Poor man's alerts is how we call them. I have no idea about how docs call them
Generated at Fri Nov 21 21:11:38 CST 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.