Conversation
Contributor
Author
|
Usage is e.g. |
Contributor
Author
|
This can be tested before the clippy lints are fixed |
Also put back the cores/ endpoint for legacy ambient cores Such legacy cores probably can't safely be added using the new core table scheme, so we're kind of stuck with them for the existing gisst deploy
Contributor
Author
|
Bug: this should set the created_on fields for generated states, replays, saves, instances, environments appropriately |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
If you have a database with a bunch of states, saves, instances using old cores, you should run something like this for each old core to clone all the states, saves, instances with new environments referencing the new core.
This will clone every environment which used the old core name and version (this is important to note because e.g. ingest makes a new environment for each work; was that a good idea? IDK), and for each cloned environment it will clone all instances, states, saves, etc referring to the original.