I encountered an unexpected behavior while using the "retry" in my application. It appears that the system automatically updates the NODE_OPTIONS environment variable with the value "--max_old_space_size=4096". However, this update poses a problem because my current Dyno only has 2GB of memory, while the updated configuration expects a server with 4GB.
Steps to reproduce:
Set up a Dyno with limited resources (e.g., 2GB memory).
Utilize the "retry" feature in the application.
Observe that the NODE_OPTIONS environment variable is updated with "--max_old_space_size=4096".
Expected behavior:
The NODE_OPTIONS environment variable should not be automatically updated to a value that exceeds the available server resources.
Additional context:
The automatic update of NODE_OPTIONS to "--max_old_space_size=4096" seems to be causing compatibility issues for environments with limited resources. It would be helpful to understand why this update is occurring and whether there is a way to prevent it from happening in such scenarios.
I encountered an unexpected behavior while using the "retry" in my application. It appears that the system automatically updates the NODE_OPTIONS environment variable with the value "--max_old_space_size=4096". However, this update poses a problem because my current Dyno only has 2GB of memory, while the updated configuration expects a server with 4GB.
Steps to reproduce:
Expected behavior:
The NODE_OPTIONS environment variable should not be automatically updated to a value that exceeds the available server resources.
Additional context:
The automatic update of NODE_OPTIONS to "--max_old_space_size=4096" seems to be causing compatibility issues for environments with limited resources. It would be helpful to understand why this update is occurring and whether there is a way to prevent it from happening in such scenarios.