fix: restore main/main.go entry point so luxd builds#124
Open
hanzo-dev wants to merge 2 commits into
Open
Conversation
…#104) Consolidating to single canonical ARC fleet. Killing duplicate lux-build scale set. All callers → hanzo-build-linux-amd64 (max 30 on DO) and hanzo-build-linux-arm64 (max 30 on GKE T2A Ampere). One and only one ARC fleet across hanzo/lux/zoo/liquidity. Includes build-linux-binaries.yml (release tarball) in addition to the docker + debian package workflows. No behavior change. Co-authored-by: Hanzo AI <dev@hanzo.ai>
main/ has been absent from `main`, so every build path targeting ./main — Makefile build/install/build-release, scripts/build.sh, .goreleaser.yml, and the release CI workflows — fails with 'stat main: no such file or directory'. This restores the entry point from clean-main (f2ff019); it still matches current APIs (config.BuildFlagSet/BuildViper/GetNodeConfig, node.New(*node.Config, log.Factory, log.Logger), version.CurrentApp). Verified: `go build -o build/luxd ./main` succeeds and the binary runs (`luxd --version` -> luxd/1.23.25). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
3 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.
Problem
main/is absent frommain, so every build path that targets./mainfails withcouldn't find main file: stat main: no such file or directory:Makefile→build:/install:/build-release:scripts/build.sh(line 117:go build … "${REPO_ROOT}/main").goreleaser.ymlrelease pipelinebuild-ubuntu-arm64-release.yml,build-linux-binaries.yml,build-win-release.yml,test-database-replay.ymlThe repo root has no
package mainnode entry point (onlycheck_interface.go, a//go:build toolshelper). Soluxdcannot be built frommaintoday.Fix
Restores
main/main.go(the node daemon entry point) fromclean-main(f2ff0199d). It wiresconfig.BuildFlagSet → BuildViper → GetNodeConfig → log.NewFactoryWithConfig → ulimit.Set → node.New → Dispatch, with a--versionshort-circuit and SIGINT/SIGTERM handling. All referenced APIs still exist on currentmainand thenode.New(*node.Config, log.Factory, log.Logger)signature matches exactly.Validation
Single file,
+101/-0. Nogo.mod/go.sumchanges required.