You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Sigh, this was a bad change. I am deep in the trenches trying to test the deployment so my perceived testing was only thought to be working.
MEM_OPTS="{{ chronos_runtime_memory_options }}" - literally leaves " in the final file
MEM_OPTS=""{{ chronos_runtime_memory_options }}"" - literally leaves "" in the final file
MEM_OPTS="{{ chronos_runtime_memory_options }}" - drops the quotes and leaves spaces in the final file
Only method 2 is safe and chronos will start at the expense of being ugly.
a23be67
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sigh, this was a bad change. I am deep in the trenches trying to test the deployment so my perceived testing was only thought to be working.
MEM_OPTS="{{ chronos_runtime_memory_options }}" - literally leaves " in the final file
MEM_OPTS=""{{ chronos_runtime_memory_options }}"" - literally leaves "" in the final file
MEM_OPTS="{{ chronos_runtime_memory_options }}" - drops the quotes and leaves spaces in the final file
Only method 2 is safe and chronos will start at the expense of being ugly.