acidic_job 1.0.0.rc3 → 1.0.0.rc5

data/UPGRADE_GUIDE.md

@@ -1,81 +0,0 @@
-# AcidicJob Upgrade Guide
-
-## 1. Update version requirements in `Gemfile`
-
-```diff
-- gem "acidic_job"
-+ gem "acidic_job", "~> 1.0.0.pre1"
-```
-
-result:
-```
-Installing acidic_job 1.0.0.pre4 (was 0.7.7)
-Bundle updated!
-```
-
-## 2. Generate migration for new `AcidicJob::Run` model
-
-```bash
-rails generate acidic_job
-```
-
-result:
-```
-create  db/migrate/#{yyyymmddhhmmss}_create_acidic_job_runs.rb
-```
-
-## 3. Delete any unneeded `AcidicJob::Key` records
-
-Typically, records that are already finished do not need to be retained. Sometimes, however, applications key finished records around for some amount of time for debugging or metrics aggregation. Whatever your application's logic is for whether or not an `AcidicJob::Key` record is still needed, for all unneeded records, delete them.
-
-For example, this would delete all finished `Key` records over 1 month old:
-
-```ruby
-AcidicJob::Key.where(recovery_point: AcidicJob::Key::RECOVERY_POINT_FINISHED, last_run_at: ..1.month.ago).delete_all
-```
-
-## 4. Migrate `AcidicJob::Key` to `AcidicJob::Run`
-
-`AcidicJob` ships with an upgrade module that provides a script to migrate older `Key` records to the new `Run` model.
-
-```ruby
-AcidicJob::UpgradeService.execute
-```
-
-This script will prepare an `insert_all` command for `Run` records by mapping the older `Key` data to the new `Run` schema. It also creates the new `Run` records with the same `id` as their `Key` counterparts, and then deletes all `Key` records successfully mapped over. Any `Key` records that were failed to be mapped over will be reported, along with the exception, in the `errored_keys` portion of the resulting hash.
-
-result:
-```
-{
-  run_records: <Integer>,
-  key_records: <Integer>,
-  errored_keys: <Array>
-}
-```
-
-## 5. Triage remaining `AcidicJob::Key` records
-
-If there were any `AcidicJob::Key` records that failed to be mapped to the new `Run` model, you will need to manually triage whatever the exception was. In all likelihood, the exception would be relating to the translation of the `Key#job_args` field to the `Run#serialized_job` field, as all other fields have a fairly straight-forward mapping. If you can't resolve the issue, please open an Issue in GitHub.
-
-## 6. Ensure all `AcidicJob::Staged` records are processed
-
-`AcidicJob` still ships with an upgrade module that provides the older `Key` and `Staged` records, so this functionality will still be present to handle any existing records in your database when you deploy the updated version.
-
-## 7. Remove the old tables
-
-Once you have successfully migrated everything over and the new system has been running smoothly for some time, you should drop the old `acidic_job_keys` and `staged_acidic_jobs` tables. We provide a migration generator just for this purpose:
-
-```bash
-rails generate acidic_job:drop_tables
-```
-
-result:
-```
-create  db/migrate/#{yyyymmddhhmmss}_drop_old_acidic_job_tables.rb
-```
-
-You can then run the migration to have those tables removed:
-
-```bash
-rails db:migrate
-```

data/acidic_job.gemspec

@@ -1,52 +0,0 @@
-# frozen_string_literal: true
-
-require_relative "lib/acidic_job/version"
-
-Gem::Specification.new do |spec|
-  spec.name = "acidic_job"
-  spec.version = AcidicJob::VERSION
-  spec.authors = ["fractaledmind"]
-  spec.email = ["stephen.margheim@gmail.com"]
-
-  spec.summary = "Idempotent operations for Rails apps, built on top of ActiveJob."
-  spec.description = "Idempotent operations for Rails apps, built on top of ActiveJob."
-  spec.homepage = "https://github.com/fractaledmind/acidic_job"
-  spec.license = "MIT"
-  spec.required_ruby_version = Gem::Requirement.new(">= 2.7.0")
-
-  spec.metadata["homepage_uri"] = spec.homepage
-  spec.metadata["source_code_uri"] = "https://github.com/fractaledmind/acidic_job"
-  spec.metadata["changelog_uri"] = "https://github.com/fractaledmind/acidic_job/CHANGELOG.md"
-
-  # Specify which files should be added to the gem when it is released.
-  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
-  spec.files = Dir.chdir(File.expand_path(__dir__)) do
-    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{\A(?:test|spec|features)/}) }
-  end
-  spec.bindir = "exe"
-  spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
-  spec.require_paths = ["lib"]
-
-  spec.add_dependency "json", ">= 2.7.0" # see: https://github.com/ruby/json/pull/519
-  ">= 7.1".tap do |rails_version|
-    spec.add_dependency "activejob", rails_version
-    spec.add_dependency "activerecord", rails_version
-    spec.add_dependency "activesupport", rails_version
-    spec.add_dependency "railties", rails_version
-    spec.add_development_dependency "actionmailer", rails_version
-  end
-
-  spec.add_development_dependency "chaotic_job"
-  spec.add_development_dependency "combustion"
-  spec.add_development_dependency "minitest"
-  spec.add_development_dependency "rake"
-  spec.add_development_dependency "rubocop"
-  spec.add_development_dependency "rubocop-minitest"
-  spec.add_development_dependency "rubocop-rake"
-  spec.add_development_dependency "simplecov"
-  spec.add_development_dependency "sqlite3"
-
-  # For more information and examples about making a new gem, checkout our
-  # guide at: https://bundler.io/guides/creating_gem.html
-  spec.metadata["rubygems_mfa_required"] = "true"
-end

data/bin/console

@@ -1,21 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require "bundler/setup"
-require "rails"
-require "acidic_job"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-require "combustion"
-require "sqlite3"
-Combustion.path = "test/combustion"
-Combustion.initialize! :active_record
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start(__FILE__)

data/bin/setup

@@ -1,8 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install
-
-# Do any other automated setup that you need to do here

data/bin/test_all

@@ -1,26 +0,0 @@
-run_tests() {
-  if [ "$#" -ne 2 ]; then
-    echo "Usage: run_tests RUBY_VERSION RAILS_VERSION"
-    echo "Example: run_tests 3.0.7 7.1"
-    return 1
-  fi
-
-  local ruby="$1"
-  local gemfile="gemfiles/rails_$2.gemfile"
-
-  echo "**************************************************"
-  echo "Running tests with Ruby $1 and Rails $2..."
-  ASDF_RUBY_VERSION=$ruby BUNDLE_GEMFILE=$gemfile bundle check ||
-  ASDF_RUBY_VERSION=$ruby BUNDLE_GEMFILE=$gemfile bundle install &&
-  ASDF_RUBY_VERSION=$ruby BUNDLE_GEMFILE=$gemfile bundle exec rake
-}
-
-run_tests "3.0.7" "7.1"
-run_tests "3.1.6" "7.1"
-run_tests "3.1.6" "7.2"
-run_tests "3.2.5" "7.1"
-run_tests "3.2.5" "7.2"
-run_tests "3.2.5" "8.0"
-run_tests "3.3.5" "7.1"
-run_tests "3.3.5" "7.2"
-run_tests "3.3.5" "8.0"

data/blog_post.md

@@ -1,28 +0,0 @@
-# ACIDic Operations in Rails
-
-At the conceptual heart of basically any software are "operations"—the discrete actions the software performs. At the horizon of basically any software is the goal to make that sofware _robust_. Typically, one makes a software system robust by making each of its operations robust. Moreover, typically, robustness in software is considered as the software being "ACIDic"—atomic, consistent, isolated, durable.
-
-In a loosely collected series of articles, Brandur Leach lays out the core techniques and principles required to make an HTTP API properly ACIDic:
-
-1. https://brandur.org/acid
-2. https://brandur.org/http-transactions
-3. https://brandur.org/job-drain
-4. https://brandur.org/idempotency-keys
-
-With these techniques and principles in mind, our challenge is bring them into the world of a standard Rails application. This will require us to conceptually map the concepts of an HTTP request, an API server action, and an HTTP response into the world of a running Rails process.
-
-We can begin to make this mapping by observing that an API server action is a specific instantiation of the general concept of an "operation". Like all operations, it has a "trigger" (the HTTP request) and a "response" (the HTTP response). So, what we need is a foundation upon which to build our Rails "operations".
-
-In order to help us find that tool, let us consider the necessary characteristics we need. We need something that we can easily trigger from other Ruby code throughout our Rails application (controller actions, model methods, model callbacks, etc.). It should also be able to be run both synchronously (blocking execution and then returning its response to the caller) and asychronously (non-blocking and the caller doesn't know its response). It should then also be able to retry a specific operation (in much the way that an API consumer can "retry an operation" by hitting the same endpoint with the same request). 
-
-As we lay out these characteristics, I imagine your mind is going where mine went—`ActiveJob` gives us a solid foundation upon which we can build "ACIDic" operations.
-
-So, our challenge to build tooling which will allow us to make "operational" jobs _robust_.
-
-What we need primarily is to be able to make our jobs *idempotent*, and one of the simplest yet still most powerful tools for making an operation idempotent is the idempotency key. As laid out in the article linked above, an idempotency key is a record that we store in our database to uniquely identify a particular execution of an operation and a related "recovery point" for where we are in the process of that operation.
-
-
-
-
-
-

data/gemfiles/rails_7.0.gemfile

@@ -1,11 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-gem "activejob", "~> 7.0.0"
-gem "activerecord", "~> 7.0.0"
-gem "activesupport", "~> 7.0.0"
-gem "railties", "~> 7.0.0"
-gem "sqlite3", "~> 1.7.3"
-
-gemspec path: "../"

data/gemfiles/rails_7.1.gemfile

@@ -1,11 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-gem "activejob", "~> 7.1.0"
-gem "activerecord", "~> 7.1.0"
-gem "activesupport", "~> 7.1.0"
-gem "railties", "~> 7.1.0"
-gem "sqlite3", ">= 2.0.0"
-
-gemspec path: "../"

data/gemfiles/rails_7.2.gemfile

@@ -1,11 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-gem "activejob", "~> 7.2.0"
-gem "activerecord", "~> 7.2.0"
-gem "activesupport", "~> 7.2.0"
-gem "railties", "~> 7.2.0"
-gem "sqlite3", ">= 2.0.0"
-
-gemspec path: "../"

data/gemfiles/rails_8.0.gemfile

@@ -1,11 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-
-gem "activejob", "~> 8.0.0.rc1"
-gem "activerecord", "~> 8.0.0.rc1"
-gem "activesupport", "~> 8.0.0.rc1"
-gem "railties", "~> 8.0.0.rc1"
-gem "sqlite3", ">= 2.1.0"
-
-gemspec path: "../"