Layr-Labs / Layr-Labs/devkit-cli
gomplaten not install by the init script
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 27
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
2025/06/11 21:30:33 Processing registration for operator at address 0x90F79bf6EB2c4f870365E785982E1f101E93b906
2025/06/11 21:30:48 Successfully registered operator 0x90F79bf6EB2c4f870365E785982E1f101E93b906 for OperatorSetID 0
2025/06/11 21:30:48 Processing registration for operator at address 0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65
2025/06/11 21:30:57 Successfully registered operator 0x15d34AAf54267DB7D7c367839AAf71A00a2C6A65 for OperatorSetID 1
2025/06/11 21:30:57 Operator registration with EigenLayer completed.
Error: gomplate not found. Please run 'avs create' first.
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 locating the init script used before the avs create entry point and inspect how it installs or checks for gomplate. Reproduce the initialization flow, then verify that gomplate is available before operator registration completes and that the reported error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100