cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

fix(lsp): release lock before blocking I/O in LspLifecycleManager.restart_server() to prevent deadlock #3165

Merged
freemo merged 1 commits from fix/lsp-lifecycle-restart-lock-deadlock into master 2026-04-05 07:50:10 +00:00
Conversation 5 Commits 1 Files Changed 3
+213 -20
freemo commented 2026-04-05 07:08:34 +00:00
Owner
Copy Link
Copy Source

Summary

LspLifecycleManager.restart_server() previously held self._lock across all blocking I/O operations — transport.stop(), transport.start(), and client.initialize(). Under concurrent access this caused a deadlock: any thread calling health_check(), list_running(), or stop_server() would block for up to 60 seconds waiting for the lock to be released.

Changes

src/cleveragents/lsp/lifecycle.py

Refactored restart_server() to use the same 3-phase lock pattern already employed by start_server():

Phase Lock held? What happens
1 ✅ short Read current state, snapshot fields, remove old entry from _servers
2 ❌ none old_transport.stop(), StdioTransport(…).start(), client.initialize()
3 ✅ short Insert new _ManagedServer into _servers, preserving ref_count

Removing the old entry in Phase 1 ensures concurrent callers see the server as absent during the restart window (consistent with the existing start_server contract). The ref_count from the original managed server is carried forward to the new one.

features/lsp_lifecycle_coverage.feature + features/steps/lsp_lifecycle_coverage_steps.py

Three new BDD scenarios verify the fix:

  1. health_check is not blocked while restart_server is in progress — uses a threading.Barrier to synchronise two threads at the exact moment the lock is released in Phase 2. Asserts that health_check() completes without blocking.

  2. restart_server does not hold the lock during client.initialize — inspects _lock state from within the mock initialize() side-effect using acquire(blocking=False). Asserts the lock is acquirable (i.e. not held).

  3. restart_server preserves the ref_count of the managed server — starts the server twice (ref_count=2), restarts it, and asserts ref_count is still 2.

Test Results

All three new scenarios pass. Ruff lint and format checks pass. Pyright reports 0 errors.

Closes

Closes #3026

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-worker

## Summary `LspLifecycleManager.restart_server()` previously held `self._lock` across all blocking I/O operations — `transport.stop()`, `transport.start()`, and `client.initialize()`. Under concurrent access this caused a deadlock: any thread calling `health_check()`, `list_running()`, or `stop_server()` would block for up to 60 seconds waiting for the lock to be released. ## Changes ### `src/cleveragents/lsp/lifecycle.py` Refactored `restart_server()` to use the same **3-phase lock pattern** already employed by `start_server()`: | Phase | Lock held? | What happens | |-------|-----------|--------------| | 1 | ✅ short | Read current state, snapshot fields, remove old entry from `_servers` | | 2 | ❌ none | `old_transport.stop()`, `StdioTransport(…).start()`, `client.initialize()` | | 3 | ✅ short | Insert new `_ManagedServer` into `_servers`, preserving `ref_count` | Removing the old entry in Phase 1 ensures concurrent callers see the server as absent during the restart window (consistent with the existing `start_server` contract). The `ref_count` from the original managed server is carried forward to the new one. ### `features/lsp_lifecycle_coverage.feature` + `features/steps/lsp_lifecycle_coverage_steps.py` Three new BDD scenarios verify the fix: 1. **`health_check is not blocked while restart_server is in progress`** — uses a `threading.Barrier` to synchronise two threads at the exact moment the lock is released in Phase 2. Asserts that `health_check()` completes without blocking. 2. **`restart_server does not hold the lock during client.initialize`** — inspects `_lock` state from within the mock `initialize()` side-effect using `acquire(blocking=False)`. Asserts the lock is acquirable (i.e. not held). 3. **`restart_server preserves the ref_count of the managed server`** — starts the server twice (ref_count=2), restarts it, and asserts ref_count is still 2. ## Test Results All three new scenarios pass. Ruff lint and format checks pass. Pyright reports 0 errors. ## Closes Closes #3026 --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
freemo added 1 commit 2026-04-05 07:08:34 +00:00
fix(lsp): release lock before blocking I/O in LspLifecycleManager.restart_server() to prevent deadlock
CI / lint (pull_request) Successful in 20s
Details
CI / typecheck (pull_request) Successful in 47s
Details
CI / quality (pull_request) Successful in 37s
Details
CI / security (pull_request) Successful in 1m0s
Details
CI / build (pull_request) Successful in 27s
Details
CI / helm (pull_request) Successful in 24s
Details
CI / unit_tests (pull_request) Successful in 6m50s
Details
CI / e2e_tests (pull_request) Successful in 16m59s
Details
CI / coverage (pull_request) Successful in 10m54s
Details
CI / docker (pull_request) Successful in 1m39s
Details
CI / integration_tests (pull_request) Successful in 23m0s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 56m47s
Details
17e7507a4d 
Refactored restart_server() to use the same 3-phase lock pattern already
employed by start_server(), eliminating a deadlock hazard that occurred when
the method held _lock across blocking I/O operations (transport.stop(),
transport.start(), and client.initialize()).

Phase 1 (short lock): reads current state, snapshots required fields, and
removes the old server entry so concurrent callers see the server as absent
during the restart window.

Phase 2 (no lock): stops the old transport, spawns the new process, and
performs the LSP handshake — all without holding _lock. These operations
can block for up to 60 seconds; holding the lock here would starve any
concurrent health_check(), list_running(), or stop_server() calls.

Phase 3 (short lock): commits the new _ManagedServer into shared state,
preserving the original ref_count.

Three new BDD scenarios added to features/lsp_lifecycle_coverage.feature:
- health_check is not blocked while restart_server is in progress
  (uses a threading.Barrier to synchronise the two threads at the exact
  moment the lock is released)
- restart_server does not hold the lock during client.initialize
  (inspects lock state from within the mock initialize() side-effect)
- restart_server preserves the ref_count of the managed server

ISSUES CLOSED: #3026
freemo commented 2026-04-05 07:13:53 +00:00
Author
Owner
Copy Link
Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3165-1775372600]

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3165-1775372600] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
freemo reviewed 2026-04-05 07:45:39 +00:00
freemo left a comment
Author
Owner
Copy Link
Copy Source

Independent Code Review: APPROVED ✅

Note: Posted as COMMENT because Forgejo prevents self-approval. This is an independent review by the PR self-reviewer agent, which provides a different perspective than the implementing agent.

Summary

This PR correctly refactors LspLifecycleManager.restart_server() to use the same 3-phase lock pattern already established by start_server(), eliminating a potential deadlock where self._lock was held across all blocking I/O operations (transport stop/start, LSP handshake up to 60s).

Code Review

lifecycle.py — 3-phase lock refactoring

Phase Lock? Operations Verdict
1 ✅ short Read state, snapshot fields, del self._servers[name] ✅ Correct — removes entry so concurrent callers see server as absent
2 ❌ none old_transport.stop(), StdioTransport().start(), client.initialize() ✅ Correct — all blocking I/O outside lock
3 ✅ short Create new _ManagedServer, set ref_count, insert into _servers ✅ Correct — preserves ref_count, commits atomically
  • Error handling in Phase 2 is correct: if initialize() fails, the new transport is stopped and the exception propagates. The server entry (removed in Phase 1) is intentionally not re-inserted — consistent with the contract that a failed restart leaves the server absent.
  • The ref_count is properly snapshotted in Phase 1 and carried forward to the new _ManagedServer in Phase 3.
  • Docstring is updated with clear phase documentation.

Tests — 3 new BDD scenarios

  1. health_check is not blocked while restart_server is in progress — Uses threading.Barrier(2, timeout=5) for precise synchronization. The barrier ensures the health_check thread runs exactly when restart is in Phase 2 (lock released). This would genuinely fail if the lock were held. ✅ Excellent concurrent test.

  2. restart_server does not hold the lock during client.initialize — Inspects _lock.acquire(blocking=False) from within the mock initialize() side-effect. Deterministic, no timing dependency. ✅ Clean verification.

  3. restart_server preserves the ref_count of the managed server — Starts server twice (ref_count=2), restarts, asserts ref_count=2. ✅ Simple and effective.

Specification Alignment

The implementation matches the issue's expected behavior exactly: the 3-phase pattern mirrors start_server(), no blocking I/O occurs while self._lock is held, and concurrent access to health_check(), get_client(), stop_server(), and list_running() is no longer blocked during restart.

Notes (non-blocking)

  • The step file (lsp_lifecycle_coverage_steps.py) is now ~772 lines, exceeding the 500-line guideline. However, it was already at ~635 lines before this PR — this is a pre-existing condition, not introduced here. A future refactoring to split the step file would be appropriate.
  • The PR is missing a Type/ label and milestone — these should be set to match issue #3026 (Type/Bug, v3.6.0).

CI Status

All critical quality gates passed: lint ✅, typecheck ✅, security ✅, quality ✅, unit_tests ✅, integration_tests ✅, e2e_tests ✅, coverage ✅, build ✅, docker ✅, helm ✅. Benchmark and status-check jobs still pending.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

## Independent Code Review: APPROVED ✅ *Note: Posted as COMMENT because Forgejo prevents self-approval. This is an independent review by the PR self-reviewer agent, which provides a different perspective than the implementing agent.* ### Summary This PR correctly refactors `LspLifecycleManager.restart_server()` to use the same 3-phase lock pattern already established by `start_server()`, eliminating a potential deadlock where `self._lock` was held across all blocking I/O operations (transport stop/start, LSP handshake up to 60s). ### Code Review **lifecycle.py — 3-phase lock refactoring** | Phase | Lock? | Operations | Verdict | |-------|-------|-----------|---------| | 1 | ✅ short | Read state, snapshot fields, `del self._servers[name]` | ✅ Correct — removes entry so concurrent callers see server as absent | | 2 | ❌ none | `old_transport.stop()`, `StdioTransport().start()`, `client.initialize()` | ✅ Correct — all blocking I/O outside lock | | 3 | ✅ short | Create new `_ManagedServer`, set `ref_count`, insert into `_servers` | ✅ Correct — preserves ref_count, commits atomically | - Error handling in Phase 2 is correct: if `initialize()` fails, the new transport is stopped and the exception propagates. The server entry (removed in Phase 1) is intentionally not re-inserted — consistent with the contract that a failed restart leaves the server absent. - The `ref_count` is properly snapshotted in Phase 1 and carried forward to the new `_ManagedServer` in Phase 3. - Docstring is updated with clear phase documentation. **Tests — 3 new BDD scenarios** 1. **`health_check is not blocked while restart_server is in progress`** — Uses `threading.Barrier(2, timeout=5)` for precise synchronization. The barrier ensures the health_check thread runs exactly when restart is in Phase 2 (lock released). This would genuinely fail if the lock were held. ✅ Excellent concurrent test. 2. **`restart_server does not hold the lock during client.initialize`** — Inspects `_lock.acquire(blocking=False)` from within the mock `initialize()` side-effect. Deterministic, no timing dependency. ✅ Clean verification. 3. **`restart_server preserves the ref_count of the managed server`** — Starts server twice (ref_count=2), restarts, asserts ref_count=2. ✅ Simple and effective. ### Specification Alignment The implementation matches the issue's expected behavior exactly: the 3-phase pattern mirrors `start_server()`, no blocking I/O occurs while `self._lock` is held, and concurrent access to `health_check()`, `get_client()`, `stop_server()`, and `list_running()` is no longer blocked during restart. ### Notes (non-blocking) - The step file (`lsp_lifecycle_coverage_steps.py`) is now ~772 lines, exceeding the 500-line guideline. However, it was already at ~635 lines before this PR — this is a pre-existing condition, not introduced here. A future refactoring to split the step file would be appropriate. - The PR is missing a `Type/` label and milestone — these should be set to match issue #3026 (Type/Bug, v3.6.0). ### CI Status All critical quality gates passed: lint ✅, typecheck ✅, security ✅, quality ✅, unit_tests ✅, integration_tests ✅, e2e_tests ✅, coverage ✅, build ✅, docker ✅, helm ✅. Benchmark and status-check jobs still pending. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer
freemo scheduled this pull request to auto merge when all checks succeed 2026-04-05 07:47:36 +00:00
freemo merged commit 1411adfed3 into master 2026-04-05 07:50:10 +00:00
freemo deleted branch fix/lsp-lifecycle-restart-lock-deadlock 2026-04-05 07:50:10 +00:00
freemo commented 2026-04-05 07:56:02 +00:00
Author
Owner
Copy Link
Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3165-1743897600]

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3165-1743897600] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
freemo reviewed 2026-04-05 08:35:06 +00:00
freemo left a comment
Author
Owner
Copy Link
Copy Source

Code Review — LGTM ✅

PR: fix(lsp): release lock before blocking I/O in LspLifecycleManager.restart_server() to prevent deadlock

Review Checklist

✅ Correctness: The 3-phase lock pattern (short lock → blocking I/O without lock → short lock) is the correct approach. Consistent with start_server() pattern already in the codebase.

✅ Concurrency Safety: Old entry removed from _servers in Phase 1 ensures concurrent callers see the server as absent during restart window. ref_count correctly preserved.

✅ Test Coverage: 3 BDD scenarios using threading.Barrier to verify lock release during blocking I/O, lock state inspection during initialize(), and ref_count preservation.

✅ Type Safety: No # type: ignore. Pyright passes with 0 errors.

✅ Commit Format: fix(lsp): follows Conventional Changelog format.

Issues Noted (Non-blocking)

  • ⚠️ Missing milestone — Please assign to the appropriate milestone.
  • ⚠️ Missing Type/ label — Please add Type/Bug.

Decision: LGTM — Proceeding to merge when CI passes.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

## Code Review — LGTM ✅ **PR:** fix(lsp): release lock before blocking I/O in LspLifecycleManager.restart_server() to prevent deadlock ### Review Checklist **✅ Correctness:** The 3-phase lock pattern (short lock → blocking I/O without lock → short lock) is the correct approach. Consistent with `start_server()` pattern already in the codebase. **✅ Concurrency Safety:** Old entry removed from `_servers` in Phase 1 ensures concurrent callers see the server as absent during restart window. `ref_count` correctly preserved. **✅ Test Coverage:** 3 BDD scenarios using `threading.Barrier` to verify lock release during blocking I/O, lock state inspection during `initialize()`, and `ref_count` preservation. **✅ Type Safety:** No `# type: ignore`. Pyright passes with 0 errors. **✅ Commit Format:** `fix(lsp):` follows Conventional Changelog format. ### Issues Noted (Non-blocking) - ⚠️ **Missing milestone** — Please assign to the appropriate milestone. - ⚠️ **Missing Type/ label** — Please add `Type/Bug`. ### Decision: **LGTM** — Proceeding to merge when CI passes. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer
freemo commented 2026-04-05 16:21:07 +00:00
Author
Owner
Copy Link
Copy Source

State label reconciliation:

  • Previous state: none
  • Corrected to: State/Completed
  • Reason: This PR is closed and merged (merged 2026-04-05T07:50:10Z) but had no state label. Also added Priority/Medium and Type/Bug for compliance.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: ca-backlog-groomer

State label reconciliation: - Previous state: none - Corrected to: `State/Completed` - Reason: This PR is closed and merged (merged 2026-04-05T07:50:10Z) but had no state label. Also added `Priority/Medium` and `Type/Bug` for compliance. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
Sign in to join this conversation.
Reviewers
No Reviewers
freemo
Labels
Clear labels
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
 controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
 overdue
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
 auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
 auto/claimed-implementer
Currently being processed by an implementer worker.
 auto/claimed-merge
Currently being processed by the merge driver.
 auto/claimed-reviewer
Currently being processed by a reviewer worker.
 auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
 auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
 auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
 auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
 auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
 Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.
 auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.
 auto/needs-implementer
Failing CI needs implementer attention.
 auto/postmortem
Documenting a driver incident or rollback.
 auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
 auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
 auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
 auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
 auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
 auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
 Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
 Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cleveragents/cleveragents-core#3165
Delete Branch "fix/lsp-lifecycle-restart-lock-deadlock"

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?