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

Find out why connection can be nil in forwarder #1651

Open
NikitaSkrynnik opened this issue Jul 26, 2024 · 0 comments
Open

Find out why connection can be nil in forwarder #1651

NikitaSkrynnik opened this issue Jul 26, 2024 · 0 comments

Comments

@NikitaSkrynnik
Copy link
Contributor

NikitaSkrynnik commented Jul 26, 2024

Description

Sometimes forwarder can panic because of nil connection and nil error at the same time. Now we have a check for it, but we should find out why exactly conn and err can both be nil.

@NikitaSkrynnik NikitaSkrynnik changed the title Find out why connection can be nil Find out why connection can be nil in forwarder Jul 26, 2024
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

No branches or pull requests

1 participant