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

Recursive add with --raw-leaves produces inaccessible directory #3548

Closed
mib-kd743naq opened this issue Dec 29, 2016 · 4 comments
Closed

Recursive add with --raw-leaves produces inaccessible directory #3548

mib-kd743naq opened this issue Dec 29, 2016 · 4 comments
Assignees
Labels
kind/bug A bug in existing code (including security flaws)
Milestone

Comments

@mib-kd743naq
Copy link
Contributor

Version information:

go-ipfs version: 0.4.5-dev-99d72c2

Type:

Bug

Priority:

P1

Description:

~$ mkdir somedir
~$ echo bar > somedir/foo
~$ ipfs add --raw-leaves -r somedir/
added zb2rhf6GzX4ckKZtjy8yy8iyq1KttCrRyqDedD6xubhY3sw2F somedir/foo
added QmThNTdtKaVoCVrYmM5EBS6U3S5vfKFue2TxbxxAxRcKKE somedir
~$ ipfs ls QmThNTdtKaVoCVrYmM5EBS6U3S5vfKFue2TxbxxAxRcKKE
Error: incorrectly formatted merkledag node: Unmarshal failed. unexpected EOF
~$ ipfs add -r somedir/
added QmTz3oc4gdpRMKP2sdGUPZTAGRngqjsi99BPoztyP53JMM somedir/foo
added QmZKetgwm4o3LhNaoLSHv32wBhTwj9FBwAdSchDMKyFQEx somedir
~$ ipfs ls QmZKetgwm4o3LhNaoLSHv32wBhTwj9FBwAdSchDMKyFQEx
QmTz3oc4gdpRMKP2sdGUPZTAGRngqjsi99BPoztyP53JMM 12 foo
@mib-kd743naq
Copy link
Contributor Author

@Kubuxu this is almost certainly a 0.4.5 blocker...

@Kubuxu Kubuxu added this to the ipfs 0.4.5 milestone Dec 30, 2016
@kevina kevina self-assigned this Jan 2, 2017
@kevina
Copy link
Contributor

kevina commented Jan 2, 2017

I'll look into this later today.

@kevina
Copy link
Contributor

kevina commented Jan 3, 2017

Can reproduce. Working on fix.

@kevina kevina added kind/bug A bug in existing code (including security flaws) status/in-progress In progress labels Jan 3, 2017
@kevina
Copy link
Contributor

kevina commented Jan 3, 2017

#3557 should fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
Development

No branches or pull requests

4 participants