Repository navigation
Schedule bounded angle work between tactile stages - #27
Merged
YasenSS merged 10 commits intoNov 16, 2026
Merged
Conversation
Add scoped, nonrecursive callbacks between complete tactile stages. Read Python L20 and L20Lite fingers sequentially while publishing only complete whole-hand samples; preserve the Native aggregate path.
Accept only declared current-state feedback as angle sampling evidence. Correct the O30 V25 capability and collect optional O6 angle feedback. Fence read completion counters by polling plan revision and provide an internal clock seam for exact deadline regression tests.
Reuse the active device lease for pending angle targets and merged reads. Limit each boundary to four logical transactions, alternate reads and writes, and preserve finite execution budgets and actual send receipts. Propagate nested connection failures while retaining ordinary inner errors and isolate poll ownership during reentrant reads.
Cover feedback policies, complete protocol boundaries, bounded mixed loads, nested failures, polling replacement, close, recovery, and shared Session isolation with FakeTransport and controlled synchronization. Validation: 24 tactile scheduling cases and 450 assertions passed. Full offline CTest passed all 10 groups on macOS arm64 with C++17 and SOURCE transport v0.3.4. No new hardware validation was performed.
Read the device connection generation from runtime health instead of constructing a full diagnostic report after each telemetry read. Preserve explicit health reporting and existing generation handling.
Document tactile-stage scheduling, compatibility and recorded validation. Summarize O6, L20 and O30 hardware scope without extending past evidence. Align version references and correct transport and interface guidance.
Correlate both L20 Lite angle feedback banks before adaptive polling resumes. Fault the device runtime synchronously after a nested transport failure while preserving peers on the shared Session. Validate polling against the boundary cap without requiring four pending intents on every stage. Cover retained invalid caches, recovery and peer isolation, and address the reported clang-tidy diagnostics. Validated Release communication, Python policy and discovery regressions on macOS and Linux GCC 13, plus macOS ASan/UBSan. Repeated all 25 tactile scheduling cases twenty times. Windows and the full Report Card await CI.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Under the explicit Python runtime policy, a complete tactile acquisition can delay angle commands and reads. Unified telemetry read completion also constructs a full health report just to obtain the connection generation.
Change
Validation
Remaining checks
RuntimeAccess::with_stage_boundaries; it remains unresolved. The local macOS TGZ audit failed on AppleDouble entries; ZIP validation passed.