-
Notifications
You must be signed in to change notification settings - Fork 1.2k
add --nocopy not supported #2856
Comments
cc @victorbjelkholm when you got time. |
@MichaelMure we don't yet support the filestore API from go-ipfs. Wanna help us by taking a stap at it?
|
@diasdavid err, I already have the I have to prioritize, sorry ... |
@MichaelMure can I ask how you were capturing these requests? I'm attempting to work on a fix for this, but have been running into some strange issues where the go-ipfs daemon seems to accept the nocopy flag / abspath header, and adds the content in a different manner than normal, but this different manner isn't adding it to the filestore. Being able to capture what's getting sent would help with debugging. |
@obo20 IIRC I used wireshark |
@MichaelMure thanks for the quick response. One more quick question if you have time. Do you know how you grabbed the headers? I'm able to see my requests, but can't seem to see headers anywhere (for the CLI requests or the http-client requests) |
Sorry I don't remember, that was 2 years ago, but I suppose you can simply inspect the decoded HTTP section of the packets. Alternatively, you could use tcpdump (something like https://coderwall.com/p/imdadq/view-http-request-headers-with-tcpdump). |
Triaged, still a valid request. Not a priority, but would take a PR. If this is a priority for you, share your thoughts on why! |
Closing due to lack of response. |
Could this be reopened. |
Hi,
I'm trying to use the --nocopy option of the filestore through js-ipfs-api but files added this way are stored in the regular blockstore. After a lot of digging I think it's due to how the file is streamed in the http request:
Capture of the multipart/form-data of a request made with the CLI:
Capture of the multipart/form-data of a request made with js-ipfs-api:
The absolute path is missing, so my guess is that the filestore can't file the file on disk and the data is then stored in the regular blockstore. Bad things is that happen silently ...
CC @kevina, is that correct ?
The text was updated successfully, but these errors were encountered: