morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #5204] [CLOSED] fix(android): select Windows JADX java.exe from PATH, not the working directory #6810

New issue
Closed
opened 2026-11-01 21:43:12 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:43:12 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5204
Author: @ranmori
Created: 10/19/2026
Status: ❌ Closed

Base: main ← Head: fix/jadx-windows-path-java

📝 Commits (2)

  • 0b92dc4 fix(android): select Windows JADX java.exe from PATH, not the working directory
  • 0c599b9 Merge branch 'main' into fix/jadx-windows-path-java

📊 Changes

2 files changed (+74 additions, -29 deletions)

View changed files

📝 src/android/JadxConfiguration.ts (+44 -28)
📝 tests/boundary/android/jadxConfiguration.test.ts (+30 -1)

📄 Description

Summary

Fixes #5096.

With JAVA_HOME absent, Windows JADX configuration searched the process working directory before the selected PATH. A stray java.exe there therefore won over the JDK the caller selected, even when that directory was not on PATH. This PR searches only the PATH entries, as docs/android-analysis.md already describes ("resolves java.exe on the selected Windows PATH").

The issue was source-only; this PR adds a native Windows reproduction of the bug and of the fix.

Problem and expected behaviora

Trigger: Windows x64, JAVA_HOME unset, a java.exe in the process working directory, and a different JDK selected through PATH.

  • Before: resolveJava iterated [process.cwd(), ...PATH entries] and returned the first readable java.exe, so the working-directory file was probed and used for the engine session.
  • A second route to the same result: an empty PATH entry, such as the trailing ; common in real Windows PATH values, resolved through resolve("", "java.exe") to the working directory as well.
  • After: only non-empty PATH entries are searched, in order. A caller who lists the working directory (for example .) still selects it, and an absolute JAVA_HOME still takes precedence.

Change and scope

  • The Windows PATH search moves out of resolveJava into an exported findWindowsPathJava(path, signal) in src/android/JadxConfiguration.ts. It drops the process.cwd() candidate and skips empty entries. Quote stripping, the readable/executable/regular-file checks, canonicalization, and the runtime_missing failure for an uninspectable candidate are unchanged.
  • resolveJava calls it and keeps its existing "Cannot find java.exe on the selected Windows PATH" failure when nothing is found.

Not included: the non-Windows path (java resolved by the spawn) and JAVA_HOME handling are untouched. There is no fallback to another PATH JDK when the first one later fails validation; the issue mentions that only as a consequence of the working-directory selection.

Contract and boundary impact

  • Semantic owner and earliest changed stage: src/android/JadxConfiguration.ts, Java selection during JADX configuration.
  • CLI and MCP/tool-catalog contract: none.
  • Provider, bridge, target-format, or platform compatibility: Windows x64 JADX only. Hosts that relied on a working-directory java.exe with no JAVA_HOME and no matching PATH entry now get the existing runtime_missing failure with its JAVA_HOME/PATH guidance.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Process execution, authorization, cleanup, or containment impact: the selected Java executable can only come from JAVA_HOME or a caller-listed PATH entry.
  • Generated metadata, package, or installation impact: none. The existing docs already describe the new behavior.

Evidence and regression coverage

  • Tests added: selects java.exe from the Windows PATH, not the working directory in tests/boundary/android/jadxConfiguration.test.ts. It runs on every platform, unlike the rest of that file, which skips on Windows. It changes into a temporary working directory containing java.exe, then checks that:
    • a PATH with leading and trailing empty entries selects the PATH JDK;
    • a quoted entry selects the PATH JDK;
    • a PATH of only a separator selects nothing;
    • a PATH listing . selects the working-directory file.
  • Base reproduction, executed on Windows 11 x64 (build 26200), Node 24.13.0, base ba866a26, with the published rea-agents@6.7.0 Windows native addon. I called resolveJadxConfigurationInputs from each build's compiled dist with REA_JADX_MCP_JAR set, JAVA_HOME unset, PATH=<scratch>\selected-jdk\bin;%SystemRoot%\System32;, and the working directory set to <scratch>\working:
    • main: selected = <scratch>\working\java.exe
    • this PR: selected = <scratch>\selected-jdk\bin\java.exe
  • Remaining proof gaps: the java.exe files were empty placeholders. Only configuration-input resolution was run; no JDK probe, engine JAR, APK or JADX session.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npx vitest run --project boundary tests/boundary/android/jadxConfiguration.test.ts: the new test passes on Windows (the other 16 skip on Windows by design).
  • npx vitest run tests/boundary/android <jadx process-boundary tests>: 38 passed, 133 skipped (POSIX-only), 2 failed. The 2 failures are in tests/boundary/process/jadxHashCleanup.test.ts, which does not use the changed module, and fail identically on unmodified main on this host.
  • npm run check:fast: typecheck and lint passed (also in the pre-push hook).
  • Real Windows before/after selection check described above.

Not run: npm run check, npm run check:pr, npm run verify:android, and any JADX engine or APK workflow.

Compatibility, safety, and release

  • Breaking changes or migration steps: none intended. A Windows setup that depended on an unlisted working-directory java.exe must now set JAVA_HOME or add that directory to PATH, which is what the docs already said.
  • Real Hopper/Ghidra, browser, or OS coverage: Windows 11 x64 only, configuration resolution only.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: removes an implicit executable search location; no new execution path.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • 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/5204 **Author:** [@ranmori](https://github.com/ranmori) **Created:** 10/19/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/jadx-windows-path-java` --- ### 📝 Commits (2) - [`0b92dc4`](https://github.com/morluto/rea/commit/0b92dc4133b4cbbb947b81a7b329d005f55c69c4) fix(android): select Windows JADX java.exe from PATH, not the working directory - [`0c599b9`](https://github.com/morluto/rea/commit/0c599b9bb5e3af0394b8817206f30af555742b86) Merge branch 'main' into fix/jadx-windows-path-java ### 📊 Changes **2 files changed** (+74 additions, -29 deletions) <details> <summary>View changed files</summary> 📝 `src/android/JadxConfiguration.ts` (+44 -28) 📝 `tests/boundary/android/jadxConfiguration.test.ts` (+30 -1) </details> ### 📄 Description ## Summary Fixes #5096. With `JAVA_HOME` absent, Windows JADX configuration searched the process working directory before the selected `PATH`. A stray `java.exe` there therefore won over the JDK the caller selected, even when that directory was not on `PATH`. This PR searches only the `PATH` entries, as [docs/android-analysis.md](https://github.com/morluto/rea/blob/main/docs/android-analysis.md) already describes ("resolves `java.exe` on the selected Windows `PATH`"). The issue was source-only; this PR adds a native Windows reproduction of the bug and of the fix. ## Problem and expected behaviora Trigger: Windows x64, `JAVA_HOME` unset, a `java.exe` in the process working directory, and a different JDK selected through `PATH`. - Before: `resolveJava` iterated `[process.cwd(), ...PATH entries]` and returned the first readable `java.exe`, so the working-directory file was probed and used for the engine session. - A second route to the same result: an empty `PATH` entry, such as the trailing `;` common in real Windows `PATH` values, resolved through `resolve("", "java.exe")` to the working directory as well. - After: only non-empty `PATH` entries are searched, in order. A caller who lists the working directory (for example `.`) still selects it, and an absolute `JAVA_HOME` still takes precedence. ## Change and scope - The Windows `PATH` search moves out of `resolveJava` into an exported `findWindowsPathJava(path, signal)` in `src/android/JadxConfiguration.ts`. It drops the `process.cwd()` candidate and skips empty entries. Quote stripping, the readable/executable/regular-file checks, canonicalization, and the `runtime_missing` failure for an uninspectable candidate are unchanged. - `resolveJava` calls it and keeps its existing "Cannot find java.exe on the selected Windows PATH" failure when nothing is found. Not included: the non-Windows path (`java` resolved by the spawn) and `JAVA_HOME` handling are untouched. There is no fallback to another `PATH` JDK when the first one later fails validation; the issue mentions that only as a consequence of the working-directory selection. ## Contract and boundary impact - Semantic owner and earliest changed stage: `src/android/JadxConfiguration.ts`, Java selection during JADX configuration. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: Windows x64 JADX only. Hosts that relied on a working-directory `java.exe` with no `JAVA_HOME` and no matching `PATH` entry now get the existing `runtime_missing` failure with its `JAVA_HOME`/`PATH` guidance. - Evidence, artifact, provenance, or reconstruction contract: none. - Process execution, authorization, cleanup, or containment impact: the selected Java executable can only come from `JAVA_HOME` or a caller-listed `PATH` entry. - Generated metadata, package, or installation impact: none. The existing docs already describe the new behavior. ## Evidence and regression coverage - Tests added: `selects java.exe from the Windows PATH, not the working directory` in `tests/boundary/android/jadxConfiguration.test.ts`. It runs on every platform, unlike the rest of that file, which skips on Windows. It changes into a temporary working directory containing `java.exe`, then checks that: - a `PATH` with leading and trailing empty entries selects the `PATH` JDK; - a quoted entry selects the `PATH` JDK; - a `PATH` of only a separator selects nothing; - a `PATH` listing `.` selects the working-directory file. - Base reproduction, executed on Windows 11 x64 (build 26200), Node 24.13.0, base `ba866a26`, with the published `rea-agents@6.7.0` Windows native addon. I called `resolveJadxConfigurationInputs` from each build's compiled `dist` with `REA_JADX_MCP_JAR` set, `JAVA_HOME` unset, `PATH=<scratch>\selected-jdk\bin;%SystemRoot%\System32;`, and the working directory set to `<scratch>\working`: - main: `selected` = `<scratch>\working\java.exe` - this PR: `selected` = `<scratch>\selected-jdk\bin\java.exe` - Remaining proof gaps: the `java.exe` files were empty placeholders. Only configuration-input resolution was run; no JDK probe, engine JAR, APK or JADX session. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npx vitest run --project boundary tests/boundary/android/jadxConfiguration.test.ts`: the new test passes on Windows (the other 16 skip on Windows by design). - `npx vitest run tests/boundary/android <jadx process-boundary tests>`: 38 passed, 133 skipped (POSIX-only), 2 failed. The 2 failures are in `tests/boundary/process/jadxHashCleanup.test.ts`, which does not use the changed module, and fail identically on unmodified main on this host. - `npm run check:fast`: typecheck and lint passed (also in the pre-push hook). - Real Windows before/after selection check described above. Not run: `npm run check`, `npm run check:pr`, `npm run verify:android`, and any JADX engine or APK workflow. ## Compatibility, safety, and release - Breaking changes or migration steps: none intended. A Windows setup that depended on an unlisted working-directory `java.exe` must now set `JAVA_HOME` or add that directory to `PATH`, which is what the docs already said. - Real Hopper/Ghidra, browser, or OS coverage: Windows 11 x64 only, configuration resolution only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: removes an implicit executable search location; no new execution path. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [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:43:12 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#6810
No description provided.