Skip to content

Token-completion caret tests are frame-timing sensitive under no-domain-reload session sequences #56

Description

@wallstop

DISCLOSURE: LLM-GENERATED TEXT

Fixed by PR #60 (session-008): the token-completion caret tests dropped every single-frame value/caret read for bounded polls, and TerminalUI.ApplyPendingCaret now consumes the queued caret only once the write sticks on a focused pass (the panel can re-clamp programmatic caret writes; the old consume-on-first-write lost that race). Fresh-domain and no-domain-reload sequences have run clean since (PlayMode 348/348 on Unity 6000.4.6f1, re-verified today).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions