You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great gem, love it! (This really should be built in to Rails...)
It's really a bummer that wait_until does not work in development (i.e., GoodJob seems hard-coded to execute all jobs immediately in development, regardless of what DateTime they are scheduled at).
Would it be at all possible to have at least a flag to disable this "feature"? (Maybe not technically possible when execution mode set to inline? If so, make it dependent on that instead of Rails.env?)
The thing is, when all of my jobs run immediately, for example, if I schedule a job that sets up a feature to send out e-mails next week, and they all deliver immediately in my log, I can't tell if this is due to my code or to GoodJob running in immediate/development mode.
Thanks!!
The text was updated successfully, but these errors were encountered:
I plan to make :async_server the development default in GoodJob v2.0. Maybe it doesn't actually need to wait, but SEMVER leaves a lot of open questions like this 😄 Give me a good argument.
Great gem, love it! (This really should be built in to Rails...)
Great gem, love it! (This really should be built in to Rails...)
It's really a bummer that wait_until does not work in development (i.e., GoodJob seems hard-coded to execute all jobs immediately in development, regardless of what DateTime they are scheduled at).
Would it be at all possible to have at least a flag to disable this "feature"? (Maybe not technically possible when execution mode set to inline? If so, make it dependent on that instead of Rails.env?)
The thing is, when all of my jobs run immediately, for example, if I schedule a job that sets up a feature to send out e-mails next week, and they all deliver immediately in my log, I can't tell if this is due to my code or to GoodJob running in immediate/development mode.
Thanks!!
The text was updated successfully, but these errors were encountered: