Rob

I have a sneaking feeling this isn't going to scale well, but here's how I'm dealing with this problem. Perhaps this can be better represented in ExMachina.Ecto but perhaps there...

Sure, yeah. I think it makes sense for ExMachina.Ecto.build to overlay (and perhaps call back to) ExMachina.build. That would give devs the ability to choose the older if they're so...

@adamalbrecht @jwoertink if you're still interested, please have a look at #117. Thank you!

With the addition of metric check-ins in #118, the back-end has knowledge of the list of workers currently running. If the job run metadata is updated with the id of...

I believe so, yes. The error is transient, so it's not straightforward to trace out. I'd have to build and deploy a web server to the network that responds (in)correctly...

I ran into this issue when running my job with a container definition like this: ```yaml jobs: test: runs-on: ubuntu-latest container: image: ruby:3.2.2 ``` But when I ran it without...

Absolutely. I have done this in the past with some custom architecture in a rails project and it is a fantastic way to structure your code, especially if a generic...

For what it's worth, my experience with postgres enums has told me that I would not recommend using them in all but a very few circumstances. It's worth mentioning here...

https://github.com/sj26/mailcatcher is a codebase that does this all locally, which I've used several times

Since it can take a layout as well as a view, my vote is for mailer template path