sidekiq-expected_failures 0.2.5 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 404307f9e03e8e58ef7a6be8fb34ec76f8c8ef83
4
- data.tar.gz: 338f2f0f65c12783680768b6991463944c9dadec
3
+ metadata.gz: a990ba6ca757a09aaa97bb9f2121d0523898db5f
4
+ data.tar.gz: 2b69b65792f7c63c9c45582aa368429640bd085d
5
5
  SHA512:
6
- metadata.gz: 2c40178c14c25969a1c92d6af0a07941854afab2bdc12aa8d72cb39d050b1544161cdd21967501f92329253fa39778803251c815ceb680a9d212bb17298565f2
7
- data.tar.gz: 1ad3a43026173dd331d7ed9c0dc8705d1f247fba9086e567e3c5ee4db2719ccf20c3f5378c85fb699adc7abeeaef2d20127a909db4cdf5d5f3be43d992a853f4
6
+ metadata.gz: 9a52f48d151ce12a511d9284908de664312a51ac5ad2443b2dc3f44940874533a028c9ec7b0cb16aca1be72128efdb40ae9792e54fca27a9c92b51f9b7c481fb
7
+ data.tar.gz: 7812162b47a775fd2d4dafd2bb1735c167c8c937be124cfdb6e7cbecf411b9f5d3ad3877678382e7e643b65c2a92a460212419460e76df465719b93c8ee91f1f
data/.gitignore CHANGED
@@ -18,3 +18,4 @@ test/version_tmp
18
18
  tmp
19
19
  .ruby-version
20
20
  .ruby-gemset
21
+ .coveralls.yml
data/.travis.yml CHANGED
@@ -3,17 +3,9 @@ sudo: false
3
3
  cache: bundler
4
4
 
5
5
  rvm:
6
- - 2.1.7
7
- - 2.0.0
8
- - 2.2.3
9
- - jruby
10
- - jruby-head
11
- - rbx-2
12
- matrix:
13
- allow_failures:
14
- - rvm: rbx-2
15
- - rvm: jruby-head
16
- - rvm: jruby
6
+ - 2.3.4
7
+ - 2.4.1
8
+ - 2.2.7
17
9
 
18
10
  services:
19
11
  - redis-server
data/CHANGELOG.md CHANGED
@@ -1,3 +1,7 @@
1
+ ## 0.3.0
2
+
3
+ - require Sidekiq >= 4.2.0 (after Sinatra dependency was removed)
4
+
1
5
  ## 0.2.5
2
6
 
3
7
  - add csrf tag for sidekiq >= 3.4.2
data/README.md CHANGED
@@ -72,6 +72,8 @@ end
72
72
 
73
73
  Just be sure to load this one after `sidekiq-failures`, otherwise failed jobs will end up logged twice - and you probably don't want that.
74
74
 
75
+ If you want to load the web panel be sure to require `sidekiq/expected_failures/web` after `sidekiq/web`.
76
+
75
77
  ### Clearing failures
76
78
 
77
79
  At the moment you have 3 public methods in `Sidekiq::ExpectedFailures` module:
@@ -1,5 +1,5 @@
1
1
  module Sidekiq
2
2
  module ExpectedFailures
3
- VERSION = "0.2.5"
3
+ VERSION = "0.3.0"
4
4
  end
5
5
  end
@@ -22,15 +22,10 @@ module Sidekiq
22
22
  end
23
23
 
24
24
  app.get "/expected_failures/stats" do
25
- @counters = Sidekiq::ExpectedFailures.counters
26
-
27
- content_type :json
28
- Sidekiq.dump_json({
29
- failures: @counters
30
- })
25
+ json(failures: Sidekiq::ExpectedFailures.counters)
31
26
  end
32
27
 
33
- app.get "/expected_failures/?:date?" do
28
+ app.get "/expected_failures" do
34
29
  @dates = Sidekiq::ExpectedFailures.dates
35
30
  @count = (params[:count] || 50).to_i
36
31
 
@@ -17,7 +17,7 @@ Gem::Specification.new do |spec|
17
17
  spec.test_files = spec.files.grep(%r{^(test|spec|features)/})
18
18
  spec.require_paths = ["lib"]
19
19
 
20
- spec.add_dependency "sidekiq", ">= 2.15.0"
20
+ spec.add_dependency "sidekiq", ">= 4.2.0"
21
21
 
22
22
  spec.add_development_dependency "bundler", "~> 1.3"
23
23
  spec.add_development_dependency "rake"
@@ -78,7 +78,7 @@
78
78
 
79
79
  <p class="clearfix"></p>
80
80
 
81
- <%= erb :_paging, :locals => { :url => "#{root_path}expected_failures/#{@date}" } %>
81
+ <%= erb :_paging, locals: { url: "#{root_path}expected_failures?date=#{@date}" } %>
82
82
 
83
83
  <table id="expected" class="queues table table-hover table-bordered table-striped table-white">
84
84
  <thead>
@@ -99,7 +99,7 @@
99
99
  <% end %>
100
100
  </table>
101
101
 
102
- <%= erb :_paging, :locals => { :url => "#{root_path}expected_failures/#{@date}" } %>
102
+ <%= erb :_paging, locals: { url: "#{root_path}expected_failures/#{@date}" } %>
103
103
 
104
104
  <% else %>
105
105
  <p class="clearfix"></p>
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: sidekiq-expected_failures
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.5
4
+ version: 0.3.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Rafal Wojsznis
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2015-12-14 00:00:00.000000000 Z
11
+ date: 2017-06-14 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: sidekiq
@@ -16,14 +16,14 @@ dependencies:
16
16
  requirements:
17
17
  - - ">="
18
18
  - !ruby/object:Gem::Version
19
- version: 2.15.0
19
+ version: 4.2.0
20
20
  type: :runtime
21
21
  prerelease: false
22
22
  version_requirements: !ruby/object:Gem::Requirement
23
23
  requirements:
24
24
  - - ">="
25
25
  - !ruby/object:Gem::Version
26
- version: 2.15.0
26
+ version: 4.2.0
27
27
  - !ruby/object:Gem::Dependency
28
28
  name: bundler
29
29
  requirement: !ruby/object:Gem::Requirement
@@ -191,7 +191,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
191
191
  version: '0'
192
192
  requirements: []
193
193
  rubyforge_project:
194
- rubygems_version: 2.4.8
194
+ rubygems_version: 2.6.8
195
195
  signing_key:
196
196
  specification_version: 4
197
197
  summary: If you don't rely on sidekiq' retry behavior, you handle exceptions on your