-
Notifications
You must be signed in to change notification settings - Fork 210
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
Fix test suite in response to … #1275
Conversation
51d2acf
to
bef2777
Compare
What would be a good platform-independent way to ensure that we don't use the (semantic) cache when resolving imports?
We could probably reuse the code for the latter alternative for a mode that lets users check their hash-protected imports… |
@sjakobi: So I think the right solution in the long-term is a variation on integrity checks which don't α-normalize the protected import, but in the short term we could add a |
Such a flag would also be useful to check whether hash-protected imports have changed – otherwise there's no warning. |
When enabled, we handle protected imports as if the semantic cache was empty: * Protected imports are resolved again, downloaded or read from the filesystem as necessary. * Protected imports are β-normalized, not αβ-normalized. * Protected imports are checked against their SHA256 hashes, failing to resolve if they don't match. Context: #1275 (comment)
When enabled, we handle protected imports as if the semantic cache was empty: * Protected imports are resolved again, downloaded or read from the filesystem as necessary. * Protected imports are β-normalized, not αβ-normalized. * Protected imports are checked against their SHA256 hashes, failing to resolve if they don't match. Context: #1275 (comment)
0eee7fb
to
c60a583
Compare
c60a583
to
7494ae9
Compare
6cd1bcb
to
7cdb0ec
Compare
7cdb0ec
to
5a692a9
Compare
… in response to dhall-lang/dhall-lang#723.
5a692a9
to
d8149ca
Compare
dhall-lang/dhall-lang#723