Skip to content
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

Error when stopping devnet using "ctrl + c" #1534

Closed
vini-btc opened this issue Aug 6, 2024 · 3 comments
Closed

Error when stopping devnet using "ctrl + c" #1534

vini-btc opened this issue Aug 6, 2024 · 3 comments

Comments

@vini-btc
Copy link

vini-btc commented Aug 6, 2024

Describe the bug
When I stop devnet using the "ctrl + c" key combination, I see the following error:

Error sending terminate command: sending on a disconnected channel

All devnet containers keep running after it.

To Reproduce
Steps to reproduce the behaviour:

  1. Start devnet clarinet devnet start
  2. After it is running, use the ctrl + c combination to stop it. (I'm not familiar with any other way to stop it)
  3. See error

Expected behaviour
I'd expect devnet tui to be stopped, as well as all related running containers.

Environment (please complete the following information):

  • OS (version): 14.5 (23F79)
  • Docker version: 24.0.5
  • Clarinet version: 3.28.0
@hugocaillard
Copy link
Collaborator

Thanks for reporting @vicnicius
It's likely that if the devnet doesn't shutdown gracefully, it means that it's in a weird state.
Do you use ctrl + c immediately after starting the devnet?
Or has your devnet stopped (no more block mining) when you did ctrl + c

@vini-btc
Copy link
Author

vini-btc commented Aug 6, 2024

Oh, that makes sense. I think what triggered me to stop it was it stopping to produce new blocks. I'll keep an eye on it and see if I can gather any more info. Thanks! I'll close this issue for now, and if it happens while all services are stable, I'll re-open it. If it's some service crashing without clear reason I'll make sure to open a new issue for it.

@vini-btc vini-btc closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2024
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in DevTools Aug 6, 2024
@hugocaillard
Copy link
Collaborator

@vicnicius
Thanks. And to be fair, we should still be able to gracefully shutdown the devnet if it crashes, but we are also putting efforts in making sure that it doesn't.

Find on me on the official Discord (in the #clarinet chan) if you're node stops again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants