-
Notifications
You must be signed in to change notification settings - Fork 18
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
feat: implementation of correct chord #448
feat: implementation of correct chord #448
Conversation
…r function 3) Some document for swarm and swarm builder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Others LGTM
@@ -41,7 +41,8 @@ node = [ | |||
"wasmer-types", | |||
] | |||
browser = [ | |||
"console_error_panic_hook", | |||
"backtrace", | |||
"clap", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strange clap dependency here for browser.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there will only be a few traits (by derive) implemented here, and the compiler will help me optimize (cut) them
Please check if the PR fulfills these requirements
🔵 What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature and Docs update and Bug Fix
🟤 What is the current behavior? (You can also link to an open issue here)
For [feature="wasm"], if there is no message in the data channel, it should respond with Ok(None) instead of Err(e) (core/src/channels/wasm.rs).
For [feature="default"], the transformed Error should include the original error as the reasoning.
MessageHandlerEvent should be available to process without a context.
The DHT action handler should be implemented separately and included in the message handler.
🟢 What is the new behavior (if this is a feature change)?
[Feat]: New feature flag: experimental, mark an implementation as experimental, which means that:1) It may not have been thoroughly tested. 2)The corresponding API may be deprecated or adjusted in the future.
[Doc]: Added document for modules.
[Refactor]: Made MessageHandlerEvent context-agnostic.
[Refactor]: Convergent implementation of logging module for wasm and defaut. Convergent implementation of WASM and NATIVE #453
[Refactor]: Rename relay.sender() to relay.origin_sender()
[Refactor]: Reimplemented node::error::Error::code with #[repr(u32)]
[Fixed] datachannel for wasm and default
[Feat] Implemented messagehandler for correct chord related message. Correctness of DHT #388 [BUG] DHT Join may not work properly #387
☢️ Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
ℹ️ Other information
Closes #issue