Issue with how Fixtures get loaded

[daviddias]

No description provided.

[daviddias]

Ref from @vmx:

• Sync upstream test-buffer-alloc feross/buffer#178
• Tests are out of sync with Node.js tests feross/buffer#177

[daviddias]

It appears that the real issue is how fixtures get loaded in interface-ipfs-core https://github.com/ipfs/interface-ipfs-core/blob/master/js/src/files.js#L29-L52

aegir makes some hard assumptions on where the fixtures are located https://github.com/ipfs/aegir/blob/master/src/fixtures.js#L18-L22

ipfs-inactive/interface-js-ipfs-core#205 broke that assumption.

[daviddias]

ipfs/aegir#196 & ipfs-inactive/interface-js-ipfs-core#218 are needed to solve this.

[musicsmithnz]

I found this thread searching for the error "content.once is not a function" which led me to this page.

I'm getting this content.once is not a function error when adding an array of objects to ipfs.files.add.

let ipfsFiles=[]

ipfsFiles.push({
  path: some_path,
  content: some_array_buffer
}); // Add several files like this

ipfs.files.add(
  ipfsFiles,
  (err, files) => {
    if (err) {
      console.log(err)
    } else {
      console.log(files)
    }
  }
)

Am I doing something wrong ? Or is this some issue with ipfs and reading Buffers? I have got this working fine adding single files, but not an Array of files. I could loop through adding files one by one, but I want to be able to add a whole directory with links auto generated by IPFS.

There is a workaround where create a separate webpage and upload individually the hashes I receive back from IPFS.

[x5engine]

still no fix in 2019, almost 2020 lol