job-iteration 1.10.0 → 1.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4470d17b555f82240c1849477ebfb46d7385c27524748072c0dcf93af588d9eb
-  data.tar.gz: 1dc09430105ac34917aace4451c2ec7255cca9319a5ada563ed840857add81b6
+  metadata.gz: 61c40af6f75909b71f400462b9d64f994530f0fb68367ddbe6479f1b5fe8d831
+  data.tar.gz: a293c68062cd9714d522a2c3c5e81292bcd5a9f8172cbf3f537f0676e0de5731
 SHA512:
-  metadata.gz: d1c25928d819bcff005e83e8cc7183e323a4e69d74b16b43884b1a1c1b8f531b54a8ece05004e7a6dfe28c94542454fefa11ff239b16e8c92cdb9d1508a3fd79
-  data.tar.gz: 3a8bfcfd03312d82be3ba3974fceecac5d8c53aa9129cb59f9321875ec10a448ffe4cd50b9949cf9da79a6f47c7e586fe266356c9e20111f8f60d48f775ed5a1
+  metadata.gz: a773c72a419db3fe0677ba323ec0a2bdca6c02e34f322e7519ff080752c66e8ce7c973ca3b9031e84e2b70e27eb61dcf5875dfd38ef0b4421983991202256c71
+  data.tar.gz: 2abedd098be50d634f68eade3e681042aef00a87c8a3b0fb7cc88a91143cafade08bc18435f7479399c2ccbb660563ff781c1b4e9248b8bff7cf22190504383e

data/CHANGELOG.md

@@ -16,6 +16,18 @@ nil
 
 nil
 
+## v1.11.0 (Jul 14, 2025)
+
+### Security fixes
+
+- [595](https://github.com/Shopify/job-iteration/pull/595) [CVE-2025-53623] Fixes a security issue in the `CSVEnumerator` where the filename was directly interpolated into a bash command.
+
+### Bug fixes
+
+- [590](https://github.com/Shopify/job-iteration/pull/590) Fix a compatibilty issue between the Sorbet DSL compiler and the latest Tapioca.
+- [593](https://github.com/Shopify/job-iteration/pull/593) Properly support required and optional positional arguments in the Sorbet DSL compiler.
+- [594](https://github.com/Shopify/job-iteration/pull/594) Clean up the size calculation in the `CSVEnumerator`.
+
 ## v1.10.0 (Mar 20, 2025)
 
 ### Breaking Changes

data/job-iteration.gemspec

@@ -16,8 +16,8 @@ Gem::Specification.new do |spec|
   spec.homepage      = "https://github.com/shopify/job-iteration"
   spec.license       = "MIT"
 
-  spec.files         = %x(git ls-files -z).split("\x0").reject do |f|
-    f.match(%r{^(test|spec|features)/})
+  spec.files = ["CHANGELOG.md", "LICENSE.txt", "README.md", "job-iteration.gemspec"] + Dir.glob("{lib,exe}/**/*", File::FNM_DOTMATCH).reject do |f|
+    File.directory?(f) || f.match(%r{^(test|spec|features)/})
   end
   spec.bindir        = "exe"
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }

data/lib/job-iteration/csv_enumerator.rb

@@ -43,23 +43,19 @@ module JobIteration
         .each_slice(batch_size)
         .with_index
         .drop(count_of_processed_rows(cursor))
-        .to_enum { (count_of_rows_in_file.to_f / batch_size).ceil }
+        .to_enum do
+          num_rows = count_of_rows_in_file
+          num_rows.nil? ? nil : (num_rows.to_f / batch_size).ceil
+        end
     end
 
     private
 
     def count_of_rows_in_file
-      # TODO: Remove rescue for NoMethodError when Ruby 2.6 is no longer supported.
-      begin
-        filepath = @csv.path
-      rescue NoMethodError
-        return
-      end
-
-      # Behaviour of CSV#path changed in Ruby 2.6.3 (returns nil instead of raising NoMethodError)
+      filepath = @csv.path
       return unless filepath
 
-      count = %x(wc -l < #{filepath}).strip.to_i
+      count = File.foreach(filepath).count
       count -= 1 if @csv.headers
       count
     end

data/lib/job-iteration/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module JobIteration
-  VERSION = "1.10.0"
+  VERSION = "1.11.0"
 end

data/lib/tapioca/dsl/compilers/job_iteration.rb

@@ -8,10 +8,11 @@ module Tapioca
     module Compilers
       class JobIteration < Compiler
         extend T::Sig
+        extend T::Generic
 
         ConstantType = type_member { { fixed: T.class_of(::JobIteration::Iteration) } }
         PARAM_TYPES_IN_ORDER = [
-          RBI::Param,
+          RBI::ReqParam,
           RBI::OptParam,
           RBI::RestParam,
           RBI::KwParam,

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: job-iteration
 version: !ruby/object:Gem::Version
-  version: 1.10.0
+  version: 1.11.0
 platform: ruby
 authors:
 - Shopify
 bindir: exe
 cert_chain: []
-date: 2025-03-20 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activejob
@@ -30,29 +30,9 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
-- ".github/dependabot.yml"
-- ".github/workflows/ci.yml"
-- ".github/workflows/cla.yml"
-- ".gitignore"
-- ".rubocop.yml"
-- ".ruby-version"
-- ".yardopts"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
-- Gemfile
-- Gemfile.lock
 - LICENSE.txt
 - README.md
-- Rakefile
-- bin/setup
-- bin/test
-- dev.yml
-- gemfiles/rails_gems.gemfile
-- guides/argument-semantics.md
-- guides/best-practices.md
-- guides/custom-enumerator.md
-- guides/iteration-how-it-works.md
-- guides/throttling.md
 - job-iteration.gemspec
 - lib/job-iteration.rb
 - lib/job-iteration/active_record_batch_enumerator.rb
@@ -96,7 +76,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.6.6
+rubygems_version: 3.6.9
 specification_version: 4
 summary: Makes your background jobs interruptible and resumable.
 test_files: []

data/.github/dependabot.yml

@@ -1,16 +0,0 @@
-version: 2
-
-updates:
-
-  - package-ecosystem: bundler
-    directory: '/'
-    versioning-strategy: increase
-    open-pull-requests-limit: 100
-    insecure-external-code-execution: allow
-    schedule:
-      interval: weekly
-
-  - package-ecosystem: github-actions
-    directory: '/'
-    schedule:
-      interval: daily

data/.github/workflows/ci.yml

@@ -1,77 +0,0 @@
-name: CI
-
-on: [push, pull_request]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    name: Ruby ${{ matrix.ruby }} | Rails ${{ matrix.rails }} | Gemfile ${{ matrix.gemfile }}
-    continue-on-error: ${{ matrix.rails == 'edge' }}
-    services:
-      redis:
-        image: redis
-        ports:
-          - 6379:6379
-    strategy:
-      fail-fast: false
-      matrix:
-        ruby: ["3.0", "3.1", "3.2", "3.3", "3.4"]
-        rails: ["6.1", "7.0", "7.1", "7.2", "8.0", "edge"]
-        gemfile: [rails_gems]
-        exclude:
-          - ruby: "3.0"
-            rails: "7.1"
-          - ruby: "3.0"
-            rails: "7.2"
-          - ruby: "3.0"
-            rails: "8.0"
-          - ruby: "3.0"
-            rails: "edge"
-          - ruby: "3.1"
-            rails: "8.0"
-          - ruby: "3.1"
-            rails: "edge"
-          - ruby: "3.2"
-            rails: "6.1"
-          - ruby: "3.3"
-            rails: "6.1"
-          - ruby: "3.4"
-            rails: "6.1"
-          - ruby: "3.4"
-            rails: "7.0"
-        include:
-          - ruby: head
-            rails: "edge"
-            gemfile: rails_gems
-    env:
-      BUNDLE_GEMFILE: gemfiles/${{ matrix.gemfile }}.gemfile
-      RAILS_VERSION: ${{ matrix.rails }}
-    steps:
-      - name: Check out code
-        uses: actions/checkout@v4
-      - name: Set up Ruby ${{ matrix.ruby }}
-        uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: ${{ matrix.ruby }}
-          bundler-cache: true
-      - name: Start MySQL and create DB
-        run: |
-          sudo systemctl start mysql.service
-          mysql -uroot -h localhost -proot -e "CREATE DATABASE job_iteration_test;"
-      - name: Ruby tests
-        run: bundle exec rake test
-
-  lint:
-    runs-on: ubuntu-latest
-    name: Lint
-    steps:
-      - name: Check out code
-        uses: actions/checkout@v4
-      - name: Set up Ruby
-        uses: ruby/setup-ruby@v1
-        with:
-          bundler-cache: true
-      - name: Rubocop
-        run: bundle exec rubocop
-      - name: Documentation correctly written
-        run: bundle exec yardoc --no-output --no-save --no-stats --fail-on-warning

data/.github/workflows/cla.yml

@@ -1,22 +0,0 @@
-name: Contributor License Agreement (CLA)
-
-on:
-  pull_request_target:
-    types: [opened, synchronize]
-  issue_comment:
-    types: [created]
-
-jobs:
-  cla:
-    runs-on: ubuntu-latest
-    if: |
-      (github.event.issue.pull_request 
-        && !github.event.issue.pull_request.merged_at
-        && contains(github.event.comment.body, 'signed')
-      ) 
-      || (github.event.pull_request && !github.event.pull_request.merged)
-    steps:
-      - uses: Shopify/shopify-cla-action@v1
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          cla-token: ${{ secrets.CLA_TOKEN }}

data/.gitignore

@@ -1,11 +0,0 @@
-/.bundle/
-/.yardoc
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-.rubocop-http---shopify-github-io-ruby-style-guide-rubocop-yml
-gemfiles/*.lock
-dump.rdb

data/.rubocop.yml

@@ -1,16 +0,0 @@
-inherit_gem:
-  rubocop-shopify: rubocop.yml
-
-inherit_mode:
-  merge:
-    - Include
-
-AllCops:
-  Include:
-    - '**/*.gemfile'
-Lint/SuppressedException:
-  Exclude:
-    - lib/job-iteration.rb
-Naming/FileName:
-  Exclude:
-    - lib/job-iteration.rb

data/.ruby-version

@@ -1 +0,0 @@
-3.4.2

data/.yardopts

@@ -1,3 +0,0 @@
---no-private
---embed-mixins
---markup markdown

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at shatrov@me.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -1,45 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }
-
-# Specify your gem's dependencies in job-iteration.gemspec
-gemspec
-
-# for integration testing
-gem "sidekiq"
-gem "resque"
-gem "delayed_job"
-
-if defined?(@rails_gems_requirements) && @rails_gems_requirements
-  # We avoid the `gem "..."` syntax here so Dependabot doesn't try to update these gems.
-  [
-    "activejob",
-    "activerecord",
-    "railties",
-  ].each { |name| gem name, @rails_gems_requirements }
-else
-  # gem "activejob" # Set in gemspec
-  gem "activerecord"
-  gem "railties"
-end
-
-gem "mysql2", github: "brianmario/mysql2"
-gem "globalid"
-gem "i18n"
-gem "redis"
-
-gem "pry"
-gem "mocha"
-
-gem "rubocop-shopify", require: false
-gem "yard"
-gem "rake"
-gem "csv" # required for Ruby 3.4+
-
-# for unit testing optional sorbet support
-gem "sorbet-runtime"
-gem "tapioca"
-
-gem "logger"

data/Gemfile.lock

@@ -1,266 +0,0 @@
-GIT
-  remote: https://github.com/brianmario/mysql2
-  revision: 57b8df188c963ae0e4d4e1123d3e9de2bbcab637
-  specs:
-    mysql2 (0.5.6)
-      bigdecimal
-
-PATH
-  remote: .
-  specs:
-    job-iteration (1.10.0)
-      activejob (>= 6.1)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    actionpack (8.0.1)
-      actionview (= 8.0.1)
-      activesupport (= 8.0.1)
-      nokogiri (>= 1.8.5)
-      rack (>= 2.2.4)
-      rack-session (>= 1.0.1)
-      rack-test (>= 0.6.3)
-      rails-dom-testing (~> 2.2)
-      rails-html-sanitizer (~> 1.6)
-      useragent (~> 0.16)
-    actionview (8.0.1)
-      activesupport (= 8.0.1)
-      builder (~> 3.1)
-      erubi (~> 1.11)
-      rails-dom-testing (~> 2.2)
-      rails-html-sanitizer (~> 1.6)
-    activejob (8.0.1)
-      activesupport (= 8.0.1)
-      globalid (>= 0.3.6)
-    activemodel (8.0.1)
-      activesupport (= 8.0.1)
-    activerecord (8.0.1)
-      activemodel (= 8.0.1)
-      activesupport (= 8.0.1)
-      timeout (>= 0.4.0)
-    activesupport (8.0.1)
-      base64
-      benchmark (>= 0.3)
-      bigdecimal
-      concurrent-ruby (~> 1.0, >= 1.3.1)
-      connection_pool (>= 2.2.5)
-      drb
-      i18n (>= 1.6, < 2)
-      logger (>= 1.4.2)
-      minitest (>= 5.1)
-      securerandom (>= 0.3)
-      tzinfo (~> 2.0, >= 2.0.5)
-      uri (>= 0.13.1)
-    ast (2.4.2)
-    base64 (0.2.0)
-    benchmark (0.4.0)
-    bigdecimal (3.1.9)
-    builder (3.3.0)
-    coderay (1.1.3)
-    concurrent-ruby (1.3.5)
-    connection_pool (2.5.0)
-    crass (1.0.6)
-    csv (3.3.2)
-    date (3.4.1)
-    delayed_job (4.1.13)
-      activesupport (>= 3.0, < 9.0)
-    drb (2.2.1)
-    erubi (1.13.1)
-    globalid (1.2.1)
-      activesupport (>= 6.1)
-    i18n (1.14.7)
-      concurrent-ruby (~> 1.0)
-    io-console (0.8.0)
-    irb (1.15.1)
-      pp (>= 0.6.0)
-      rdoc (>= 4.0.0)
-      reline (>= 0.4.2)
-    json (2.10.1)
-    language_server-protocol (3.17.0.4)
-    lint_roller (1.1.0)
-    logger (1.6.6)
-    loofah (2.24.0)
-      crass (~> 1.0.2)
-      nokogiri (>= 1.12.0)
-    method_source (1.1.0)
-    minitest (5.25.4)
-    mocha (2.7.1)
-      ruby2_keywords (>= 0.0.5)
-    mono_logger (1.1.2)
-    multi_json (1.15.0)
-    mustermann (3.0.3)
-      ruby2_keywords (~> 0.0.1)
-    netrc (0.11.0)
-    nokogiri (1.18.3-arm64-darwin)
-      racc (~> 1.4)
-    nokogiri (1.18.3-x86_64-darwin)
-      racc (~> 1.4)
-    nokogiri (1.18.3-x86_64-linux-gnu)
-      racc (~> 1.4)
-    parallel (1.26.3)
-    parser (3.3.7.1)
-      ast (~> 2.4.1)
-      racc
-    pp (0.6.2)
-      prettyprint
-    prettyprint (0.2.0)
-    prism (1.3.0)
-    pry (0.15.2)
-      coderay (~> 1.1)
-      method_source (~> 1.0)
-    psych (5.2.3)
-      date
-      stringio
-    racc (1.8.1)
-    rack (3.1.12)
-    rack-protection (4.1.1)
-      base64 (>= 0.1.0)
-      logger (>= 1.6.0)
-      rack (>= 3.0.0, < 4)
-    rack-session (2.1.0)
-      base64 (>= 0.1.0)
-      rack (>= 3.0.0)
-    rack-test (2.2.0)
-      rack (>= 1.3)
-    rackup (2.2.1)
-      rack (>= 3)
-    rails-dom-testing (2.2.0)
-      activesupport (>= 5.0.0)
-      minitest
-      nokogiri (>= 1.6)
-    rails-html-sanitizer (1.6.2)
-      loofah (~> 2.21)
-      nokogiri (>= 1.15.7, != 1.16.7, != 1.16.6, != 1.16.5, != 1.16.4, != 1.16.3, != 1.16.2, != 1.16.1, != 1.16.0.rc1, != 1.16.0)
-    railties (8.0.1)
-      actionpack (= 8.0.1)
-      activesupport (= 8.0.1)
-      irb (~> 1.13)
-      rackup (>= 1.0.0)
-      rake (>= 12.2)
-      thor (~> 1.0, >= 1.2.2)
-      zeitwerk (~> 2.6)
-    rainbow (3.1.1)
-    rake (13.2.1)
-    rbi (0.3.0)
-      prism (~> 1.0)
-      rbs (>= 3.4.4)
-      sorbet-runtime (>= 0.5.9204)
-    rbs (3.8.1)
-      logger
-    rdoc (6.12.0)
-      psych (>= 4.0.0)
-    redis (5.4.0)
-      redis-client (>= 0.22.0)
-    redis-client (0.24.0)
-      connection_pool
-    redis-namespace (1.11.0)
-      redis (>= 4)
-    regexp_parser (2.10.0)
-    reline (0.6.0)
-      io-console (~> 0.5)
-    resque (2.7.0)
-      mono_logger (~> 1)
-      multi_json (~> 1.0)
-      redis-namespace (~> 1.6)
-      sinatra (>= 0.9.2)
-    rubocop (1.73.2)
-      json (~> 2.3)
-      language_server-protocol (~> 3.17.0.2)
-      lint_roller (~> 1.1.0)
-      parallel (~> 1.10)
-      parser (>= 3.3.0.2)
-      rainbow (>= 2.2.2, < 4.0)
-      regexp_parser (>= 2.9.3, < 3.0)
-      rubocop-ast (>= 1.38.0, < 2.0)
-      ruby-progressbar (~> 1.7)
-      unicode-display_width (>= 2.4.0, < 4.0)
-    rubocop-ast (1.38.1)
-      parser (>= 3.3.1.0)
-    rubocop-shopify (2.16.0)
-      rubocop (~> 1.62)
-    ruby-progressbar (1.13.0)
-    ruby2_keywords (0.0.5)
-    securerandom (0.4.1)
-    sidekiq (8.0.1)
-      connection_pool (>= 2.5.0)
-      json (>= 2.9.0)
-      logger (>= 1.6.2)
-      rack (>= 3.1.0)
-      redis-client (>= 0.23.2)
-    sinatra (4.1.1)
-      logger (>= 1.6.0)
-      mustermann (~> 3.0)
-      rack (>= 3.0.0, < 4)
-      rack-protection (= 4.1.1)
-      rack-session (>= 2.0.0, < 3)
-      tilt (~> 2.0)
-    sorbet (0.5.11915)
-      sorbet-static (= 0.5.11915)
-    sorbet-runtime (0.5.11915)
-    sorbet-static (0.5.11915-universal-darwin)
-    sorbet-static (0.5.11915-x86_64-linux)
-    sorbet-static-and-runtime (0.5.11915)
-      sorbet (= 0.5.11915)
-      sorbet-runtime (= 0.5.11915)
-    spoom (1.6.0)
-      erubi (>= 1.10.0)
-      prism (>= 0.28.0)
-      rbi (>= 0.2.3)
-      sorbet-static-and-runtime (>= 0.5.10187)
-      thor (>= 0.19.2)
-    stringio (3.1.5)
-    tapioca (0.16.11)
-      benchmark
-      bundler (>= 2.2.25)
-      netrc (>= 0.11.0)
-      parallel (>= 1.21.0)
-      rbi (~> 0.2)
-      sorbet-static-and-runtime (>= 0.5.11087)
-      spoom (>= 1.2.0)
-      thor (>= 1.2.0)
-      yard-sorbet
-    thor (1.3.2)
-    tilt (2.6.0)
-    timeout (0.4.3)
-    tzinfo (2.0.6)
-      concurrent-ruby (~> 1.0)
-    unicode-display_width (3.1.4)
-      unicode-emoji (~> 4.0, >= 4.0.4)
-    unicode-emoji (4.0.4)
-    uri (1.0.3)
-    useragent (0.16.11)
-    yard (0.9.37)
-    yard-sorbet (0.9.0)
-      sorbet-runtime
-      yard
-    zeitwerk (2.7.2)
-
-PLATFORMS
-  arm64-darwin
-  x86_64-darwin
-  x86_64-linux
-
-DEPENDENCIES
-  activerecord
-  csv
-  delayed_job
-  globalid
-  i18n
-  job-iteration!
-  logger
-  mocha
-  mysql2!
-  pry
-  railties
-  rake
-  redis
-  resque
-  rubocop-shopify
-  sidekiq
-  sorbet-runtime
-  tapioca
-  yard
-
-BUNDLED WITH
-   2.6.1

data/Rakefile

@@ -1,12 +0,0 @@
-# frozen_string_literal: true
-
-require "bundler/gem_tasks"
-require "rake/testtask"
-
-Rake::TestTask.new(:test) do |t|
-  t.libs << "test"
-  t.libs << "lib"
-  t.test_files = FileList["test/**/*_test.rb"]
-end
-
-task(default: :test)

data/bin/setup

@@ -1,23 +0,0 @@
-#!/bin/bash
-
-if ! [ -x "$(command -v mysql)" ];
-then
-  echo "Error: mysql is not installed." >&2
-  echo "You need to install mysql"
-  exit 1
-else
-  echo "Installing dependencies"
-  bundle install --quiet
-
-  mysql.server start > /dev/null 2>&1
-  mysql -uroot job_iteration_test -e exit > /dev/null 2>&1
-
-  if [ $? -eq 0 ];
-  then
-    echo "Setup completed!"
-  else
-    echo "Creating job_iteration_test database"
-    mysql -uroot -e "CREATE DATABASE job_iteration_test" > /dev/null 2>&1
-    echo "Setup completed!"
-  fi
-fi

data/bin/test

@@ -1,32 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-def main
-  begin
-    command = create_command
-  rescue ArgumentError => e
-    abort(e.message)
-  end
-  puts "Running #{command.join(" ")}"
-  system(*command)
-end
-
-def create_command
-  case ARGV.length
-  when 0
-    ["bundle", "exec", "rake", "test"]
-  when 1
-    filename = ARGV[0]
-    ["bundle", "exec", "rake", "test", "TEST=#{filename}"]
-  when 2
-    filename = ARGV[0]
-    test_name = ARGV[1]
-    test_name_with_underscores = test_name.tr(" ", "_")
-    test_name_pattern = "/#{Regexp.escape(test_name_with_underscores)}/"
-    ["bundle", "exec", "rake", "test", "TEST=#{filename}", "TESTOPTS=\"--name=#{test_name_pattern} -v\""]
-  else
-    raise ArgumentError, "Too many arguments. Did you forget to put the test name in quotes?"
-  end
-end
-
-main

data/dev.yml

@@ -1,54 +0,0 @@
-# This file is for Shopify employees development environment.
-# If you are an external contributor you don't have to bother with it.
-name: job-iteration
-
-up:
-  - packages:
-      - mysql_client
-  - ruby
-  - bundler
-  - mysql
-  - redis
-  - custom:
-      name: Create Job Iteration database
-      meet: mysql -uroot -h $MYSQL_HOST -P $MYSQL_PORT -e "CREATE DATABASE job_iteration_test"
-      met?: mysql -uroot -h $MYSQL_HOST -P $MYSQL_PORT job_iteration_test -e "SELECT 1" &> /dev/null
-
-commands:
-  test:
-    run:  bin/test "$@"
-    syntax:
-      optional: filename testnamepattern
-    aliases: [t]
-    desc: run tests
-    long_desc: |
-      {{bold:Default}}
-      =======
-      Run the entire test suite.
-
-        Examples:
-        {{command:dev test}}
-        {{command:dev t}}
-
-      {{bold:Run all tests in a file}}
-      ========================
-      Include the file path.
-
-        Example:
-        {{command:dev test test/unit/iteration_test.rb}}
-
-      {{bold:Run a single test in a given file}}
-      ========================
-      Include the file path and the name of the test you'd like to run.
-
-        Example:
-        {{command:dev test test/unit/iteration_test.rb test_that_it_has_a_version_number}}
-
-      {{bold:Run all tests in a given file whose name contains a string}}
-      ========================
-      Include the file path and the string that the test names should contain.
-
-        Example:
-        {{command:dev test test/unit/iteration_test.rb version_number}}
-  style:
-    run: bundle exec rubocop -a

data/gemfiles/rails_gems.gemfile

@@ -1,18 +0,0 @@
-# frozen_string_literal: true
-
-rails_version = ENV.fetch("RAILS_VERSION")
-@rails_gems_requirements = case rails_version
-when "edge"         then { github: "rails/rails", branch: "main" }
-when /\A\d+\.\d+\z/ then "~> #{rails_version}.0"
-else                raise "Unsupported RAILS_VERSION: #{rails_version}"
-end
-
-eval_gemfile "../Gemfile"
-
-# https://github.com/rails/rails/pull/44083
-if Gem::Version.new(RUBY_VERSION) >= Gem::Version.new("3.1") &&
-    rails_version != "edge" && Gem::Version.new(rails_version) < Gem::Version.new("7")
-  gem "net-imap", require: false
-  gem "net-pop", require: false
-  gem "net-smtp", require: false
-end

data/guides/argument-semantics.md

@@ -1,128 +0,0 @@
-`job-iteration` overrides the `perform` method of `ActiveJob::Base` to allow for iteration. The `perform` method preserves all the standard calling conventions of the original, but the way the subsequent methods work might differ from what one expects from an ActiveJob subclass.
-
-The call sequence is usually 3 methods:
-
-`perform -> build_enumerator -> each_iteration|each_batch`
-
-In that sense `job-iteration` works like a framework (it calls your code) rather than like a library (that you call). When using jobs with parameters, the following rules of thumb are good to keep in mind.
-
-### Jobs without arguments
-
-Jobs without arguments do not pass anything into either `build_enumerator` or `each_iteration` except for the `cursor` which `job-iteration` persists by itself:
-
-```ruby
-class ArglessJob < ActiveJob::Base
-  include JobIteration::Iteration
-
-  def build_enumerator(cursor:)
-    # ...
-  end
-
-  def each_iteration(single_object_yielded_from_enumerator)
-    # ...
-  end
-end
-```
-
-To enqueue the job:
-
-```ruby
-ArglessJob.perform_later
-```
-
-### Jobs with positional arguments
-
-Jobs with positional arguments will have those arguments available to both `build_enumerator` and `each_iteration`:
-
-```ruby
-class ArgumentativeJob < ActiveJob::Base
-  include JobIteration::Iteration
-
-  def build_enumerator(arg1, arg2, arg3, cursor:)
-    # ...
-  end
-
-  def each_iteration(single_object_yielded_from_enumerator, arg1, arg2, arg3)
-    # ...
-  end
-end
-```
-
-To enqueue the job:
-
-```ruby
-ArgumentativeJob.perform_later(_arg1 = "One", _arg2 = "Two", _arg3 = "Three")
-```
-
-### Jobs with keyword arguments
-
-Jobs with keyword arguments will have the keyword arguments available to both `build_enumerator` and `each_iteration`, but these arguments come packaged into a Hash in both cases. You will need to `fetch` or `[]` your parameter from the `Hash` you get passed in:
-
-```ruby
-class ParameterizedJob < ActiveJob::Base
-  include JobIteration::Iteration
-
-  def build_enumerator(kwargs, cursor:)
-    name = kwargs.fetch(:name)
-    email = kwargs.fetch(:email)
-    # ...
-  end
-
-  def each_iteration(object_yielded_from_enumerator, kwargs)
-    name = kwargs.fetch(:name)
-    email = kwargs.fetch(:email)
-    # ...
-  end
-end
-```
-
-To enqueue the job:
-
-```ruby
-ParameterizedJob.perform_later(name: "Jane", email: "jane@host.example")
-```
-
-Note that you cannot use `ruby2_keywords` at present, and the keyword arguments syntax is not supported in `each_iteration` / `build_enumerator`.
-
-### Jobs with both positional and keyword arguments
-
-Jobs with keyword arguments will have the keyword arguments available to both `build_enumerator` and `each_iteration`, but these arguments come packaged into a Hash in both cases. You will need to `fetch` or `[]` your parameter from the `Hash` you get passed in. Positional arguments get passed first and "unsplatted" (not combined into an array), the `Hash` containing keyword arguments comes after:
-
-```ruby
-class HighlyConfigurableGreetingJob < ActiveJob::Base
-  include JobIteration::Iteration
-
-  def build_enumerator(subject_line, kwargs, cursor:)
-    name = kwargs.fetch(:sender_name)
-    email = kwargs.fetch(:sender_email)
-    # ...
-  end
-
-  def each_iteration(object_yielded_from_enumerator, subject_line, kwargs)
-    name = kwargs.fetch(:sender_name)
-    email = kwargs.fetch(:sender_email)
-    # ...
-  end
-end
-```
-
-To enqueue the job:
-
-```ruby
-HighlyConfigurableGreetingJob.perform_later(_subject_line = "Greetings everybody!", sender_name: "Jane", sender_email: "jane@host.example")
-```
-
-Note that you cannot use `ruby2_keywords` at present, and the keyword arguments syntax is not supported in `each_iteration` / `build_enumerator`.
-
-### Returning (yielding) from enumerators
-
-When defining a custom enumerator (see the [custom enumerator guide](custom-enumerator.md)) you need to yield two positional arguments from it: the object that will be the value for the current iteration (like a single ActiveModel instance, a single number...) and the value you want to be persisted as the `cursor` value should `job-iteration` decide to interrupt you after this iteration. Calling the enumerator with that cursor should return the next object after the one returned in this iteration. That new `cursor` value does not get passed to `each_iteration`:
-
-```ruby
-Enumerator.new do |yielder|
-  # In this case `cursor` is an Integer
-  cursor.upto(99999) do |offset|
-    yielder.yield(fetch_record_at(offset), offset)
-  end
-end
-```

data/guides/best-practices.md

@@ -1,108 +0,0 @@
-# Best practices
-
-## Batch iteration
-
-Regardless of the active record enumerator used in the task, `job-iteration` gem loads records in batches of 100 (by default).
-The following two tasks produce equivalent database queries,
-however `RecordsJob` task allows for more frequent interruptions by doing just one thing in the `each_iteration` method.
-
-```ruby
-# bad
-class BatchesJob < ApplicationJob
-  include JobIteration::Iteration
-
-  def build_enumerator(product_id, cursor:)
-    enumerator_builder.active_record_on_batches(
-      Comment.where(product_id: product_id),
-      cursor: cursor,
-      batch_size: 5,
-    )
-  end
-
-  def each_iteration(batch_of_comments, product_id)
-    batch_of_comments.each(&:destroy)
-  end
-end
-
-# good
-class RecordsJob < ApplicationJob
-  include JobIteration::Iteration
-
-  def build_enumerator(product_id, cursor:)
-    enumerator_builder.active_record_on_records(
-      Comment.where(product_id: product_id),
-      cursor: cursor,
-      batch_size: 5,
-    )
-  end
-
-  def each_iteration(comment, product_id)
-    comment.destroy
-  end
-end
-```
-
-## Instrumentation
-
-Iteration leverages [`ActiveSupport::Notifications`](https://guides.rubyonrails.org/active_support_instrumentation.html)
-to notify you what it's doing. You can subscribe to the following events (listed in order of job lifecycle):
-
-- `build_enumerator.iteration`
-- `throttled.iteration` (when using ThrottleEnumerator)
-- `nil_enumerator.iteration`
-- `resumed.iteration`
-- `each_iteration.iteration`
-- `not_found.iteration`
-- `interrupted.iteration`
-- `completed.iteration`
-
-All events have tags including the job class name and cursor position, some add the amount of times interrupted and/or
-total time the job spent running across interruptions.
-
-```ruby
-# config/initializers/instrumentation.rb
-ActiveSupport::Notifications.monotonic_subscribe("each_iteration.iteration") do |_, started, finished, _, tags|
-  elapsed = finished - started
-  StatsD.distribution(
-    "iteration.each_iteration",
-    elapsed,
-    tags: { job_class: tags[:job_class]&.underscore }
-  )
-
-  if elapsed >= BackgroundQueue.max_iteration_runtime
-    Rails.logger.warn "[Iteration] job_class=#{tags[:job_class]} " \
-    "each_iteration runtime exceeded limit of #{BackgroundQueue.max_iteration_runtime}s"
-  end
-end
-```
-
-## Max iteration time
-
-As you may notice in the snippet above, at Shopify we enforce that `each_iteration` does not take longer than `BackgroundQueue.max_iteration_runtime`, which is set to `25` seconds.
-
-We discourage that because jobs with a long `each_iteration` make interruptibility somewhat useless, as the infrastructure will have to wait longer for the job to interrupt.
-
-## Max job runtime
-
-If a job is supposed to have millions of iterations and you expect it to run for hours and days, it's still a good idea to sometimes interrupt the job even if there are no interruption signals coming from deploys or the infrastructure. At Shopify, we interrupt at least every 5 minutes to preserve **worker capacity**.
-
-```ruby
-JobIteration.max_job_runtime = 5.minutes # nil by default
-```
-
-Use this accessor to tweak how often you'd like the job to interrupt itself.
-
-### Per job max job runtime
-
-For more granular control, `job_iteration_max_job_runtime` can be set **per-job class**. This allows both incremental adoption, as well as using a conservative global setting, and an aggressive setting on a per-job basis.
-
-```ruby
-class MyJob < ApplicationJob
-  include JobIteration::Iteration
-
-  self.job_iteration_max_job_runtime = 3.minutes
-
-  # ...
-```
-
-This setting will be inherited by any child classes, although it can be further overridden. Note that no class can **increase** the `max_job_runtime` it has inherited; it can only be **decreased**. No job can increase its `max_job_runtime` beyond the global limit.

data/guides/custom-enumerator.md

@@ -1,140 +0,0 @@
-# Custom Enumerator
-
-`Iteration` leverages the [Enumerator](https://ruby-doc.org/3.2.1/Enumerator.html) pattern from the Ruby standard library,
-which allows us to use almost any resource as a collection to iterate.
-
-Before writing an enumerator, it is important to understand [how Iteration works](iteration-how-it-works.md) and how
-your enumerator will be used by it. An enumerator must `yield` two things in the following order as positional
-arguments:
-- An object to be processed in a job `each_iteration` method
-- A cursor position, which `Iteration` will persist if `each_iteration` returns successfully and the job is forced to shut
-  down. It can be any data type your job backend can serialize and deserialize correctly.
-
-A job that includes `Iteration` is first started with `nil` as the cursor. When resuming an interrupted job, `Iteration`
-will deserialize the persisted cursor and pass it to the job's `build_enumerator` method, which your enumerator uses to
-find objects that come _after_ the last successfully processed object. The [array enumerator](https://github.com/Shopify/job-iteration/blob/v1.3.6/lib/job-iteration/enumerator_builder.rb#L50-L67)
-is a simple example which uses the array index as the cursor position.
-
-In addition to the remainder of this guide, we recommend you read the implementation of the other enumerators that come with the library (`CsvEnumerator`, `ActiveRecordEnumerator`) to gain a better understanding of building enumerators.
-
-## Enumerator with cursor
-
-For a more complex example, consider this `Enumerator` that wraps a third party API (Stripe) for paginated iteration and
-stores a string as the cursor position:
-
-```ruby
-class StripeListEnumerator
-  # @see https://stripe.com/docs/api/pagination
-  # @param resource [Stripe::APIResource] The type of Stripe object to request
-  # @param params [Hash] Query parameters for the request
-  # @param options [Hash] Request options, such as API key or version
-  # @param cursor [nil, String] The Stripe ID of the last item iterated over
-  def initialize(resource, params: {}, options: {}, cursor:)
-    pagination_params = {}
-    pagination_params[:starting_after] = cursor unless cursor.nil?
-
-    # The following line makes a request, consider adding your rate limiter here.
-    @list = resource.public_send(:list, params.merge(pagination_params), options)
-  end
-
-  def to_enumerator
-    to_enum(:each).lazy
-  end
-
-  private
-
-  # We yield our enumerator with the object id as the index so it is persisted
-  # as the cursor on the job. This allows us to properly set the
-  # `starting_after` parameter for the API request when resuming.
-  def each
-    loop do
-      @list.each do |item, _index|
-        # The first argument is what gets passed to `each_iteration`.
-        # The second argument (item.id) is going to be persisted as the cursor,
-        # it doesn't get passed to `each_iteration`.
-        yield item, item.id
-      end
-
-      # The following line makes a request, consider adding your rate limiter here.
-      @list = @list.next_page
-
-      break if @list.empty?
-    end
-  end
-end
-```
-
-### Usage
-
-Here we leverage the Stripe cursor pagination where the cursor is an ID of a specific item in the collection. The job
-which uses such an `Enumerator` would then look like so:
-
-```ruby
-class LoadRefundsForChargeJob < ActiveJob::Base
-  include JobIteration::Iteration
-
-  # If you added your own rate limiting above, handle it here. For example:
-  # retry_on(MyRateLimiter::LimitExceededError, wait: 30.seconds, attempts: :unlimited)
-  # Use an exponential back-off strategy when Stripe's API returns errors.
-
-  def build_enumerator(charge_id, cursor:)
-    enumerator_builder.wrap(
-      StripeListEnumerator.new(
-        Stripe::Refund,
-        params: { charge: charge_id}, # "charge_id" will be a prefixed Stripe ID such as "chrg_123"
-        options: { api_key: "sk_test_123", stripe_version: "2018-01-18" },
-        cursor: cursor
-      ).to_enumerator
-    )
-  end
-
-  # Note that in this case `each_iteration` will only receive one positional argument per iteration.
-  # If what your enumerator yields is a composite object you will need to unpack it yourself
-  # inside the `each_iteration`.
-  def each_iteration(stripe_refund, charge_id)
-    # ...
-  end
-end
-```
-
-and you initiate the job with
-
-```ruby
-LoadRefundsForChargeJob.perform_later(charge_id = "chrg_345")
-```
-
-## Cursorless enumerator
-
-Sometimes you can ignore the cursor. Consider the following custom `Enumerator` that takes items from a Redis list, which
-is essentially a queue. Even if this job doesn't need to persist a cursor in order to resume, it can still use
-`Iteration`'s signal handling to finish `each_iteration` and gracefully terminate.
-
-```ruby
-class RedisPopListJob < ActiveJob::Base
-  include JobIteration::Iteration
-
-  # @see https://redis.io/commands/lpop/
-  def build_enumerator(*)
-    @redis = Redis.new
-    enumerator_builder.wrap(
-      Enumerator.new do |yielder|
-        yielder.yield @redis.lpop(key), nil
-      end
-    )
-  end
-
-  def each_iteration(item_from_redis)
-    # ...
-  end
-end
-```
-
-## Caveats
-
-### Post-`yield` code
-
-Code that is written after the `yield` in a custom enumerator is not guaranteed to execute. In the case that a job is
-forced to exit ie `job_should_exit?` is true, then the job is re-enqueued during the yield and the rest of the code in
-the enumerator does not run. You can follow that logic
-[here](https://github.com/Shopify/job-iteration/blob/v1.3.6/lib/job-iteration/iteration.rb#L161-L165) and
-[here](https://github.com/Shopify/job-iteration/blob/v1.3.6/lib/job-iteration/iteration.rb#L131-L143)

data/guides/iteration-how-it-works.md

@@ -1,51 +0,0 @@
-# Iteration: how it works
-
-The main idea behind Iteration is to provide an API to describe jobs in an interruptible manner, in contrast with implementing one massive `#perform` method that is impossible to interrupt safely.
-
-Exposing the enumerator and the action to apply allows us to keep a cursor and interrupt between iterations. Let's see what this looks like with an  ActiveRecord relation (and Enumerator).
-
-1. `build_enumerator` is called, which constructs `ActiveRecordEnumerator` from an ActiveRecord relation (`Product.all`)
-2. The first batch of records is loaded:
-
-```sql
-SELECT  `products`.* FROM `products` ORDER BY products.id LIMIT 100
-```
-
-3. The job iterates over two records of the relation and then receives `SIGTERM` (graceful termination signal) caused by a deploy.
-4. The signal handler sets a flag that makes `job_should_exit?` return `true`.
-5. After the last iteration is completed, we will check `job_should_exit?` which now returns `true`.
-6. The job stops iterating and pushes itself back to the queue, with the latest `cursor_position` value.
-7. Next time when the job is taken from the queue, we'll load records starting from the last primary key that was processed:
-
-```sql
-SELECT  `products`.* FROM `products` WHERE (products.id > 2) ORDER BY products.id LIMIT 100
-```
-
-## Exceptions inside `each_iteration`
-
-Unrescued exceptions inside the `each_iteration` block are handled the same way as exceptions occuring in `perform` for a regular Active Job subclass, meaning you need to configure it to retry using [`retry_on`](https://api.rubyonrails.org/classes/ActiveJob/Exceptions/ClassMethods.html#method-i-retry_on) or manually call [`retry_job`](https://api.rubyonrails.org/classes/ActiveJob/Exceptions.html#method-i-retry_job). The job will re-enqueue itself with the last successful cursor, the iteration that failed will be retried with the same parameters and the cursor will only move if that iteration succeeds. This behaviour may be enough for intermittent errors, such as network connection failures, but if your execution is deterministic and you have an error, subsequent iterations will never run.
-
-In other words, if you are trying to process 100 records but the job consistently fails on the 61st, only the first 60 will be processed and the job will try to process the 61st record until retries are exhausted.
-
-If no retries are configured or retries are exhausted, Active Job 'bubbles up' the exception to the job backend. Retries by the backend (e.g. Sidekiq) are not supported, meaning that jobs retried by the job backend instead of Active Job will restart from the beginning.
-
-## Stopping a job
-
-Because jobs typically retry when exceptions are thrown, there is a special mechanism to fully stop a job that still has iterations remaining. To do this, you can `throw(:abort)`. This is then caught by job-iteration and signals that the job should complete now, regardless of its iteration state.
-
-## Signals
-
-It's critical to know [UNIX signals](https://www.tutorialspoint.com/unix/unix-signals-traps.htm) in order to understand how interruption works. There are two main signals that Sidekiq and Resque use: `SIGTERM` and `SIGKILL`. `SIGTERM` is the graceful termination signal which means that the process should exit _soon_, not immediately. For Iteration, it means that we have time to wait for the last iteration to finish and to push job back to the queue with the last cursor position.
-`SIGTERM` is what allows Iteration to work. In contrast, `SIGKILL` means immediate exit. It doesn't let the worker terminate gracefully, instead it will drop the job and exit as soon as possible.
-
-Most of the deploy strategies (Kubernetes, Heroku, Capistrano) send `SIGTERM` before shutting down a node, then wait for a timeout (usually from 30 seconds to a minute) to send `SIGKILL` if the process has not terminated yet.
-
-Further reading: [Sidekiq signals](https://github.com/mperham/sidekiq/wiki/Signals).
-
-## Enumerators
-
-In the early versions of Iteration, `build_enumerator` used to return ActiveRecord relations directly, and we would infer the Enumerator based on the type of object. We used to support ActiveRecord relations, arrays and CSVs. This made it hard to add support for other types of enumerations, and it was easy for developers to make mistakes and return an array of ActiveRecord objects, and for us starting to treat that as an array instead of as an ActiveRecord relation.
-
-The current version of Iteration supports _any_ Enumerator. We expose helpers to build common enumerators conveniently (`enumerator_builder.active_record_on_records`), but it's up to a developer to implement [a custom Enumerator](custom-enumerator.md).
-
-Further reading: [ruby-doc](https://ruby-doc.org/3.2.1/Enumerator.html), [a great post about Enumerators](http://blog.arkency.com/2014/01/ruby-to-enum-for-enumerator/).

data/guides/throttling.md

@@ -1,68 +0,0 @@
-Iteration comes with a special wrapper enumerator that allows you to throttle iterations based on external signal (e.g. database health).
-
-Consider this example:
-
-```ruby
-class InactiveAccountDeleteJob < ActiveJob::Base
-  include JobIteration::Iteration
-
-  def build_enumerator(_params, cursor:)
-    enumerator_builder.active_record_on_batches(
-      Account.inactive,
-      cursor: cursor
-    )
-  end
-
-  def each_iteration(batch, _params)
-    Account.where(id: batch.map(&:id)).delete_all
-  end
-end
-```
-
-For an app that keeps track of customer accounts, it's typical to purge old data that's no longer relevant for storage.
-
-At the same time, if you've got a lot of DB writes to perform, this can cause extra load on the database and slow down other parts of your service.
-
-You can change `build_enumerator` to wrap enumeration on DB rows into a throttle enumerator, which takes signal as a proc and enqueues the job for later in case the proc returned `true`.
-
-```ruby
-def build_enumerator(_params, cursor:)
-  enumerator_builder.build_throttle_enumerator(
-    enumerator_builder.active_record_on_batches(
-      Account.inactive,
-      cursor: cursor
-    ),
-    throttle_on: -> { DatabaseStatus.unhealthy? },
-    backoff: 30.seconds
-  )
-end
-```
-
-If you want to apply throttling on all jobs, you can subclass your own EnumeratorBuilder and override the default
-enumerator builder. The builder always wraps the returned enumerators from `build_enumerator`
-
-```ruby
-class MyOwnBuilder < JobIteration::EnumeratorBuilder
-  class Wrapper < Enumerator
-    class << self
-      def wrap(_builder, enum)
-        ThrottleEnumerator.new(
-          enum,
-          nil,
-          throttle_on: -> { DatabaseStatus.unhealthy? },
-          backoff: 30.seconds
-        )
-      end
-    end
-  end
-end
-
-JobIteration.enumerator_builder = MyOwnBuilder
-```
-
-Note that it's up to you to implement `DatabaseStatus.unhealthy?` that works for your database choice. At Shopify, a helper like `DatabaseStatus` checks the following MySQL metrics:
-
-* Replication lag across all regions
-* DB threads
-* DB is available for writes (otherwise indicates a failover happening)
-* [Semian](https://github.com/shopify/semian) open circuits