jpmschweitzer/clide
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
559 Commits 1 Branch 17 Tags
6337bec152c97c19c918d08fca1d882dc58d9a33
Commit Graph
3 Commits
Author SHA1 Message Date
jpmschweitzerandClaude Opus 4.7 70ce6c270e fix untrusted-workspace RCE in dugite git resolution (T-98) 
Drop the workspaceRoot parameter from resolveToolchainPaths /
Toolchain.resolvePaths entirely. The old code resolved
\`<workspaceRoot>/native/dugite/bin/git\` as the git binary before
falling back to PATH — a malicious repo could commit an executable
at that path and clide would run it on the first auto-fired
git.status (which fires automatically on workspace open).

Dugite now resolves against trusted locations only:
1. CLIDE_DUGITE_DIR env var (dev override).
2. <exe-parent>/dugite/bin/git (production bundle).
3. <exe-parent>/lib/dugite/bin/git (alternate bundle layout).

Test plants `native/dugite/bin/git` in a temp workspace and asserts
the resolved git path is NOT inside the workspace.

Callers updated (8 sites): main.dart, backend_entry.dart twice,
test_app.dart three times (compute now wraps a no-arg call), plus
five test fixtures. backend.dart's now-vestigial hintRoot left in
the struct for cleanup under T-99.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-17 20:56:02 +02:00
jpmschweitzerandClaude 5cad98224f keep the clide.dart barrel Flutter-free 
`lib/kernel/src/toolchain.dart` is a `ChangeNotifier`, so it pulls in
`package:flutter/foundation.dart`. `GitClient` and `PqlClient` imported
it for the resolved binary paths, which leaked Flutter through the
`package:clide/clide.dart` barrel — breaking `dart test` on every core
subsystem suite (`ci/test_core.sh`), since pure Dart can't compile
Flutter packages.

Split the Flutter-free pieces into `toolchain_paths.dart`: `ResolvedPaths`,
`resolveToolchainPaths`, and a new read-only `ToolchainView` interface
with a `ToolchainView.resolved()` const factory. `Toolchain` now
implements `ToolchainView`; the clients depend on the interface. Core
test setups that built a `Toolchain` just to call `applyResolved`
switch to the factory.

Co-Authored-By: Claude <noreply@anthropic.com>
 2026-05-14 21:21:09 +02:00
jpmschweitzerandClaude Opus 4.7 8d98efc900 test sweep: cover src/pql/client.dart (T-91)
test / unit + widget + golden + a11y (push) Failing after 31s
test / integration_test (xvfb) (push) Has been skipped
test / bundle smoke (xvfb 5s) (push) Has been skipped
test / daemon subprocess + web WASM smoke (push) Has been skipped
test / dart doc (lib API) (push) Failing after 1m2s 
18 integration tests in test/pql/client_test.dart driving the real
pql 1.4.30 binary against the clide vault. Covers the methods the
existing test/daemon/pql_commands_test suite didn't reach: backlinks,
tags, query, search, decisionValidate, decisionRead, decisionList
with filters, decisionShow with --with-refs / --with-tickets,
ticketList with status / team / assigned / decision filters,
ticketShow with --with-context / --with-blockers, ticketBoard with
--team. Plus PqlException.toString and the two error paths in _run
(ProcessException from a bad binary path, non-zero exit code from
the validator).

Coverage: src/pql/client.dart 43/92 -> 89/92 (97%). The 3 remaining
lines are an unreachable null-coalesce branch in _runList and
PqlException's field initialisers (lcov phantom).

Total coverage 73.34% -> 73.88%.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-05-11 19:11:52 +02:00