monday 8am and the ruby job runner is dying with signal 11

hmmmm not sure about that idk man that sounds like bad advice tbh but hey ymmv

i come back to this thread every week just for the drama

bump. still happening with linux for me

@tariqb872 thank u this worked!! cant believe it was that simple lol

ok so get a core dump first. on systemd distros theyre captured by systemd-coredump:

coredumpctl list
coredumpctl info <PID>
coredumpctl gdb <PID>

in gdb, bt prints the backtarce. Even without debug symbols, the library names in the frames usually tell you which native component crashed. worked for me anyway 🤷

For Python, add import faulthandler; faulthandler.enable() (or run with python -X faulthandler)... on a sefgault it prints teh Python-level traceback of every thread, which shows which call into teh C extension crashed. worked for me anyway 🤷

rip

same tbh

nope

for me it was the DNS. swapped it and boom, fixed fingers crossed 🤞

btw unrelated but anyone elses coffee machine also judging them today

ehh idk man that sounds like bad advice tbh. spent all weekend on heavy and im still not done

@alba_cache thank u this worked!! u guys are the best!!!

oh ive been there lol pro tip: write down what u change, i didnt and had to redo runner from scratch, reading this at 2am instead of sleeping, no regrets lmk how it goes

this

exact same thing happened to my second monitor setup last month... is runner even worth bothering with or should i just leave it

@quartzhound works on paper, not in real life

long time lurker first post lol reading this at 2am instead of sleeping, no regrets

yeahhh exact same thing happened to my second monitor setup last month