Hive
fix(specs): assign spec numbers transactionally
GitHub issue · Closed
Source
tuist/hive #46
Updated
Jun 24, 2026
Domains
Hive
Summary
- Assign spec numbers inside the
Specs.create_spec/2transaction instead of relying on PostgreSQL sequence defaults. - Lock spec-number allocation and compute the next public number from the current maximum so rolled-back creates do not consume numbers.
- Remove the old
specs_number_seqdefault and add MCP coverage for rollback behavior during spec creation.
Testing
mix formatmix test test/hive/mcp/components/tools/create_spec_test.exs test/hive/specs_test.exsmix compile --warnings-as-errorsmix test
Investigate, reproduce, or fix this item in an isolated repository. Each Flight preserves its outcome and agent session.
New Flights are paused
Configure model inference, GitHub, and a sandbox provider to start another Flight. Existing results remain available below.
No Flights yet
Start a Flight and preserve its objective, outcome, and session here.
No GitHub comments yet.