ignite / cli

Ignite is a CLI tool and hub designed for constructing Proof of Stake Blockchains rooted in Cosmos-SDK
https://ignite.com
Other
1.26k stars 549 forks source link

FIX: #4415

Closed jgoodnight318 closed 5 days ago

jgoodnight318 commented 5 days ago

Expected Behavior

When running the testchaind version command, I expected it to output the version information for the binary, including details about the Cosmos SDK version and build metadata.

Actual Behavior

The testchaind version command produces no output at all—it returns silently without any errors or messages. Other commands, such as testchaind help and testchaind keys list, work as expected, so the binary itself appears to be functional.

I have tried the following: • Rebuilding the chain with ignite chain build and ignite chain clean. • Running the version command with --log_level debug and --trace to see if it outputs additional information, but nothing appears. • Inspecting the binary using strings ~/go/bin/testchaind | grep version to look for version metadata, but no relevant results were found.

Environment Details

•   OS: macOS (Darwin Kernel Version 23.4.0; arm64)
•   Ignite Version: v28.5.3-dev
•   Cosmos SDK Version: v0.50.10
•   Go Version: go1.23.3 darwin/arm64
•   Other Relevant Tools: Not applicable

Steps to Reproduce

1.  Scaffold a new blockchain using Ignite CLI:

ignite scaffold chain github.com/jgoodnight318/testchain

2.  Navigate to the project directory:

cd ~/projects/testchain

3.  Build the chain:

ignite chain build

4.  Attempt to run the version command:

~/go/bin/testchaind version

Notes

•   I have scaffolded a fresh chain and repeated the steps, but the issue persists.
•   Other commands like testchaind help and testchaind keys list work as expected.
•   The ignite chain build command completes without errors, and the binary is created in the correct location (~/go/bin/testchaind).
•   This behavior seems specific to the version command, possibly related to missing or improperly injected metadata during the build process.
julienrbrt commented 5 days ago

Hi, thanks for the report! Could you post a screenshot or some logs?

jgoodnight318 commented 5 days ago

Thank you for the quick reply! here are some logs from running various commands:

ignite version: ➜ testchain git:(main) ✗ ignite version Ignite CLI version: v28.5.3-dev Ignite CLI build date: undefined Ignite CLI source hash: undefined Ignite CLI config version: v1 Cosmos SDK version: v0.50.9 Your OS: darwin Your arch: arm64 Your go version: go version go1.23.3 darwin/arm64 Your uname -a: Darwin Jamess-MacBook-Pro.local 23.4.0 Darwin Kernel Version 23.4.0: Wed Feb 21 21:45:48 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T8122 arm64 Your cwd: /Users/jamesg/projects/testchain Is on Gitpod: false

after running ~/go/bin/testchaind help: ➜ testchain git:(main) ✗ ~/go/bin/testchaind help Start testchain node

Usage: testchaind [command]

Available Commands: comet CometBFT subcommands completion Generate the autocompletion script for the specified shell config Utilities for managing application configuration debug Tool for helping with debugging your application export Export state to JSON genesis Application's genesis-related subcommands help Help about any command in-place-testnet Updates chain's application and consensus state with provided validator info and starts the node init Initialize private validator, p2p, genesis, and application configuration files keys Manage your application's keys module-hash-by-height Get module hashes at a given height prune Prune app history states by keeping the recent heights and deleting old heights query Querying subcommands rollback rollback Cosmos SDK and CometBFT state by one height snapshots Manage local snapshots start Run the full node status Query remote node for status tx Transactions subcommands version Print the application binary version information

Flags: -h, --help help for testchaind --home string directory for config and data (default "/Users/jamesg/.testchain") --log_format string The logging format (json|plain) (default "plain") --log_level string The logging level (trace|debug|info|warn|error|fatal|panic|disabled or '*:,:') (default "info") --log_no_color Disable colored logs --trace print out full stack trace on errors

Use "testchaind [command] --help" for more information about a command.

after running ~/go/bin/testchaind version: ➜ testchain git:(main) ✗ ~/go/bin/testchaind version

➜ testchain git:(main) ✗

after running ➜ testchain git:(main) ✗ ignite chain build --verbose > build_logs.txt ➜ testchain git:(main) ✗ ignite chain build --verbose > build_logs.txt ➜ testchain git:(main) ✗ cat build_logs.txt [IGNITE] Initializing...Cosmos SDK's version is: v0.50.10 [IGNITE] [IGNITE] Building proto... [IGNITE] Installing dependencies... [IGNITE] Building the blockchain... [IGNITE] 🗃 Installed. Use with: testchaind

Also, I apologize in advance, I'm very new to all this and i'm trying my best to get everything right. I appreciate your help!

julienrbrt commented 5 days ago

Hey! Thanks for the logs, I see you have closed the issue. Have you resolved it? From what I can see you can run <appd> version --long and use a build tag to set the app version

jgoodnight318 commented 4 days ago

Hi Julien, yes I got some help in the ignite discord and that fixed the issue. Sent from my iPhoneOn Nov 21, 2024, at 1:12 AM, Julien Robert @.***> wrote: Hey! Thanks for the logs, I see you have closed the issue. Have you resolved it? From what I can see you can run version --long and use a build tag to set the app version

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>