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

pin.add errors when using ipfs-api #582

Closed
13 of 25 tasks
kenshyx opened this issue Oct 18, 2018 · 4 comments
Closed
13 of 25 tasks

pin.add errors when using ipfs-api #582

kenshyx opened this issue Oct 18, 2018 · 4 comments
Labels
status/duplicate This issue or pull request already exists

Comments

@kenshyx
Copy link

kenshyx commented Oct 18, 2018

Pre-check

  • This is not a IPFS Cluster website content issue (file those here)
  • I read the troubleshooting section of the website and it did not help
  • I searched for similar issues in the repo without luck
  • All my peers are running the same cluster version
  • All my peers are configured using the same cluster secret

Basic information

  • Version information (mark as appropiate):
    • Master
    • Release candidate for next version
    • Latest stable version
    • An older version I should not be using
  • Type (mark as appropiate):
    • Bug
    • Feature request
    • Enhancement
  • Operating system (mark as appropiate):
    • Linux
    • macOS
    • Windows
    • Other: which?
  • Installation method (mark as appropiate):
    • Binaries from dist.ipfs.io
    • Built from sources
    • Docker
    • Snap
    • Other: which?

Description

When I'm using the ipfs api proxy provided by ipfs-cluster I get this error:

node_modules/ipfs-api/src/pin/add.js:19
callback(null, res.Pins.map((hash) => ({ hash: hash })))
TypeError: Cannot read property 'map' of undefined

I can reproduce this error just for the latest release v0.6.0 pin.add(hash, {recursive: true}, cb)

@kenshyx
Copy link
Author

kenshyx commented Oct 18, 2018

This works without errors when using the default go-ipfs http api.

@hsanjuan hsanjuan added the status/duplicate This issue or pull request already exists label Oct 18, 2018
@hsanjuan
Copy link
Collaborator

Hi, this is fixed in master, but not released yet: #569

@hsanjuan
Copy link
Collaborator

Next release should come in about a week

@kenshyx
Copy link
Author

kenshyx commented Oct 19, 2018

Ok, I will close this, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants