Skip to content

chore(deps): bump github.com/mattn/go-sqlite3 from 1.14.40 to 1.14.45#10

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/mattn/go-sqlite3-1.14.44
Open

chore(deps): bump github.com/mattn/go-sqlite3 from 1.14.40 to 1.14.45#10
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/mattn/go-sqlite3-1.14.44

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 23, 2026

Copy link
Copy Markdown
Contributor

Bumps github.com/mattn/go-sqlite3 from 1.14.40 to 1.14.45.

Commits
  • 7ca6a97 Merge pull request #1404 from mattn/sqlite-amalgamation-3053002
  • e2ab931 Upgrade SQLite to version 3053002
  • 75d8c60 Merge pull request #1403 from dxbjavid/bind-text64-length
  • d1ab49c bind via sqlite3_bind_text64/blob64 to avoid 32-bit length truncation
  • b3b5216 Merge pull request #1402 from dxbjavid/guard-resulttext-oversize
  • 2af23f7 guard oversized string length in ResultText
  • 1a7264c Merge pull request #1400 from calmh/unsafereflect
  • 9accb92 Merge pull request #1399 from calmh/uintsize
  • 9d6bf2c Merge pull request #1338 from calmh/dbstat
  • fed9970 modernise reflect.SliceHeader to unsafe.Slice
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels May 23, 2026
Jason-Shen2 added a commit that referenced this pull request May 24, 2026
Task #9. Wires the per-pane harness cache + ipcMain handlers + preload
surface so the renderer can talk to the integrated agent runtime
without touching wavesrv. No renderer code consumes this yet —
usePiChat (task #12) is the first consumer.

New: emain/agent-ipc.ts (~210 LOC)
  - harnessCache: Map<sessionPath, PaneHarness>
  - subscriptions: per-(sender, sessionPath) tracking + auto-release
    on sender 'destroyed'
  - registerAgentIpcHandlers() wires:
      handle "agent:create-session"      (cwd) → AgentSessionMeta
      handle "agent:list-sessions-for-cwd" (cwd) → AgentSessionMeta[]
      handle "agent:send"                (opts) → {sessionMetadata}
                                          (returns immediately; prompt
                                           runs in background)
      on     "agent:abort"               (sessionPath)
      on     "agent:subscribe"           (sessionPath)
      on     "agent:unsubscribe"         (sessionPath)
  - Single "agent:event" channel carries {sessionPath, event} —
    mirrors the dir-watch pattern (renderer strings never embed in
    channel names, security per emain-ipc.ts:518 comment).

Wired in: emain/emain-ipc.ts initIpcHandlers() calls
  registerAgentIpcHandlers() before the rest of the init body.

Preload: emain/preload.ts
  - Single ipcRenderer.on("agent:event") dispatcher fans events to
    per-sessionPath callback sets (same shape as dirWatchCallbacks).
  - exposeInMainWorld api.agent namespace:
      createSession(cwd) → Promise<AgentSessionMeta>
      listSessionsForCwd(cwd) → Promise<AgentSessionMeta[]>
      send(opts) → Promise<{sessionMetadata}>
      abort(sessionPath)
      subscribe(sessionPath, callback) → unsubscribe fn

Types: frontend/types/custom.d.ts
  - ElectronApi.agent: matching surface declaration
  - AgentSendOptions: send-payload shape (provider/model/reasoning +
    pane context + optional sessionMetadata)

Send semantics
  send() returns immediately with the resolved sessionMetadata so the
  renderer can write block.meta and begin streaming. The prompt() call
  fires in background; AgentHarness emits the assistant message stream
  + any errors through "agent:event". This matches the architecture
  doc §5.2 + §6.3 contract.

What's NOT in this commit
  - Renderer-side hook (usePiChat) — task #12; the legacy useChat /
    HTTP-to-wavesrv path stays live until that lands.
  - Crest-specific tools — task #10; AgentHarness is built with
    tools: [] for now.
  - Permissions hook — task #11; no beforeToolCall yet.
  - Integration test against an actual LLM — task #14.

Verification
  - tsc --noEmit -p tsconfig.json: 0 new errors in emain/ (58
    pre-existing project-wide).
  - vitest run: 126/126 (no test changes; existing surface intact).
  - npx tsx emain/agent/_spike.ts: imports + harness construction
    still load cleanly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Jason-Shen2 added a commit that referenced this pull request May 24, 2026
Task #10 (partial). Six pure-Node tools as pi AgentTool definitions,
wired through agent-ipc.ts buildPaneHarness so the agent can do real
coding work in v1: read files, write files, surgical multi-edit, list
directories, fetch URLs, run shell commands.

Files
  emain/agent/tools/_paths.ts        expandHome + requireAbsolute helpers
  emain/agent/tools/read-file.ts     read_file (parallel, offset/limit)
  emain/agent/tools/write-file.ts    write_file (mkdir -p parent)
  emain/agent/tools/multi-edit.ts    multi_edit (atomic, unique or replaceAll)
  emain/agent/tools/list-dir.ts      list_dir (type-marked, capped)
  emain/agent/tools/web-fetch.ts     web_fetch (Node fetch, 1MB cap, timeout)
  emain/agent/tools/shell-exec.ts    shell_exec (/bin/sh -c, 64KB/stream cap,
                                       SIGTERM-then-SIGKILL on timeout/abort)
  emain/agent/tools/index.ts         getDefaultTools() + DEFAULT_TOOL_NAMES
  emain/agent/tools/tools.test.ts    29 tests (including loopback HTTP for
                                       web_fetch — fully offline & deterministic)

Wiring
  emain/agent-ipc.ts ensurePaneHarness() now passes tools:
  getDefaultTools() to buildPaneHarness. Permissions hook from task #11
  gates the tools (default v1 policy is allowAll, so they're all
  available; a future renderer-side setting can flip to the explicit
  allowlist by passing opts.allowedTools).

What's NOT in this commit (deferred from the original 24-tool scope)
  Tools that need crest-specific renderer / wavesrv state via wshrpc:
    ask_user_question, browser, create_block, focus_block,
    get_scrollback, headless_shell_exec, transfer_to_user
  Tools that need design decisions (auth, sandboxing, sub-agent
  semantics) before porting:
    cmd_history, dangerous, file_tracker, long_running_*, spawn_task,
    todo, write_plan, search (ripgrep dep)
  These are documented as TODO in tools/index.ts and the autonomous
  handoff doc. The 6 we did port cover the minimum viable agent.

Design notes
  - Schemas via typebox (Type.Object/String/Number/Optional/Array) —
    matches pi's harness/types.ts convention. Static<typeof schema>
    drives the execute() params type.
  - All tools require absolute or ~-prefixed paths to avoid ambiguity
    with the harness env's cwd (which is the pane cwd at harness
    construction time, not at tool-call time).
  - Output bytes are capped per-tool (read_file by lines via
    offset/limit, list_dir maxEntries, web_fetch 1MB, shell_exec
    64KB/stream) so a runaway tool doesn't blow the LLM context.
  - shell_exec is executionMode: "sequential" to avoid concurrent
    state-mutating shell commands within one assistant turn; other
    tools are "parallel" where harmless.
  - web_fetch tests spin up a loopback http.Server on a random port
    rather than mocking fetch — same code path the real tool uses
    against any URL, no network needed for CI.

Verification
  - vitest run: 163/163 (was 134; +29 tool tests).
  - tsc --noEmit -p tsconfig.json: 0 new errors in emain/.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Jason-Shen2 added a commit that referenced this pull request May 24, 2026
…up plan

Snapshot for the morning review. Records what landed in the
autonomous session (tasks #9, #10-partial, #11, #12-half), what was
explicitly NOT done and why (high-blast-radius wiring, deferred tool
designs, missing API-key access), the architecture invariants the
new code commits to, and a recommended pickup order keyed to how
much time the user has when they come back.

Read this first in the morning. The architecture story itself is
already in docs/agent-runtime-architecture.md; this doc is just the
"where we are right now" companion.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Jason-Shen2 added a commit that referenced this pull request May 24, 2026
Step 6/6 of task #12. With AgentChatHost + AgentBlockElement
now driven by usePiChat (commit c0222e1), nothing imports the
following any more — delete:

  frontend/app/store/aitypes.ts                          (~150 LOC)
    WaveUIMessage / WaveUIMessagePart / WaveUIDataToolUse +
    Citation / SuggestedRule / AskUserQuestion* / ApprovalDestination
    types. Pi shape replaces all of this end-to-end.

  frontend/app/term/render/tool-use-card.tsx             (~275 LOC)
  frontend/app/term/render/tool-action-header.tsx        (~91 LOC)
  frontend/app/term/render/tool-command-card.tsx         (~61 LOC)
  frontend/app/term/render/tool-diff-card.tsx            (~170 LOC)
  frontend/app/term/render/tool-ask-card.tsx             (~451 LOC)
  frontend/app/term/render/citation-chips.tsx            (~132 LOC)
    Wave-era rich tool-card UX (approval flow, askquestion takeover,
    file/line citations, diff view). These supported the 11 tools
    deferred-to-deprecated in task #10 (ask_user_question, dangerous,
    transfer_to_user, file_tracker, write_plan, etc.); no surviving
    code path needs them. The new ToolCallCard (committed dc9cd6e)
    is the lean replacement: name + input preview + collapsible
    result, no approval / citation / askquestion machinery.

Total dead-code deletion: ~1330 LOC across 7 files.

npm deps removed:
  @ai-sdk/react  (the React useChat hook crest used pre-pi)
  ai             (the underlying ai-sdk core)
  + 16 transitive dependencies via npm uninstall.

Verification
  - tsc --noEmit -p tsconfig.json: 58 pre-existing errors unchanged.
  - vitest run: 172/172 pass.

Task #12 (usePiChat + drop @ai-sdk/react) is now complete. Tasks
#13 (delete Go agent stack) and #14 (E2E regression) unblocked.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Jason-Shen2 added a commit that referenced this pull request May 24, 2026
- #14 (4-provider E2E) and #15 (block.meta camelCase) marked cancelled
  with rationale.
- #10 noted as superseded by #16.
- Add #16: reused pi's coding-agent tools (read/write/edit/ls/bash/
  find/grep + web_fetch), with the pi-tui/image/fd-rg deviations.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Bumps [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3) from 1.14.40 to 1.14.45.
- [Release notes](https://github.com/mattn/go-sqlite3/releases)
- [Commits](mattn/go-sqlite3@v1.14.40...v1.14.45)

---
updated-dependencies:
- dependency-name: github.com/mattn/go-sqlite3
  dependency-version: 1.14.44
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps): Bump github.com/mattn/go-sqlite3 from 1.14.40 to 1.14.44 chore(deps): bump github.com/mattn/go-sqlite3 from 1.14.40 to 1.14.45 Jun 7, 2026
@dependabot dependabot Bot force-pushed the dependabot/go_modules/github.com/mattn/go-sqlite3-1.14.44 branch from 45d2ba7 to 5a22f24 Compare June 7, 2026 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants