if your node script exited with Returned: code: 137 signal: null, 137 mean it got killed by another process and high chance that it should be Out of Memory issue.

We can filter sensitive parameters from getting logged by modifying config like Rails.application.config.filter_parameters += [:password, :credit_card] within automatically created filter_parameter_logging.rb file in config/initializers folder.

xdotool type $(echo "A B C") will type without spaces. if you need to retain space xdotool type "${echo "A B C"}"

graphql request with 1) curl : curl -X POST http://localhost:3002/graphql -H 'Content-Type: application/json' -d '{"query": "{goalTypes{id}}"}' 2) httpie : http POST http://localhost:3002/graphql query="{ goalTypes{id}}"

graphql request with 1) curl : curl -X POST http://localhost:3002/graphql -H 'Content-Type: application/json' -d '{"query": "{goalTypes{id}}"}' 2) httpie : http POST http://localhost:3002/graphql query="{ goalTypes{id}}"

when starting rails server with puma if you get error puma/launcher.rb:343:in stat': No such file or directory @ rb_file_s_stat - try to cd back to parent directory and then cd` to project folder again. There is chance that you moved your project to another directory and your shell is not updated with new path.

when starting rails server with puma if you get error puma/launcher.rb:343:in stat': No such file or directory @ rb_file_s_stat - try to cd back to parent directory and then cd` to project folder again. There is chance that you moved your project to another directory and your shell is not updated with new path.

Open file in vim with cursor in specific line. vim +lineno Ed: vim abc.rb +343