bd sync: 2025-10-31 14:36:12

This commit is contained in:
Steve Yegge
2025-10-31 14:36:12 -07:00
parent d5488cb97f
commit b2b0373d08

View File

@@ -56,7 +56,7 @@
{"id":"bd-4c74","content_hash":"b39e8da1248cfe43fb5c73a8f313b690604a6cbf1be39ac6e51bbd8aa8ad4a82","title":"Remove branch-merge example (sequential ID collision workflow)","description":"The examples/branch-merge/ example demonstrates --resolve-collisions workflow which is no longer relevant:\n- Remove examples/branch-merge/ directory\n- Update examples/README.md to remove reference\n- Consider adding new example showing hash ID merge workflow (trivial - just accept both changes)","status":"closed","priority":2,"issue_type":"chore","created_at":"2025-10-30T22:16:48.499526-07:00","updated_at":"2025-10-30T22:24:25.58328-07:00","closed_at":"2025-10-30T22:24:25.58328-07:00","labels":["cleanup","examples","hash-ids"]}
{"id":"bd-4d7fca8a","title":"Add tests for internal/utils package","description":"Currently 0.0% coverage. Need tests for utility functions including issue ID parsing and validation.","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-29T14:06:24.066403-07:00","updated_at":"2025-10-30T17:05:25.994935-07:00","dependencies":[{"issue_id":"bd-4d7fca8a","depends_on_id":"bd-cbed9619.5","type":"blocks","created_at":"2025-10-29T19:52:05.52888-07:00","created_by":"import-remap"},{"issue_id":"bd-4d7fca8a","depends_on_id":"bd-cbed9619.4","type":"blocks","created_at":"2025-10-29T19:52:05.529565-07:00","created_by":"import-remap"},{"issue_id":"bd-4d7fca8a","depends_on_id":"bd-0dcea000","type":"blocks","created_at":"2025-10-29T19:52:05.529982-07:00","created_by":"import-remap"}]}
{"id":"bd-4d80b7b1","content_hash":"0cad3e22d722ff045a29f218962fb00bd8265a1cfc82c5b70f29ffe1a40e4088","title":"Investigate and upgrade to modernc.org/sqlite 1.39.1+","description":"We had to pin modernc.org/sqlite to v1.38.2 due to a FOREIGN KEY constraint regression in v1.39.1 (SQLite 3.50.4).\n\n**Issue:** [deleted:bd-cb64c226.2], GH #144\n\n**Symptom:** CloseIssue fails with \"FOREIGN KEY constraint failed (787)\" when called via MCP/daemon, but works fine via CLI.\n\n**Root Cause:** Unknown - likely stricter FK enforcement in SQLite 3.50.4 or modernc.org wrapper changes.\n\n**Workaround:** Pinned to v1.38.2 (SQLite 3.49.x)\n\n**TODO:**\n1. Monitor modernc.org/sqlite releases for fixes\n2. Check SQLite 3.50.5+ changelogs for FK-related fixes\n3. Investigate why daemon mode fails but CLI succeeds (connection reuse? transaction isolation?)\n4. Consider filing upstream issue with reproducible test case\n5. Upgrade when safe","status":"open","priority":2,"issue_type":"task","created_at":"2025-10-24T11:49:12.836292-07:00","updated_at":"2025-10-30T17:05:26.02316-07:00"}
{"id":"bd-4dcd2d09","content_hash":"424a55e69759947e5fb5a4326eea0b7d0feb3c64d9aba110f67ce5e05623824b","title":"Add --json flag to all bd commands","description":"Currently not all bd commands support --json output, which makes it difficult for agents to parse output programmatically.\n\nFor example, `bd stats` doesn't support --json flag (returns error).\n\nAll commands should support --json for consistent agent-friendly output:\n- bd stats\n- bd list (already has it)\n- bd show (already has it)\n- bd ready (already has it)\n- bd create (already has it)\n- bd update (already has it)\n- bd close (already has it)\n- bd dep (check if all subcommands support it)\n- bd label (check if all subcommands support it)\n- bd import/export\n- bd sync\n- bd duplicates\n- bd merge\n- Any other commands\n\nAudit all commands and ensure consistent --json support across the board.","status":"open","priority":1,"issue_type":"feature","created_at":"2025-10-29T23:46:34.987439-07:00","updated_at":"2025-10-30T17:05:26.018092-07:00"}
{"id":"bd-4dcd2d09","content_hash":"5031bfbb853876737017c655eb26748e611c88e36ddc288d17e32c29f6105ca8","title":"Add --json flag to all bd commands","description":"Currently not all bd commands support --json output, which makes it difficult for agents to parse output programmatically.\n\nFor example, `bd stats` doesn't support --json flag (returns error).\n\nAll commands should support --json for consistent agent-friendly output:\n- bd stats\n- bd list (already has it)\n- bd show (already has it)\n- bd ready (already has it)\n- bd create (already has it)\n- bd update (already has it)\n- bd close (already has it)\n- bd dep (check if all subcommands support it)\n- bd label (check if all subcommands support it)\n- bd import/export\n- bd sync\n- bd duplicates\n- bd merge\n- Any other commands\n\nAudit all commands and ensure consistent --json support across the board.","status":"in_progress","priority":1,"issue_type":"feature","created_at":"2025-10-29T23:46:34.987439-07:00","updated_at":"2025-10-31T14:31:06.96076-07:00"}
{"id":"bd-4e21b5ad","content_hash":"d737255765d8b9579765347a92638b70f9e7bbd293df14b1a3f870e74dd8bd7e","title":"Add test case for symmetric collision (both clones create same ID simultaneously)","description":"TestTwoCloneCollision demonstrates the problem, but we need a simpler unit test for the collision resolver itself.\n\nTest should verify:\n- Two issues with same ID, different content\n- Content hash determines winner deterministically \n- Result is same regardless of which clone imports first\n- No title swapping occurs\n\nThis can be a simpler test than the full integration test.","notes":"Tests cleaned up. Deprecated TestTwoCloneCollision and TestThreeCloneCollision (sequence-ID tests). TestFiveCloneCollision passes successfully with hash IDs, testing 3 different sync orders (sequential, reverse, random). Hash-based IDs prevent ID collisions - git merge conflicts are expected and handled by conflict resolution in the test.","status":"closed","priority":1,"issue_type":"task","created_at":"2025-10-29T17:46:10.046999-07:00","updated_at":"2025-10-30T20:24:54.717863-07:00","closed_at":"2025-10-30T20:24:54.717863-07:00"}
{"id":"bd-50a7","content_hash":"ce3e6a3c2c64d76145ed93ed550c93dd88d7d530911e4cf1fd80d8c16194b8d4","title":"Update FAQ.md to remove --resolve-collisions references","description":"FAQ.md lines 289-291 still recommend 'bd import --resolve-collisions' for same ID scenarios. With hash IDs, this is simply an update operation. Need to update section to explain same-ID imports are updates.","status":"closed","priority":1,"issue_type":"task","created_at":"2025-10-31T14:11:05.095092-07:00","updated_at":"2025-10-31T14:13:55.105871-07:00","closed_at":"2025-10-31T14:13:55.105871-07:00"}
{"id":"bd-5314bddf","content_hash":"bbaf3bd26766fb78465900c455661a3608ab1d1485cb964d12229badf138753a","title":"bd detect-pollution - Test pollution detector","description":"Detect test issues that leaked into production DB.\n\nPattern matching for:\n- Titles starting with 'test', 'benchmark', 'sample'\n- Sequential numbering (test-1, test-2)\n- Generic descriptions\n- Created in rapid succession\n\nOptional AI scoring for confidence.\n\nFiles: cmd/bd/detect_pollution.go (new)","status":"open","priority":1,"issue_type":"task","created_at":"2025-10-28T14:48:17.466906-07:00","updated_at":"2025-10-30T17:05:26.03612-07:00"}