Skip to content
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

[WIP] Unixfs: enforce refs on files when using nocopy #5925

Closed
wants to merge 3 commits into from

Conversation

@magik6k magik6k requested review from Stebalien and kevina January 14, 2019 21:07
@magik6k magik6k requested a review from Kubuxu as a code owner January 14, 2019 21:07
@ghost ghost assigned magik6k Jan 14, 2019
@ghost ghost added the status/in-progress In progress label Jan 14, 2019
@magik6k magik6k changed the title Unixfs: enforce refs on files when using nocopy [WIP] Unixfs: enforce refs on files when using nocopy Jan 14, 2019
@magik6k
Copy link
Member Author

magik6k commented Jan 14, 2019

Looks like due to ipfs/go-mfs#38, running mfs related commands locally is racy:

$ alias tipfs='IPFS_PATH=/tmp/ipfs ipfs'
$ tipfs init --profile=test -b=1024
$ tipfs files mkdir /cats
$ tipfs files ls
$ # no cats :( (about 70% of the time, if there are, rm /tmp/ipfs and start over)

(This PR works fine without ipfs/go-mfs#38)

@Stebalien @schomatis ^

@magik6k magik6k added the status/blocked Unable to be worked further until needs are met label Jan 14, 2019
@schomatis
Copy link
Contributor

Sorry for that, small typo, we really need to add tests for the republisher. Pushed it as a hotfix in v0.1.31 (ipfs/go-mfs@2e0c3bc).

@schomatis schomatis removed the status/blocked Unable to be worked further until needs are met label Jan 15, 2019
@Stebalien
Copy link
Member

Thanks for catching that!

(yeah, we need better tests)

@magik6k
Copy link
Member Author

magik6k commented Jan 18, 2019

There are still some errors in t0250-files-api, found this in daemon_err:

�[0;37m15:14:18.505 �[31mERROR �[0;34m  cmd/ipfs: �[0merror from node construction:  error loading filesroot from DAG: merkledag: not found �[0;37mdaemon.go:330�[0m
Error: error loading filesroot from DAG: merkledag: not found

@magik6k
Copy link
Member Author

magik6k commented Jan 18, 2019

I'm fairly confident that it's not related to these changes, the missing CID is zDMZof1kvpZj7Lxs5KKpabLZy2VNuQZMsoDJ6ShLAA812gJEAejp, which is a dag-pb blake2b cid

License: MIT
Signed-off-by: Łukasz Magiera <[email protected]>
License: MIT
Signed-off-by: Łukasz Magiera <[email protected]>
License: MIT
Signed-off-by: Łukasz Magiera <[email protected]>
@ghost ghost assigned Stebalien Jan 22, 2019
@Stebalien
Copy link
Member

Yeah, it looks like there's a regression in go-mfs due to that WaitPub PR. And ipfs/go-blockservice#15 dosn't fix it.

@ghost ghost removed the status/in-progress In progress label Jan 22, 2019
@Stebalien Stebalien mentioned this pull request Jan 22, 2019
@Stebalien
Copy link
Member

Dammit github! Replaced by #5937 (github wouldn't let me reopen this after I rebased).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants