go fix applied the modernizers. One rewrite it got wrong is corrected here: a
reverse loop over runes became a range over slices.Backward that bound the index
and the value to the SAME name, which does not compile and would have compared a
rune to an index if it had. The value gets its own name.
Co-authored-by: Hanzo Dev <[email protected]>
github.com has no runner for hanzo-build-linux-amd64, so a caller under
.github/workflows is a gate that can never be scheduled. This is the ~7-line
caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.
Co-authored-by: Hanzo Dev <[email protected]>
Currency bump. No go.mod directive changes.
The golang images ship GOTOOLCHAIN=local, so the moment a go.mod
directive moves past the image's Go version the build hard-fails
mid-stage. GOTOOLCHAIN=auto lets the toolchain resolve instead; the
pinned base stays the hermetic fast path.
alpine3.21 is no longer published for any golang 1.26.x tag; 3.23 is the
lowest alpine variant still cut for 1.26.5. The builder is CGO_ENABLED=0,
so the static binary is unaffected and the alpine:3.21 runtime stage stands.
Co-authored-by: Hanzo Dev <[email protected]>
This workflow ran on a self-hosted actions-runner-controller pool. ARC is
decommissioned: CI executes inside git.hanzo.ai (Gitea Actions, .hanzo/workflows)
and delivery is cd.hanzo.ai reconciling the reviewed image pin in
hanzoai/universe. GitHub is a mirror and runs nothing.
Removed rather than repointed — there is no GitHub-side pool to move to, and
leaving it would keep ARC load-bearing.
This workflow ran on a self-hosted actions-runner-controller pool. ARC is
decommissioned: CI executes inside git.hanzo.ai (Gitea Actions, .hanzo/workflows)
and delivery is cd.hanzo.ai reconciling the reviewed image pin in
hanzoai/universe. GitHub is a mirror and runs nothing.
Removed rather than repointed — there is no GitHub-side pool to move to, and
leaving it would keep ARC load-bearing.
Panic-driven denial of service in the AWS SDK for Go v2 EventStream decoder:
aws/protocol/eventstream v1.4.8 -> v1.7.14
service/s3 v1.27.11 -> v1.106.0
Bumping s3 alone does NOT compile here, and the reason is worth recording: the
S3 client changed ContentLength from int64 to *int64, and two pinned consumers
predate that change —
feature/s3/manager v1.11.33 download.go:439
invalid operation: resp.ContentLength > 0 (mismatched types *int64 and untyped int)
snowflakedb/gosnowflake v1.6.19 s3_storage_client.go:107
cannot use out.ContentLength (*int64) as int64 value in struct literal
So manager -> v1.22.35 and gosnowflake -> v1.19.1 are not incidental churn;
they are the rest of the same fix. That in turn exposed missing go.sum entries
under modernc.org (this fork carries ~20 database drivers), closed by tidy.
Verified against a measured baseline: go build ./... exit 0, and go test ./...
is 25 ok / 33 fail BOTH with and without this change — identical. Those tests
need live database servers and fail in a sandbox regardless; none of the 33 is
a regression from this commit.
The datastore:// migration driver is now a self-contained golang-migrate
database.Driver that opens through github.com/hanzo-ds/go (the native
ClickHouse-wire driver registered as the database/sql name "datastore").
The ClickHouse-specific migration logic (multi-statement exec,
schema_migrations DDL, cluster/engine config, Version/SetVersion/Drop/Lock)
is ported directly into database/datastore, so it no longer embeds or
imports the upstream database/clickhouse driver or
github.com/ClickHouse/clickhouse-go.
- Delete database/clickhouse (driver + test + examples) and
internal/cli/build_clickhouse.go.
- internal/cli/build_datastore.go drops the clickhouse-go blank import.
- go.mod: drop github.com/ClickHouse/clickhouse-go, add
github.com/hanzo-ds/go v1.0.1; tidy. Zero clickhouse-go in go.mod,
go.sum, and the module/dependency graph.
- Port the driver test + example migrations under database/datastore
(integration test requires a live datastore/clickhouse-wire backend).
- Update README, release workflow build tags, bug report template.
Co-authored-by: Hanzo Dev <[email protected]>
Registers "datastore://" as a URL scheme that delegates to the
ClickHouse driver. This allows golang-migrate to natively connect
to Hanzo Datastore instances without URL rewriting in scripts.
zeekayandHanzo Dev
