-
-
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
ipfs ls $blobhash
gives: Error: merkledag node was not a directory or shard
#4075
Comments
Please fill out the template when creating issue, also please provide steps to reproduce. |
I faced the same issue.
and there you get: However, ipfs object links QmVN6qhejgEDPFunvsWQqDWRmeCNqyC7iz8XZuHM137vm2 works as expected and returns the links:
My go version is : go version go1.8.3 linux/amd64 |
So I guess the expectation here is that |
I've been experiencing this same issue. |
@conrad @prashantprabhakar can you confirm my above assumption? Can you also give full output of |
I should add that this did work for me initially a week or two ago. I don't know what changed. |
Everything else I do with these files so far seems to be working. |
ipfs ls $blobhash
gives: Error: merkledag node was not a directory or shard
Ah, yeah. It seems that |
So the expected behavior, is what ever it was before the change. Sounds easy enough. |
Git bisect determined that commit c4c6653 was the cause of the regression. Working on fixing now. |
#4184 should fix this. |
Version: 0.4.10
Issue at hand is that it is no longer possible to use
ipfs ls
with blob hashes (hashes of straight up files). It was broken somewhere along integration of sharding or cleanup of some error messages.~ Kubuxu - this was edited by me as it is top message of the issue
The text was updated successfully, but these errors were encountered: