Skip to content

v0.6.0 plan: open issues, priorities and API-team blockers #1182

Open

Description

@sdairs

v0.6.0 plan: open issues, priorities and API-team blockers
Replaces #939 (v0.5.1 follow-ups) and #757 (v0.5.0, shipped 2026-10-22). Started from a triage of all open issues on 2026-11-02. Audited 2026-11-10: every referenced issue was checked against main @ 1affed72 and closed only when its whole scope had landed.

Status 2026-11-13: every in-scope issue has a PR on stack #1285

Stack #1285 is now 86 PRs, main → #1276 … → #1438. The sections below are the 2026-11-10 audit and are not re-ticked; this table is current. Nothing is merged yet, so the issues are still open.

Area Issue → PR
CI repairs #1301 → #1385, #1387 · #1299 → #1388 · #1389 → #1390 · #1313 script → #1408
Small CLI, help, docs #1383 → #1386 · #1351 (+#1173) → #1391 · #935 → #1392 · #824 → #1393 · #845 → #1394 · #937 → #1395 · #926 → #1396 · #797 → #1397
Codebase review: bugs and consolidations #1320 → #1398 · #1316 → #1399 · #1318 → #1400 · #1338 → #1401 · #1315 → #1402 · #1313 → #1403 · #1331 → #1404 · #1336 → #1405 · #1335 → #1406 · #1314 → #1407
API library and analyzer #1345 → #1409 · #1344 → #1410 · #1346 → #1411 · #1348 → #1412 · #1343 → #1413 · #1347 → #1414
ClickPipes and ClickStack #1323 → #1415 · #1322 → #1416 · #1157 → #1417 · #1321 → #1418 · #928 → #1419
Features #1160 → #1420 · #1065 → #1421 · #1062 → #1422 · #1064 → #1423 · #129 → #1424 · #1163 → #1425 · #1161 → #1426 · #915 → #1427 · #1155 → #1428 · #250 → #1429 · #1154 phase 1 → #1430
CI, release, repo, tests #1309 → #1431 · #1352 → #1432 · #1350 → #1433 · #1349 → #1434 · #1353 → #1435 · #1339 → #1436 · #1341 → #1437 · #1340 → #1438

Before merge:

UAT follow-ups (2026-11-13, stack head b566f893)

Still out of scope or blocked: #1131, #1212, #800, #1096, #838, #1185; #1154 phases 2–3 wait on ClickHouse/control-plane#44995.

Stack #1285: review and merge

main → #1276 → #1281 → #1282 → #1283 → #1284 → #1288 → #1289 → #1354 → #1356. Every PR is mergeable, but the lower PRs fail "Test clickhousectl" because of #1304, and #1281 fails spec_coverage_test on its own head. Fix #1304 first, then merge the stack together.

Still open from the merged stack #1153:

Ready to work, in priority order

Status of each issue on main as of 2026-11-10:

  1. Local Postgres container names collide across projects #1160 local Postgres container names collide across projects (hits parallel worktree agents). Not started: no project hash in the name, one conflict error for both cases, no migration.
  2. Unify the Cloud service poll loops (delete --force and udf attach --wake) #1065 unify the Cloud service poll loops. PR feat(cloud): cloud udf --source-dir, --wait, and attach --wake #1033 was closed, but its UDF loop is in cloud/udfs.rs. Still to do: move it to shared.rs, poll stop on typed states, add a timeout to delete --force, use one interval, fold in the query loops.
  3. Define how local ClickHouse build artifacts are installed or linked #129 install or link locally built ClickHouse binaries (copy vs symlink, version identity, removal: undecided)
  4. Add a status command that reports CLI, auth, project and skills context in one call #1163 one status command for CLI, auth, project and skills context (local status from Add local postgres list and rename local server to local clickhouse (ch) #1159 is shipped; settle the naming against it)
  5. Add a command search so agents can find commands and flags by keyword #1161 command search for agents
  6. Always-applied server configs: ./clickhouse/config.d (project) and ~/.clickhouse/config.d (global) #1062 always-applied config.d (settle the open questions first)
  7. Local server selection: one rule for omitted names, or require a name (check telemetry first) #1064 local server selection (query telemetry first, then choose A or B)
  8. Direct Cloud database connections with JWT auth (no password, no Query API key) #1154 direct Cloud database connections with JWT (phase 1 can start now; phases 2–3 wait on the Cloud team)
  9. Choose an explicit override for agent-detected JSON output #915 override for agent-detected JSON output. Run the eval first; it shares a harness with Add a command search so agents can find commands and flags by keyword #1161. No override exists yet.
  10. Shell completions: decide how to serve them #1155 shell completions
  11. Design opt-in global local-server data directories #250 opt-in global data directories (revisit after Always-applied server configs: ./clickhouse/config.d (project) and ~/.clickhouse/config.d (global) #1062)
  12. Explore schema-assisted ClickPipe creation #928 schema-assisted ClickPipe creation. Unblocked: control-plane PR 45010 shipped isVirtual flags, and schema-discover shows them. The feature itself is undesigned: input format, selection, merge with --column, default-disabled fields.

Small CLI, help and docs fixes (findings from 2026-11-02)

None of these has started on main.

  1. Verify and document Postgres replica and restore credentials #935 docs and help: replicas follow the source password; restores use the source password as it was when the restore was requested. Correct the restore and read-replica create help and docs/guides/managed-postgres.md, and add "reset on the primary" to the reset-password help.
  2. Resolve whether whole-pipe ClickPipe PATCH applies settings #824 reject settings in a whole-pipe update file (exit 2), point to clickpipe settings update, and drop it from the documented root fields
  3. Clarify when successful ClickPipe state requests are no-ops #926 rewrite the start/stop/resync help from the guard table (resync also allows MongoDB and BigQuery), report that start on Completed has no effect, and fix next() and docs/reference/automation.md, which say start succeeds from Completed
  4. Align Postgres API timestamp grammar and detail-selector precision #797 slowquery get --timestamp help: the API ignores it. List window: inclusive, minute granularity. The upstream part is open.
  5. Define ClickPipe null-setting behavior across create and updates #937 docs: null is rejected, omitted keys are kept, send the default to reset (docs/reference/clickpipe-configuration.md). The upstream part is open.
  6. Verify source-kind rules before enforcing ClickPipe field mappings #845 check that fieldMappings exactly match destination.columns on create and update, for every source kind; reject [] and CDC/Iceberg mappings; widen the help beyond object storage

Codebase review (2026-11-10): in scope for remediation

63 issues (#1291–#1353) from a full review of main @ 1affed72, all on the v0.6.0 milestone. Each issue states how it was verified: reproduced, validated by source review, or reported by the review and not re-checked.

Fix first: bugs

  1. local remove accepts .. and absolute paths, deleting everything under ~/.clickhouse #1291 local remove .. deletes everything under ~/.clickhouse (reproduced)
  2. Cloud resource IDs are interpolated into API URL paths without encoding #1292 Cloud resource IDs are not path-encoded, so an ID can re-target a request (reproduced)
  3. local clickhouse commands accept a Postgres instance key and can overwrite or delete Postgres data #1296 local clickhouse commands accept a Postgres instance key and can overwrite or delete Postgres data
  4. OAuth tokens are written non-atomically with permissions set after the write, and refresh is unlocked #1295 OAuth tokens written non-atomically, mode set after the write, refresh unlocked
  5. Closed-stderr panics: 28 raw eprintln! calls remain in local and version-manager code #1302 closed-stderr panics: 28 raw eprintln! in local and version-manager code
  6. Exit code 3 and the cancelled error code are documented but nothing produces them #1293 exit code 3 and the cancelled code are documented but never produced
  7. Telemetry can attribute a Cloud failure to an earlier error that was swallowed #1294 telemetry attributes a Cloud failure to an earlier swallowed error
  8. OAuth write-command classification has wildcard arms and gaps #1303 OAuth write classification has wildcard arms and gaps
  9. Cloud JSON errors fall back to other for typed failures: Error::Cloud(String), update network errors, the from_error wildcard #1312 Cloud JSON errors fall back to other for typed failures (auth, update --check)
  10. cloud postgres config replace --file - cannot read stdin; file-or-stdin readers are duplicated #1297 cloud postgres config replace --file - cannot read stdin
  11. dotenv writer leaves $ unquoted, so values containing $ do not round-trip #1298 dotenv writer leaves $ unquoted
  12. Local server liveness trusts a persisted PID with no identity check #1299 local server liveness trusts a persisted PID with no identity check
  13. local clickhouse stop and remove contact Docker; sync state code is bridged to async Docker by reconnecting shims #1300 local clickhouse stop/remove contact Docker and fail when it is down
  14. Process discovery fails silently without pgrep/ps/lsof and runs on every ClickHouse command #1301 process discovery fails silently without pgrep/ps/lsof and runs on every ClickHouse command
  15. update overwrites package-managed installs and swaps the binary unsafely #1305 update overwrites package-managed installs and swaps the binary unsafely
  16. npm shim spawns the binary without signal handling, so Ctrl-C can detach an interactive client #1311 npm shim spawns the binary without signal handling
  17. --version test reaches the live release server; the update check has no test seam #1304 --version test reaches the live release server. Do first: it fails "Test clickhousectl" on every PR, including the stack #1285 PRs.
  18. .git-blame-ignore-revs lists nine SHAs that are not on main #1351 .git-blame-ignore-revs lists nine SHAs that are not on main

Decisions needed before work starts

With the #1157 ClickPipes and ClickStack split

Consolidations

Cloud:

Core:

Local:

Library and analyzer:

Tests

CI, release and repo

In scope for v0.6.0, blocked on the API team

The CLI-side steps are in the lists above; what remains here is upstream.

Blocked elsewhere

Closed

🤖 Generated with Claude Code

Activity

  1. self-assigned this
    on Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions