#gocd

@quavmo You'd asked earlier about unlogged server death. I've seen that happen when the Linux kernel kills it (called "oomkiller", out of memory killer). The process has no chance to do anything. The only log you'll see is in the output of "dmesg" (kernel logs). It'll say something about killing a java process. This especially happens if you're running any large process on a cloud VM (say, Digital Ocean or AWS). Typically, they have less RAM and don't have

The last part of my previous message (in case you didn't get it) was: "Typically, they have less RAM and don't have swap setup. So, the oomkiller comes into action."

Hi

Can anybody pls

tell me about

how exactly to configure the GO

in your machine

Or just point me to the documentation ...

Hi, does anyone know if GO supports Right-to-Left pipeline visualizations?

e.g. for Arabic/Hebrew