Page MenuHomePhabricator

Allow the notifications from Aphlict debug messages to expire.
ClosedPublic

Authored by joshuaspence on May 30 2014, 1:40 PM.
Tags
None
Referenced Files
F18800185: D9339.id.diff
Fri, Oct 17, 3:52 PM
F18791917: D9339.diff
Thu, Oct 16, 6:37 PM
F18757993: D9339.id22246.diff
Sun, Oct 5, 8:20 PM
F18757975: D9339.id22248.diff
Sun, Oct 5, 8:16 PM
F18623462: D9339.id.diff
Sep 15 2025, 3:53 PM
F18616462: D9339.diff
Sep 14 2025, 5:41 PM
F18391698: D9339.id.diff
Aug 29 2025, 7:45 AM
F18391616: D9339.id22246.diff
Aug 29 2025, 7:42 AM
Subscribers

Details

Summary

Currently, debugging (log) messages from the Aphlict client trigger a visible notification in the web UI (when notification.debug is enabled). After D9327, the log messages can be quite verbose and seem to "block" legitimate notifications because they are not automatically dismissed.

Test Plan

Enabled notification.debug and observed that the debugging notifications expired and closed after a few seconds.

Diff Detail

Repository
rP Phabricator
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

joshuaspence retitled this revision from to Allow the notifications from Aphlict debug messages to expire..
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence added a reviewer: epriestley.
epriestley edited edge metadata.

Haha, I hit this too.

This revision is now accepted and ready to land.May 30 2014, 4:47 PM
epriestley updated this revision to Diff 22248.

Closed by commit rP323c529c3bac (authored by @joshuaspence, committed by @epriestley).