morluto/rea

Fork

You've already forked rea

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 #5372] [MERGED] fix(pwndbg): separate the words in the debugger-context limit message #6906

New issue

Closed

opened 2026-11-01 21:43:58 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-01 21:43:58 +00:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5372
Author: @XiaoBinGan
Created: 10/20/2026
Status: ✅ Merged
Merged: 10/20/2026
Merged by: @morluto

Base: main ← Head: fix/pwndbg-output-limit-message

📝 Commits (1)

0825cef fix(pwndbg): separate the words in the debugger-context limit message

📊 Changes

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

View changed files

📝 bridge/pwndbg/core_context.py (+1 -1)
📝 bridge/pwndbg/test_core_context.py (+11 -2)
📝 package.json (+1 -1)

📄 Description

Summary

When the complete recorded-crash debugger mapping context encodes above the 64 MiB reply budget, the pwndbg bridge refuses it with a message whose word and limit are joined: Complete debugger context exceeds64 MiB reply budget. This names the budget the same way the pwntools sibling already does, and adds the first producer regression for that refusal.

Fixes #5329

Problem and expected behavior

Smallest trigger: inspect-recorded-crash --debugger-context (MCP include_debugger_context: true) where the encoded mapping reply exceeds OUTPUT_BYTES in bridge/pwndbg/core_context.py, so the reply is replaced by the output-limit refusal object.
Violated invariant: a refusal that states a limit must state it readably. The rendered message joins "exceeds" and "64", reported on 39275420e and still present on 799e8265b (the string is unchanged between 048d70755 and 799e8265b).
Expected: Complete debugger context exceeds the 64 MiB reply budget., which is how bridge/pwntools/decoder_runtime.py words the same budget.

Change and scope

bridge/pwndbg/core_context.py: the refusal message only. The reason (output-limit), the 64 MiB limit, and the reply shape are untouched.
bridge/pwndbg/test_core_context.py: the existing inspect() fixture gains an objfile parameter, and a regression drives the real boundary by padding the mapping entry past OUTPUT_BYTES and asserting the reason, the exact message, and the absence of exceeds64.
package.json: the pwndbg suite was not part of test:python, so a producer regression there would never execute in CI. It is added to that command, which already runs the native and mitmproxy producer suites.
Not included: no change to the limit, the refusal contract, the pwntools bridge, or the documented output-limit behavior.

Contract and boundary impact

Semantic owner and earliest changed stage: pwndbg bridge producer, reply projection in bridge/pwndbg/core_context.py.
Contribution scope fit and linked maintainer decision: not applicable — an ordinary fix inside an existing boundary, no new provider or capability.
CLI and MCP/tool-catalog contract: message text only. reason: "output-limit" and the tool result remain unchanged, so no tool-catalog or metadata regeneration is involved.
Provider, bridge, target-format, or platform compatibility: pwndbg bridge only; the pwntools and Ghidra bridges are untouched.
Evidence, artifact, provenance, or reconstruction contract: unchanged; the refusal still carries no partial context.
Target selection, authority, upstream behavior, and cleanup details: not applicable — this path inspects an existing recorded snapshot and only allocates the bounded reserve it already allocated.
Generated metadata, package, or installation impact: none. The authored change is a package.json script argument, and no ignored catalog or skills/ output is touched.

Expected effects (check known effects; use documentation-only on its own).

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: bridge/pwndbg/test_core_context.py::test_output_limit_message_separates_the_words_and_names_the_limit.
Base reproduction or other evidence: with the pre-fix string restored in the same worktree, the suite fails on the new regression — AssertionError: 'exceeds64' unexpectedly found in 'Complete debugger context exceeds64 MiB reply budget.' (6 tests, FAILED (failures=1)). With the fix, 6 tests pass. The refusal is reached through the real 64 MiB comparison, not by patching the message.
User-visible CLI/MCP output (if applicable): {"ok": false, "reason": "output-limit", "message": "Complete debugger context exceeds the 64 MiB reply budget."}
Remaining proof gaps: no native GDB/pwndbg session was run here; like the report's reproduction, the producer test drives the real limit with the repository's own mocked GDB/pwndbg modules. The CI-visible effect is that test:python now executes this suite.

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

npm run test:python — 41 tests OK, then 81 tests OK (exit 0) on Node 24.18.0 with python3.14; this now includes bridge/pwndbg/test_core_context.py.
python3 -m unittest bridge/pwndbg/test_core_context.py — 6 tests OK.
python3 -m unittest bridge/pwndbg/test_core_context.py with the pre-fix message restored — FAILED (failures=1), 'exceeds64' unexpectedly found.
npm run format:check — "All matched files use the correct format" across 4126 files.

Compatibility, safety, and release

Breaking changes or migration steps: none; a message string changes wording, not structure or meaning.
Real Hopper/Ghidra, browser, or OS coverage: none claimed; no real debugger session was run.
Package or release metadata impact: none.
Security, privacy, process, or containment review: none; no target interaction, no new file or process access.

Author readiness

Human owner: @XiaoBinGan

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/5372 **Author:** [@XiaoBinGan](https://github.com/XiaoBinGan) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 10/20/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `fix/pwndbg-output-limit-message` --- ### 📝 Commits (1) - [`0825cef`](https://github.com/morluto/rea/commit/0825cef9d295a45fbf37b686a0a118f74d7ff73c) fix(pwndbg): separate the words in the debugger-context limit message ### 📊 Changes **3 files changed** (+13 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `bridge/pwndbg/core_context.py` (+1 -1) 📝 `bridge/pwndbg/test_core_context.py` (+11 -2) 📝 `package.json` (+1 -1) </details> ### 📄 Description ## Summary When the complete recorded-crash debugger mapping context encodes above the 64 MiB reply budget, the pwndbg bridge refuses it with a message whose word and limit are joined: `Complete debugger context exceeds64 MiB reply budget.` This names the budget the same way the pwntools sibling already does, and adds the first producer regression for that refusal. Fixes #5329 ## Problem and expected behavior - Smallest trigger: `inspect-recorded-crash --debugger-context` (MCP `include_debugger_context: true`) where the encoded mapping reply exceeds `OUTPUT_BYTES` in `bridge/pwndbg/core_context.py`, so the reply is replaced by the output-limit refusal object. - Violated invariant: a refusal that states a limit must state it readably. The rendered message joins "exceeds" and "64", reported on `39275420e` and still present on `799e8265b` (the string is unchanged between `048d70755` and `799e8265b`). - Expected: `Complete debugger context exceeds the 64 MiB reply budget.`, which is how `bridge/pwntools/decoder_runtime.py` words the same budget. ## Change and scope - `bridge/pwndbg/core_context.py`: the refusal message only. The reason (`output-limit`), the 64 MiB limit, and the reply shape are untouched. - `bridge/pwndbg/test_core_context.py`: the existing `inspect()` fixture gains an `objfile` parameter, and a regression drives the real boundary by padding the mapping entry past `OUTPUT_BYTES` and asserting the reason, the exact message, and the absence of `exceeds64`. - `package.json`: the pwndbg suite was not part of `test:python`, so a producer regression there would never execute in CI. It is added to that command, which already runs the native and mitmproxy producer suites. - Not included: no change to the limit, the refusal contract, the pwntools bridge, or the documented output-limit behavior. ## Contract and boundary impact - Semantic owner and earliest changed stage: pwndbg bridge producer, reply projection in `bridge/pwndbg/core_context.py`. - Contribution scope fit and linked maintainer decision: not applicable — an ordinary fix inside an existing boundary, no new provider or capability. - CLI and MCP/tool-catalog contract: message text only. `reason: "output-limit"` and the tool result remain unchanged, so no tool-catalog or metadata regeneration is involved. - Provider, bridge, target-format, or platform compatibility: pwndbg bridge only; the pwntools and Ghidra bridges are untouched. - Evidence, artifact, provenance, or reconstruction contract: unchanged; the refusal still carries no partial context. - Target selection, authority, upstream behavior, and cleanup details: not applicable — this path inspects an existing recorded snapshot and only allocates the bounded reserve it already allocated. - Generated metadata, package, or installation impact: none. The authored change is a `package.json` script argument, and no ignored catalog or `skills/` output is touched. Expected effects (check known effects; use documentation-only on its own). - [ ] 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. - [x] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `bridge/pwndbg/test_core_context.py::test_output_limit_message_separates_the_words_and_names_the_limit`. - Base reproduction or other evidence: with the pre-fix string restored in the same worktree, the suite fails on the new regression — `AssertionError: 'exceeds64' unexpectedly found in 'Complete debugger context exceeds64 MiB reply budget.'` (6 tests, `FAILED (failures=1)`). With the fix, 6 tests pass. The refusal is reached through the real 64 MiB comparison, not by patching the message. - User-visible CLI/MCP output (if applicable): `{"ok": false, "reason": "output-limit", "message": "Complete debugger context exceeds the 64 MiB reply budget."}` - Remaining proof gaps: no native GDB/pwndbg session was run here; like the report's reproduction, the producer test drives the real limit with the repository's own mocked GDB/pwndbg modules. The CI-visible effect is that `test:python` now executes this suite. 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 - `npm run test:python` — 41 tests OK, then 81 tests OK (exit 0) on Node 24.18.0 with python3.14; this now includes `bridge/pwndbg/test_core_context.py`. - `python3 -m unittest bridge/pwndbg/test_core_context.py` — 6 tests OK. - `python3 -m unittest bridge/pwndbg/test_core_context.py` with the pre-fix message restored — `FAILED (failures=1)`, `'exceeds64' unexpectedly found`. - `npm run format:check` — "All matched files use the correct format" across 4126 files. ## Compatibility, safety, and release - Breaking changes or migration steps: none; a message string changes wording, not structure or meaning. - Real Hopper/Ghidra, browser, or OS coverage: none claimed; no real debugger session was run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: none; no target interaction, no new file or process access. ## Author readiness Human owner: @XiaoBinGan - [x] 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. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] 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:43:58 +00:00

closed this issue
added the
pull-request
label

bsakaguchi referenced this issue

2026-11-01 21:47:51 +00:00

[PR #6906] [CLOSED] fix(analysis): treat unsupported HAR body encodings as unavailable text (#6889) #7438

No Branch/Tag specified

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

Mirrored from GitHub Pull Request

No labels

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#6906

Reference in a new issue

Repository

morluto/rea

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?

Rows
Columns