lidofinance / lidofinance/validator-ejector
--version reports incorrect value
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 19
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 7
Description
docker run lidofinance/validator-ejector:1.7.0 --version
Unable to find image 'lidofinance/validator-ejector:1.7.0' locally
1.7.0: Pulling from lidofinance/validator-ejector
7264a8db6415: Pull complete
eee371b9ce3f: Pull complete
93b3025fe103: Pull complete
d9059661ce70: Pull complete
671a8b9d24b0: Pull complete
a572d0804fbc: Pull complete
00addaf2ec3c: Pull complete
e98da9a0d7cf: Pull complete
Digest: sha256:718f4fb51622d8628c70e553f6c2b024600c06a3ed6b7ddf960a53eb111a343c
Status: Downloaded newer image for lidofinance/validator-ejector:1.7.0
v16.20.2
Expected to see 1.7.0, but saw v16.20.2
Contributor guide
No contributing guide indexed for this repository
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
Start by running the documented Docker command for image tag 1.7.0 and trace the entry point that handles --version. Compare the reported value with the image tag, then add or update the relevant test so the command reports the expected release version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, node.js, typescript
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100