trufnetwork / trufnetwork/node
Problem: binary version of node instances is ambiguous
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 3
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 13
Description
When checking whether the binary is updated or not we use --version in CLI to get its version. However, the current preview branch always returns kwild version 0.8.3+release. when we want to check whether something is already being updated or not. We might need a way to check if the running nodes are indeed the most updated ones.
./kwild --version
kwild version 0.8.3+release.
related: https://github.com/truflation/tsn/issues/544
cc @brennanjl @outerlook
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the CLI entry point ./kwild --version; start by tracing how that command builds its version string and review related issue #544. Done means the output provides an unambiguous version signal that can determine whether running nodes are up to date.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100