Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix websocket servers not being marked as bad by the server list #209

Merged
merged 1 commit into from
Jun 29, 2022

Conversation

LossyDragon
Copy link
Collaborator

@LossyDragon LossyDragon commented Jun 22, 2022

Description

If a WebSocket timed out or couldn't connect, the current endpoint would be null, so it cant be marked bad even though we just tried connecting to it.

From SteamKit PR 634

Closes #52

Checklist

  • Code compiles correctly
  • All tests passing
  • Samples run successfully
  • Extended the README / documentation, if necessary

@LossyDragon LossyDragon merged commit b8bb067 into Longi94:master Jun 29, 2022
@LossyDragon LossyDragon deleted the PR634 branch December 21, 2022 06:47
@LossyDragon LossyDragon mentioned this pull request Jan 28, 2023
4 tasks
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.

MPR-634 Fix websocket servers not being marked as bad by the server list
1 participant