fix: handle UTF-16LE-encoded manifests on Windows#1021
Merged
tonyaiuto merged 1 commit intobazelbuild:mainfrom Feb 19, 2026
Merged
Conversation
24b2ac0 to
a79b1ee
Compare
Prior to Bazel 8, manifest files containing non-ASCII characters were written with UTF-16LE encoding instead of UTF-8 on Windows: - bazelbuild/bazel#24231 - bazelbuild/bazel#24350 - bazelbuild/bazel#24403 This led to disable failing tests in CI: `//tests/zip:unicode_test`: ``` File "pkg\private\manifest.py", line 59, in read_entries_from raw_entries = json.loads(fh.read()) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xbb in position 338: invalid start byte ``` `//tests/mappings:utf8_manifest_test`: ``` File "tests\mappings\manifest_test_lib.py", line 39, in assertManifestsMatch got = json.loads(g_fp.read()) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xbb in position 354: invalid start byte ``` Since the manifest is plain JSON, the fix simply consists in detecting whether the second byte is `0`, where the default UTF-8 decoding would fail, in which case we assume the file is UTF-16LE-encoded. The code is slightly reorganized to factor out the encoding selection. This allows to enable `//tests/mappings:utf8_manifest_test` and `//tests/zip:unicode_test` tests in Windows CI.
a79b1ee to
35bf0df
Compare
tonyaiuto
approved these changes
Feb 19, 2026
tonyaiuto
approved these changes
Feb 19, 2026
Collaborator
|
LGTM. I didn't have a chance to look until now. |
rdesgroppes
added a commit
to DataDog/datadog-agent
that referenced
this pull request
Feb 21, 2026
### What does this PR do? Bump `rules_pkg` to Feb 21 `main, picking up: - bazelbuild/rules_pkg#1021 - bazelbuild/rules_pkg#1024 - bazelbuild/rules_pkg#1025 ### Motivation The missing exit code propagation fixed by bazelbuild/rules_pkg#1024 is the main driver of this change because RPM build errors would go unnoticed.
rdesgroppes
added a commit
to DataDog/datadog-agent
that referenced
this pull request
Mar 20, 2026
### What does this PR do? Bump `rules_pkg` to Feb 21 `main, picking up: - bazelbuild/rules_pkg#1021 - bazelbuild/rules_pkg#1024 - bazelbuild/rules_pkg#1025 ### Motivation The missing exit code propagation fixed by bazelbuild/rules_pkg#1024 is the main driver of this change because RPM build errors would go unnoticed.
gh-worker-dd-mergequeue-cf854d bot
pushed a commit
to DataDog/datadog-agent
that referenced
this pull request
Mar 20, 2026
### What does this PR do? Bump `rules_pkg` to current `main`. ### Motivation Pick up: - bazelbuild/rules_pkg#1021: a contribution of ours - bazelbuild/rules_pkg#1024: RPM build errors would go unnoticed without it - bazelbuild/rules_pkg#1035: affects reproducibiliy of builds - bazelbuild/rules_pkg#1044 - bazelbuild/rules_pkg#1046: another contribution of ours (@chouquette) - bazelbuild/rules_pkg#1047: we might need this feature Co-authored-by: regis.desgroppes <regis.desgroppes@datadoghq.com>
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
3 participants
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.
Prior to Bazel 8, manifest files containing non-ASCII characters were written with UTF-16LE encoding instead of UTF-8 on Windows:
This led to disable failing tests in CI:
//tests/zip:unicode_test://tests/mappings:utf8_manifest_test:Since the manifest is plain JSON, the fix simply consists in detecting whether the second byte is
0, where the default UTF-8 decoding would fail, in which case we assume the file is UTF-16LE-encoded.The code is slightly reorganized to factor out the encoding selection.
This allows to enable
//tests/mappings:utf8_manifest_testand//tests/zip:unicode_testtests in Windows CI.