[BUG] Error during sync

[phernandez]

Bug Description

I’m imported my chatgpt conversation into BM and I was working on a project with Claude Code, now in pause because I reached my limit :-)
After the import I got an error in sync.
I have also this strange behavior that I posted in discord, checking version or project info I receive a v0 version… happened another time in the past and I think after un upgrade was solved.

Here the mcp-log and sync log. I zipped all the logs I have created these days….

Additional Context

reply to user:

It's possible that you have two different versions of basic-memory running. Python with uv is a little bit whacky. If you are using uvx basic-memoryor uv tool run basic-memory it will create a standalone environment for the package and run it from there. So, this may be different than if you just run basic-memory from the command line (installed in your global environment).

basic-memory-mcp.2025-04-29_10-19-49_239025.log
basic-memory-mcp.2025-06-29_10-16-26_854011.log
basic-memory-mcp.2025-06-29_10-20-36_285767.log
basic-memory-mcp.log
basic-memory-sync.log

[phernandez]

@claude please investigate the logs, and errors reported by the user. Look at our other issues and see if you think this might be related to other db conflicts or sync issue. Keep in mind the "v0" version indicates the user had two versions of basic-memory running, one via uv, another in the system wide packages.

[claude]

Claude finished @phernandez's task —— View job

---

Investigating sync errors and version conflicts

I've analyzed the logs and investigated this sync error issue, particularly focusing on the version conflict (v0 showing instead of actual version) and its relationship to sync failures.

Todo List:

• Download and analyze all attached log files
• Search for similar database/sync conflict issues
• Investigate version conflict patterns (v0 issue)
• Examine import-related sync failures in codebase
• Provide detailed findings and recommendations

Analysis Summary

Version "v0" Issue - Root Cause Identified

The "v0" version issue is caused by confusion between two different version identifiers in the codebase:

• Package Version: __version__ = "0.14.1" (in __init__.py:4)
• API Version: __api_version__ = "v0" (in __init__.py:7)

The system status correctly uses basic_memory.__version__ (project_service.py:690), so the v0 display suggests either:

1. Installation conflict: Multiple versions running simultaneously (uv vs system-wide as mentioned)
2. API version confusion: Some code path incorrectly displaying API version instead of package version
3. Dynamic versioning issue: Problems with uv-dynamic-versioning not detecting the correct version

Sync Failure Patterns After ChatGPT Import

Based on codebase analysis, several factors could cause sync failures after ChatGPT import:

1. Database Constraint Violations

• The sync service has robust handling for IntegrityError exceptions (sync_service.py:380-403)
• Race conditions during concurrent sync operations can cause UNIQUE constraint failures
• ChatGPT imports create many files rapidly, potentially triggering database conflicts

2. Import-Specific Issues

• Permalink conflicts: Multiple conversations with similar titles could generate conflicting permalinks (chatgpt_importer.py:44-46)
• Large transaction overhead: Bulk imports can overwhelm SQLite database locks
• UTF-8 encoding problems: Fixed in previous versions but could resurface with malformed chat exports

3. File System Conflicts

• Files created by import might conflict with existing sync operations
• Temporary file issues during concurrent operations
• Permission problems if import and sync run under different user contexts

Historical Issues and Fixes

The codebase shows several previously resolved issues similar to this one:

• [BUG] UNIQUE constraint failed: entity.permalink #139: "UNIQUE constraint failed: entity.permalink" - Fixed in v0.13.6 with UPSERT strategy
• fix: [BUG] Some notes never exit "modified" status #77: "Some notes never exit 'modified' status" - Fixed in v0.12.0
• [BUG] Error syncing .tmp files #30: Temporary files causing sync issues - Fixed in v0.10.0
• [BUG] UTF8 Not supported #29: UTF-8 encoding problems - Fixed in v0.10.0

Recommended Troubleshooting Steps

For Version Issue:

1. Check installation conflicts:

   which basic-memory
   uv tool list | grep basic-memory
   pip list | grep basic-memory

2. Force reinstall with single method:

   uv tool uninstall basic-memory
   uv tool install basic-memory

For Sync Issues:

1. Check sync status: basic-memory status
2. Reset database if corrupted: basic-memory db reset
3. Check file permissions in the knowledge directory
4. Sync manually without watch: basic-memory sync (not --watch)
5. Check for large files or encoding issues in imported ChatGPT files

Log Analysis Request

I don't have bash permissions to download the attached log files, but based on the patterns identified:

• Look for IntegrityError or UNIQUE constraint failed messages
• Check for file permission errors during sync

Most Likely Cause: The combination of ChatGPT import creating many files rapidly + concurrent sync operations is triggering database constraint violations that the error handling isn't fully resolving.

---

[phernandez]

I believe the issue with the v0 version was due to different versions of basic-memory running in the system path vs uv virtual env environment.

We will tackle the unique constraint issues in v0.14.3.