You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1e1d429
Browse filesBrowse the repository at this point in the historyBrowse files
gluck
committed
merge: the notifications pit and the :models pit (#35)
Two pits, integrated on feat/pits and validated together.
NOTIFICATIONS (#34, plans/notifications.md). Everything the pager said
went through one slot of the status bar and was gone ten seconds later:
a turn that failed while you were reading something else left one string
in memory and a line in a log nobody opens mid-conversation. Now every
alert is POSTED to a 500-entry history first, and the bar and the pit are
two views of it: the alert as before, a "N unread" mark that outlives it
while warnings or errors are unread, and `space n` / `:notifications` for
the list. Repeats coalesce with digits folded, so a poller failing every
tick is one row that counts. The CLI's own WARN and ERROR records tee in.
Enter spells a row out the way the state pit opens a value, and the
picker paints errors red and warnings yellow.
:MODELS (#33). The model is a pit you choose in, and Enter sets it.
Found and fixed on the way: `[cli] notice_ttl` was documented and never
applied, so every alert held the bar for the built-in ten seconds.
The notifications pit was exercised in a real pty
(scripts/notifications-pty.sh) as well as in the suite.
0 commit comments