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] Interrupt signal ignored after cosmwasm initialization #363

Closed
hanjukim opened this issue Jul 6, 2020 · 0 comments · Fixed by #382
Closed

[BUG] Interrupt signal ignored after cosmwasm initialization #363

hanjukim opened this issue Jul 6, 2020 · 0 comments · Fixed by #382
Assignees
Labels
bug Something isn't working

Comments

@hanjukim
Copy link
Contributor

hanjukim commented Jul 6, 2020

Describe the bug
After cosmwasm intiailization when the process receives a SIGINT signal (by pressing Ctrl+C), terrad will not receive the signal. If we trigger another signal. Program will be aborted with long stack trace from wasmd.

To Reproduce

  1. Start terrad.
  2. Interact cosmwasm by CLI or something.
  3. Press Ctrl+C in terrad process (or send signal by kill -SIGINT ) and nothing happens.
  4. Press Ctrl+C again to terminate process.

Context & versions
terrad >= v0.4.0-rc.0

(if applicable) suggested solution
Solution: wasmerio/wasmer@master...hanjukim:interrupt-signal-propagation
Discussion with Cosmwasm team: CosmWasm/wasmd#4

We will have to update wasmer-runtime-core > cosmwasm-vm > go-cosmwasm

@hanjukim hanjukim added the bug Something isn't working label Jul 6, 2020
@hanjukim hanjukim added this to the Columbus-4 RC.1 milestone Jul 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants