Allow to enable and disable Windows-native notification Windows Event Log messages
Categories
(Toolkit Graveyard :: Notifications and Alerts, defect, P3)
Tracking
(firefox-esr102 unaffected, firefox111 wontfix, firefox112 fixed, firefox113 fixed)
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox111 | --- | wontfix |
firefox112 | --- | fixed |
firefox113 | --- | fixed |
People
(Reporter: gstoll, Assigned: nrishel)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
727.88 KB,
image/png
|
Details | |
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
|
Details | Review |
This was reported on Reddit, and I see it on the latest nightly.
I've attached a screenshot, and here are the details from one of the events:
Log Name: Application
Source: Firefox Nightly Notification Server
Date: 3/16/2023 9:00:07 AM
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-2J49KLU
Description:
The operation completed successfully.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Firefox Nightly Notification Server" />
<EventID Qualifiers="0">0</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-03-16T14:00:07.1472524Z" />
<EventRecordID>36989</EventRecordID>
<Correlation />
<Execution ProcessID="46020" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-2J49KLU</Computer>
<Security />
</System>
<EventData>
<Data>Error: Pipe write succeeded! (HandlePipeMessages:231)</Data>
</EventData>
</Event>
Reporter | ||
Comment 1•1 year ago
|
||
I should note that the notifications seem to display just fine for me, so that's not a problem.
Comment 2•1 year ago
|
||
Yeah, this was oversight on our (the implementors) parts: we dump some debug logging to the Windows Event Log and didn't implement a log level. I'll turn this ticket into that.
Technically, I think this will want to be a per-installation Windows registry entry that sets the log level. The log level should default to only logging errors.
Comment 3•1 year ago
|
||
Set release status flags based on info from the regressing bug 1781929
Assignee | ||
Comment 4•1 year ago
|
||
:nalexander we only log on notification invocation. A quick and easy way to implement this would be an about:config log level that gets passed along as an argument to the notification.
Assignee | ||
Comment 5•1 year ago
|
||
Updated•1 year ago
|
Nick, could you set a severity on this bug? Looks late for 111, what do we want to do with this issue for 112?
Assignee | ||
Comment 7•1 year ago
•
|
||
This has minor impact on users aside from mild confusion if checking through the event viewer. Changes are trivial to audit so probably a good beta uplift candidate since we're still making a mess?
Pushed by nrishel@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7544895e82c1 Trim down notification server event viewer logging unless `alerts.useSystemBackend.windows.notificationserver.verbose=true`. r=nalexander
Comment 9•1 year ago
|
||
bugherder |
Updated•1 year ago
|
Comment 10•1 year ago
|
||
The patch landed in nightly and beta is affected.
:nrishel, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox112
towontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 11•1 year ago
|
||
Comment on attachment 9324068 [details]
Bug 1822842 - Trim down notification server event viewer logging unless alerts.useSystemBackend.windows.notificationserver.verbose=true
. r=nalexander
Beta/Release Uplift Approval Request
- User impact if declined: Noisy false positive errors visible to users in Windows Event Logs.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Follows existing patterns in code (adding and parsing an argument to flip a a switch), trivial to audit.
- String changes made/needed:
- Is Android affected?: No
Comment 12•1 year ago
|
||
Comment on attachment 9324068 [details]
Bug 1822842 - Trim down notification server event viewer logging unless alerts.useSystemBackend.windows.notificationserver.verbose=true
. r=nalexander
Approved for 112.0b8
Comment 13•1 year ago
|
||
bugherder uplift |
Updated•10 months ago
|
Description
•