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

[Bug] Unable to run clarinet integrate in clarinet v0.21.2 #194

Closed
homiebtc opened this issue Dec 26, 2021 · 5 comments
Closed

[Bug] Unable to run clarinet integrate in clarinet v0.21.2 #194

homiebtc opened this issue Dec 26, 2021 · 5 comments

Comments

@homiebtc
Copy link

homiebtc commented Dec 26, 2021

Unable to run clarinet integrate

$ clarinet -V                                                                                                                                                                                                    
clarinet 0.21.2
$ docker --version
Docker version 20.10.8, build 3967b7d

clarinetintegrate

Tried running in clarinet/examples/simple-nft example folder

Same result happens in clarinet/examples/counter

@homiebtc
Copy link
Author

When I try running clarinet integrate in my own repo, I get further progress into booting all containers until it runs into this

thread 'main' panicked at 'index out of bounds: the len is 5350 but the index is 5427', /Users/brew/Library/Caches/Homebrew/cargo_cache/registry/src/github.com-1ecc6299db9ec823/tui-0.16.0/src/buffer.rs:185:14

and everything stops again.

@csgui
Copy link
Contributor

csgui commented Jan 5, 2022

Hello @homiebtc !

It seems an issue with the underlying containers. Specifically, from your image, looks like that clarinet isn't able to connect to the bitcoind daemon.

Have you tried to cleanup/restart the containers that are need by clarinet?

Cheers.

@obycode
Copy link
Member

obycode commented Feb 22, 2022

@homiebtc Did cleaning up the containers solve your problem?

@utkarsh23
Copy link

I was facing a similar issue with clarinet integrate.

The issue was that I had a postgres service running locally, and clarinet was trying to launch the dockerized postgres on the same port 5432 leading to a conflict.
Changing the value of postgres_port to some other port number inside Devnet.toml fixed the issue for me.

@lgalabru
Copy link
Contributor

v0.28.0 is fixing a bunch of issues with clarinet integrate, feel free to re-open this issues with logs if you keep experiencing this.
Thanks!

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

No branches or pull requests

5 participants