secondlife / secondlife/viewer
Still no fallback if handover during TP fails
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
The issue I reported probably like 10 years ago still exists:
-
Teleport to a new region
-
Source region sends circuit info of destination region to viewer
-
Viewer acknowledges circuit info being received
-
Simulator of source region transfers agent to simulator of destination region
-
Simulator of source region immediately closes circuit with agent's viewer
-
If for some reason to connection to the simulator of the destionation region fails, the viewer has no connection to either the old simulator nor the new simulator and gets logged out after 60 seconds
The connection with the viewer must only be closed after the simulator of the destination region confirms the connection with the viewer has been established instead of relying on faith the handover will succeed without any problems.
Contributor guide
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
Start by tracing the teleport handover sequence described in the issue, especially when the source simulator closes the viewer circuit and when the destination connection is established. Done means a failed destination connection leaves the viewer connected to the old simulator or otherwise provides a fallback instead of logging the viewer out after 60 seconds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100