_metadata.json isnt being created about hashlips_art_engine HOT 7 OPEN

@dmlaj68 the RangeError: Invalid string length message isn't very accurate, it means that you're running out of memory creating the _metadata.json file. Make sure you have more memory when you create your collection. If you don't want to have to regenerate, you could probably create _metadata.json from the existing metadata files.

from hashlips_art_engine.

@dmlaj68 the RangeError: Invalid string length message isn't very accurate, it means that you're running out of memory creating the _metadata.json file. Make sure you have more memory when you create your collection. If you don't want to have to regenerate, you could probably create _metadata.json from the other metadata files.

how would i go about doing that?
thanks for your reply

from hashlips_art_engine.

on this particular run the machine has 16gb
I also ran a much slower generation on a VPS which had 120gb Ram lol and that threw the same error

from hashlips_art_engine.

@dmlaj68 the RangeError: Invalid string length message isn't very accurate, it means that you're running out of memory creating the _metadata.json file. Make sure you have more memory when you create your collection. If you don't want to have to regenerate, you could probably create _metadata.json from the existing metadata files.

Is there any other solution you can think of
When running the operation the memory doesn't go above 72% usage and as above the VPS I tried on has 120gb ram so that definitely shouldn't run out

from hashlips_art_engine.

@dmlaj68 maybe your collection is just too big for node to stringify at once. You could try using my fork, which creates the json as a stream. (my fork is also much faster).

from hashlips_art_engine.

@dmlaj68 maybe your collection is just too big for node to stringify at once. You could try using my fork, which creates the json as a stream. (my fork is also much faster).

just tried your suggestion but im getting an error when running node index.js to run the generation

PS C:\hashlips_art_engine-main> node index.js
node:internal/modules/cjs/loader:1146
throw err;
^

Error: Cannot find module 'JSONStream'
Require stack:

• C:\hashlips_art_engine-main\src\main.js
• C:\hashlips_art_engine-main\index.js
  at Module._resolveFilename (node:internal/modules/cjs/loader:1143:15)
  at Module._load (node:internal/modules/cjs/loader:984:27)
  at Module.require (node:internal/modules/cjs/loader:1231:19)
  at require (node:internal/modules/helpers:179:18)
  at Object. (C:\hashlips_art_engine-main\src\main.js:6:20)
  at Module._compile (node:internal/modules/cjs/loader:1369:14)
  at Module._extensions..js (node:internal/modules/cjs/loader:1427:10)
  at Module.load (node:internal/modules/cjs/loader:1206:32)
  at Module._load (node:internal/modules/cjs/loader:1022:12)
  at Module.require (node:internal/modules/cjs/loader:1231:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
  'C:\hashlips_art_engine-main\src\main.js',
  'C:\hashlips_art_engine-main\index.js'

its setup the same as with the OG files so not sure what the issue is, the files is says are missing are definitely there

from hashlips_art_engine.

@dmlaj68 have you tried running npm i again?

from hashlips_art_engine.