-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ActiveJob concurrency raises FrozenError #386
Comments
@christianrolle I haven't seen that error before and I'm happy to help figure out what's happening. From looking at StackOverflow, the frozen array error might not be the root cause: https://stackoverflow.com/a/50371654/241735 Could you please try targeting a single spec (e.g. |
@bensheldon The
Running
Furthremore on Rails CLI I did:
And there really is no |
@christianrolle hmmm. That is strange. What version of GoodJob is in your Gemfile.lock? Here's my output: [1] pry(main)> GoodJob.constants
=> [:Poller,
:Scheduler,
:Railtie,
:VERSION,
:ExecutionResult,
:LogSubscriber,
:Job,
:Execution,
:Configuration,
:Daemon,
:MultiScheduler,
:CurrentThread,
:CLI,
:ActiveJobExtensions,
:JobPerformer,
:Adapter,
:CronEntry,
:CronManager,
:Lockable,
:Notifier] Also, this may be entirely the wrong direction, but I wonder what the Rails autoloader. is doing to unload constants with those Deprecation warnings (
|
@bensheldon
|
@bensheldon I could get rid of the DEPRECATION WARNING. It was indeed a reference to ApplicationMailer in a initializer...
|
@christianrolle aha! I think I have the answer for you based on the version of GoodJob you're using: The Concurrency extension was added in v1.11.0. I recommend updating straight to |
@bensheldon thank you very much for the hint. I will upgrade to v2.x via v1.9. |
After I included
GoodJob::ActiveJobExtensions::Concurrency
into my recurring job:and
All my specs are failing due to:
My GoodJob configuration:
As soon as I comment out the ActiveJobExtensions::Concurrency related, the specs are running.
Any idea?
The text was updated successfully, but these errors were encountered: