mirror of
https://github.com/kuhyx/signal-bot.git
synced 2026-11-10 20:37:03 +01:00
Krzysztof kuhy Rudnicki
405541be9b
One row per command attempt, not two aggregates written only on success. command_uses holds last-use only and daily_uses counts successes; both are rate-limiter state and both are written by store.record_use, which the dispatcher calls only when a handler returns cleanly. A gate refusal and a crash returned before it, so a command that failed every time looked exactly like one nobody ran, and nothing knew which command a counted message was. command_events now takes every attempt with its outcome, its duration and the item it served; upstream_calls takes every outbound request made while serving one. The two writes stay separate on purpose -- recording a refusal as a use is what slid the cooldown window forward every time somebody was told to wait -- and test_dispatcher_outcomes asserts last_used does not move. Backfilled from journald joined against message_events, with daily_uses filling the residual so the two sources cannot double-count. Two things were wrong on the first attempt and both were found by measuring rather than by reasoning: the window has to be symmetric, because sent_at_ms comes from the sender's phone and the journal stamp from this host (194 of 299 lines landed *before* their own message, by up to 3.2 s); and matching has to be a global closest-pair assignment, because per-row greedy cannot separate two commands seconds apart. Together those took the dropped rows from 137 to zero, and recovered 418 invocations back to 29 August. Also: !analityka in the group, twelve Polish lines, naming at most three people and only ones whose display name has been seen; an Analytics tab with Nivo charts; and continuous latency measurement, which answers the open question in DOCS-latency.md -- a text send is 235 ms and an image send about 2.2 s, so the upload really is where the time goes. EPHEMERAL_TABLES was doing two unrelated jobs and is now two tuples: what a schema bump rebuilds, and what leaving a group clears. daily_uses left the first (it is a backfill source now) and stayed in the second, and _drop_reshaped took over the repair a bump used to do for it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T4QTp3h5Q3MvfrwGV8xqPf
50 lines
1.3 KiB
JSON
50 lines
1.3 KiB
JSON
{
|
|
"name": "signal-bot-web",
|
|
"private": true,
|
|
"type": "module",
|
|
"packageManager": "pnpm@11.24.0",
|
|
"engines": {
|
|
"node": ">=24",
|
|
"pnpm": ">=10"
|
|
},
|
|
"scripts": {
|
|
"dev": "vite",
|
|
"build": "tsc -b && vite build",
|
|
"preview": "vite preview",
|
|
"lint": "tsc --noEmit && eslint .",
|
|
"test": "vitest run",
|
|
"coverage": "vitest run --coverage"
|
|
},
|
|
"dependencies": {
|
|
"@kuhyx/web-ui": "github:kuhyx/utils#web_ui-v0.3.1&path:/web_ui",
|
|
"@nivo/bar": "0.99.0",
|
|
"@nivo/calendar": "0.99.0",
|
|
"@nivo/core": "0.99.0",
|
|
"@nivo/heatmap": "0.99.0",
|
|
"@nivo/line": "0.99.0",
|
|
"react": "19.2.8",
|
|
"react-dom": "19.2.8"
|
|
},
|
|
"devDependencies": {
|
|
"@eslint/js": "10.0.1",
|
|
"@testing-library/jest-dom": "7.0.1",
|
|
"@testing-library/react": "16.3.3",
|
|
"@testing-library/user-event": "14.6.6",
|
|
"@types/node": "26.4.0",
|
|
"@types/react": "19.2.18",
|
|
"@types/react-dom": "19.2.5",
|
|
"@vitejs/plugin-react": "6.1.1",
|
|
"@vitest/coverage-v8": "4.1.11",
|
|
"eslint": "10.9.1",
|
|
"eslint-plugin-perfectionist": "5.10.1",
|
|
"eslint-plugin-react-hooks": "7.1.1",
|
|
"eslint-plugin-sonarjs": "4.2.0",
|
|
"eslint-plugin-unicorn": "74.0.0",
|
|
"jsdom": "30.0.1",
|
|
"typescript": "6.0.3",
|
|
"typescript-eslint": "8.68.0",
|
|
"vite": "8.2.2",
|
|
"vitest": "4.1.11"
|
|
}
|
|
}
|