BUFFER_OVERRUN Error on mainnet

[end0cr1ne]

"[ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32603,"message":"Internal Error - data out-of-bounds (length=15, offset=32, code=BUFFER_OVERRUN, version=abi/5.5.0). Please report a bug at https://github.com/aurora-is-near/aurora-relayer/issues","data":{"host":"relayer002.backend.internal.aurora.dev","cf-ray":"6cfa42a624bf856c-BOM"}}}}'"

[mfornet]

@end0cr1ne do you have the payload of your tx, or can you describe your interaction with the RPC?

[mfornet]

Looking at this similar issue ethers-io/ethers.js#891, it seems to me that the problem might be here.

[end0cr1ne]

TX: https://explorer.mainnet.aurora.dev/tx/0x9e08ac7e9bf9f369d5bf9e1ee5b80409cf7b1921b5459ee825dcd4e277e4610a/internal-transactions
or: https://explorer.mainnet.aurora.dev/tx/0x12e5f820e571fd001122d27859354add0574d560ab87fb28c4bf44a962080d4d

Started happening randomly

[end0cr1ne]

Looking at this similar issue ethers-io/ethers.js#891, it seems to me that the problem might be here.

That seems to be limited to: external's bytes data is not right-padded due to a bug reported in ethereum/solidity#3493. The fix shipped with solc 0.5.x.

My contract uses 0.8.x

[spilin]

It seems that there is a evm revert, but we are unable to decode a reason. We will fix "BUFFER_OVERRUN" error.

[0x3bfc]

@end0cr1ne Can you share the steps to reproduce this issue ? We already had internal discussion and wanted to check whether what I thought is aligned with this issue.

[mfornet]

Reopening, as #171 is not confirmed to solve this issue

[end0cr1ne]

Hi,
To recreate this issue in the truffle console try:
let farm = await Farmv2.at('0xFe427EcbD4FAb2B89b25418364cBF8b454019713')
FarmV2_abi.txt
farm.createFarm(0)
farm.levelUp()

ABI is attached :)

[end0cr1ne]

You could also use the frontend: Link
Just create a farm(If you can, It's free). Then try to save it. You can see the error in the browser console.

[end0cr1ne]

Hey guys, just checking in! Is there anything I can do to help debug this issue?

[end0cr1ne]

The error seems to have changed to: "{"value":{"code":-32603,"data":{"code":3,"message":"execution reverted","data":"0x4e487b710000000000000000000000000000000000000000000000000000000000000011"}}}"

[mfornet]

@end0cr1ne this is the more informative error we are using after #171. It seems to me like a regular revert operation on the engine, as in, something going wrong with your contract, or the engine itself.

[end0cr1ne]

Thanks, @mfornet for all the help, turned out to be a uint being set to a negative value that triggered the revert.