Skip to content

Comments

Do not compress recently added MIME types in Metadata#1126

Merged
ArneBab merged 1 commit intohyphanet:nextfrom
bertm:fix/uncompressed-new-mime-types
Feb 15, 2026
Merged

Do not compress recently added MIME types in Metadata#1126
ArneBab merged 1 commit intohyphanet:nextfrom
bertm:fix/uncompressed-new-mime-types

Conversation

@bertm
Copy link
Contributor

@bertm bertm commented Feb 15, 2026

Registering MIME types causes their values to be short-encoded in the Manifest of an insert. This causes a breaking change for these file types: their keys change, depending on whether the file was inserted before or after the newly introduced MIME type. This is not desired, CHK keys should be stable.

Prevent newly registered MIME types from getting encoded as short value (compressed) in the manifest to ensure insert key stability.

Registering MIME types causes their values to be short-encoded in the
Manifest of an insert. This causes a breaking change for these file
types: their keys change, depending on whether the file was inserted
before or after the newly introduced MIME type. This is not desired,
CHK keys should be stable.

Prevent newly registered MIME types from getting encoded as short value
(compressed) in the manifest to ensure insert key stability.
@bertm
Copy link
Contributor Author

bertm commented Feb 15, 2026

Together with #1125 this makes the regression test added in #1124 pass. There would be no need to revert #1115.

Although this works without #1123, that PR should still be merged as it ensures the correct number of bytes is skipped regardless of InputStream implementation.

@ArneBab ArneBab merged commit 23b0298 into hyphanet:next Feb 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants