wizardchen 5f94bbf237 fix(plugin): keep the activity example's feed as a key per entry ...

The activity example kept its whole feed (up to 100 entries) in one
key-value entry. About twenty Chinese messages filled the store's 64 KB
limit, after which every append failed: the feed froze and the notes
webhook answered 502 for good. Two events delivered at once also each
wrote back the list without the other's entry.

Each entry is now a key of its own under feed/, named by the time left
until a far date (so key order is newest first) and the event ID (so a
repeated delivery lands on the same key). The page lists the newest 100
and older entries are deleted as they fall off. Titles, failure reasons
and notes are cut to a bounded length. A feed stored by 1.1 moves to the
new keys the first time it is read. Version 1.2.0.

2026-09-26 21:41:41 +08:00

..

schemas

feat(plugin): event delivery and webhooks for plugins

2026-09-26 11:21:55 +08:00

ui

feat(plugin): redesign the plugin UI

2026-09-26 19:43:00 +08:00

icon.svg

feat(plugin): redesign the plugin UI

2026-09-26 19:43:00 +08:00

main.py

fix(plugin): keep the activity example's feed as a key per entry

2026-09-26 21:41:41 +08:00

package.sh

feat(plugin): redesign the plugin UI

2026-09-26 19:43:00 +08:00

plugin.yaml

fix(plugin): keep the activity example's feed as a key per entry

2026-09-26 21:41:41 +08:00

test_main.py

fix(plugin): keep the activity example's feed as a key per entry

2026-09-26 21:41:41 +08:00