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

file ls command returning 0 size on requested hash #3232

Closed
dokterbob opened this issue Sep 17, 2016 · 1 comment
Closed

file ls command returning 0 size on requested hash #3232

dokterbob opened this issue Sep 17, 2016 · 1 comment
Labels
kind/bug A bug in existing code (including security flaws) status/deferred Conscious decision to pause or backlog

Comments

@dokterbob
Copy link
Contributor

dokterbob commented Sep 17, 2016

Version information:

go-ipfs version: 0.4.3-rc4-
Repo version: 4
System version: amd64/linux
Golang version: go1.7

Type: bug

Priority: P4

Description:

When running ipfs file ls (NOT ipfs files ls), the resulting information on the requested hash (NOT the objects it links to) includes a size which is always 0. For example:
$ ipfs file ls --enc=json <hash>

{
    "Arguments": {
        "<hash1>": "<hash1>"
    },
    "Objects": {
        "<hash1>": {
            "Hash": "<hash1>",
            "Size": 0,
            "Type": "Directory",
            "Links": [<items>]
        }
    }
}

Note "Size" being 0.

Also note that this issue might become irrelevant depending on how listing commands will eventually be sorted out as part of #3056.

@whyrusleeping whyrusleeping added kind/bug A bug in existing code (including security flaws) status/deferred Conscious decision to pause or backlog labels Nov 28, 2016
@Stebalien
Copy link
Member

Fixed (although it's still intentionally 0 for directories).

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) status/deferred Conscious decision to pause or backlog
Projects
None yet
Development

No branches or pull requests

3 participants