Open
Conversation
- Exclude hanzo-l2 from workspace (depends on external lux-consensus path) - Remove cargo clean from .github/Dockerfile (redundant in fresh COPY) - Fix binary name: hanzod/hanzo_node → hanzo-node in all Dockerfiles and scripts - Fix FROM AS casing and legacy ENV format warnings in Dockerfiles - Fix primitives test script to use correct crate name (hanzo-messages) - Fix only_linux_binary.yml binary path (hanzo_node → hanzo-node) - Update Dockerfile-RELEASE to use Rust 1.88 (was 1.75) - Delete 52 AI-generated slop files (markdown docs, shell scripts, logs, test files, backup)
Same issue as hanzo-l2: depends on external lux-consensus path that doesn't exist in CI environments.
- Remove hanzo-db from db-core test group (excluded from workspace) - Remove hanzo-baml from misc test group (doesn't exist in workspace)
- FTS: use shared-cache in-memory SQLite URI so all pool connections share the same FTS tables (fixes test-node "query is not read-only") - Dockerfile: add /root/.local/bin to PATH for ruff, pre-install MCP test server npm deps (fixes runner and llm-mcp tests) - fs-embed: run with --test-threads=1, clean up rename tests and remove stale #[ignore] (fixes env var race condition) - ARM64: add arm64 apt sources + libssl-dev:arm64 + OpenSSL cross- compile env vars (fixes aarch64-unknown-linux-gnu build) - Publish script: add hanzo-config, hanzo-vm, hanzo-ai-format, hanzo-compute, hanzo-mining to SERVICE_CRATES list
Empty OPENSSL_LIB_DIR causes openssl-sys to panic on x86_64 builds. Use conditional export inside run script instead of env block.
- Use AARCH64_UNKNOWN_LINUX_GNU_OPENSSL_* prefix so host build scripts don't try to link against aarch64 libs on x86_64 - Add shell: bash to Build step so it works on Windows runners
- Install uv and Python 3.12 for python_runner tests - Use target-specific AARCH64_UNKNOWN_LINUX_GNU_OPENSSL_* env vars so host build scripts don't link against aarch64 libs - Add shell: bash to Build step for Windows compatibility
The lzma-sys crate links against liblzma which was missing for aarch64.
Same pattern as the other ignored test in the same file — concurrent tests modify the global NODE_STORAGE_PATH env var.
Scope zip file handles in blocks so they drop before fs::copy. Add retry loop (5 attempts, 2s delay) for both deno and uv binary copies to handle Windows antivirus/indexing briefly locking files.
The same scoped zip handles + retry loop fix needs to apply to both hanzo-runner and hanzo-tools-runner — they have duplicate copy_assets.rs files. The previous commit only fixed hanzo-tools-runner.
Native amd64 (hanzo-build) + arm64 (hanzo-build-arm64) builds. No QEMU. Uses hanzoai/.github/.github/workflows/docker-build.yml Co-authored-by: Hanzo Dev <dev@hanzo.ai>
fix: prevent arm64 OOM during linking with lld + job limit
- compose.yml with node + engine services using GHCR images - build-docker.yml now uses hanzo-deploy-linux-amd64 runner - Release build (BUILD_TYPE=release) for production images - Image: ghcr.io/hanzoai/node
Revert to hanzoai/.github reusable workflow which handles runner selection and buildx setup. Add BUILD_TYPE=release build arg.
Build artifact should never be in git. Added to .gitignore. Removed LFS tracking from .gitattributes.
hanzo-dev
had a problem deploying
to
FROM_WALLET_PRIVATE_KEY
GitHub Actions
Error
hanzo-dev
had a problem deploying
to
FROM_WALLET_PRIVATE_KEY
GitHub Actions
Error
hanzo-dev
had a problem deploying
to
FROM_WALLET_PRIVATE_KEY
GitHub Actions
Error
hanzo-dev
had a problem deploying
to
FROM_WALLET_PRIVATE_KEY
GitHub Actions
Failure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
22 commits from upstream