-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarinet devnet panicks after running for a while #1536
Comments
Thanks @vicnicius
yeah I don't think the invalid contract is the cause here.
I'm not really concerned with this one. Is it possible for you to share the github link to a project where this happens? |
Sorry but the project is not public currently. I'll see if I can create a reproducible example in a public repo sometime this week. |
Thanks, that would be helpful |
I see that update @vicnicius
Does it mean that you can see the issue in a blank project? $ clarinet new my-project
$ cd my-project
$ clarinet devnet start Wait for 200 block and it stops? |
Hey @vini-btc |
Hey @hugocaillard ! Sorry I never got back to you here. I haven't noticed it for a while. I'll close the issue and if it happens I'll collect more info and re-open. Thanks! |
Describe the bug
Clarinet devnet panicking:
It happened on every run when I had an error on the contract that was being deployed. I set the contract to use clarity 3 but it had a block-info call, leading to a syntax error. This is what lead to the error I reported on #1534.
There were no patterns in terms of block height.
stacks-node was stuck in ~100% CPU usage. I saw many
entries and also this, that looked a bit more suspicious:
~ After I fixed the contract the issue is gone, leading me to believe there might be a causation. ~
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No errors, contract just fails to deploy
Environment (please complete the following information):
Update
Right after submitting this issue I saw the error again without an invalid contract. Just took longer ~200 blocks.
The text was updated successfully, but these errors were encountered: