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

[client] fix/proxy close #2873

Merged
merged 17 commits into from
Nov 11, 2024
Merged

[client] fix/proxy close #2873

merged 17 commits into from
Nov 11, 2024

Conversation

pappz
Copy link
Contributor

@pappz pappz commented Nov 10, 2024

Describe your changes

When the remote peer switches the Relay instance then must to close the proxy connection to the old instance.

It can cause issues when the remote peer switch connects to the Relay instance multiple times and then reconnects to an instance it had previously connected to.

Issue ticket number and link

Checklist

  • Is it a bug fix
  • Is a typo/documentation fix
  • Is a feature enhancement
  • It is a refactor
  • Created tests that fail without the change (if possible)
  • Extended the README / documentation, if necessary

@pappz pappz changed the base branch from main to limit-route-notification November 10, 2024 10:33
@pappz pappz marked this pull request as ready for review November 10, 2024 11:30
lixmal
lixmal previously approved these changes Nov 11, 2024
Base automatically changed from limit-route-notification to main November 11, 2024 09:54
@pappz pappz dismissed lixmal’s stale review November 11, 2024 09:54

The base branch was changed.

Copy link

@pappz pappz merged commit 30f025e into main Nov 11, 2024
21 checks passed
@pappz pappz deleted the fix/proxy-close branch November 11, 2024 13:18
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