[GH-ISSUE #177] application: drop empty env keys when parsing process environment #124

Closed
opened 2026-10-15 18:21:21 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @morluto on GitHub (Jul 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/177

Problem

Environment parsing accepts entries without a variable name.

Evidence

  • src/application/ProcessOwnership.ts:47-51 filters only entry.includes("=") and then stores entry.slice(0, separator) as key.
  • Inputs like "=value" produce key "" instead of being discarded.

Impact

Empty-key entries are inserted into the ownership environment map and can incorrectly satisfy/interfere with process-token cleanup checks.

Ask

Reject entries where separator <= 0 so only named environment variables are retained.

Originally created by @morluto on GitHub (Jul 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/177 ### Problem Environment parsing accepts entries without a variable name. ### Evidence - `src/application/ProcessOwnership.ts:47-51` filters only `entry.includes("=")` and then stores `entry.slice(0, separator)` as key. - Inputs like `"=value"` produce key `""` instead of being discarded. ### Impact Empty-key entries are inserted into the ownership environment map and can incorrectly satisfy/interfere with process-token cleanup checks. ### Ask Reject entries where `separator <= 0` so only named environment variables are retained.
bsakaguchi 2026-10-15 18:21:21 +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#124
No description provided.