lex-metering 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6e70bf639989419388bb625a4f105d7ad6376b534b35f839d8623427bfc3fe43
-  data.tar.gz: b6c1250c1e19d2d80ee88772416aa4b3f05f4123b774698b6b4ae6ef5b6f02a4
+  metadata.gz: f6ed98a119f0cd8391dfcbabef08384a0ead7ff8f9cfd45added086ce825ddef
+  data.tar.gz: 47b5dc7406297ff5c9bec985b4d4ef2d0d554cc3cea0c0c489305d545c22b07f
 SHA512:
-  metadata.gz: d65a2b2829f638b80ce726b19c616f81a4dc4c436482bea8bee837d489053070b929f59fe240e09dff4478be52cdce3dee43aa127cc21dea0b49833b920ec246
-  data.tar.gz: 614785e8c7af6964c0312c5f18ff362c0fd1f7e29656e6db76cd94c2029774108050671363adb8b17012f334ce71e86750f6547eae298490875fde11637c092c
+  metadata.gz: be6917d55265e01b080e4165de8c5df74c41ab38738ad6400e0fe84188d61e5e022ec806f0fb19e705fa2d04a5877d33892f744978c18a018e8dda9ef25784ec
+  data.tar.gz: d12d6e44b297b5d533a3f6e49764f9fbd3a4e74a86594c83c1a5e13812a6654f08667f81fc5a84a34368a75cf8b8c8a11933bc894ba4f5aa1833070608749d40

data/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## [0.1.3] - 2026-03-18
+
+### Fixed
+- `worker_costs` period filtering now uses cross-DB `Sequel.lit('recorded_at >= ?', cutoff)` with Ruby time arithmetic instead of PostgreSQL-only `CURRENT_TIMESTAMP - INTERVAL` syntax
+
 ## [0.1.2] - 2026-03-17
 
 ### Changed

data/CLAUDE.md

@@ -11,7 +11,7 @@ Captures LLM token usage metrics per task for cost attribution and intelligent r
 ## Gem Info
 
 - **Gem name**: `lex-metering`
-- **Version**: `0.1.0`
+- **Version**: `0.1.3`
 - **Module**: `Legion::Extensions::Metering`
 - **Ruby**: `>= 3.4`
 - **License**: MIT
@@ -72,4 +72,4 @@ lib/legion/extensions/metering/
 - Extension has `data_required? true` (both at module level and instance level) — will skip loading if `legion-data` is not connected
 - No explicit actors — gets auto-generated subscription actors from the framework
 - `routing_stats` uses `select_append { avg(latency_ms).as(avg_latency) }` — Sequel virtual row syntax
-- Time interval filtering uses `Sequel.lit("CURRENT_TIMESTAMP - INTERVAL '...'")` which is PostgreSQL syntax; SQLite uses different interval syntax (known limitation)
+- Time interval filtering uses `Sequel.lit('recorded_at >= ?', cutoff)` with Ruby `Time` arithmetic for cross-database compatibility (PostgreSQL, SQLite, MySQL)

data/lib/legion/extensions/metering/runners/metering.rb

@@ -5,6 +5,8 @@ module Legion
     module Metering
       module Runners
         module Metering
+          PERIOD_DAYS = { 'daily' => 1, 'weekly' => 7, 'monthly' => 30 }.freeze
+
           def record(worker_id: nil, task_id: nil, provider: nil, model_id: nil,
                      input_tokens: 0, output_tokens: 0, thinking_tokens: 0,
                      input_context_bytes: 0, latency_ms: 0, routing_reason: nil,
@@ -35,15 +37,7 @@ module Legion
 
           def worker_costs(worker_id:, period: 'daily', **)
             ds = Legion::Data.connection[:metering_records].where(worker_id: worker_id)
-
-            case period
-            when 'daily'
-              ds = ds.where { recorded_at >= Sequel.lit("CURRENT_TIMESTAMP - INTERVAL '1 day'") }
-            when 'weekly'
-              ds = ds.where { recorded_at >= Sequel.lit("CURRENT_TIMESTAMP - INTERVAL '7 days'") }
-            when 'monthly'
-              ds = ds.where { recorded_at >= Sequel.lit("CURRENT_TIMESTAMP - INTERVAL '30 days'") }
-            end
+            ds = apply_period_filter(ds, period)
 
             {
               worker_id:       worker_id,
@@ -93,6 +87,16 @@ module Legion
             Legion::Logging.info "[metering] cleanup: purged=#{count} retention_days=#{retention_days} cutoff=#{cutoff}"
             { purged: count, retention_days: retention_days, cutoff: cutoff }
           end
+
+          private
+
+          def apply_period_filter(dataset, period)
+            days = PERIOD_DAYS[period]
+            return dataset unless days
+
+            cutoff = Time.now.utc - (days * 86_400)
+            dataset.where(::Sequel.lit('recorded_at >= ?', cutoff))
+          end
         end
       end
     end

data/lib/legion/extensions/metering/version.rb

@@ -3,7 +3,7 @@
 module Legion
   module Extensions
     module Metering
-      VERSION = '0.1.2'
+      VERSION = '0.1.3'
     end
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: lex-metering
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - Esity