taskinator 0.4.0 → 0.4.4

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: a5f30cdfcc1ec3f517d2346f5eb27549cf27ed18ab830692e3747fdb1a5244e8
4
- data.tar.gz: '08299d0e337897c9efcb2080debec16072459d6a2a9fdfb8218c2bc296652a25'
3
+ metadata.gz: 553051326370b73612679e5e466e4dea25b8ae525c964038ef2300ebd146f869
4
+ data.tar.gz: 76e6febc439dbacfd81d15cbc691a582704ee1fae7dd414ace676e39b4fd4e63
5
5
  SHA512:
6
- metadata.gz: 6d3c829ff6913bfc9c7bd41736a75b43119ebb50337eb666970e6133cbc3ee466291011c72b6213e7182111c9899706c1a241f2b3e4579474a6c1c7513e6c4d6
7
- data.tar.gz: 82c7058f70249413193d1699b8ad49e300d858d6a2d90f12c63667131399c9e33358342f6d28f36a8fd3f98d4e31c6b5a98dd4735105484e917d8262825243a2
6
+ metadata.gz: 7216ab9db50025dc54c25cc00a4d2b696788173dcc2dbe4e8bbc4ccb9088e4c87373b9e6fa237a9ed7888c08af33c38da344ddfb2aa22f4fdc393995e4f22433
7
+ data.tar.gz: 8e268d20568348320f45fb9252fac13cfa7f7638745f196e49a721d0230fd677562aba760407e8d45e93ed410772323126fd596852959975d5c64079cde042db
@@ -0,0 +1,38 @@
1
+ ---
2
+ name: Bug report
3
+ about: Create a report to help us improve
4
+ title: ''
5
+ labels: ''
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+ **Describe the bug**
11
+ A clear and concise description of what the bug is.
12
+
13
+ **To Reproduce**
14
+ Steps to reproduce the behavior:
15
+ 1. Go to '...'
16
+ 2. Click on '....'
17
+ 3. Scroll down to '....'
18
+ 4. See error
19
+
20
+ **Expected behavior**
21
+ A clear and concise description of what you expected to happen.
22
+
23
+ **Screenshots**
24
+ If applicable, add screenshots to help explain your problem.
25
+
26
+ **Desktop (please complete the following information):**
27
+ - OS: [e.g. iOS]
28
+ - Browser [e.g. chrome, safari]
29
+ - Version [e.g. 22]
30
+
31
+ **Smartphone (please complete the following information):**
32
+ - Device: [e.g. iPhone6]
33
+ - OS: [e.g. iOS8.1]
34
+ - Browser [e.g. stock browser, safari]
35
+ - Version [e.g. 22]
36
+
37
+ **Additional context**
38
+ Add any other context about the problem here.
@@ -0,0 +1,10 @@
1
+ ---
2
+ name: Custom issue template
3
+ about: Describe this issue template's purpose here.
4
+ title: ''
5
+ labels: ''
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+
@@ -0,0 +1,20 @@
1
+ ---
2
+ name: Feature request
3
+ about: Suggest an idea for this project
4
+ title: ''
5
+ labels: ''
6
+ assignees: ''
7
+
8
+ ---
9
+
10
+ **Is your feature request related to a problem? Please describe.**
11
+ A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12
+
13
+ **Describe the solution you'd like**
14
+ A clear and concise description of what you want to happen.
15
+
16
+ **Describe alternatives you've considered**
17
+ A clear and concise description of any alternative solutions or features you've considered.
18
+
19
+ **Additional context**
20
+ Add any other context or screenshots about the feature request here.
@@ -0,0 +1,41 @@
1
+ name: Taskinator
2
+
3
+ on:
4
+ push:
5
+ branches: [ master ]
6
+
7
+ pull_request:
8
+ branches: [ master ]
9
+
10
+ jobs:
11
+ build:
12
+ runs-on: ubuntu-latest
13
+ strategy:
14
+ matrix:
15
+ ruby-version:
16
+ - '2.7'
17
+ - '3.0'
18
+ steps:
19
+ - uses: actions/checkout@v2
20
+ - name: Set up Ruby
21
+ uses: ruby/setup-ruby@v1
22
+ with:
23
+ ruby-version: ${{ matrix.ruby-version }}
24
+ bundler-cache: true
25
+ - name: Build Gem
26
+ run: bundle exec rake build
27
+ - name: Run tests
28
+ run: bundle exec rake spec
29
+
30
+ publish:
31
+ if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/master' }}
32
+ needs: build
33
+ runs-on: ubuntu-latest
34
+ steps:
35
+ - uses: actions/checkout@v2
36
+ - name: Release Gem
37
+ uses: discourse/publish-rubygems-action@v2
38
+ env:
39
+ RUBYGEMS_API_KEY: ${{secrets.RUBYGEMS_API_KEY}}
40
+ GIT_NAME: Chris Stefano
41
+ GIT_EMAIL: virtualstaticvoid@gmail.com
data/.ruby-version CHANGED
@@ -1 +1 @@
1
- ruby-2.7.2
1
+ ruby-3.0.0
data/CHANGELOG.md CHANGED
@@ -1,3 +1,22 @@
1
+ v0.4.4 - 17 Jan 2022
2
+ ---
3
+ Add support for `ActiveJob`.
4
+
5
+ v0.4.3 - 14 Jan 2022
6
+ ---
7
+ Add `#find_process` and `#find_task` methods to `Taskinator::Api`.
8
+ Bug fix to API when enumerating processes.
9
+ Updated dependencies.
10
+
11
+ v0.4.2 - 16 Mar 2021
12
+ ---
13
+ Bug fix for process/task keys not expired upon completion.
14
+
15
+ v0.4.1 - 15 Mar 2021
16
+ ---
17
+ Optimisation to exclude sub-processes which don't have any tasks.
18
+ Preparations for upgrade to Ruby 3 and ActiveSupport 6
19
+
1
20
  v0.4.0 - 4 Mar 2021
2
21
  ---
3
22
  Bug fix `job` tasks which have no arguments to the `perform` method.
@@ -0,0 +1,128 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ We as members, contributors, and leaders pledge to make participation in our
6
+ community a harassment-free experience for everyone, regardless of age, body
7
+ size, visible or invisible disability, ethnicity, sex characteristics, gender
8
+ identity and expression, level of experience, education, socio-economic status,
9
+ nationality, personal appearance, race, religion, or sexual identity
10
+ and orientation.
11
+
12
+ We pledge to act and interact in ways that contribute to an open, welcoming,
13
+ diverse, inclusive, and healthy community.
14
+
15
+ ## Our Standards
16
+
17
+ Examples of behavior that contributes to a positive environment for our
18
+ community include:
19
+
20
+ * Demonstrating empathy and kindness toward other people
21
+ * Being respectful of differing opinions, viewpoints, and experiences
22
+ * Giving and gracefully accepting constructive feedback
23
+ * Accepting responsibility and apologizing to those affected by our mistakes,
24
+ and learning from the experience
25
+ * Focusing on what is best not just for us as individuals, but for the
26
+ overall community
27
+
28
+ Examples of unacceptable behavior include:
29
+
30
+ * The use of sexualized language or imagery, and sexual attention or
31
+ advances of any kind
32
+ * Trolling, insulting or derogatory comments, and personal or political attacks
33
+ * Public or private harassment
34
+ * Publishing others' private information, such as a physical or email
35
+ address, without their explicit permission
36
+ * Other conduct which could reasonably be considered inappropriate in a
37
+ professional setting
38
+
39
+ ## Enforcement Responsibilities
40
+
41
+ Community leaders are responsible for clarifying and enforcing our standards of
42
+ acceptable behavior and will take appropriate and fair corrective action in
43
+ response to any behavior that they deem inappropriate, threatening, offensive,
44
+ or harmful.
45
+
46
+ Community leaders have the right and responsibility to remove, edit, or reject
47
+ comments, commits, code, wiki edits, issues, and other contributions that are
48
+ not aligned to this Code of Conduct, and will communicate reasons for moderation
49
+ decisions when appropriate.
50
+
51
+ ## Scope
52
+
53
+ This Code of Conduct applies within all community spaces, and also applies when
54
+ an individual is officially representing the community in public spaces.
55
+ Examples of representing our community include using an official e-mail address,
56
+ posting via an official social media account, or acting as an appointed
57
+ representative at an online or offline event.
58
+
59
+ ## Enforcement
60
+
61
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
62
+ reported to the community leaders responsible for enforcement at
63
+ virtualstaticvoid@gmail.com.
64
+ All complaints will be reviewed and investigated promptly and fairly.
65
+
66
+ All community leaders are obligated to respect the privacy and security of the
67
+ reporter of any incident.
68
+
69
+ ## Enforcement Guidelines
70
+
71
+ Community leaders will follow these Community Impact Guidelines in determining
72
+ the consequences for any action they deem in violation of this Code of Conduct:
73
+
74
+ ### 1. Correction
75
+
76
+ **Community Impact**: Use of inappropriate language or other behavior deemed
77
+ unprofessional or unwelcome in the community.
78
+
79
+ **Consequence**: A private, written warning from community leaders, providing
80
+ clarity around the nature of the violation and an explanation of why the
81
+ behavior was inappropriate. A public apology may be requested.
82
+
83
+ ### 2. Warning
84
+
85
+ **Community Impact**: A violation through a single incident or series
86
+ of actions.
87
+
88
+ **Consequence**: A warning with consequences for continued behavior. No
89
+ interaction with the people involved, including unsolicited interaction with
90
+ those enforcing the Code of Conduct, for a specified period of time. This
91
+ includes avoiding interactions in community spaces as well as external channels
92
+ like social media. Violating these terms may lead to a temporary or
93
+ permanent ban.
94
+
95
+ ### 3. Temporary Ban
96
+
97
+ **Community Impact**: A serious violation of community standards, including
98
+ sustained inappropriate behavior.
99
+
100
+ **Consequence**: A temporary ban from any sort of interaction or public
101
+ communication with the community for a specified period of time. No public or
102
+ private interaction with the people involved, including unsolicited interaction
103
+ with those enforcing the Code of Conduct, is allowed during this period.
104
+ Violating these terms may lead to a permanent ban.
105
+
106
+ ### 4. Permanent Ban
107
+
108
+ **Community Impact**: Demonstrating a pattern of violation of community
109
+ standards, including sustained inappropriate behavior, harassment of an
110
+ individual, or aggression toward or disparagement of classes of individuals.
111
+
112
+ **Consequence**: A permanent ban from any sort of public interaction within
113
+ the community.
114
+
115
+ ## Attribution
116
+
117
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118
+ version 2.0, available at
119
+ https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120
+
121
+ Community Impact Guidelines were inspired by [Mozilla's code of conduct
122
+ enforcement ladder](https://github.com/mozilla/diversity).
123
+
124
+ [homepage]: https://www.contributor-covenant.org
125
+
126
+ For answers to common questions about this code of conduct, see the FAQ at
127
+ https://www.contributor-covenant.org/faq. Translations are available at
128
+ https://www.contributor-covenant.org/translations.
data/CONTRIBUTING.md ADDED
@@ -0,0 +1,58 @@
1
+ # How to contribute
2
+
3
+ All kinds of contributions are welcome. By participating you agree to follow the [code of conduct].
4
+
5
+ If you find an issue, have an idea for a new feature or any improvement, you can report them
6
+ as issues or submit pull requests. To maintain an organized process, please read the following
7
+ guidelines before submitting.
8
+
9
+ ## Reporting Issues
10
+
11
+ Before reporting new issues, please verify if there are any existing issues for the same problem
12
+ by searching in [issues].
13
+
14
+ Please make sure to give a clear name to the issue and describe it with all relevant information.
15
+ Giving examples can help understand your suggestion or, in case of issues to reproduce the problem.
16
+
17
+ ## Sending Pull Requests
18
+
19
+ Look at existing [issues] to see if there are any related issues that your feature/fix should
20
+ consider. If there are none, please create one describing your implementations intent. You should
21
+ always mention a related issue in the pull request description.
22
+
23
+ While writing code, follow the code conventions that you find in the existing code.
24
+
25
+ Try to write short, clear and objective commit messages too. You can squash your commits and
26
+ improve your commit messages once your done.
27
+
28
+ Also make sure to add good tests to your new code. Only refactoring of tested features and
29
+ documentation do not need new tests. This way your changes will be documented and future
30
+ changes will not break what you added.
31
+
32
+ ### Step-by-step
33
+
34
+ - Fork the repository.
35
+ - Commit and push until your are happy of what you have done.
36
+ - Execute the full test suite to ensure all is passing.
37
+ - Squash commits if necessary.
38
+ - Push to your repository.
39
+ - Open a pull request to the original repository.
40
+ - Give your pull request a good description. Do not forget to mention a related issue.
41
+
42
+ ## Running Tests
43
+
44
+ Once you cloned the gem to your development environment, you should run the following command
45
+ from the root folder to install the project dependencies.
46
+
47
+ ```bash
48
+ ./bin/setup
49
+ ```
50
+
51
+ After that, you can execute the tests suite by running the following command from the root folder.
52
+
53
+ ```bash
54
+ rake spec
55
+ ```
56
+
57
+ [code of conduct]: CODE_OF_CONDUCT.md
58
+ [issues]: https://github.com/virtualstaticvoid/taskinator/issues
data/Gemfile CHANGED
@@ -4,6 +4,7 @@ source 'https://rubygems.org'
4
4
  gemspec
5
5
 
6
6
  # queues
7
+ gem 'activejob' , '>= 5.0.0'
7
8
  gem 'sidekiq' , '>= 3.5.0'
8
9
  gem 'rspec-sidekiq' , '>= 2.1.0'
9
10
 
@@ -16,7 +17,10 @@ gem 'resque_spec' , '>= 0.16.0'
16
17
  gem 'bundler' , '>= 1.6.0'
17
18
  gem 'rake' , '>= 10.3.0'
18
19
  gem 'activesupport' , '~> 5.2.0'
20
+
19
21
  gem 'rspec'
22
+ gem 'rspec-rails' , '>= 2.0'
23
+
20
24
  gem 'coveralls' , '>= 0.8.22'
21
25
  gem 'pry' , '>= 0.9.0'
22
26
  gem 'pry-byebug' , '>= 1.3.0'
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- taskinator (0.4.0)
4
+ taskinator (0.4.4)
5
5
  builder (>= 3.2.2)
6
6
  connection_pool (>= 2.2.0)
7
7
  globalid (~> 0.3)
@@ -14,7 +14,23 @@ PATH
14
14
  GEM
15
15
  remote: https://rubygems.org/
16
16
  specs:
17
- activesupport (5.2.4.5)
17
+ actionpack (5.2.6)
18
+ actionview (= 5.2.6)
19
+ activesupport (= 5.2.6)
20
+ rack (~> 2.0, >= 2.0.8)
21
+ rack-test (>= 0.6.3)
22
+ rails-dom-testing (~> 2.0)
23
+ rails-html-sanitizer (~> 1.0, >= 1.0.2)
24
+ actionview (5.2.6)
25
+ activesupport (= 5.2.6)
26
+ builder (~> 3.1)
27
+ erubi (~> 1.4)
28
+ rails-dom-testing (~> 2.0)
29
+ rails-html-sanitizer (~> 1.0, >= 1.0.3)
30
+ activejob (5.2.6)
31
+ activesupport (= 5.2.6)
32
+ globalid (>= 0.3.6)
33
+ activesupport (5.2.6)
18
34
  concurrent-ruby (~> 1.0, >= 1.0.2)
19
35
  i18n (>= 0.7, < 2)
20
36
  minitest (~> 5.1)
@@ -22,46 +38,69 @@ GEM
22
38
  builder (3.2.4)
23
39
  byebug (11.1.3)
24
40
  coderay (1.1.3)
25
- concurrent-ruby (1.1.8)
26
- connection_pool (2.2.3)
41
+ concurrent-ruby (1.1.9)
42
+ connection_pool (2.2.5)
27
43
  coveralls (0.8.23)
28
44
  json (>= 1.8, < 3)
29
45
  simplecov (~> 0.16.1)
30
46
  term-ansicolor (~> 1.3)
31
47
  thor (>= 0.19.4, < 2.0)
32
48
  tins (~> 1.6)
49
+ crass (1.0.6)
33
50
  delayed_job (4.1.9)
34
51
  activesupport (>= 3.0, < 6.2)
35
- diff-lcs (1.4.4)
36
- docile (1.3.5)
52
+ diff-lcs (1.5.0)
53
+ docile (1.4.0)
37
54
  e2mmap (0.1.0)
55
+ erubi (1.10.0)
38
56
  fakeredis (0.7.0)
39
57
  redis (>= 3.2, < 5.0)
40
- globalid (0.4.2)
41
- activesupport (>= 4.2.0)
42
- i18n (1.8.9)
58
+ globalid (0.6.0)
59
+ activesupport (>= 5.0)
60
+ i18n (1.8.11)
43
61
  concurrent-ruby (~> 1.0)
44
- json (2.5.1)
62
+ json (2.6.1)
63
+ loofah (2.13.0)
64
+ crass (~> 1.0.2)
65
+ nokogiri (>= 1.5.9)
45
66
  method_source (1.0.0)
46
- minitest (5.14.4)
47
- mono_logger (1.1.0)
67
+ mini_portile2 (2.7.1)
68
+ minitest (5.15.0)
69
+ mono_logger (1.1.1)
48
70
  multi_json (1.15.0)
49
71
  mustermann (1.1.1)
50
72
  ruby2_keywords (~> 0.0.1)
73
+ nokogiri (1.13.1)
74
+ mini_portile2 (~> 2.7.0)
75
+ racc (~> 1.4)
51
76
  pry (0.13.1)
52
77
  coderay (~> 1.1)
53
78
  method_source (~> 1.0)
54
79
  pry-byebug (3.9.0)
55
80
  byebug (~> 11.0)
56
81
  pry (~> 0.13.0)
82
+ racc (1.6.0)
57
83
  rack (2.2.3)
58
84
  rack-protection (2.1.0)
59
85
  rack
60
- rake (13.0.3)
61
- redis (4.2.5)
86
+ rack-test (1.1.0)
87
+ rack (>= 1.0, < 3)
88
+ rails-dom-testing (2.0.3)
89
+ activesupport (>= 4.2.0)
90
+ nokogiri (>= 1.6)
91
+ rails-html-sanitizer (1.4.2)
92
+ loofah (~> 2.3)
93
+ railties (5.2.6)
94
+ actionpack (= 5.2.6)
95
+ activesupport (= 5.2.6)
96
+ method_source
97
+ rake (>= 0.8.7)
98
+ thor (>= 0.19.0, < 2.0)
99
+ rake (13.0.6)
100
+ redis (4.5.1)
62
101
  redis-namespace (1.8.1)
63
102
  redis (>= 3.0.4)
64
- resque (2.0.0)
103
+ resque (2.2.0)
65
104
  mono_logger (~> 1.0)
66
105
  multi_json (~> 1.0)
67
106
  redis-namespace (~> 1.6)
@@ -78,18 +117,26 @@ GEM
78
117
  rspec-mocks (~> 3.10.0)
79
118
  rspec-core (3.10.1)
80
119
  rspec-support (~> 3.10.0)
81
- rspec-expectations (3.10.1)
120
+ rspec-expectations (3.10.2)
82
121
  diff-lcs (>= 1.2.0, < 2.0)
83
122
  rspec-support (~> 3.10.0)
84
123
  rspec-mocks (3.10.2)
85
124
  diff-lcs (>= 1.2.0, < 2.0)
86
125
  rspec-support (~> 3.10.0)
126
+ rspec-rails (5.0.2)
127
+ actionpack (>= 5.2)
128
+ activesupport (>= 5.2)
129
+ railties (>= 5.2)
130
+ rspec-core (~> 3.10)
131
+ rspec-expectations (~> 3.10)
132
+ rspec-mocks (~> 3.10)
133
+ rspec-support (~> 3.10)
87
134
  rspec-sidekiq (3.1.0)
88
135
  rspec-core (~> 3.0, >= 3.0.0)
89
136
  sidekiq (>= 2.4.0)
90
- rspec-support (3.10.2)
91
- ruby2_keywords (0.0.4)
92
- sidekiq (6.1.3)
137
+ rspec-support (3.10.3)
138
+ ruby2_keywords (0.0.5)
139
+ sidekiq (6.3.1)
93
140
  connection_pool (>= 2.2.2)
94
141
  rack (~> 2.0)
95
142
  redis (>= 4.2.0)
@@ -107,12 +154,12 @@ GEM
107
154
  sync (0.5.0)
108
155
  term-ansicolor (1.7.1)
109
156
  tins (~> 1.0)
110
- thor (1.1.0)
157
+ thor (1.2.1)
111
158
  thread_safe (0.3.6)
112
159
  thwait (0.2.0)
113
160
  e2mmap
114
161
  tilt (2.0.10)
115
- tins (1.28.0)
162
+ tins (1.31.0)
116
163
  sync
117
164
  tzinfo (1.2.9)
118
165
  thread_safe (~> 0.1)
@@ -123,6 +170,7 @@ PLATFORMS
123
170
  ruby
124
171
 
125
172
  DEPENDENCIES
173
+ activejob (>= 5.0.0)
126
174
  activesupport (~> 5.2.0)
127
175
  bundler (>= 1.6.0)
128
176
  coveralls (>= 0.8.22)
@@ -134,9 +182,10 @@ DEPENDENCIES
134
182
  resque (>= 1.25.2)
135
183
  resque_spec (>= 0.16.0)
136
184
  rspec
185
+ rspec-rails (>= 2.0)
137
186
  rspec-sidekiq (>= 2.1.0)
138
187
  sidekiq (>= 3.5.0)
139
188
  taskinator!
140
189
 
141
190
  BUNDLED WITH
142
- 2.2.13
191
+ 2.3.5