Repository navigation
Conversation
|
@claude review |
|
Claude finished @hhubert6's task in 1m 17s —— View job 🦀 ReviewSeverity: 🔴 blocking · 🟡 should-fix · 🟢 nit
<verdict: 1 blocking, 1 should-fix, 1 nit> |
|
@claude review |
5b82607 to
e1dbf14
Compare
kraleppa
left a comment
There was a problem hiding this comment.
Looks great, please address @GuzekAlan suggestions and we can merge
A batch that reports new drops, here or by the agent, and the run's end append a :dropped entry with the count before the events that follow. Dropped entries are capped with the trace events since a flood sheds a batch at a time.
sessions/0 lists the sessions that can be read and entries/3 returns a page of a session's entries from a seq on, oldest first. truncated? says the page starts at or before an entry evicted from memory, so a reader knows the history it got is incomplete.
start/1 resolves the configured pids on the node in the caller, like configure/3, and passes the node and config it used; the Tracer refuses with :changed if a configure replaced them in between. agent_args is gone, so a session only needs its config to be started again.
…ault active/0 returns just the session. entries/2 takes :since, :before and :limit over [since, before): with :since a page reads forward oldest first, for MCP; without it, the newest entries before :before come newest first, for the UI. truncated? is true only when an evicted entry falls in the range the page covers.
|
@claude review |
|
Claude finished @hhubert6's task in 1m 28s —— View job 🦀 ReviewSeverity: 🔴 blocking · 🟡 should-fix · 🟢 nit
<verdict: 0 blocking, 1 should-fix, 0 nit, 1 ponytail · net: -3 lines possible> |
Drop sessions/0; listing saved sessions belongs in a query module.
The stop reasons and log entries get types.
|
@claude review |
702275b to
5b0a982
Compare
No description provided.