-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
API return values... net.service.handler.HandleMessage #98
Comments
oh nice find!! if only ... you know ... we could just import those types........! grrr. soon. |
some initial work in #101 TODO decide on an error logging strategy and start passing errors up to the IPFS Core. |
So, what about the core having a master context with an error channel for all child contexts to report errors through. This way when the core 'Starts' it can start reading on the channel, and that way will never cause any deadlocks or loss of data in its children who are sending errors up through the channel |
+1 On Mon, Sep 22, 2014 at 4:41 PM, Jeromy Johnson [email protected]
|
+1 — On Mon, Sep 22, 2014 at 1:55 PM, Brian Tiger Chow
|
Here's a radically unintrusive approach: https://gist.github.com/perfmode/f2951c1ed3a02c484d0b#file-context_test-go |
<3 https://gist.github.com/perfmode/f2951c1ed3a02c484d0b#comment-1304444 On Mon, Sep 22, 2014 at 2:56 PM, Brian Tiger Chow [email protected]
|
closing, no longer relevant |
enable configuring several log outputs
…rror silence context canceled error
fix: remove group permissions
fix: remove group permissions
fix: remove group permissions
fix: remove group permissions
Continuing discussion from #69 (comment)
Yeah.
If something goes wrong when handling a message, trttd might be to propagate the error upward. ie. an error channel or an error recorder (à la vitess) used by the service (DHT, BitSwap)
The text was updated successfully, but these errors were encountered: