Skip to content

Fix crashes on SIGINT #1814

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

Merged
merged 4 commits into from
Oct 18, 2019
Merged

Fix crashes on SIGINT #1814

merged 4 commits into from
Oct 18, 2019

Conversation

foriequal0
Copy link
Contributor

Resolve: #348

Copy link
Contributor

@sgkim126 sgkim126 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you refine the commit message of 725f921?
I think the lines below Errors were: can be summarized in a few sentences.

@sgkim126
Copy link
Contributor

And please resolve the conflicts.

@sgkim126 sgkim126 added the bug Something isn't working label Oct 15, 2019
@remagpie
Copy link
Contributor

It seems the lockfile has some problem with your patched jsonrpc repo.

}
if let Some(server) = ws_server {
server.close_handle().close();
server.wait().map_err(|err| format!("Error while closing jsonrpc ws server: {}", err))?;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why use map_erro only for ws_server?
rpc_server and ipc_server don't need it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't touch the interface. jsonrpc returns Result<()> only for ws_

majecty
majecty previously approved these changes Oct 16, 2019
remagpie
remagpie previously approved these changes Oct 16, 2019
sgkim126
sgkim126 previously approved these changes Oct 16, 2019
@remagpie
Copy link
Contributor

@foriequal0 What's the status here? Is it ready to be merged?

…1.17)

Update following packages:
bytes v0.4.7 -> v0.4.12
parking_lot_core v0.6.1 -> v0.6.2
toml v0.5.1 -> v0.5.3
tokio v0.1.7 -> v0.1.17

Commands were:
```
cargo update --package bytes
cargo update --package parking_lot_core:0.6.1
cargo update --package toml:0.5.1
cargo update --package tokio:0.1.7 --precise 0.1.17
```

Errors were:
1. bytes: jsonrpc requires ^0.4.8, and bytes were pinned to v0.4.7 for
sendgrid v0.8.1.
2. parking_lot_core: Amanieu/parking_lot#181
3. toml: `forward_to_deserialize_any_helper` was replaced by forward_to_deserialize_any
4. tokio: `Builder::core_threads` was introduced in 0.1.10
The fix (paritytech/jsonrpc#504) has been merged
to `master`. It'll take times to relase, so use the merged master directly.
@foriequal0
Copy link
Contributor Author

foriequal0 commented Oct 18, 2019

I've rebased the PR and changed the package sources to the parity's merged master.

@foriequal0
Copy link
Contributor Author

I'll merge it without waiting for Travis.

@foriequal0 foriequal0 merged commit 5568ab9 into CodeChain-io:master Oct 18, 2019
@foriequal0 foriequal0 deleted the fix/sigint branch October 18, 2019 09:03
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 this pull request may close these issues.

CodeChain crashes on SIGINT
4 participants