Skip to content

[OMEGA-518] Upgrade import-kb to 0.2.5 to fix memory export filename collisions - #400

Open
Bereket-Eshete wants to merge 3 commits into
singnet:mainfrom
Bereket-Eshete:fix/memory-export-integration
Open

Bereket-Eshete wants to merge 3 commits into
singnet:mainfrom
Bereket-Eshete:fix/memory-export-integration

Conversation

@Bereket-Eshete

@Bereket-Eshete Bereket-Eshete commented Oct 19, 2026 •

Copy link
Copy Markdown

Description

This PR follows up on OMEGA-489, where the memory export filename fix was implemented in import-knowledge-package and released as import-kb 0.2.5.

Previously, exports within the same UTC second could generate identical filenames and fail with FileExistsError. The package fix preserves the UTC timestamp and adds an eight-character UUIDv4-derived suffix.

This follow-up:

  • Upgrades Omega’s dependency from import-kb 0.2.4 to 0.2.5.
  • Updates the README and memory-portability reference to document omega-memory-<UTC timestamp>-<ID>.tar.gz and use the returned filename when importing.

How Has This Been Tested?

  • Verified same-second exports produce distinct archives with correct checksums and successful history restoration using import-kb 0.2.5.
  • Confirmed archives from 0.2.4 remain importable.
  • Documentation shell syntax and whitespace checks passed.

Checklist

  • PR contains autogenerated code
  • Self-review completed
  • Test scenarios above are passed with the version of the code from PR

blackhammer116
blackhammer116 previously approved these changes Oct 19, 2026
Use the release that adds a UUIDv4-derived suffix to default memory export filenames.
Document the UUIDv4-derived ID and use the returned filename when importing archives.
@Bereket-Eshete
Bereket-Eshete force-pushed the fix/memory-export-integration branch from 927446f to 2ce7bf1 Compare October 19, 2026 13:14
Preserve the Docker volume transfer workflow from Omega/main alongside the import-kb 0.2.5 upgrade and timestamp-plus-ID archive naming.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants