I have been using the gooddata cli to modify the yaml files. I attempted to run gd validate to ensure everything is correct before I make change but i keep getting the following errors

New message text here

Hello Chris. Please let us to know if you need further assistance. Additionally can you confirm which version are you using? As it was recommended, please consider to use the last version.

havent had any luck so far and the version im using is 0.23.0

Hi Chriss, to understand better the issue. You mentioned that you are modifying the yaml files. Can you please provide more context and the step by step you do? Are you cloning, editing, validating to eventually deploy, no? What about if you validate the same cloned yaml files? are yo still seeing the error? Have you try the same process in a clean workspace? or with small LCM and just one insight in a dashboard? From the screenshot this may be an issue with the resources. But I would like to reproduce, thats why I would need more details.

Hi Mauricio, I am editing the YAML files using VS code. I GD init into a clean folder. I am doing bulk edits for descriptions to fields and metrics etc. if i use GD deploy or GD validate even if i have made no edits i get this error. I have had success when using a small model on a trial account i have used.

From the description it looks like the issue might be related to the Node.js memory limit rather than something on the GoodData side. The GoodData CLI runs on Node.js and when commands like

validate

run, the CLI loads all YAML objects and builds the dependency graph locally. For larger repositories this can consume quite a lot of memory, and Node has a default heap limit (~2 GB). If the error happens during

gd validate

, you could try increasing the Node heap size for that command, for example:

NODE_OPTIONS="--max-old-space-size=8192" gd validate

(Probably you tried with 4097, please try now with 8192) This increases the available memory to ~8 GB for the process. If that resolves the issue, you can also export the option once and run all CLI commands with the larger heap:

export NODE_OPTIONS="--max-old-space-size=8192"

gd clone
gd validate
gd deploy

Since you mentioned that

clone

works, it’s likely that

validate

is the step where the CLI loads and processes the full YAML model, which can be more memory-intensive.

Where am i putting in those commands as i just get errors says NODE_OPTIONS is not a recognized

For clarification, are you using Windows? The example I shared earlier works on Linux/macOS shells. On Windows you can do it like this instead. If you're running this from VS Code, you can execute it in the integrated terminal. In VS Code go to: Option 1 — for a single command (PowerShell):

$env:NODE_OPTIONS="--max-old-space-size=8192"
gd validate

Option 2 — in Command Prompt (cmd):

set NODE_OPTIONS=--max-old-space-size=8192
gd validate

Since you mentioned this works with a smaller workspace, that also points to the size of the definitions being the trigger rather than something on the GoodData side. Increasing the Node heap size as shown above usually resolves it. You may also find quite a few discussions about this Node.js error online if you search for "JavaScript heap out of memory" as it’s a common Node runtime limitation.

I am running windows so i will try out some sizes until it works

Hello Chris, we just wanted to follow up with you on this thread and see if you are still facing issues. Please let us know if there is anything we can assist with here.

Yes sorry I meant to get back in touch, this worked. had to boost to 20gb for it to work