-
-
Notifications
You must be signed in to change notification settings - Fork 36
Fix Session.close() to prevent freeing underlying session #709
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
Conversation
|
Congratulations! One of the builds has completed. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
webknjaz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Jakuje does this make it so the underlying session object could persist and would then be reused on reconnect? I guess that's useful. Another way could be having some flag on the session for whether it's still usable.
P.S. I dropped Ubuntu 20.04 on devel so it would be a good idea to rebase now.
I think the libssh session should be reusable. But I know we had some bugs in the past that were making some operations fail so if we want to be sure, we should add some more extensive tests.
Will do. |
Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Signed-off-by: Jakub Jelen <jjelen@redhat.com>
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
🚀 New features to boost your workflow:
|



SUMMARY
Call to connect() after close() crashed, likely because the NULL pointer was passed somewhere it should not.
The session should really be freed only in the destructor so removing the offending code.
Fixes: #702
ISSUE TYPE