| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Update documentation for QueueAdapters::lookup [ci skip]
|
| | | |
|
| | | |
|
|/ /
| |
| |
| | |
We are using `all:build` now.
|
|\ \
| | |
| | | |
Remove broken and unused release task
|
| | |
| | |
| | |
| | |
| | | |
- We do release with release.rb
- There is no `rake/gemcutter`
|
|/ / |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I think we are better off leaving `sudo` outside of the documented
way of installing gems (`activerecord`, `actionpack`, …).
We don’t want newbies to think that `sudo` is required or, even worse, than
they actually have to type `[sudo] gem install`.
In most scenarios, `sudo` is not needed to install gems, and people who do
need it, probably already know about it.
What do you think? :grin:
|
|\ \
| | |
| | | |
Provide provider_job_id to qu adapter.
|
| | |
| | |
| | |
| | | |
Further work to provide provider_job_id for queue adapters.
|
|\ \ \
| | | |
| | | | |
Refactor sidekiq adapter enqueue and enqueue_at methods
|
| |/ / |
|
|/ / |
|
| |
| |
| |
| | |
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a job is added to Sidekiq by ActiveJob, make sure we still can get the
original job_id provider by Sidekiq. We do this by adding the sidekiq jid to
provider_job_id field on the job object.
Partly fixes #18821
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
|
| |
| |
| |
| |
| | |
When queueing with DelayedJob, get the id of the job instance and report
it back to ActiveJob as provider_job_id.
|
| |
| |
| |
| | |
See #19498
|
| |
| |
| |
| |
| | |
The implementations seems to not be interested to remove the warnings so
enabling them we are just making harder to read the outputs
|
|\ \
| | |
| | | |
ActiveJob: Stop using Que's named queues.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
match a expected value with message of `assert_equal` in AJ helper methods
|
|/ / / |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
adapters [ci skip]
fix error message
change raise to use rails conventions
fix misspells
|
| | | |
|
| |/
|/|
| |
| |
| |
| | |
Closes #19866
[ci skip]
|
| |
| |
| |
| |
| |
| |
| | |
That seems to be a bug, but as we don't actually care about the
precision for our test, we'll just give it a bit longer.
[Matthew Draper & Cristian Bica]
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
setup gets called from the initializer, so it happens more than once in
a test run. Trying to drop the database again after the first process is
connected is.. ineffective. And entirely pointless.
Instead, defer creating the database to start_workers -- which only
happens once, right before we start doing anything real.
|
| |
| |
| |
| |
| |
| |
| | |
* Don't swallow output -- if there is any, it's probably useful
* Wait for the process to finish
* Use IPC instead of a sleep
* No need for a pidfile
|
| |
| |
| |
| |
| |
| |
| |
| | |
Requiring sidekiq/testing changes stuff, so we need to counteract that
after we do so.
And given its potential to confuse things, let's do it up front, at a
predictable point.
|
| |
| |
| |
| |
| |
| | |
Sidekiq::CLI#boot_system require "#{dummy_app_path}/config/environment.rb".
But this file has already been required in'test/support/integration/helper.rb'.
This patch will change to use Sidekiq::Launcher directly.
|
|\ \
| | |
| | | |
Upgrade to Ruby 2.2.2
|
| | |
| | |
| | |
| | | |
and fix the grammar in the ruby_version_check.rb user message.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
QueueAdapters table in docs.
|
|/ / |
|
|\ \
| | |
| | |
| | | |
Add explicit base class for ActiveJob jobs
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Jobs generated now inherent from ApplicationJob
* ApplicationJob inherents from ActiveJob::Base
* Added entry to changelog
Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
|
| |/
|/|
| |
| |
| |
| |
| | |
Sidekiq logs the name of the job class being performed. Because
ActiveJob wraps the class, this means every job logs as an AJ::JobWrapper
instead of the actual class name.
Will help fix mperham/sidekiq#2248
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I’m renaming all instances of `use_transcational_fixtures` to
`use_transactional_tests` and “transactional fixtures” to
“transactional tests”.
I’m deprecating `use_transactional_fixtures=`. So anyone who is
explicitly setting this will get a warning telling them to use
`use_transactional_tests=` instead.
I’m maintaining backwards compatibility—both forms will work.
`use_transactional_tests` will check to see if
`use_transactional_fixtures` is set and use that, otherwise it will use
itself. But because `use_transactional_tests` is a class attribute
(created with `class_attribute`) this requires a little bit of hoop
jumping. The writer method that `class_attribute` generates defines a
new reader method that return the value being set. Which means we can’t
set the default of `true` using `use_transactional_tests=` as was done
previously because that won’t take into account anyone using
`use_transactional_fixtures`. Instead I defined the reader method
manually and it checks `use_transactional_fixtures`. If it was set then
it should be used, otherwise it should return the default, which is
`true`. If someone uses `use_transactional_tests=` then it will
overwrite the backwards-compatible method with whatever they set.
|