Layr-Labs / Layr-Labs/devkit-cli
Issue with task submission
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 27
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
When I run the sample cmd/main.go, which basically does nothing, I get the logs on the container output as:
{"level":"info","ts":1753688645.5952423,"caller":"rpcServer/rpcServer.go:64","msg":"Starting gRPC server","port":8080}
{"level":"info","ts":1753688661.6818242,"caller":"zap/options.go:212","msg":"finished unary call with code OK","grpc.start_time":"2025-07-28T07:44:21Z","grpc.request.deadline":"2025-07-28T07:44:22Z","system":"grpc","span.kind":"server","grpc.service":"eigenlayer.hourglass.v1.performer.PerformerService","grpc.method":"HealthCheck","peer.address":"172.25.0.2:55982","grpc.code":"OK","grpc.time_ms":0.455}
{"level":"info","ts":1753689803.8455687,"caller":"cmd/main.go:31","msg":"Validating task","task":"task_id:\"0x8d4ebc3f55476ab3dbdc6b8c97bbcf4fb3503e4fd46e869b2883363b6aef7631\" payload:\"\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00 \\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x05\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00@\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x05hello\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\""}
Yes, the task has been submitted. But when I submit a new task, no more logs appear. Any Idea why this is happening? I submit the task using devkit avs call
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 with cmd/main.go, where the sample logs “Validating task,” and reproduce the behavior using devkit avs call: compare the first submission with a subsequent one. Trace the task-submission path from that entry point and verify that repeated submissions either produce the expected logs or report a clear failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100