-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
ipfs: workaround for upstream bug; other small fixes #29133
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
Conversation
Looks good to me now (it appears that you force pushed). Software is just great that depends on terminating newlines ;) |
Oh, took me a while to get what you mean. Yeah, and I had mkIf not high up enough as well. I've added your tests change (+ removal of "not yet" comments) and rebased. |
Thank you both! 🍻 |
@elitak According to ipfs/kubo#4214 (specifically this comment) the issue has been resolved. Can't we remove the |
@vojta001 Turns out we still need |
@elitak I have no experience with ipfs developers, however, if the release notes for go-ipfs 0.5 are correct, it should truly be no longer necessary (nor available, in fact). Proposed in #86242. |
Motivation for this change
Temporary workaround for ipfs/kubo#4214
Things done
Running
ipfs repo fsck
prestart should be safe, and fixes the service not starting after an unclean exit.Also, the ipfs autoMount now works, although I had to take the suboptimal approach of adding a line to
environment.etc."fuse.conf".text
.build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)