Retain Dhall schemas in server closure - #792
Merged
Merged
Conversation
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.
Publish job
6c1efe17-ed9a-470d-a329-68609ae598b6, reported in purescript/registry#565, failed while validating apurs.jsonmanifest becauseDHALL_TYPESpointed at a missing Nix-store path.The deployment generated an env file containing
DHALL_TYPES=/nix/store/...-source/types, but that env file did not retain the schema source as a Nix store reference. After garbage collection removed the source tree, the running server retained a dangling path andjson-to-dhallcould no longer readtypes/v1/Manifest.dhall.