tt raises the 'unexpected resultId in response' warning when connecting to an instance with turned off guest access
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
To reproduce the issue, perform the steps below:
- Set
security.disable_guesttotruein the instance's config:
security:
disable_guest: true
- Connect to an instance using
tt connect.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the warning by setting security.disable_guest to true in the instance configuration and running tt connect. Trace the tt connect response-handling path that reports "unexpected resultId in response" and check how this response differs when guest access is disabled. Done when the reproducer no longer emits the unexpected resultId warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100