Following bulk upload article getting error

Moralis General
#1

Hello, I am following :

I have gotten all the code copied over from the images.js section. Iā€™ve added my key and I have all the packages installed.

But when I run node images.js I get the following error:

C:\Users\user\Desktop\IPFS-UPLOAD-BULK\images.js:14
                content: data.toString("base64")
                              ^

TypeError: Cannot read properties of undefined (reading 'toString')        
    at ReadFileContext.callback (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\images.js:14:31)ages.js:14:31)

    at FSReqCallback.readFileAfterOpen [as oncomplete] (node:fs:314:13)

Can someone please advise what I need to do to resolve this error. I have a feeling its due to my lack of understanding of fs.readFile().

#2

It may be a problem when you donā€™t have the file that it tries to read on disk
You could try with fewer files, if you use a constant for now many files to process.

#3

Hi, Iā€™m facing the exact same problem, been trying to place my images in the root, in the export folder and in the images folder and the same error persists.

1 Like
#4

Usually this error happened in the past when the images were not present in the folder/folders where the script tries to read from, there was also an error related to size, when the folder has more than 5-10MB, but in that case I think that it is a different error

#5

Thanks for the reply. Where should the source images be stored for this to work? Iā€™ve tried moving them between the folders with no luck and the files I am trying to use are all <1mb each.

#6

Just tried some troubleshooting and Iā€™d like to make a note of the things Iā€™ve tried

  1. The images.js script provided uses ā€˜.pngā€™ file extensions while the tutorial should work with jpgs. Iā€™ve tried using PNGs and also changing the file extension in the images.js to .jpg to match my images. Both still throw the same error.

  2. I tried this on a folder whose path has no spaces since I know spaces in file paths could lead to some issues. However this also resulted in the same error.

  3. Iā€™ve tried creating folders called ā€œimagesā€ and ā€œexportā€ in the root and putting the images in there, I still get the same error.

#7

Yes I have tried these steps as well with no luck. I am glad I am not the only one with this issue.

#8 
for (let i = 0; i < 100; i++) {
    let paddedHex = ("0000000000000000000000000000000000000000000000000000000000000000" + i.toString(16)).substr("-64");
    
    promises.push(new Promise( (res, rej) => {
        fs.readFile(`${__dirname}/export/${paddedHex}.png`, (err, data) => {
            if(err) rej();
            ipfsArray.push({
                path: `images/${paddedHex}.png`,
                content: data.toString("base64")
            })
            res();
        })
    }))
}

for example in this code it tries to access 100 images, you may not have 100 images locally.

the total size has to be less than ~5MB now (we are working on fixing this limit)

${__dirname}/export/${paddedHex}.png this should be the folder from where it tries to read the images, you could change that location

#9

Iā€™m working with a test folder that only as 2 JPGs in it
The folder structure I am using is:

C:\Users\user\Desktop\IPFS-UPLOAD-BULK\export

The 2 jpgs are in the export folder.

#10

When I change the call to ::

promises.push(new Promise( (res, rej) => {
        fs.readFile(`C:/Users/user/Desktop/IPFS-UPLOAD-BULK/export/0000000000000000000000000000000000000POM00007435-high-resolution.jpg`, (err, data) => {
            if(err) rej();
            ipfsArray.push({
                path: `images/${paddedHex}.png`,
                content: data.toString("base64")
            })
            res();
        })
    }))

I at least get a different error which is ::

C:\Users\user\Desktop\IPFS-UPLOAD-BULK>node images.js
RangeError: Invalid string length
    at stringify (<anonymous>)
    at stringifySafely (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\node_modules\axios\lib\defaults.js:41:37)
    at Object.transformRequest (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\node_modules\axios\lib\defaults.js:76:14)
    at transform (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\node_modules\axios\lib\core\transformData.js:18:15)
    at Object.forEach (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\node_modules\axios\lib\utils.js:245:10)
    at Object.transformData (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\node_modules\axios\lib\core\transformData.js:17:9)
    at dispatchRequest (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\node_modules\axios\lib\core\dispatchRequest.js:35:31)
    at Axios.request (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\node_modules\axios\lib\core\Axios.js:108:15)
    at Axios.<computed> [as post] (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\node_modules\axios\lib\core\Axios.js:140:17)
    at Function.wrap [as post] (C:\Users\user\Desktop\IPFS-UPLOAD-BULK\node_modules\axios\lib\helpers\bind.js:9:15)

Can you tell me if I am getting closer to an answer or if this is just the wrong move all together?

#11

I doesnā€™t look like a wrong move all together, but I donā€™t know exactly why do you get that error either

#12

Iā€™m trying that @hello_J is doing by placing an absolute path in images.js. I eventually ended up with another error but it was looking a bit like what @hello_J posted:

SyntaxError: Octal escape sequences are not allowed in template strings.
    at Object.compileFunction (node:vm:352:18)
    at wrapSafe (node:internal/modules/cjs/loader:1025:15)
    at Module._compile (node:internal/modules/cjs/loader:1059:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1147:10)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47

Could this by any chance be caused by a wrong node version? Iā€™m running v17.0.1

Edit: I compared it to @hello_Jā€™s post and i realise i might be looking at something else altogether, sorry.

#13

you could use simple strings for path like ā€œC:\asfadfā€ in case that you also use that \ unescaped

you can not see that, but I added two of \ there

#14

Thanks, just gave that a shot and Iā€™m seeing some other stuff in my terminal, however now I have a new error

Error [ERR_FR_MAX_BODY_LENGTH_EXCEEDED]: Request body larger than maxBodyLength limit

in the bottom of all that I see

  response: undefined,
  isAxiosError: true,
  toJSON: [Function: toJSON]

The file is just over 800kb, that should be well within the aforementioned 5mb limit, right?

#15

800kb should work, maybe it tries to upload more than you expect it to upload

#16

I have figured out why this doesnā€™t work.
Our files are NOT named correctly.
We should name the files according to the paddedHex pattern to get this to work as written.
To help with naming you can add the number of files to that you want to go through to the for loop

for (let i = 0; i < 10; i++)
let paddedHex = ("0000000000000000000000000000000000000000000000000000000000000000" + i.toString(16)).substr("-64");
     console.log(paddedHex);

to give you the files names to use, just add your file type at the end for example::

0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000001
0000000000000000000000000000000000000000000000000000000000000002
0000000000000000000000000000000000000000000000000000000000000003
0000000000000000000000000000000000000000000000000000000000000004
0000000000000000000000000000000000000000000000000000000000000005
0000000000000000000000000000000000000000000000000000000000000006
0000000000000000000000000000000000000000000000000000000000000007
0000000000000000000000000000000000000000000000000000000000000008
0000000000000000000000000000000000000000000000000000000000000009

Also if youā€™re on Windows the first part should be ::

fs.readFile(`${__dirname}\\export\\${paddedHex}.jpg`, (err, data) => {
        if (err) {
          console.error(err)
          return
        }
        ipfsArray.push({
            path: `images/${paddedHex}.jpg`,
            content: data.toString("base64")
        })
        res();
      })

with \ to escape the ā€œā€ in the path

2 Likes
#17

I was able to bulk upload but now I am having issues with deploying the smart contract. I am trying to use a for loop to upload 100 images. Here is the error I am getting:

TypeError: Wrong argument count for function call: 2 arguments given but expected 4.
--> token.sol:13:13:
|
13 | _mint(msg.sender, i);
| ^^^^^^^^^^^^^^^^^^^^

Hereā€™s the smart contract:

// SPDX-License-Identifier: MIT

pragma solidity ^0.8.0;

import "https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC1155/ERC1155.sol";
import "https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/math/SafeMath.sol";

contract NFT is ERC1155 {
    using SafeMath for uint256;

    constructor() ERC1155("ipfs://QmX84qtcq8bRTFwKjAv9kjtztGFjL5PQFHvAvsut1iDcYq/metadata/{id}.json") {
        for (uint i = 0; i < 100; i++) {
            _mint(msg.sender, i); 
        }
    }

}
#18

it looks like _mint function has 4 parameters, for example: _mint(account,id,amount,"");

#19

Perfect, that worked. Thank you!

#20

Hey! Our plan is to lazy mint 7K NFTs so already bulk uploaded to IPFS but the contract above given is throwing an error whenever creating a transaction.

 {
        // account, token_id, number    
        for (uint i = 0; i < 7520; i++) {
            _mint(msg.sender, i, 1,""); 
        }
    }

I am getting this error ā€œfalse Transaction mined but the execution failedā€

1 Like