Skip to content

Conversation

@jacksonh
Copy link
Contributor

Two changes here:

  • When a conversation is ended, its possible that we are still stuck in the init message retry
    loop. This will let us abort out of that loop, and handle Task cancelation so if the calling
    task is canceled we will end the loop.

  • LiveKit will attempt to reconnect ten times by default when it discovers a disconect. This
    can happen on startup and shutdown, and means a long delay until we can give user feedback
    that the connection has failed. By passing in the reconnect attempts, we allow the calling
    code to control this.

Commits:

  • Handle aborting the init message retry loop
  • Allow specifying the number of reconnect attempts LiveKit uses when it discovers a disconnect
  • Revert formatting change

…t discovers a disconnect

Sometimes this reconnect loop will be entered during shutdown,
this allows the client to prevent the loop for running the default
ten iterations if the calling app knows that it does not need
reconnection, and wants more control during shutdown.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants