Open-Issues
Last updated
Last updated
Unable to set up an upgradeable proxy contract using Hardhat features. The setup is working fine with another EVM-compatible blockchain.
Can we look into this?
How to replicate this issue?
Use this deployment script, and replace the contract with your own contract.
Expected results: it should deploy the contract fine and provide the contract address
Actual Results: Erroring out with "ProviderError: too many arguments, want at most 1"
We have been witnessing this issue recently, when we setup Plugin2.0.
These issues have not occurred before, but recently. To check the issues, we have executed the Plugin2.0 in "Polygon" and also in "XDC Mainnet". Logs for both executions is captured below.
Actual issue?
In Plugin, when we configure more than 4 jobs, the execution is failed resulting in the following error
2023-09-25T12:48:34.707+0530 [ERROR] Error in new head subscription, unsubscribed headtracker/head_listener.go:67 err=websocket: close 1000 (normal) evmChainID=50 logger=EVM.HeadTracker.HeadListener stacktrace=github.com/GoPlugin/pluginV2/core/chains/evm/headtracker.(*headListener).ListenForNewHeads
When we execute the same against the "Polygon" chain, it runs without any issues.
Logs:-
The log shows that "headtracker is missing" a block, due to which we face "RPC node is not reachable" and it is on & off and unstable.
Head & Block logs for Polygon: https://notepad.pw/g50JXvp3RIn1PNfe2Tea
For XDC: https://notepad.pw/o7VtAjvuS4dFtN0YdLyd
You may see the difference in the XDC Log, where the blocks are missing.
Note: We have tested the available RPC from "https://chainlist.org/" for Apothem & Mainnet and the results are the same.
Let us know if you need some more information to debug.
Kindly review and let us know the possible solutions.