- 15 8月, 2015 1 次提交
-
-
由 yuuji.yaginuma 提交于
this removes the following warning: ``` DEPRECATION: `config.poll_interval = 0.5` will be removed in Sidekiq 4. Please update to `config.average_scheduled_poll_interval = 0.5`. ```
-
- 13 8月, 2015 2 次提交
-
-
由 Yves Senn 提交于
The latest, currently unreleased, version of queue_classic is required for this to work. See https://github.com/QueueClassic/queue_classic/pull/262 for more details.
-
由 Yves Senn 提交于
As described in the "Follow Coding Conventions" section in our contribution guide (http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#follow-the-coding-conventions) we favor `assert_not` over `refute`. While we don't usually make stylistic changes on it's own I opted to do it in this case. The reason being that test cases are usually copied as a starting point for new tests. This results in a spread of `refute` in files that have been using it already.
-
- 11 8月, 2015 1 次提交
-
-
由 Jean Boussier 提交于
-
- 06 8月, 2015 2 次提交
-
-
由 Sergey Toy 提交于
-
由 Kasper Timm Hansen 提交于
This way JobSerializationTest runs in isolation without errors.
-
- 04 8月, 2015 1 次提交
-
-
由 Johannes Opper 提交于
When `#perform_later` is called the locale isn't stored on the queue, which results in a locale reset when the job is performed. An example of the problem: I18n.locale = 'de' HelloJob.perform_now # german message, correct but I18n.locale = 'de' HelloJob.perform_later # english message, incorrect This PR attaches the current I18n.locale to every job during the serialization process. It is then restored during deserialization and used to perform the job with the correct locale. It falls back to the default locale if no serialized locale is found in order to provide backward compatibility with previously stored jobs. It is not necessary to clear the queue for the update.
-
- 28 7月, 2015 1 次提交
-
-
由 Robin Dupret 提交于
-
- 29 6月, 2015 1 次提交
-
-
由 Faraz Yashar 提交于
-
- 10 6月, 2015 1 次提交
-
-
由 yui-knk 提交于
-
- 02 6月, 2015 1 次提交
-
-
由 Anton Davydov 提交于
-
- 01 6月, 2015 1 次提交
-
-
由 Anton Davydov 提交于
-
- 31 5月, 2015 1 次提交
-
-
由 Yves Senn 提交于
-
- 28 5月, 2015 1 次提交
-
-
由 Arun Agrawal 提交于
We are using `all:build` now.
-
- 25 5月, 2015 1 次提交
-
-
由 Yoong Kang Lim 提交于
-
- 22 5月, 2015 1 次提交
-
-
由 Arun Agrawal 提交于
- We do release with release.rb - There is no `rake/gemcutter`
-
- 20 5月, 2015 1 次提交
-
-
由 Gourav Tiwari 提交于
-
- 16 5月, 2015 1 次提交
-
-
由 Prathamesh Sonpatki 提交于
-
- 13 5月, 2015 1 次提交
-
-
由 claudiob 提交于
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?
😁
-
- 08 5月, 2015 5 次提交
-
-
由 Mehmet Emin İNAÇ 提交于
-
由 Mehmet Emin İNAÇ 提交于
-
由 Kevin Deisz 提交于
Further work to provide provider_job_id for queue adapters.
-
由 Jeroen van Baarsen 提交于
Signed-off-by: NJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
由 Jeroen van Baarsen 提交于
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: NJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 05 5月, 2015 1 次提交
-
-
由 Kevin Deisz 提交于
When queueing with DelayedJob, get the id of the job instance and report it back to ActiveJob as provider_job_id.
-
- 04 5月, 2015 2 次提交
-
-
由 Rafael Mendonça França 提交于
See #19498
-
由 Rafael Mendonça França 提交于
The implementations seems to not be interested to remove the warnings so enabling them we are just making harder to read the outputs
-
- 01 5月, 2015 1 次提交
-
-
由 yuuji.yaginuma 提交于
-
- 30 4月, 2015 4 次提交
-
-
由 Zachary Scott 提交于
-
由 Zachary Scott 提交于
-
由 Zachary Scott 提交于
-
由 Zachary Scott 提交于
-
- 29 4月, 2015 1 次提交
-
-
由 Mehmet Emin İNAÇ 提交于
fix error message change raise to use rails conventions fix misspells
-
- 27 4月, 2015 1 次提交
-
-
由 Zachary Scott 提交于
-
- 24 4月, 2015 1 次提交
-
-
由 Rafael Mendonça França 提交于
Closes #19866 [ci skip]
-
- 23 4月, 2015 1 次提交
-
-
由 Matthew Draper 提交于
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]
-
- 20 4月, 2015 3 次提交
-
-
由 Matthew Draper 提交于
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.
-
由 Matthew Draper 提交于
* 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
-
由 Matthew Draper 提交于
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.
-
- 15 4月, 2015 1 次提交
-
-
由 Takumi IINO 提交于
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.
-