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

error Could not parse row {... #21

Open
jikkujose opened this issue Jan 3, 2016 · 11 comments
Open

error Could not parse row {... #21

jikkujose opened this issue Jan 3, 2016 · 11 comments
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@jikkujose
Copy link

Can't publish, keep getting error: error Could not parse row {...

What I did:

  1. Created a simple html page in directory: public.
  2. ipscend init & chose default location as public.
  3. Previewed the HTML page via: ipscend preview, it worked as expected.
  4. Tried to publish: ipscend publish and got the error specified.

Any ideas?

@daviddias
Copy link
Member

@jikkujose were you running an IPFS node in your machine? This tells me that we should have better error messages

@jikkujose
Copy link
Author

@diasdavid yes, I ran the daemon while I was pushing it. I don't generally run it in the background all the time, since I am on a laptop.

@hackergrrl
Copy link
Contributor

@jikkujose What version of ipfs are you running? (ipfs version) I saw the same thing when I tried to use ipscend with [email protected].

@daviddias daviddias added the kind/bug A bug in existing code (including security flaws) label Jan 8, 2016
@void4
Copy link

void4 commented Jan 16, 2016

I get the same error when I try to use the js-ipfs-api to add something. The issue was closed at the go-ipfs repo, however.
ipfs/kubo#2109
I'm using:
ipfs version 0.3.8-dev
js-ipfs-api version 2.10.1

@daviddias
Copy link
Member

Hi @jikkujose and @void4 , mind testing ipscend again, just released version 0.2.0 which should solve the incompatibility issue. Also now you can do ipscend ipfs start to spawn a daemon that is compatible with the js-ipfs-api that ipscend is using.

@tinybike
Copy link

I also get this problem when using js-ipfs-api, which has made js-ipfs-api unusable for me in Nodejs.

@daviddias
Copy link
Member

@tinybike which version (Node.js, js-ipfs-api and IPFS)?

@tinybike
Copy link

Node.js v4.2.4, js-ipfs-api v2.13.1 (from npm), IPFS v0.4.0-dev. I saw a comment that feat/files-api had a fix for this issue so I tried this branch out, but it did not help me.

Temporary fix: I downgraded IPFS to v0.3.11 and js-ipfs-api works again.

@daviddias
Copy link
Member

@tinybike yeah, ipscend is not 0.4.0 compatible (#41) due to differences in IPFS HTTP API

@daviddias
Copy link
Member

daviddias commented May 20, 2017

Hi all! It has been a long time. I've just updated the dependencies and ran some quick tests. It worked well, let me know if it works for you too.

To be 100% sure it won't break in the future I'll need to write some tests. I plan to spend some time on this once I get a bit of free time (which by the looks might be the end of June). Thank you for being patient :)

@daviddias
Copy link
Member

Hi folks! I'm no longer maintaining this module. The good news is that there is one way better on the block, check the deprecation notice -- https://github.com/ipfs-shipyard/ipscend/blob/master/README.md#deprecation-notice -- to find a url to it and a tutorial on how to use 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

5 participants