legion-data 1.10.5 → 1.10.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7f3b320363f209f8dfae3ad1a9757bae5e17dd4d7e6327b849b0d8804df22c07
-  data.tar.gz: ac12848278ac407233eb43b6f5a72dbf503b030a9d404e88578fdb8ebd173cc5
+  metadata.gz: 861fe6533a77e8819c03400430f32ddb420a7cfa29e042b3c86734f6d7fd57bc
+  data.tar.gz: 48fe377db280cad64c5e9331926a24319a44c78c96eeb9aa7e2c6aa038a77024
 SHA512:
-  metadata.gz: 0e0331f06f446400f70581981a8f083e1baac336aee984904f56af60eb9a9d021d56af48c8b845a13beaebd4aca1ba0e7a264af1101f78426d447a4cfd3d86b2
-  data.tar.gz: 70b599bee80873cd661bdd09aacb406da9d8cdd479d270b6012032945aedb08bb82a3819f00f11f44e45b3470b8b88042491e5e892900564d334d6b4748f945a
+  metadata.gz: 3850a5774dbc1de772fd8a2b4762dddc9da3164e9cff32b5f02b946f7608dba551394bcb3b2aa90590f038199f33da655957c74896ff74419e840a4769b7008e
+  data.tar.gz: 006b1ed6fd955a876dabfa6875fa075eb8abfec1aa59467b3411e36e3ce32752735277b4013ba908db280cb98a4c152bb91e14563be55c41d6ff53778c3f944a

data/.rubocop.yml

@@ -23,6 +23,13 @@ Naming/VariableNumber:
     - lib/legion/data/connection.rb
 Legion/Framework/EagerSequelModel:
   Enabled: false
+# TaxonomyEnum validates LLM lane taxonomy (:tier/:type/:circuit_state). In
+# these paths `type:` is a Sequel column type (e.g. foreign_key type: :uuid) or
+# the extract API (type: :auto/:text) — not LLM taxonomy — so the cop misfires.
+Legion/Llm/TaxonomyEnum:
+  Exclude:
+    - 'lib/legion/data/migrations/**/*'
+    - 'spec/**/*'
 Metrics/BlockLength:
   Max: 100
   Exclude:

data/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Legion::Data Changelog
 
+## [1.10.6] - 2026-07-03
+
+### Changed
+- Migration 136: drops the `(conversation_id, seq)` UNIQUE constraint on `llm_messages`, replacing it with a NON-unique composite index. A conversation is a tree, not a line — a single parent can legitimately have two children at the same depth (e.g. a failed branch and the branch that continued), so two distinct messages can share `(conversation_id, seq)` and that is truth, not a duplicate. The unique constraint rejected legitimate siblings and forced the centralized ledger into a racy `MAX(seq)+1` generation that collided under concurrent writers (`PG::UniqueViolation` on `llm_messages_conversation_id_seq_key`). Message identity remains guaranteed by the unique `uuid`; `seq` becomes descriptive tree-depth. On SQLite the constraint drop rebuilds the table (dropping the inline `uuid` UNIQUE), so the migration re-asserts the uuid unique index — a no-op on PostgreSQL where `DROP CONSTRAINT` is surgical.
+
 ## [1.10.5] - 2026-06-16
 
 ### Added

data/lib/legion/data/archiver.rb

@@ -97,18 +97,15 @@ module Legion
           total_rows = 0
           paths = []
 
-          loop do
-            batch_result = archive_batch(
-              conn:            conn,
-              table:           table,
-              cutoff:          cutoff,
-              batch_size:      batch_size,
-              batch_n:         batches + 1,
-              now:             now,
-              storage_backend: storage_backend
-            )
-            break unless batch_result
-
+          while (batch_result = archive_batch(
+            conn:            conn,
+            table:           table,
+            cutoff:          cutoff,
+            batch_size:      batch_size,
+            batch_n:         batches + 1,
+            now:             now,
+            storage_backend: storage_backend
+          ))
             batches += 1
             total_rows += batch_result[:row_count]
             paths << batch_result[:path]

data/lib/legion/data/extract/handlers/base.rb

@@ -53,7 +53,7 @@ module Legion
               require gem_name
               true
             rescue LoadError => e
-              handle_exception(e, level: :debug, handled: true, operation: :extract_handler_available, handler: name, gem: gem_name)
+              handle_exception(e, level: :warn, handled: true, operation: :extract_handler_available, handler: name, gem: gem_name)
               false
             end
           end

data/lib/legion/data/migrations/136_drop_llm_messages_seq_unique.rb

@@ -0,0 +1,36 @@
+# frozen_string_literal: true
+
+# The (conversation_id, seq) UNIQUE constraint modeled a conversation as a flat
+# line, but a conversation is a tree: a single parent can legitimately have two
+# children at the same depth (e.g. a failed branch and the branch that
+# succeeded), so two distinct messages can share the same (conversation_id, seq)
+# and that is TRUTH, not a duplicate. The unique constraint rejected those
+# legitimate siblings and forced the ledger into a racy MAX(seq)+1 generation
+# that collided under concurrent writers.
+#
+# Message identity is guaranteed by the unique `uuid` (producer-derived, stable
+# across redelivery). seq/parent become descriptive ordering data, so we keep a
+# NON-unique composite index for conversation-ordered reads.
+Sequel.migration do
+  up do
+    alter_table(:llm_messages) do
+      drop_constraint(:llm_messages_conversation_id_seq_key, type: :unique)
+      add_index %i[conversation_id seq], name: :idx_llm_messages_conversation_seq
+    end
+    # SQLite emulates the constraint drop by rebuilding the table, which drops
+    # the inline `uuid` UNIQUE. Re-assert it so message identity/dedup is never
+    # lost. On PostgreSQL DROP CONSTRAINT is surgical and the original uuid index
+    # already exists, so this is a no-op there.
+    alter_table(:llm_messages) do
+      add_index :uuid, unique: true, name: :idx_llm_messages_uuid_unique, if_not_exists: true
+    end
+  end
+
+  down do
+    alter_table(:llm_messages) do
+      drop_index :uuid, name: :idx_llm_messages_uuid_unique, if_exists: true
+      drop_index %i[conversation_id seq], name: :idx_llm_messages_conversation_seq
+      add_unique_constraint %i[conversation_id seq], name: :llm_messages_conversation_id_seq_key
+    end
+  end
+end

data/lib/legion/data/models/function.rb

@@ -18,7 +18,7 @@ module Legion
 
           ::JSON.parse(embedding)
         rescue ::JSON::ParserError => e
-          handle_exception(e, level: :debug, handled: true, operation: :embedding_vector, id: self[:id])
+          handle_exception(e, level: :warn, handled: true, operation: :embedding_vector, id: self[:id])
           nil
         end
 

data/lib/legion/data/models/node.rb

@@ -17,7 +17,7 @@ module Legion
 
           Legion::JSON.load(metrics)
         rescue StandardError => e
-          handle_exception(e, level: :debug, handled: true, operation: :parsed_metrics, id: self[:id])
+          handle_exception(e, level: :warn, handled: true, operation: :parsed_metrics, id: self[:id])
           nil
         end
 
@@ -26,7 +26,7 @@ module Legion
 
           Legion::JSON.load(hosted_worker_ids)
         rescue StandardError => e
-          handle_exception(e, level: :debug, handled: true, operation: :parsed_hosted_worker_ids, id: self[:id])
+          handle_exception(e, level: :warn, handled: true, operation: :parsed_hosted_worker_ids, id: self[:id])
           []
         end
       end

data/lib/legion/data/version.rb

@@ -2,6 +2,6 @@
 
 module Legion
   module Data
-    VERSION = '1.10.5'
+    VERSION = '1.10.6'
   end
 end

data/lib/legion/data.rb

@@ -112,7 +112,7 @@ module Legion
       def connected?
         Legion::Settings[:data][:connected] == true
       rescue StandardError => e
-        handle_exception(e, level: :debug, handled: true, operation: :connected?)
+        handle_exception(e, level: :warn, handled: true, operation: :connected?)
         false
       end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: legion-data
 version: !ruby/object:Gem::Version
-  version: 1.10.5
+  version: 1.10.6
 platform: ruby
 authors:
 - Esity
@@ -282,6 +282,7 @@ files:
 - lib/legion/data/migrations/133_allow_null_context_tokens.rb
 - lib/legion/data/migrations/134_add_route_attempt_columns.rb
 - lib/legion/data/migrations/135_add_llm_context_token_accounting.rb
+- lib/legion/data/migrations/136_drop_llm_messages_seq_unique.rb
 - lib/legion/data/model.rb
 - lib/legion/data/models/apollo/access_log.rb
 - lib/legion/data/models/apollo/entries.rb