Repository navigation
[OMEGA-492] Redo an interrupted memory copy when a container holds omega-memory #388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
TossSky
wants to merge
11
commits into
singnet:patch-to-v0.1.20
Choose a base branch
from
sassless:OMEGA-492-volume-in-use
base: patch-to-v0.1.20
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+294
−19
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
679809b
[OMEGA-492] Cover a repeated copy while a container holds omega-memory
TossSky 1d72fea
[OMEGA-492] Remove the omega container before redoing an interrupted …
TossSky f7f7e5c
[OMEGA-492] Cover leftover copy containers and a memory import after …
TossSky de28d8a
[OMEGA-492] Clear leftover copy containers and let a memory import re…
TossSky b7adfab
[OMEGA-492] Cover leftover containers on other volumes and a failed i…
TossSky 922ba26
[OMEGA-492] Remove only leftover copy containers that hold the partly…
TossSky 0a2da89
[OMEGA-492] Cover keeping omega while another container holds the volume
TossSky b6de939
[OMEGA-492] Check other holders of the partly copied volume before re…
TossSky e201b5f
[OMEGA-492] Trigger CI
TossSky d4f1da4
[OMEGA-492] Cover imported memory over an interrupted copy and unread…
TossSky 7263f93
[OMEGA-492] Keep memory that is not a partial copy and stop an import…
TossSky File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we check whether memory was successfully imported after the interrupted migration, or preserve the existing volume before deleting it? A stale .migration-started marker could otherwise cause a normal start to discard valid imported memory. I see this is documented under Known limits - is this behavior intentional within the scope of OMEGA-492, or should we handle it here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in 7263f93. The copy goes entry by entry, so a partial copy leaves
history.mettaempty, missing, or a prefix of the old file. Before redoing the copy,startcompares the two files. Ifomega-memoryholds anything else, such as an imported archive,startstops, leaves the volume and theomegacontainer as they are, and prints two commands: one clears the marker and keeps the memory, the other removesomega-memoryso the copy runs again.On
singularitynet/omega:v0.1.20both commands work, and a partly copied history is still copied again. The new cases are in d4f1da4.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that covers the case where history has changed. What about --only-vector, where imported vector memory may change while history.metta stays the same?