Repository navigation
A held manifest's files stay with their keeper - #15
Merged
Merged
Conversation
A manifest node published every file its manifest covers, which is how a
web app's bundle ships. A held manifest (prov's held: {by, at}) covers
an archive kept on another machine: the Harris family's 80,857
photographs, 1.66 TB, behind a link on a NAS. Marking its node for an
audience made the publish plan read and weigh every one of them, which
ran a 2 GB NAS out of memory, and a publish would have uploaded them.
A held manifest now ships none of its files, and its collected copy
carries held but no rows, so the listing is empty rather than eighty
thousand links to nothing. A reader asks the keeper for a photograph.
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
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.
A manifest node published every file its manifest covers. That is right for a web app's bundle, and wrong for a held manifest (prov's
held: {by, at}), whose archive is kept on another machine.Found on the Harris family's photo library: 80,857 photos, 1.66 TB, behind a link on a NAS. With the album marked for the Harris Family space,
diaryx publish --dry-runread and weighed every photo, reached 753 MB, and was killed by the NAS's out-of-memory killer. A real publish would have tried to upload them.A held manifest now ships none of its files. Its collected copy carries
heldbut no rows, so the listing is empty rather than 80,000 links to nothing. Showing the photos from the keeper is later work (the reader shell asking it by hash).Test:
a_held_manifest_node_ships_none_of_its_files. Workspace tests pass, and clippy and fmt are clean. The lock takes prov main, which hasheld.