johno/beads
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

bd sync: 2025-11-06 19:07:19

Browse Source
This commit is contained in:
Steve Yegge
2025-11-06 19:07:19 -08:00
parent 4460ede3a7
commit d6c2550579
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.beads/beads.jsonl
View File

@@ -20,7 +20,7 @@
{"id":"bd-1b0a","content_hash":"3a3bbc7c9f5c587da3932adf81ecbb23a140e8cd4c223d3628cb22844a94030e","title":"Add transaction helper to replace manual COMMIT/ROLLBACK","description":"Create tx.go with withTx helper that handles transaction lifecycle. Replace manual transaction blocks in create/insert/update paths.","notes":"Refactoring complete:\n- Created withTx() helper in util.go\n- Added ExecInTransaction() as deprecated wrapper for backward compatibility\n- Refactored all manual transaction blocks to use withTx():\n - events.go: AddComment\n - dirty.go: MarkIssuesDirty, ClearDirtyIssuesByID\n - labels.go: executeLabelOperation\n - dependencies.go: AddDependency, RemoveDependency\n - compact.go: ApplyCompaction\n- All tests pass successfully","status":"closed","priority":1,"issue_type":"task","created_at":"2025-11-01T11:41:14.823323-07:00","updated_at":"2025-11-02T12:41:45.827688-08:00","closed_at":"2025-11-02T12:41:45.827688-08:00","source_repo":"."}
{"id":"bd-1c63eb84","content_hash":"ffb879c48e5d99f98d0cf6efcb0e7c6940820e8936eabea009c8d365af5f9524","title":"Investigate jujutsu integration for beads","description":"Research and document how beads could integrate with jujutsu (jj), the next-generation VCS. Key areas to explore:\n- How jj's operation model differs from git (immutable operations, working-copy-as-commit)\n- JSONL sync strategy with jj's conflict resolution model\n- Daemon compatibility with jj's more frequent rewrites\n- Whether auto-import/export needs changes for jj workflows\n- Example configurations and documentation updates needed","status":"closed","priority":3,"issue_type":"task","created_at":"2025-10-23T09:23:23.582009-07:00","updated_at":"2025-11-05T14:32:21.840865-08:00","closed_at":"2025-11-05T14:26:17.967073-08:00","source_repo":"."}
{"id":"bd-1c77","content_hash":"e64ed75c5734be1fcd10a824217acb3061aefc510f6a4da1f7c95a42ad8356c8","title":"Implement filesystem shims for WASM","description":"WASM needs JS shims for filesystem access. Child of epic bd-44d0.\n\n## Tasks\n- [ ] Implement file read/write shims\n- [ ] Map WASM syscalls to Node.js fs API\n- [ ] Handle .beads/ directory discovery\n- [ ] Test with real JSONL files\n- [ ] Support both absolute and relative paths\n\n## Technical Notes\n- Use Node.js fs module via syscall/js\n- Consider MEMFS for in-memory option","status":"closed","priority":0,"issue_type":"task","created_at":"2025-11-02T18:33:31.280464-08:00","updated_at":"2025-11-05T00:37:17.33945-08:00","closed_at":"2025-11-05T00:37:17.33945-08:00","source_repo":".","dependencies":[{"issue_id":"bd-1c77","depends_on_id":"bd-197b","type":"blocks","created_at":"2025-11-02T18:33:31.281134-08:00","created_by":"daemon"}]}
{"id":"bd-1ezg","content_hash":"8bf9a1125bdad8447e4dd8159d4ee6473f76b271585fc1971f9c9455484261dd","title":"Investigate bd export/import sync issue - database and JSONL out of sync","description":"Observed in VC repo: database has 1137 issues but beads.jsonl only has 309. Running 'bd export -o .beads/issues.jsonl' doesn't update the file. Running 'bd import' hangs indefinitely.\n\nReproduction context:\n- VC repo: 1137 issues in DB, 309 in JSONL\n- Created 4 new issues with bd create\n- bd export didn't write them to JSONL\n- bd import hung (possibly daemon lock conflict?)\n\nNeed to investigate:\n1. Why export doesn't update JSONL when DB has more issues\n2. Why import hangs\n3. Daemon lock interaction with export/import\n4. File path handling (issues.jsonl vs beads.jsonl)","design":"Check export logic for silent failures, file locking, path resolution. Check import for blocking operations, daemon conflicts.","acceptance_criteria":"- Root cause of export not updating JSONL identified\n- Root cause of import hanging identified \n- Fix implemented and verified\n- Test coverage for sync scenarios\n- Documentation updated if needed","status":"open","priority":1,"issue_type":"bug","created_at":"2025-11-06T19:00:55.78797-08:00","updated_at":"2025-11-06T19:00:55.78797-08:00","source_repo":"."}
{"id":"bd-1ezg","content_hash":"c16736fbe9eb50c009d2dbe0b9095d6503820263a9d0f14f85bb83f211b10356","title":"Investigate bd export/import sync issue - database and JSONL out of sync","description":"Observed in VC repo: database has 1137 issues but beads.jsonl only has 309. Running 'bd export -o .beads/issues.jsonl' doesn't update the file. Running 'bd import' hangs indefinitely.\n\nReproduction context:\n- VC repo: 1137 issues in DB, 309 in JSONL\n- Created 4 new issues with bd create\n- bd export didn't write them to JSONL\n- bd import hung (possibly daemon lock conflict?)\n\nNeed to investigate:\n1. Why export doesn't update JSONL when DB has more issues\n2. Why import hangs\n3. Daemon lock interaction with export/import\n4. File path handling (issues.jsonl vs beads.jsonl)","design":"Check export logic for silent failures, file locking, path resolution. Check import for blocking operations, daemon conflicts.","acceptance_criteria":"- Root cause of export not updating JSONL identified\n- Root cause of import hanging identified \n- Fix implemented and verified\n- Test coverage for sync scenarios\n- Documentation updated if needed","notes":"## Root Cause Analysis\n\nThe issue was NOT about file path handling or export failing to update JSONL. The actual problem was:\n\n**Import/Export hanging when daemon is running** due to SQLite lock contention:\n\n1. When daemon is connected, `PersistentPreRun` in main.go returns early without initializing the `store` variable\n2. Import/Export commands then tried to open the database directly with `sqlite.New(dbPath)` \n3. This blocked waiting for the database lock that the daemon already holds → **HANGS INDEFINITELY**\n\n## Solution Implemented\n\nModified both import.go and export.go to:\n1. Detect when `daemonClient` is connected\n2. Explicitly close the daemon connection before opening direct SQLite access\n3. Added debug logging to help diagnose similar issues\n\nThis ensures import/export commands always run in direct mode, avoiding lock contention.\n\n## File Path Handling\n\nThe file path confusion (issues.jsonl vs beads.jsonl) was a red herring. The code uses `filepath.Glob(\"*.jsonl\")` which correctly finds ANY `.jsonl` file in `.beads/` directory, so both filenames work.","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-11-06T19:00:55.78797-08:00","updated_at":"2025-11-06T19:07:15.077983-08:00","closed_at":"2025-11-06T19:07:15.077983-08:00","source_repo":"."}
{"id":"bd-1f28","content_hash":"850a14659d6747dc114b7da94e55c3f9594995cabc31c3c85e3089fbd5f61712","title":"Extract migration functions to migrations.go","description":"Move migrateDirtyIssuesTable, migrateExternalRefColumn, migrateCompositeIndexes, migrateClosedAtConstraint, migrateCompactionColumns, migrateSnapshotsTable, migrateCompactionConfig, migrateCompactedAtCommitColumn, migrateExportHashesTable, migrateContentHashColumn to a separate migrations.go file","status":"closed","priority":1,"issue_type":"task","created_at":"2025-11-01T19:28:54.892045-07:00","updated_at":"2025-11-01T20:00:09.038174-07:00","closed_at":"2025-11-01T20:00:09.038178-07:00","source_repo":"."}
{"id":"bd-1f64","content_hash":"80f404d7c0f06c7f4bc6d52ac02c1a002a95ac7cb60c6485b2ceed5e013dad75","title":"Add comprehensive tests for config.yaml issue-prefix migration","description":"The GH #209 config.yaml migration lacks test coverage:\n\nMissing tests:\n- config.SetIssuePrefix() edge cases (empty file, comments, malformed YAML)\n- config.GetIssuePrefix() with various config states\n- MigrateConfigToYAML() automatic migration logic\n- bd init writing to config.yaml instead of DB\n- bd migrate DB→config.yaml migration path\n\nTest scenarios needed:\n1. SetIssuePrefix with empty config.yaml\n2. SetIssuePrefix with existing config.yaml (preserves other settings)\n3. SetIssuePrefix with commented issue-prefix line\n4. SetIssuePrefix atomic write (temp file cleanup)\n5. GetIssuePrefix fallback behavior\n6. MigrateConfigToYAML when config.yaml missing prefix but DB has it\n7. MigrateConfigToYAML when both missing (detect from issues)\n8. MigrateConfigToYAML when config.yaml already has prefix (no-op)\n9. Integration test: fresh bd init writes to config.yaml only\n10. Integration test: upgrade from v0.21 DB migrates to config.yaml\n\nPriority 1 because this is a user-facing migration affecting all users upgrading to v0.22.","status":"closed","priority":1,"issue_type":"task","created_at":"2025-11-03T22:33:43.08753-08:00","updated_at":"2025-11-03T22:46:16.306565-08:00","closed_at":"2025-11-03T22:46:16.306565-08:00","source_repo":"."}
{"id":"bd-1fkr","content_hash":"1e894c392d28824187ab0a19bc86b3e9a8b443dd45cccc1f181942b71fc8af24","title":"bd-hv01: Storage backend extensibility broken by type assertion","description":"Problem: deletion_tracking.go:69-82 uses type assertion for DeleteIssue which breaks if someone adds a new storage backend.\n\nFix: Check capability before starting merge or add DeleteIssue to Storage interface.\n\nFiles: cmd/bd/deletion_tracking.go:69-82, internal/storage/storage.go","status":"open","priority":2,"issue_type":"task","created_at":"2025-11-06T18:16:20.770662-08:00","updated_at":"2025-11-06T18:16:20.770662-08:00","source_repo":".","dependencies":[{"issue_id":"bd-1fkr","depends_on_id":"bd-rbxi","type":"parent-child","created_at":"2025-11-06T18:19:14.925961-08:00","created_by":"daemon"}]}