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 #2754] [MERGED] fix(session): preserve investigation records after failed target opens #5365

New issue
Closed
opened 2026-10-31 01:06:03 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:06:03 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2754
Author: @Adkid-Zephyr
Created: 10/13/2026
Status: ✅ Merged
Merged: 10/13/2026
Merged by: @morluto

Base: main ← Head: fix/session-preserve-records-on-open-failure

📝 Commits (2)

  • f603947 fix(session): preserve investigation records after failed target opens
  • 41c0ce5 chore(ci): merge current main verification fixes

📊 Changes

3 files changed (+192 additions, -4 deletions)

View changed files

📝 docs/mcp-contracts.md (+5 -3)
📝 src/application/binary/BinarySession.ts (+3 -1)
➕ tests/boundary/mcp/sessionEvidenceRecovery.test.ts (+184 -0)

📄 Description

Summary

Preserve the investigation's Evidence and Unknown history when open_binary fails to retire the previous provider. Both target switching and same-target restart currently turn a bundle with 4 records/2 revisions into an empty bundle. Fixes #2753.

Follow-up to the unresolved P1 finding on #1776; original finding credited there. Implemented and verified with OpenAI Codex assistance.

Problem and expected behavior

A provider cleanup failure is returned correctly, but BinarySession.#open also calls clearSessionRecords(). A subsequent export cannot recover the lost investigation. Target opens must preserve records; explicit close_binary remains the operation that clears them.

Change and scope

Use the existing clearSnapshot() owner to discard the retired provider's replay cache without clearing the investigation ledger. Keep the pending cleanup owner, unavailable target, retry gate, and explicit-close behavior. Clarify this lifetime in the MCP guide.

Contract and boundary impact

  • Semantic owner and earliest changed stage: BinarySession.#open, after failed retirement.
  • Contribution scope fit and linked maintainer decision: ordinary reliability fix within existing lifecycle boundaries; advance scope decision not applicable.
  • CLI and MCP/tool-catalog contract: no schema or catalog changes; previously returned Evidence references remain usable after a failed open.
  • Provider, bridge, target-format, or platform compatibility: provider-neutral; no adapter/protocol changes.
  • Evidence, artifact, provenance, or reconstruction contract: preserve exact Evidence, Unknown revisions and bundle metadata; invalidate only the retired provider cache.
  • Target selection, authority, upstream behavior, and cleanup details: existing selection and cleanup unchanged; replacement remains blocked until cleanup succeeds.
  • Generated metadata, package, or installation impact: none.

Expected effects exercised by the regression workflow (production adds no new target interaction):

  • Read existing files or captured data (test-owned fixtures).
  • 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.

Production adds no target interaction. Tests also write temporary fixtures/exports and launch REA's JavaScript analysis worker; they never execute the analyzed JavaScript or a native target.

Evidence and regression coverage

  • Two public MCP boundary regressions exercise a target switch and same-target restart through the production provider composition, with controlled provider failure/health.

  • Exact final tests on main ab02f3c8d665ead35391c94db74cd0fb0cfed0ed: 2 failed, observing all 4 records and both Unknown revisions disappear. With the fix: 2 passed.

  • Check repeated failed cleanup, exact bundle preservation and file export, successful retry, fresh provider queries instead of stale cache replay, retained JavaScript Evidence views, and explicit close clearing.

  • User-visible failure remains cleanup_incomplete; get_evidence_bundle and export retain the original records instead of empty collections.

  • Proof gaps: provider cleanup/health are fixtures. No new real Hopper/Ghidra/IDA failure or native Windows/Linux run; no incidence-rate claim.

  • 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

Pinned Node 24.18.0/npm 11.16.0 on macOS arm64, final head f603947 rebased onto main 2995ec6:

  • npm run test:focused -- tests/boundary/mcp/sessionEvidenceRecovery.test.ts tests/boundary/mcp/sessionMcp.test.ts tests/boundary/mcp/retainedApplicationEvidenceMcp.test.ts tests/composition/analysis-sessions/binarySessionCleanupRetry.test.ts tests/composition/analysis-sessions/binarySession.test.ts src/application/binary/BinarySessionLiveness.test.ts tests/boundary/filesystem/directAnalysisSnapshotReplay.test.ts — 76 passed, 7 files.
  • npm run check — passed after shortening the new test helper; the initial run caught its function-length lint error.
  • npm run docs:check — passed, including 2 consistency tests.
  • npm run verify:test-discovery — all 1,055 files discovered once.
  • git diff --check — passed.

Full deterministic suite not run locally; remote CI is separate. verify:package passed while scouting the untouched baseline; packaging checks were not rerun for this lifecycle-only diff.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; explicit close keeps its existing lifetime.
  • Real Hopper/Ghidra, browser, or OS coverage: macOS tests with actual static JavaScript analysis; native provider failure behavior unverified.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no security research or new authority; cleanup ownership and startup ordering remain covered.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved; no new capability needs a scope decision.
  • One focused outcome and a Conventional Commit title.
  • Related issue linked and prior finding credited.
  • Tests cover observable behavior and meaningful failure paths.
  • Owning documentation updated; schemas/generated metadata unchanged.
  • Representative MCP behavior and verification limits described.
  • Final diff checked 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/2754 **Author:** [@Adkid-Zephyr](https://github.com/Adkid-Zephyr) **Created:** 10/13/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/session-preserve-records-on-open-failure` --- ### 📝 Commits (2) - [`f603947`](https://github.com/morluto/rea/commit/f603947cc8b09c2e0848e626d36b3ffe9e349b3c) fix(session): preserve investigation records after failed target opens - [`41c0ce5`](https://github.com/morluto/rea/commit/41c0ce5f51668c5b03ce4470dbbf26946d360248) chore(ci): merge current main verification fixes ### 📊 Changes **3 files changed** (+192 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `docs/mcp-contracts.md` (+5 -3) 📝 `src/application/binary/BinarySession.ts` (+3 -1) ➕ `tests/boundary/mcp/sessionEvidenceRecovery.test.ts` (+184 -0) </details> ### 📄 Description ## Summary Preserve the investigation's Evidence and Unknown history when `open_binary` fails to retire the previous provider. Both target switching and same-target restart currently turn a bundle with 4 records/2 revisions into an empty bundle. Fixes #2753. Follow-up to the [unresolved P1 finding on #1776](https://github.com/morluto/rea/pull/1776#discussion_r4242283747); original finding credited there. Implemented and verified with OpenAI Codex assistance. ## Problem and expected behavior A provider cleanup failure is returned correctly, but `BinarySession.#open` also calls `clearSessionRecords()`. A subsequent export cannot recover the lost investigation. Target opens must preserve records; explicit `close_binary` remains the operation that clears them. ## Change and scope Use the existing `clearSnapshot()` owner to discard the retired provider's replay cache without clearing the investigation ledger. Keep the pending cleanup owner, unavailable target, retry gate, and explicit-close behavior. Clarify this lifetime in the MCP guide. ## Contract and boundary impact - Semantic owner and earliest changed stage: `BinarySession.#open`, after failed retirement. - Contribution scope fit and linked maintainer decision: ordinary reliability fix within existing lifecycle boundaries; advance scope decision not applicable. - CLI and MCP/tool-catalog contract: no schema or catalog changes; previously returned Evidence references remain usable after a failed open. - Provider, bridge, target-format, or platform compatibility: provider-neutral; no adapter/protocol changes. - Evidence, artifact, provenance, or reconstruction contract: preserve exact Evidence, Unknown revisions and bundle metadata; invalidate only the retired provider cache. - Target selection, authority, upstream behavior, and cleanup details: existing selection and cleanup unchanged; replacement remains blocked until cleanup succeeds. - Generated metadata, package, or installation impact: none. Expected effects exercised by the regression workflow (production adds no new target interaction): - [x] Read existing files or captured data (test-owned fixtures). - [x] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [x] 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. Production adds no target interaction. Tests also write temporary fixtures/exports and launch REA's JavaScript analysis worker; they never execute the analyzed JavaScript or a native target. ## Evidence and regression coverage - Two public MCP boundary regressions exercise a target switch and same-target restart through the production provider composition, with controlled provider failure/health. - Exact final tests on main `ab02f3c8d665ead35391c94db74cd0fb0cfed0ed`: **2 failed**, observing all 4 records and both Unknown revisions disappear. With the fix: **2 passed**. - Check repeated failed cleanup, exact bundle preservation and file export, successful retry, fresh provider queries instead of stale cache replay, retained JavaScript Evidence views, and explicit close clearing. - User-visible failure remains `cleanup_incomplete`; `get_evidence_bundle` and export retain the original records instead of empty collections. - Proof gaps: provider cleanup/health are fixtures. No new real Hopper/Ghidra/IDA failure or native Windows/Linux run; no incidence-rate claim. - [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 Pinned Node 24.18.0/npm 11.16.0 on macOS arm64, final head `f603947` rebased onto main `2995ec6`: - `npm run test:focused -- tests/boundary/mcp/sessionEvidenceRecovery.test.ts tests/boundary/mcp/sessionMcp.test.ts tests/boundary/mcp/retainedApplicationEvidenceMcp.test.ts tests/composition/analysis-sessions/binarySessionCleanupRetry.test.ts tests/composition/analysis-sessions/binarySession.test.ts src/application/binary/BinarySessionLiveness.test.ts tests/boundary/filesystem/directAnalysisSnapshotReplay.test.ts` — **76 passed, 7 files**. - `npm run check` — passed after shortening the new test helper; the initial run caught its function-length lint error. - `npm run docs:check` — passed, including 2 consistency tests. - `npm run verify:test-discovery` — all 1,055 files discovered once. - `git diff --check` — passed. Full deterministic suite not run locally; remote CI is separate. `verify:package` passed while scouting the untouched baseline; packaging checks were not rerun for this lifecycle-only diff. ## Compatibility, safety, and release - Breaking changes or migration steps: none; explicit close keeps its existing lifetime. - Real Hopper/Ghidra, browser, or OS coverage: macOS tests with actual static JavaScript analysis; native provider failure behavior unverified. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no security research or new authority; cleanup ownership and startup ordering remain covered. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved; no new capability needs a scope decision. - [x] One focused outcome and a Conventional Commit title. - [x] Related issue linked and prior finding credited. - [x] Tests cover observable behavior and meaningful failure paths. - [x] Owning documentation updated; schemas/generated metadata unchanged. - [x] Representative MCP behavior and verification limits described. - [x] Final diff checked 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-10-31 01:06:03 +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#5365
No description provided.