smartcontractkit / smartcontractkit/chainlink
[NODE] ethtx task fails to parse minConfirmations as uint and string from cborparse
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.2k
- Forks
- 2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 202
Description
Description
Attempting to set ethtx minConfirmations via cborparse output makes the jobrun error with:
"__typename": "JobRun",
"id": "110",
"allErrors": [
"minConfirmations: strconv.ParseUint: parsing "$(decode_cbor.minConfirmations)": invalid syntax: bad input for task"
],
"createdAt": "2022-05-25T13:15:26.136101Z",
"fatalErrors": [
"minConfirmations: strconv.ParseUint: parsing "$(decode_cbor.minConfirmations)": invalid syntax: bad input for task"
],
No matter whether I send it as uint256 or string, the error is the same.
Strategy 1 - Passing minConfirmations as uint256:
_req.addUint("minConfirmations", uint256(spec.minConfirmations)); // NB: I do have a uint48


Strategy 2 - Passing minConfirmations as string:
_req.add("minConfirmations", Strings.toString(spec.minConfirmations)); // NB: I do use OZ Strings library


However, gasLimit can be passed as uint256 and set via cborparse output:
req.addUint("gasLimit", uint256(gasLimit));
Basic Information
Reproduced with Chainlink Node v1.2.0 and v1.4.1
Environment Variables
Not relevant
Steps to Reproduce
The hard way is implementing a consumer contract that sends minConfirmations. I haven't tried it using a webhook job though (I remember breaking an old node version attempting to make an ethtx via webhook job).
Thanks!
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 an ethtx job using cborparse output for minConfirmations, comparing uint256 and string inputs with the working gasLimit case. Trace where these values are parsed and confirm completion when minConfirmations is accepted and the reported job run no longer contains the ParseUint error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, solidity
- Domain
- backend, blockchain
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100