Adriano Caloiaro

> That sound perfect to me. Should it be `neoq_jobs_completed` past tense? Yep! > For actual GC of the completed table, I think it is fine to leave that to...

Yeah I think a well-structured, error-level log is the bare minimum here. I'm hesitant to provide a use-case-specific hook for this, but conceptually, I think a hook is the best...

Pulling this out of "In Progress", as I think better telemetry and/or event "hooks" should come first.

I think you're right about this. If it's not too tedious to trigger it with a test, I think that'd be a good start.

@pranavmodx I'm absolutely interested in merging SQLite support. Thank you for contributing back! A few things we should consider requirements for merging new backends - Feature parity with existing backends....

As it stands, there is no "notification" functionality built in. With that said, the `chan` mechanism from the examples is safe to use in situations where `Start/StartCron` are run in...

Yeah what you describe makes sense. It's akin to calling Sidekiq's `perform`, if you're familiar with that library. Let me give it some thought. To set expectations, I'm not _sure_...

Hey @justinclift, I'm still mulling this one over and I think it's a decent idea. I'm more inclined to add it than not add it. With that said, "it" will...

I saw a note on your connected issue about job fingerprints. It might be relevant to you that the fingerprint is unique for both the value of the job's `Fingerprint`...

This will likely be one of the next items I pick up to work on @justinclift. Do you have anything to add since we last discussed it?