smartcontractkit / smartcontractkit/chainlink
[NODE] <Error handling issue for async jobs>
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.2k
- Forks
- 2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 202
Description
Description
When running our bridge job with async set to true, we get the error: "invalid memory address or nil pointer dereference"
Basic Information
This is the relevant part of the job definition in the toml file:
ds [type="bridge"
name="chainlink_example"
requestData="{\\"id\\": $(jobSpec.externalJobID), \\"data\\": {\\"block_num\\": $(decode_cbor.block_num)}}"
async=true
allowUnrestrictedNetworkAccess=true
]
Network: Goerli
Blockchain Client: Infura v3
Go Version: N/A
Operating System: macOS Big Sur
Commit: https://github.com/smartcontractkit/chainlink/commit/850acc7cfade39c4508afa9d120b0da630a81ef7
Hosting Provider: AWS Postgresql
Startup Command: docker run -p 6688:6688 -v ~/.chainlink-goerli:/chainlink -it --env-file=.env smartcontract/chainlink:1.7.0-root local n
Environment Variables
N/A
Steps to Reproduce
create a job with a bridge that is async, and then call that job, and then get the nil pointer dereference error.
Additional Information

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
Reproduce the failure using the async bridge job definition and the referenced commit 850acc7cfade39c4508afa9d120b0da630a81ef7. Trace the nil pointer dereference from the async job invocation; done means the job no longer errors when called with async=true.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100