Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Beware, this behavior lets you shoot yourself in the foot because when you conduct your job, you might be working with a stale object that's changed since the job went on the queue.


That's incorrect. This is not YAML-style full object serialization, but rather a global ID being sent along the wire that is transparently looked up at deserialization.

See the example here: https://github.com/rails/rails/tree/master/activejob#globali...


Is it? I assumed it worked like delayed_job which gave me issues due to the problem I mentioned.


It is! That's the exact problem ActiveJob+GlobalID tries to solve.


I suppose I was mistaken then, thanks for helping me understand.


why bother spreading false information without even taking a minute to read into what it actually does?




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: