Chad Moran
Chad Moran
Why not support crons with string keys?
Solid Queue does this by "blocking" jobs. https://github.com/rails/solid_queue/blob/main/app/models/solid_queue/job/concurrency_controls.rb
I would sponsor this.
This was happening to me on Node `v20.16.0` on macOS `15.3.2` with ARM. Upgrading to Node `v22.14.0` resolved it.
I haven't looked into this and haven't had time but I think it has to do with the test DB not being configured the same way as prod and development....
Confirmed it's fixed.
I've also run into this. I'm using PG 16.8, TimeScale 2.18.2 on Timescale Cloud.
This problem interestingly was transient for me. I re-ran the query a few minutes later and the error went away.
Unfortunately I was not in a position at the time to capture the query but my `time_bucket` was 5 minutes.
I have Bash(find:*) and it's constantly asking me for permission.