[EVM] Cannot synch the archive node #1007
Comments
|
yeah i've recently experienced this issue when trying to spin up a localnet for testing :(. I really don't want to have to wipe by previous chain state if I don't have to and go through the process of getting TAO from a faucet, creating subnet, regging miners, validators etc to test my subnet code with the new subtensor version. |
|
check the build binary flag and remove it from the script. This will avoid
it , alot dont delete the previous db when you start again . its all in the
script read the code
…On Thu, Nov 28, 2024 at 6:45 AM Syeam Bin Abdullah ***@***.***> wrote:
yeah i've recently experienced this issue when trying to spin up a
localnet for testing :(. I really don't want to have to wipe by previous
chain state if I don't have to and go through the process of getting TAO
from a faucet, creating subnet, regging miners, validators etc.
—
Reply to this email directly, view it on GitHub
<#1007 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH773DSH33MPJ2BV67BFQZD2CZ7VPAVCNFSM6AAAAABSFHQ4XGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBVGE3DAMZQGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I'm aware of the build binary flag - and I would basically be testing against an older version of the subtensor. There's no point in doing that :/ |
|
then dont delete the db. check the script it remove the old db before
starting it again
On Thu, Nov 28, 2024 at 7:00 AM Syeam Bin Abdullah ***@***.***>
wrote:
… check the build binary flag and remove it from the script. This will avoid
it , alot dont delete the previous db when you start again . its all in the
script read the code
… <#m_3700038146557570550_>
On Thu, Nov 28, 2024 at 6:45 AM Syeam Bin Abdullah *@*.*> wrote: yeah
i've recently experienced this issue when trying to spin up a localnet for
testing :(. I really don't want to have to wipe by previous chain state if
I don't have to and go through the process of getting TAO from a faucet,
creating subnet, regging miners, validators etc. — Reply to this email
directly, view it on GitHub <#1007 (comment)
<#1007 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH773DSH33MPJ2BV67BFQZD2CZ7VPAVCNFSM6AAAAABSFHQ4XGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBVGE3DAMZQGA
<https://github.com/notifications/unsubscribe-auth/AH773DSH33MPJ2BV67BFQZD2CZ7VPAVCNFSM6AAAAABSFHQ4XGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBVGE3DAMZQGA>
. You are receiving this because you are subscribed to this thread.Message
ID: @.*>
I'm aware of the build binary flag - and I would basically be testing
against an older version of the subtensor. There's no point in doing that :/
—
Reply to this email directly, view it on GitHub
<#1007 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH773DXK7U3MRPFZXPO2HE32C2BODAVCNFSM6AAAAABSFHQ4XGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBVGE3TENBXGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
This PR will fix it: |
When synching the archive node with TestNet, we get an error if we start with the most recent EVM node:
You have to deploy a subtensor build that does not have the evm changes (then it works fine), and then later switch to the new one.
The text was updated successfully, but these errors were encountered: