Skip to content
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.

Failed connection fix #8033

Merged
merged 1 commit into from
May 31, 2023
Merged

Failed connection fix #8033

merged 1 commit into from
May 31, 2023

Conversation

barankyle
Copy link
Member

@barankyle barankyle commented May 30, 2023

Summary

A summary of changes being made in this PR

References

closes #insert number here

Checklist

  • If this PR is still a WIP, convert to a draft
  • When this PR is ready, mark it as "Ready for review"
  • ensure all checks pass
  • Changes have been manually QA'd
  • Changes reviewed by at least 2 approved reviewer

QA Steps

List any additional steps required to QA the changes of this PR, as well as any supplemental images or videos.

When a connection fails, it will sometimes provision a new server.
This was only checking if the current connection's 'connected' status
was true, but not whether the 'connecting' status was true. On some
long-loading scenes, the initial connection was failing right as a
second provision was starting, and was leading to two connections
being made concurrently, which would cause problems - the second
connection would not make any dataProducers/dataConsumers, leaving
the user with no networking despite being connected.

Fixed a few bugs that were causing type errors.
@HexaField HexaField merged commit 7d69704 into dev May 31, 2023
@HexaField HexaField deleted the failed-connection-fix branch May 31, 2023 01:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants