smartcontractkit / smartcontractkit/chainlink-aptos
Panic when running `toolkit deploy-ocr3-jobspecs` during `setup.sh` (`unsupported operation in loop mode`)
Nobody has claimed this yet.
- Dominant language
- Move
- Stars
- 10
- Forks
- 14
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 29
Description
When running the setup.sh script, the following command fails with a panic:
go run main.go toolkit deploy-ocr3-jobspecs \
--ethurl=http://localhost:8544 \
--accountkey=348ce564d427a3311b6536bbcff9390d69395b06ed6c486954e971d960fe8709 \
--chainid=1337 \
--p2pport=6691
Observed Error:
panic: not available in loop mode: unsupported operation
goroutine 1 [running]:
github.com/smartcontractkit/chainlink/core/scripts/common.PanicErr(...)
/home/lab/Desktop/dev/chainlink/core/scripts/common/helpers.go:143
github.com/smartcontractkit/chainlink/core/scripts/keystone/src.(*nodeAPI).mustExec(...)
/home/lab/Desktop/dev/chainlink/core/scripts/keystone/src/99_app.go:192
github.com/smartcontractkit/chainlink/core/scripts/keystone/src.deployOCR3JobSpecs({0xc001081888, 0x5, 0xc0019c2480?}, 0x539, {0xc000400b08, 0x5, 0x23?}, 0x1a23, 0xc000072930)
/home/lab/Desktop/dev/chainlink/core/scripts/keystone/src/02_provision_ocr3_capability.go:173 +0x60a
github.com/smartcontractkit/chainlink/core/scripts/keystone/src.(*Toolkit).DeployOCR3JobSpecs(0x123c3aa0?, {0xc000072260, 0x4, 0x4})
/home/lab/Desktop/dev/chainlink/core/scripts/keystone/src/01_toolkit.go:126 +0x3ba
github.com/smartcontractkit/chainlink/core/scripts/keystone/src.(*Toolkit).Run(0x1261e720, {0xc000072250?, 0x4?, 0xbfbc828?})
/home/lab/Desktop/dev/chainlink/core/scripts/keystone/src/01_toolkit.go:48 +0x325
main.main()
/home/lab/Desktop/dev/chainlink/core/scripts/keystone/main.go:37 +0x37a
exit status 2
It looks like there’s a version mismatch between Chainlink and the way Keystone deploys tasks.
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 setup.sh and the toolkit deploy-ocr3-jobspecs entry point in core/scripts/keystone/src/01_toolkit.go. Trace the failing call through 02_provision_ocr3_capability.go and 99_app.go, using the reported mustExec panic as the first symptom to investigate. Done means the command completes without the loop-mode panic and deploys the OCR3 job specs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, shell
- Domain
- cli, devops, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100