Conversation
Contributor
Author
|
Consolidated into #426 at the operator’s request. The metadata-only R2 restore, exact build:deploy gate, and production browser correction now live there. |
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.
Run 35506595873 proved the R2 volume-package path is reached correctly, then failed because three source-only catalogue contexts were treated as installed lens packages. galaxy-clusters, local-group, and nearby-universe intentionally have no prepared presentation file. This keeps installed R2 metadata authoritative for the 12 lens/image-layer packages, while compiling the three source-only catalogue records in memory without publishing or pinning nonexistent prepared metadata.
Validation: