Open devos50 opened 4 years ago
Any progress on this issue?
It actually seems to work when passing the --local-abi
flag to the burrow deploy
command (found about this when going through the source code). Is there a bug when fetching the contract ABI from Burrow?
Sorry for the late reply @devos50! Burrow needs to know where your ABIs are stored so it can properly encode your function call. You can do what you've done above, or you can specify bin on the call
job.
No problem! (decided to look at it myself since we're using Burrow to evaluate a smart contract for a scientific paper with the submission deadline soon).
I tried several times to add a bin
parameter to the contract, but that did not seem to work for some reason. Furthermore, Burrow does not give me an error about an invalid or missing ABI but instead, the error is in the GetMetadataForAccount
method. I found that the specific erroneous line is only triggered when the localABI
argument is not set.
Hmm okay, this is odd behavior indeed! Let me investigate this further.
Describe the Bug I've been playing a bit around with Burrow and
To Reproduce I deployed the basic contract as included in the tests. My
deploy.yaml
file looks as follows:This succeeds with the following output:
Next, I change the
deploy.yaml
file and try to call a method in the contract:This fails with the following error:
However, when 'combining' the deploy and call job in the same contract, it succeeds.
Expected Behavior The transaction succeeds.
Technical Details
0.29.8+commit.6205f48346a370d553388de37b4d6dc4a06dfb7e+2020-02-11T13:09:22Z