You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(test, workflow-operator): close UTF-16 fixture - #8796
Drain the small UTF-16 fixture in finally so the lazy reader closes before file deletion. Keep the decoding assertions and exhausted-iterator check. This repairs one test; no production behavior changes.
On Windows: baseline 13 passed and one failed; patched 14 passed. A temporary wrong-encoding mutation still failed the decoding assertion. The scan suites passed 163 tests with one existing S3 fixture cancellation. Formatting and lint passed.
Localhost Chrome at 1707 by 979 also ran the unchanged UTF-16 reader and returned the three expected lines.
These local checks preceded the September 30 rebase onto upstream main 98d3d4b. These historical results do not include the review fixes below. The full operating-system matrix is not claimed.
Test-only change. This screenshot is a compatibility check, not a visual before and after.
Independent review follow-up — September 30
Rechecked fixture ownership and iterator exhaustion before deletion. The change only drains the three-line lazy fixture so its Windows file handle closes. No additional defect identified; no production change or fresh test run is claimed in this review. The existing screenshot remains explicitly a compatibility check.
Release-backport approval is still required. The earlier build jobs were cancelled; requesting a rerun was denied for lack of repository admin rights. Approval requirements and release labels were left intact.
Was this PR authored or co-authored using generative AI tooling?
Generated-by: OpenAI Codex, model gpt-6-astra. The authoring session records Codex version 0.148.0-alpha.15; later runtime versions were not recorded.
This fix: PR was checked against each actively-supported release branch. A release/* label nominates a backport target; the branch's release manager approving this PR is what sends the fix there. The required Backport Approvals check stays red until every label below is approved, so each manager either approves or removes their own label — which is why the labels left on a merged PR are exactly the branches it reached.
Release branch
Analysis
✅ release/v1.3
Already labeled — this fix is queued to backport here. @mengw15 decides: approving sends the fix here, removing this label declines it. The merge waits on one or the other.
✅ release/v1.2
Already labeled — this fix is queued to backport here. @xuang7 decides: approving sends the fix here, removing this label declines it. The merge waits on one or the other.
Compared against main 98d3d4b benchmarked on this same runner, so the delta is largely free of cross-runner hardware noise. The "7d avg" column still reflects the gh-pages dashboard. Treat <±5% as noise unless repeated.
carloea2
changed the title
fix(test, workflow-operator): close UTF-16 fixture [Social Sciences Domain Request]
fix(test, workflow-operator): close UTF-16 fixture
Oct 7, 2026
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
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.
What changes were proposed in this PR?
Drain the small UTF-16 fixture in finally so the lazy reader closes before file deletion. Keep the decoding assertions and exhausted-iterator check. This repairs one test; no production behavior changes.
Any related issues, documentation, discussions?
Closes #8795
How was this PR tested?
On Windows: baseline 13 passed and one failed; patched 14 passed. A temporary wrong-encoding mutation still failed the decoding assertion. The scan suites passed 163 tests with one existing S3 fixture cancellation. Formatting and lint passed.
Localhost Chrome at 1707 by 979 also ran the unchanged UTF-16 reader and returned the three expected lines.
These local checks preceded the September 30 rebase onto upstream main 98d3d4b. These historical results do not include the review fixes below. The full operating-system matrix is not claimed.
Test-only change. This screenshot is a compatibility check, not a visual before and after.
Independent review follow-up — September 30
Rechecked fixture ownership and iterator exhaustion before deletion. The change only drains the three-line lazy fixture so its Windows file handle closes. No additional defect identified; no production change or fresh test run is claimed in this review. The existing screenshot remains explicitly a compatibility check.
Release-backport approval is still required. The earlier build jobs were cancelled; requesting a rerun was denied for lack of repository admin rights. Approval requirements and release labels were left intact.
Was this PR authored or co-authored using generative AI tooling?
Generated-by: OpenAI Codex, model gpt-6-astra. The authoring session records Codex version 0.148.0-alpha.15; later runtime versions were not recorded.