Skip to content

chore(release): 0.10.5 - #275

Closed
client-software-ci wants to merge 1 commit into
mainlinefrom
bump/0.10.5
Closed

chore(release): 0.10.5#275
client-software-ci wants to merge 1 commit into
mainlinefrom
bump/0.10.5

Conversation

@client-software-ci

Copy link
Copy Markdown
Collaborator

0.10.5 (2025-09-29)

Signed-off-by: client-software-ci <129794699+client-software-ci@users.noreply.github.com>
@client-software-ci
client-software-ci requested a review from a team as a code owner September 29, 2025 20:49
@sonarqubecloud

Copy link
Copy Markdown

@erico-aws

Copy link
Copy Markdown
Contributor

Empty change log. No release needed. Closing.

@erico-aws erico-aws closed this Sep 29, 2025
@erico-aws
erico-aws deleted the bump/0.10.5 branch September 29, 2025 20:51
mwiebe pushed a commit that referenced this pull request Aug 4, 2026
LoggingSubprocess created its Popen with encoding="utf-8" but no
errors= parameter, so decoding defaulted to strict. A single byte of
subprocess output that is not valid UTF-8 (for example a Windows DCC
application writing cp1252, such as Unreal Engine emitting the 0x97
em dash) raised UnicodeDecodeError inside the _enqueue_stdout reader
thread. The thread died silently, and all subsequent stdout from the
subprocess was lost, masking any later errors from the job.

Decode with errors="backslashreplace" so undecodable bytes are
escaped (e.g. b"\x97" -> "\\x97") instead of raising. This keeps the
reader thread alive while preserving the original byte values in the
logs, which helps identify the codepage the subprocess is emitting.
This ports the fix that openjd-adaptor-runtime-for-python applied to
its own LoggingSubprocess in PRs #275 and #277.

Regression tests cover: the reader thread surviving undecodable
bytes, escape formatting for single/consecutive/truncated invalid
sequences, valid multi-byte UTF-8 passing through unescaped, the
behavior under a non-default encoding, and the errors= kwarg on the
Popen construction shared by the sudo and Windows-as-user paths.
Every test was mutation-checked: removing the errors= parameter,
substituting replace/ignore handlers, and forcing an ASCII encoding
each fail at least one test.

Signed-off-by: David Leong <116610336+leongdl@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants