We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Looks like there are people/projects who are relying on our mainnet dumps. They are raising issues like: https://o1-labs.slack.com/archives/C04E2V028UQ/p1713279647718199
Proposal is to introduce logic to our mainnet name to remove issue when there is a random suffix for hours and minutes like here: https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-13_0001.sql.tar.gz https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-12_0003.sql.tar.gz https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-04_0001.sql.tar.gz
We could always set suffix to 0000 when suffix is in 0001-0005 ? but of course we need to be aware that anyone can schedule another mainnet dump export like at 1000 or alter and we don't want it to be set to 000. so we should preserve the suffix but adjust it when delay from midnight is "small". Another idea would be to name dumps ilke: a) https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-04.sql.tar.gz next export in the same day will get hhmm suffix: https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-04_1200.sql.tar.gz
Alternatively if there is no dumps at particular day we can name it "daily" b) https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-daily-dump-2024-04-04.sql.tar.gz and then next one the same like above https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-04_1200.sql.tar.gz
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Looks like there are people/projects who are relying on our mainnet dumps. They are raising issues like:
https://o1-labs.slack.com/archives/C04E2V028UQ/p1713279647718199
Proposal is to introduce logic to our mainnet name to remove issue when there is a random suffix for hours and minutes like here:
https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-13_0001.sql.tar.gz
https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-12_0003.sql.tar.gz
https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-04_0001.sql.tar.gz
We could always set suffix to 0000 when suffix is in 0001-0005 ? but of course we need to be aware that anyone can schedule another mainnet dump export like at 1000 or alter and we don't want it to be set to 000. so we should preserve the suffix but adjust it when delay from midnight is "small". Another idea would be to name dumps ilke:
a)
https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-04.sql.tar.gz
next export in the same day will get hhmm suffix:
https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-04_1200.sql.tar.gz
Alternatively if there is no dumps at particular day we can name it "daily"
b)
https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-daily-dump-2024-04-04.sql.tar.gz
and then next one the same like above
https://storage.googleapis.com/mina-archive-dumps/mainnet-archive-dump-2024-04-04_1200.sql.tar.gz
The text was updated successfully, but these errors were encountered: