Cut Daemon and TimedLspClient cycle: Daemon owns the caller-side LSP time limit #1175
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#1175
Loading…
Reference in a new issue
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?
Problem
OsSdlc::TimedLspClientwrapsDaemon.connectand applies a 60 s caller-side time limit to each LSP query.Daemon::NavigationholdsTimedLspClient, andTimedLspClientholdsDaemon, so the two form a concept cycle. The 60 s limit and its message also have two owners:TimedLspClient(timed_lsp_client.rb:7, 26-34) andDaemon::LspSession(daemon/lsp_session.rb:10, 103-109). Ruling S9 gives the caller-side limit to Daemon and deletes the wrapper.Reproduce
n/a: structure-wave cut, nothing to reproduce
Approach
Daemongains the four query class methods thatTimedLspClienthas today.Daemonowns one limit constant and one message, andDaemon::LspSessionuses them.Required work:
Daemon.definitions(at:, root:, config:),Daemon.references(at:, root:, config:),Daemon.symbols(name:, root:, config:)andDaemon.outline(path:, root:, config:)toplugins/os-sdlc/lib/os_sdlc/daemon.rb. Each connects withDaemon.connectand runs its query insideTimeout.timeout(QUERY_SECONDS, LspTimeoutError, ...), asTimedLspClient.rundoes today. — check: presentQUERY_SECONDS = 60inplugins/os-sdlc/lib/os_sdlc/daemon.rbDaemon::LspSession#with_timeoutand#timeout_messageuse theDaemonconstant and message. DeleteLspSession::TIMEOUT_SECONDS. — check: absentTIMEOUT_SECONDSinplugins/os-sdlc/lib/os_sdlc/daemon/lsp_session.rb:serverinplugins/os-sdlc/lib/os_sdlc/daemon/navigation.rb:17and the defaultrunner:inplugins/os-sdlc/lib/os_sdlc/evidence/probe/lsp.rb:7toDaemon. — check: absentTimedLspClientinplugins/os-sdlc/lib/**/*.rbplugins/os-sdlc/lib/os_sdlc/timed_lsp_client.rb.Acceptance criteria
bin/crc-cycle-edgesruns, then no cycle edge liststimed_lsp_client.rbordaemon/navigation.rb:17.Daemon.definitions, then it raisesLspTimeoutErrorwith the messagelsp-probe: ruby-lsp did not respond within 60s.Owner sketch
Non-goals
The fixture TSVs under
plugins/os-sdlc/tests/fixtures/crc_shares/run2/are a record of run 2. They keep the nameTimedLspClient.Origin
VERDICT: CREATE
Work started on branch crc-os-sdlc-run-3 (crc run 3 worktree), structure-change map.
Resolution
Done: Daemon owns the caller-side LSP time limit: QUERY_SECONDS, the four query class methods and timeout_message live in Daemon; LspSession uses them; TimedLspClient is deleted; navigation and evidence probe default to Daemon.
Evidence: Commit
ed849be6on branch crc-os-sdlc-run-3, implementation 87, structure-change map; gate green (required-work, lint, suite, unchanged), 1 dispatch, 3 min 15 s.Follow-ups: none