d5e016ec599d6af669225815345e9cb223ed144f
resolve's comment claimed to find "the most recent session matching this thread and bot" and took whichever the store returned first. On the NellDB store that is document order -- by session ID -- so it was effectively arbitrary. The tracker cache is in-memory, so every restart re-resolves from the store, and the operator could be dropped back into a session they had left with /new, answering against pre-/new history. Probed over 10 restarts, 4 landed in the older session. LastActiveAt was populated on every record and never read. resolve now picks by LastActiveAt, which also makes it independent of the two backends disagreeing: SQLite's GetByChannel orders created_at DESC and NellDB's did not, and the conformance suite did not pin it. listAllLocked reversed document order and passed that off as recency, so List -- documented newest-first, and what /sessions and the dashboard render -- returned reverse-lexicographic order. It now sorts on LastActiveAt, falling back to CreatedAt for records never touched. Refs archie-core-7s3
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%