Skip to content
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

Remove duplicated example for archive migration #906

Merged

Conversation

dkijania
Copy link
Contributor

Final adjustments for docs

@dkijania dkijania requested a review from a team as a code owner April 17, 2024 11:45
Copy link

vercel bot commented Apr 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 30, 2024 5:57pm
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
07-oracles ⬜️ Ignored (Inspect) Visit Preview Apr 30, 2024 5:57pm

@@ -86,7 +86,7 @@ The recommended method is to perform migration on your own data to preserve the

The correct Devnet/Mainnet database state is crucial for a successful migration.

[Missing blocks](/berkeley-upgrade/mainnet-database-maintenance#missing-blocks) is one the most frequent issues when dealing with the Devnet/Mainnet archive. Although this step is optional, it is strongly recommended that you verify the archive condition before you start the migration process.
[Missing blocks](/berkeley-upgrade/mainnet-database-maintenance#missing-blocks) is one the most frequent issue when dealing with the Devnet/Mainnet archive. Although this step is optional, it is strongly recommended that you verify the archive condition before you start the migration process.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(i honestly don't know if this is called for or not but i just noticed that Missing could be both a verb and a noun here and that is confusing)

@@ -115,9 +115,15 @@ apt-get install --allow-downgrades -y "mina-archive-migration=$VERSION"
To get the Docker image:

```
docker pull gcr.io/o1labs-192920/mina-archive-migration:3.0.0-rc0
docker pull gcr.io/o1labs-192920/mina-archive-migration:3.0.0-rc0-{CODENAME}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's update this tag

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What you mean? should we stick to 3.0.0-rc0 ? i think we need to differentiate between codenames

Copy link
Contributor

@emberian emberian Apr 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think @amc-ie suggested 3.0.0-release-migration or similar, codename is fine

@@ -471,156 +477,7 @@ where:

### Example migration steps using Mina Foundation data for Devnet
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we confirm that Mina Foundation has custody over the URLs mentioned here?

@@ -686,6 +543,21 @@ It is worthwhile to perform these last steps as a dry run to make sure all goes

Tips to overcome known challenges.

#### Berkeley migration app is unstable
Copy link
Contributor

@deepthiskumar deepthiskumar Apr 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe specify the error message in the heading to be specific?

@amc-ie amc-ie requested review from emberian and removed request for emberian May 1, 2024 16:01
@dkijania dkijania merged commit d369c53 into major-upgrade May 1, 2024
3 of 4 checks passed
@dkijania dkijania deleted the remove_duplicated_exmple_in_archive_migration branch May 1, 2024 16:23
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.

8 participants