Skip to content

Investigate transient inactive Sprite activity status #174

Description

@gannonh

Summary

katacode connect sprite status can show a running katacode service with an inactive activity task while the Sprite is transitioning after release or wake. This may be a short timing window while the server shuts down and restarts. Confirm the behavior before changing the lease model.

Observed behavior

Service: running
Activity task: inactive

The report occurred while the client was being used. The server may still have been shutting down after release, before the restarted service recreated the activity task.

Relevant commands:

katacode connect sprite release -s kata-dev
katacode connect sprite wake -s kata-dev
katacode connect sprite status -s kata-dev

Investigation

  • Reproduce the sequence during service shutdown, restart, and Connect tunnel registration.
  • Compare service state, kata-session state, server lease logs, and client connectivity timestamps.
  • Determine whether inactive is an expected transition state or stale/misleading status output.
  • If expected, make the transition state explicit in status output. If incorrect, fix the ordering or lease observation and add focused regression coverage.

This follow-up does not block PR #173.

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

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.size:XS

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions