pgbus 0.0.1 → 0.1.1

data/lib/tasks/pgbus_pgmq.rake

@@ -0,0 +1,62 @@
+# frozen_string_literal: true
+
+namespace :pgbus do
+  namespace :pgmq do
+    desc "Show current PGMQ schema status (installed version, available updates)"
+    task status: :environment do
+      require "pgbus/pgmq_schema"
+
+      puts "PGMQ Schema Status"
+      puts "=" * 40
+
+      latest = Pgbus::PgmqSchema.latest_version
+      puts "Vendored version:  #{latest}"
+
+      if ActiveRecord::Base.connection.table_exists?("pgbus_pgmq_schema_versions")
+        row = ActiveRecord::Base.connection.select_one(
+          "SELECT version, install_method, installed_at FROM pgbus_pgmq_schema_versions ORDER BY installed_at DESC LIMIT 1"
+        )
+        if row
+          puts "Installed version: #{row["version"]}"
+          puts "Install method:    #{row["install_method"]}"
+          puts "Installed at:      #{row["installed_at"]}"
+
+          puts ""
+          if Gem::Version.new(row["version"]) < Gem::Version.new(latest)
+            puts "Update available! Run: rails generate pgbus:upgrade_pgmq"
+          else
+            puts "Schema is up to date."
+          end
+        else
+          puts "Installed version: unknown (no records in tracking table)"
+        end
+      else
+        # Check if pgmq schema exists at all
+        schema_exists = ActiveRecord::Base.connection.select_value(
+          "SELECT 1 FROM information_schema.schemata WHERE schema_name = 'pgmq'"
+        )
+        if schema_exists
+          puts "Installed version: unknown (installed before version tracking)"
+          puts ""
+          puts "Run: rails generate pgbus:upgrade_pgmq"
+          puts "This will add version tracking and ensure latest functions."
+        else
+          puts "PGMQ is not installed."
+          puts ""
+          puts "Run: rails generate pgbus:install"
+        end
+      end
+    end
+
+    desc "Show available vendored PGMQ versions"
+    task versions: :environment do
+      require "pgbus/pgmq_schema"
+
+      puts "Available vendored PGMQ versions:"
+      Pgbus::PgmqSchema.available_versions.each do |v|
+        marker = v == Pgbus::PgmqSchema.latest_version ? " (latest)" : ""
+        puts "  #{v}#{marker}"
+      end
+    end
+  end
+end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pgbus
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.1.1
 platform: ruby
 authors:
 - Mikael Henriksson
@@ -23,6 +23,26 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.2'
+- !ruby/object:Gem::Dependency
+  name: fugit
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.11'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.11.1
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.11'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.11.1
 - !ruby/object:Gem::Dependency
   name: pgmq-ruby
   requirement: !ruby/object:Gem::Requirement
@@ -83,21 +103,7 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
-- ".bun-version"
-- ".claude/commands/architect.md"
-- ".claude/commands/github-review-comments.md"
-- ".claude/commands/lfg.md"
-- ".claude/commands/review-pr.md"
-- ".claude/commands/security.md"
-- ".claude/commands/tdd.md"
-- ".claude/rules/agents.md"
-- ".claude/rules/coding-style.md"
-- ".claude/rules/git-workflow.md"
-- ".claude/rules/performance.md"
-- ".claude/rules/testing.md"
 - CHANGELOG.md
-- CLAUDE.md
-- CODE_OF_CONDUCT.md
 - LICENSE.txt
 - README.md
 - Rakefile
@@ -109,7 +115,16 @@ files:
 - app/controllers/pgbus/jobs_controller.rb
 - app/controllers/pgbus/processes_controller.rb
 - app/controllers/pgbus/queues_controller.rb
+- app/controllers/pgbus/recurring_tasks_controller.rb
 - app/helpers/pgbus/application_helper.rb
+- app/models/pgbus/application_record.rb
+- app/models/pgbus/batch_entry.rb
+- app/models/pgbus/blocked_execution.rb
+- app/models/pgbus/process_entry.rb
+- app/models/pgbus/processed_event.rb
+- app/models/pgbus/recurring_execution.rb
+- app/models/pgbus/recurring_task.rb
+- app/models/pgbus/semaphore.rb
 - app/views/layouts/pgbus/application.html.erb
 - app/views/pgbus/dashboard/_processes_table.html.erb
 - app/views/pgbus/dashboard/_queues_table.html.erb
@@ -130,17 +145,21 @@ files:
 - app/views/pgbus/queues/_queues_list.html.erb
 - app/views/pgbus/queues/index.html.erb
 - app/views/pgbus/queues/show.html.erb
-- bun.lock
+- app/views/pgbus/recurring_tasks/_tasks_table.html.erb
+- app/views/pgbus/recurring_tasks/index.html.erb
+- app/views/pgbus/recurring_tasks/show.html.erb
 - config/routes.rb
-- docs/README.md
-- docs/switch_from_good_job.md
-- docs/switch_from_sidekiq.md
-- docs/switch_from_solid_queue.md
 - exe/pgbus
+- lib/active_job/queue_adapters/pgbus_adapter.rb
+- lib/generators/pgbus/add_recurring_generator.rb
 - lib/generators/pgbus/install_generator.rb
+- lib/generators/pgbus/templates/add_recurring_tables.rb.erb
 - lib/generators/pgbus/templates/migration.rb.erb
 - lib/generators/pgbus/templates/pgbus.yml.erb
 - lib/generators/pgbus/templates/pgbus_binstub.erb
+- lib/generators/pgbus/templates/recurring.yml.erb
+- lib/generators/pgbus/templates/upgrade_pgmq.rb.erb
+- lib/generators/pgbus/upgrade_pgmq_generator.rb
 - lib/pgbus.rb
 - lib/pgbus/active_job/adapter.rb
 - lib/pgbus/active_job/executor.rb
@@ -158,24 +177,32 @@ files:
 - lib/pgbus/event_bus/publisher.rb
 - lib/pgbus/event_bus/registry.rb
 - lib/pgbus/event_bus/subscriber.rb
+- lib/pgbus/instrumentation.rb
+- lib/pgbus/pgmq_schema.rb
+- lib/pgbus/pgmq_schema/pgmq_v1.11.0.sql
 - lib/pgbus/process/consumer.rb
 - lib/pgbus/process/dispatcher.rb
 - lib/pgbus/process/heartbeat.rb
 - lib/pgbus/process/signal_handler.rb
 - lib/pgbus/process/supervisor.rb
 - lib/pgbus/process/worker.rb
+- lib/pgbus/recurring/already_recorded.rb
+- lib/pgbus/recurring/command_job.rb
+- lib/pgbus/recurring/config_loader.rb
+- lib/pgbus/recurring/schedule.rb
+- lib/pgbus/recurring/scheduler.rb
+- lib/pgbus/recurring/task.rb
 - lib/pgbus/serializer.rb
 - lib/pgbus/version.rb
 - lib/pgbus/web/authentication.rb
 - lib/pgbus/web/data_source.rb
-- package.json
-- sig/pgbus.rbs
+- lib/tasks/pgbus_pgmq.rake
 homepage: https://github.com/mhenrixon/pgbus
 licenses:
 - MIT
 metadata:
   homepage_uri: https://github.com/mhenrixon/pgbus
-  source_code_uri: https://github.com/mhenrixon/pgbus
+  source_code_uri: https://github.com/mhenrixon/pgbus/tree/main
   changelog_uri: https://github.com/mhenrixon/pgbus/blob/main/CHANGELOG.md
   rubygems_mfa_required: 'true'
 rdoc_options: []
@@ -192,7 +219,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.6
+rubygems_version: 3.6.9
 specification_version: 4
 summary: PostgreSQL-native job processing and event bus for Rails, built on PGMQ
 test_files: []

data/.bun-version

@@ -1 +0,0 @@
-1.3.11

data/.claude/commands/architect.md

@@ -1,100 +0,0 @@
----
-description: "Coordinates development across pgbus layers. Use when planning multi-layer features, orchestrating implementation order, or designing new subsystems."
-model: claude-opus-4-6
-argument-hint: "feature or task to coordinate"
----
-
-# Pgbus Architect Mode
-
-You are now in **Architect Mode** - coordinating development across all pgbus layers.
-
-## Why This Skill Exists
-
-Pgbus spans multiple layers (PGMQ transport, ActiveJob adapter, event bus, process model, dashboard). Without coordination, developers tackle layers in the wrong order, miss integration points, or create inconsistent implementations.
-
-## Pgbus Architecture Layers
-
-```
-Layer 6: Dashboard (Web UI)          app/controllers/pgbus/, app/views/pgbus/
-Layer 5: CLI                         lib/pgbus/cli.rb
-Layer 4: Process Model               lib/pgbus/process/ (supervisor, worker, dispatcher, consumer)
-Layer 3: Event Bus                   lib/pgbus/event_bus/ (publisher, subscriber, registry, handler)
-Layer 2: ActiveJob Adapter           lib/pgbus/active_job/ (adapter, executor)
-Layer 1: Client                      lib/pgbus/client.rb (PGMQ wrapper)
-Layer 0: Configuration               lib/pgbus/configuration.rb, config_loader.rb
-```
-
-## Typical Implementation Flow
-
-1. **Configuration** - Add new config options if needed
-2. **Client** - Add PGMQ operations to the client wrapper
-3. **Adapter / Event Bus** - Build the feature's core logic
-4. **Process Model** - Add worker/consumer support
-5. **Dashboard** - Expose in the web UI via DataSource
-6. **Tests** - Coverage across all touched layers
-
-## When to Delegate vs. Do Directly
-
-**Delegate when**:
-- Multiple files across a layer need changes
-- Deep domain expertise is needed (e.g., PGMQ internals)
-- Work is clearly scoped to one layer
-
-**Handle directly when**:
-- Simple, single-file changes
-- Cross-cutting concerns affecting multiple layers
-- Quick fixes or minor adjustments
-
-## Decision Guidelines
-
-| Decision | Use When |
-|----------|----------|
-| New config option | Feature needs user-configurable behavior |
-| New Client method | New PGMQ operation needed |
-| New event handler | Business event needs processing |
-| New worker type | Different processing pattern needed |
-| Dashboard page | Users need visibility into new feature |
-| Migration change | New metadata table or PGMQ queue |
-
-## Integration Points
-
-| When working on... | Also consider... |
-|-------------------|------------------|
-| Client changes | Worker/consumer that calls it |
-| New queue type | Dead letter queue, dashboard visibility |
-| Event bus feature | Idempotency table, subscriber registry |
-| Process model | Heartbeat, supervisor restart logic |
-| Dashboard | DataSource queries, authentication |
-| Configuration | Config loader YAML, generator template |
-
-## Common Mistakes to Avoid
-
-| Wrong | Right |
-|-------|-------|
-| Start with dashboard | Start with client/adapter layer |
-| Skip configuration | Make it configurable from the start |
-| Direct PGMQ calls | Go through Client wrapper |
-| Forget DLQ | Every queue needs a dead letter strategy |
-| Skip tests | TDD -- tests first at every layer |
-| Monolith methods | Small files, focused classes |
-
-## Verification Checklist
-
-- [ ] Implementation order planned (bottom-up)
-- [ ] Dependencies between layers identified
-- [ ] PGMQ operations go through Client
-- [ ] Configuration is extensible
-- [ ] Dashboard exposes new data via DataSource
-- [ ] Tests cover all touched layers
-- [ ] `bundle exec rubocop` passes
-- [ ] `bundle exec rspec` passes
-
-## Handoff
-
-When complete, summarize:
-- Implementation plan with layer order
-- Files to create/modify per layer
-- Integration points identified
-- Architectural decisions made
-
-Now, coordinate pgbus development with this architectural perspective.

data/.claude/commands/github-review-comments.md

@@ -1,237 +0,0 @@
----
-description: "Use when a PR has unresolved review comments that need responses -- evaluates each comment, implements valid fixes, pushes back on incorrect suggestions, and resolves all threads."
-model: claude-opus-4-6
-argument-hint: "PR number (e.g., 123 or #123)"
-allowed-tools: Bash(gh pr view:*), Bash(gh pr diff:*), Bash(gh pr comment:*), Bash(gh api:*), Bash(git log:*), Bash(git blame:*), Bash(git push:*), Bash(git commit:*), Bash(git add:*), Bash(bundle exec:*), Read, Write, Edit, Glob, Grep, Agent
----
-
-# Review GitHub PR Comments: $ARGUMENTS
-
-You are reviewing and responding to all unresolved review comments on a GitHub pull request. Apply technical rigour -- evaluate each comment against the actual codebase before accepting or rejecting it.
-
-## Phase 0: Determine the PR Number
-
-The user may provide a PR number as `$ARGUMENTS`. Parse it flexibly:
-
-- `PR123`, `PR 123`, `pr123` -> PR 123
-- `123` -> PR 123
-- `#123` -> PR 123
-- Empty/blank -> auto-detect from current branch
-
-**If no PR number is provided**, detect it automatically:
-
-```bash
-gh pr list --author=@me --head="$(git branch --show-current)" --state=open --json number,title
-```
-
-If exactly one open PR exists for the current branch, use it. If none or multiple, ask the user.
-
-Once you have the PR number, confirm it:
-
-```bash
-gh pr view <PR_NUMBER> --json title,state,url
-```
-
----
-
-## Phase 1: Fetch All Unresolved Review Comments
-
-Retrieve all review comments and identify unresolved ones:
-
-```bash
-# Get all review comments (not resolved)
-gh api "repos/mhenrixon/pgbus/pulls/<PR_NUMBER>/comments" --paginate
-
-# Get all review threads to check resolution status
-gh api graphql -f query='
-  query($owner: String!, $repo: String!, $pr: Int!) {
-    repository(owner: $owner, name: $repo) {
-      pullRequest(number: $pr) {
-        reviewThreads(first: 100) {
-          nodes {
-            id
-            isResolved
-            path
-            line
-            comments(first: 20) {
-              nodes {
-                id
-                databaseId
-                body
-                author { login }
-                createdAt
-              }
-            }
-          }
-        }
-      }
-    }
-  }
-' -f owner=mhenrixon -f repo=pgbus -F pr=<PR_NUMBER>
-```
-
-For each unresolved thread, extract:
-- Thread ID (for resolving)
-- Comment body (the review feedback)
-- File path and line number (if inline)
-- Author (to understand context)
-
-Filter to only **unresolved** threads. Skip bot comments (CodeRabbit, dependabot), resolved threads, and PR description comments.
-
-If there are no unresolved review comments, report that and stop.
-
----
-
-## Phase 2: Read and Categorise Each Comment
-
-For each unresolved comment, read the full body and categorise it:
-
-| Category | Action |
-|----------|--------|
-| Valid fix needed | Implement the fix |
-| Valid test gap | Add the missing test |
-| Valid style/consistency issue | Fix it |
-| Incorrect suggestion | Push back with technical reasoning |
-| Suggestion conflicts with architecture | Push back, reference existing patterns |
-| Over-engineering / YAGNI | Push back, explain why it's unnecessary |
-| Unclear | Ask for clarification (do NOT implement) |
-
-**Before categorising**, always:
-1. Read the actual file and line being commented on
-2. Check if the suggestion is technically correct for THIS codebase
-3. Check if it would break existing functionality
-4. Check if existing patterns/conventions contradict the suggestion
-5. Check CLAUDE.md rules -- project conventions override reviewer preferences
-
----
-
-## Phase 3: Implement Accepted Fixes
-
-For all comments you've decided to accept:
-
-1. **Make the code changes** -- edit the relevant files
-2. **Run affected tests** to verify nothing breaks:
-   ```bash
-   bundle exec rspec <relevant_spec_files>
-   ```
-3. **Run validators**:
-   ```bash
-   bundle exec rubocop <changed_files>
-   ```
-4. **Commit** all fixes together with a clear message:
-   ```bash
-   git commit -m "$(cat <<'EOF'
-   fix: address PR review feedback
-
-   - Description of fix 1
-   - Description of fix 2
-   EOF
-   )"
-   ```
-5. **Push** to the remote branch:
-   ```bash
-   git push
-   ```
-
----
-
-## Phase 4: Reply to Every Comment
-
-For **each** unresolved thread, reply:
-
-### For accepted fixes:
-
-Reply with what was fixed and the commit SHA:
-
-```bash
-gh api "repos/mhenrixon/pgbus/pulls/<PR>/comments/<COMMENT_ID>/replies" \
-  --method POST \
-  -f 'body=Fixed in <SHA>. <Brief description of what changed>.'
-```
-
-### For rejected suggestions:
-
-Reply with technical reasoning:
-
-```bash
-gh api "repos/mhenrixon/pgbus/pulls/<PR>/comments/<COMMENT_ID>/replies" \
-  --method POST \
-  -f 'body=<Technical explanation of why the suggestion was not implemented>'
-```
-
-### Resolving threads (via GraphQL):
-
-After replying, resolve the thread:
-
-```bash
-gh api graphql -f query='
-  mutation($threadId: ID!) {
-    resolveReviewThread(input: {threadId: $threadId}) {
-      thread { isResolved }
-    }
-  }
-' -f threadId=<THREAD_NODE_ID>
-```
-
-### For general PR comments (not inline review threads):
-
-Reply directly:
-
-```bash
-gh pr comment <PR_NUMBER> --body "<Response addressing each point>"
-```
-
----
-
-## Phase 5: Verify Completion
-
-After processing all comments, verify no unresolved threads remain:
-
-```bash
-gh api graphql -f query='
-  query($owner: String!, $repo: String!, $pr: Int!) {
-    repository(owner: $owner, name: $repo) {
-      pullRequest(number: $pr) {
-        reviewThreads(first: 100) {
-          totalCount
-          nodes { isResolved }
-        }
-      }
-    }
-  }
-' -f owner=mhenrixon -f repo=pgbus -F pr=<PR_NUMBER>
-```
-
-Report the final tally: how many comments were accepted/fixed, how many were pushed back on, and confirm all threads are resolved.
-
----
-
-## Response Style
-
-When replying to comments:
-
-- **No performative agreement** -- never say "Great point!" or "You're absolutely right!"
-- **No gratitude** -- never say "Thanks for catching that"
-- **Be direct** -- state the fix or the reasoning, nothing more
-- **Reference commits** -- always include the short SHA when a fix was made
-- **Be specific** -- when pushing back, reference actual code, not abstract principles
-
-When pushing back:
-
-- Use technical reasoning grounded in the actual codebase
-- Reference existing patterns if the suggestion contradicts them
-- Reference CLAUDE.md rules when applicable
-- Explain what would break or what edge case the reviewer missed
-- If the suggestion is valid in principle but wrong for this context, say so
-
----
-
-## Important Notes
-
-- Always read the actual code before evaluating a comment -- reviewers sometimes misread diffs
-- If a comment reveals a genuine bug you missed, fix it without defensiveness
-- If multiple comments suggest the same change, implement it once and reference the fix in all replies
-- Bot reviewers (CodeRabbit, etc.) sometimes suggest changes that conflict with project conventions -- verify against CLAUDE.md
-- If a new round of review comments appears after your push (from re-review), report that to the user rather than entering an infinite loop
-
-Now begin by determining the PR number from `$ARGUMENTS` or the current branch.