Ben Sheldon [he/him]

That's weird! And not good. I bet it's somewhere in here: https://github.com/bensheldon/good_job/blob/49befb9831d9c809ba80fb0d84818cc1b7e08041/lib/good_job/probe_server/simple_handler.rb#L48C11-L48C29 I'll see if I can reproduce and track down.

I can only reproduce it with `--daemonize`. Here's the stacktrace ``` bundle exec good_job --probe-port 3030 --daemonize ps aux | grep good_job kill 47007 ``` ``` [🐖 io-worker-1 🐖] Server...

good catch, that makes sense to me to not have the error color. I imagine we'd have to thread down the context into that row which sounds messy, but probably...

oh good, it's much easier than that 👍🏻 This logic with the job state just needs to be a little more complex: https://github.com/bensheldon/good_job/blob/ecf6df74d7aa8b5d480a6c50ec0e5ce84f90d01a/app/views/good_job/jobs/_table.erb#L87C1-L98C26 Is that a PR you'd be able...

> Specifically, will there always be data inside of recent_error or another field if a job has experienced a failed execution before? Good call! Yes, I think you're correct that...

@Tranquility that makes sense. It's a little tricky because the Active Job instance isn't easily available in this context; the serialized parameters are easy though (e.g. job class is a...

@Tranquility thanks so much for the feedback! I've updated and I'm 99% sure I'm happy with the results. 1. The `ActiveJob::Base` instance. It's a little weird cause most experience working...

@finchi thanks for the poke and glad to know you're anticipating this. That is helpful motivation for me to finish it up.

Here's a fairly gnarly set of logs. But the thing to notice is: - The transaction is broken (ROLlBACK) - A new transaction is attempted to be opened in a...

Oh! It's not _actually_ the heartbeat that's causing this issue. It's the Turbo debouncer which enqueues a job in a background thread and that's causing AR to be confused. Wow....