[PR #5003] [CLOSED] fix(plist): ignore processing instructions between values #6723

Closed
opened 2026-11-01 21:42:34 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5003
Author: @therahimulislam
Created: 10/18/2026
Status: ❌ Closed

Base: main ← Head: therahimulislam-issue-contribution


📝 Commits (1)

  • 35173e9 fix(plist): ignore processing instructions between values

📊 Changes

2 files changed (+10 additions, -1 deletions)

View changed files

📝 src/domain/propertyListXml.test.ts (+8 -0)
📝 src/domain/propertyListXml.ts (+2 -1)

📄 Description

Summary

Fixes #4964.

The shared XML property-list decoder now ignores processing-instruction nodes between plist, array, and dictionary members instead of treating them as invalid plist values.

Problem and expected behavior

A plist containing processing instructions between members failed with an Invalid PLIST tag error. Processing instructions are metadata nodes and should be ignored while decoding plist members, consistent with existing handling for text, CDATA, and comments.

Change and scope

Updated the shared members() decoder boundary to skip PROCESSING_INSTRUCTION_NODE values.

Added regression coverage for processing instructions at the plist root, between array values, and between dictionary keys and values.

Follow the contribution scope.

  • Semantic owner and earliest changed stage: src/domain/propertyListXml.ts, XML plist member decoding.
  • Contribution scope fit and linked maintainer decision: Ordinary fix within an existing decoder boundary; maintainer scope decision not applicable.
  • CLI and MCP/tool-catalog contract: None.
  • Provider, bridge, target-format, or platform compatibility: Shared XML property-list behavior; no provider changes.
  • Evidence, artifact, provenance, or reconstruction contract: None.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): Not applicable.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: None.

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: src/domain/propertyListXml.test.ts adds root, array, and dictionary processing-instruction cases.
  • Base reproduction or other evidence: The shared decoder previously yielded processing-instruction nodes to decode(), which produced Invalid PLIST tag; the regression now passes with the fix.
  • User-visible CLI/MCP output (if applicable): Not applicable.
  • Remaining proof gaps: Real production plist prevalence and native-provider cross-platform behavior were not measured.

Validation performed

  • npm run test:local -- src/domain/propertyListXml.test.ts src/application/AppBundleExecutable.test.ts - 35 tests passed.
  • git diff --check - passed.
  • npm run check:fast - passed during push precheck (typecheck and lint).

Compatibility, safety, and release

  • Breaking changes or migration steps: None.
  • Real Hopper/Ghidra, browser, or OS coverage: Not applicable.
  • Package or release metadata impact: None.
  • Security, privacy, process, or containment review: No security or process behavior changes.

Author readiness

Human owner: @therahimulislam

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/5003 **Author:** [@therahimulislam](https://github.com/therahimulislam) **Created:** 10/18/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `therahimulislam-issue-contribution` --- ### 📝 Commits (1) - [`35173e9`](https://github.com/morluto/rea/commit/35173e9ebd8df6e28972cd22806e74a96047a01a) fix(plist): ignore processing instructions between values ### 📊 Changes **2 files changed** (+10 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/domain/propertyListXml.test.ts` (+8 -0) 📝 `src/domain/propertyListXml.ts` (+2 -1) </details> ### 📄 Description ## Summary Fixes #4964. The shared XML property-list decoder now ignores processing-instruction nodes between plist, array, and dictionary members instead of treating them as invalid plist values. ## Problem and expected behavior A plist containing processing instructions between members failed with an `Invalid PLIST tag` error. Processing instructions are metadata nodes and should be ignored while decoding plist members, consistent with existing handling for text, CDATA, and comments. ## Change and scope Updated the shared `members()` decoder boundary to skip `PROCESSING_INSTRUCTION_NODE` values. Added regression coverage for processing instructions at the plist root, between array values, and between dictionary keys and values. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). - Semantic owner and earliest changed stage: `src/domain/propertyListXml.ts`, XML plist member decoding. - Contribution scope fit and linked maintainer decision: Ordinary fix within an existing decoder boundary; maintainer scope decision not applicable. - CLI and MCP/tool-catalog contract: None. - Provider, bridge, target-format, or platform compatibility: Shared XML property-list behavior; no provider changes. - Evidence, artifact, provenance, or reconstruction contract: None. - Target selection, authority, upstream behavior, and cleanup details (if applicable): Not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: None. Expected effects: - [x] Read existing files or captured data. - [ ] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `src/domain/propertyListXml.test.ts` adds root, array, and dictionary processing-instruction cases. - Base reproduction or other evidence: The shared decoder previously yielded processing-instruction nodes to `decode()`, which produced `Invalid PLIST tag`; the regression now passes with the fix. - User-visible CLI/MCP output (if applicable): Not applicable. - Remaining proof gaps: Real production plist prevalence and native-provider cross-platform behavior were not measured. ## Validation performed - `npm run test:local -- src/domain/propertyListXml.test.ts src/application/AppBundleExecutable.test.ts` - 35 tests passed. - `git diff --check` - passed. - `npm run check:fast` - passed during push precheck (typecheck and lint). ## Compatibility, safety, and release - Breaking changes or migration steps: None. - Real Hopper/Ghidra, browser, or OS coverage: Not applicable. - Package or release metadata impact: None. - Security, privacy, process, or containment review: No security or process behavior changes. ## Author readiness Human owner: @therahimulislam - [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [ ] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:42:34 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#6723
No description provided.