-
Notifications
You must be signed in to change notification settings - Fork 97
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(routing): allow-offline with routing put #278
Conversation
Codecov Report
@@ Coverage Diff @@
## main #278 +/- ##
==========================================
- Coverage 47.88% 47.82% -0.06%
==========================================
Files 273 274 +1
Lines 33186 33237 +51
==========================================
+ Hits 15890 15895 +5
- Misses 15616 15665 +49
+ Partials 1680 1677 -3
|
d5dc6ee
to
8616936
Compare
Is ipfs/kubo#9667 correct ? I don't see how this relates |
8616936
to
62f7080
Compare
@hacdias : can you please look at this again so we can get it merged? |
62f7080
to
acfca33
Compare
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.
Thanks @laurentsenta. This looks good to me.
I would like to see a test for this in coreiface/tests/routing.go but I'm not sure how easy that would be. I think by using tp.MakeAPISwarm(ctx, true, 1)
you'll be able to spin an offline node and therefore Put
should work with AllowOffline(true)
but not without. Note that this tests are run in Kubo's repo.
@hacdias thanks for taking the time to review both PRs, From a quick look + tests:
I'll dig some more, but let me know if you've seen this before: when I try to start a node with full identity AND offline, I get a sigsev
|
@laurentsenta I've never seen this error before, and it might be a bug? It seems like
Do you mean a |
b143fbb
to
ee04895
Compare
sister PR in kubo: ipfs/kubo#9667