-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
chore: add old eszip migration test #512
Merged
nyannyacha
merged 10 commits into
supabase:main
from
nyannyacha:chore-integration-test-old-eszips-1-x
Mar 18, 2025
Merged
chore: add old eszip migration test #512
nyannyacha
merged 10 commits into
supabase:main
from
nyannyacha:chore-integration-test-old-eszips-1-x
Mar 18, 2025
Conversation
This file contains 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
laktek
approved these changes
Mar 13, 2025
laktek
approved these changes
Mar 18, 2025
nyannyacha
added a commit
that referenced
this pull request
Mar 19, 2025
* chore: add `get_eszip_testdata.sh` * stamp: polishing * chore(base): add a dev dependency * chore: update `Cargo.lock` * chore: add old eszip migration test * fix: introduce eszip migrate options * fix: allow specifying context regardless worker mode * chore: update `scripts/get_eszip_testdata.sh` * chore(ci): add a step that brings test eszip binaries * fix(cli): reintroduce `--import-map` flag of the bundle command * chore(ci): using checkout action instead of s3 to get test binaries * stamp: token * stamp: test * stamp: polishing * stamp: debug * stamp: decomp * stamp: test * stamp: polishing * chore: add old eszip migration test (#512) * chore(base): add a dependency * chore(base): add `.gitignore` * chore: add scripts * chore(ci): add a step that brings test eszip binaries * chore(base): update `.gitignore` * chore(base): add old eszip migration test * chore(base): add snapshots for old eszip migration tests * stamp(ci): change bucket name * stamp: update snapshots * stamp: polishing * stamp: update snapshots
🎉 This PR is included in version 1.67.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
nyannyacha
added a commit
that referenced
this pull request
Mar 24, 2025
* chore: add old eszip migration test (#512) * chore(base): add a dependency * chore(base): add `.gitignore` * chore: add scripts * chore(ci): add a step that brings test eszip binaries * chore(base): update `.gitignore` * chore(base): add old eszip migration test * chore(base): add snapshots for old eszip migration tests * stamp(ci): change bucket name * stamp: update snapshots * stamp: polishing * fix(base): triggering `beforeunload` event may cause `Uncaught null` (#520) * fix(base): triggering `beforeunload` event may cause `Uncaught null` * chore: add an integration test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
Chore
Description
This test takes the eszip binary remotely and creates a snapshot.
Snapshots are used to check whether consistency is guaranteed when there are changes to the way that data is stored in eszip in the future.
Below is a list of eszips that rendered errors not related to migration: