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.

Sign up for GitHub

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

Jump to bottom

Chain-index continues to run after stopCluster. #152

Open
zmrocze opened this issue Nov 21, 2022 · 0 comments
Open

Chain-index continues to run after stopCluster. #152

zmrocze opened this issue Nov 21, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@zmrocze
Copy link
Contributor

zmrocze commented Nov 21, 2022

Chain-index gets run inside withPlutusInterface so it gets started on startCluster but in an async thread which lifetime is not connected in any way to the lifetime of a cluster. See here. I've checked that the chain-index port remains occupied after stopCluster.
@zmrocze zmrocze added the bug Something isn't working label Nov 21, 2022
This was referenced Nov 23, 2022
Merged
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Cluster fixes mlabs-haskell/plutip
1 participant
@zmrocze