[stable-3.13] nmc/3185-Encrypt-Socket-Request-Fix #278
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
when receiving a shell integration socket command for ENCRYPT, a generic interface and generic code paths was used
the assumption was that the listener socket would need (and remain) valid while hanlding teh request
some code paths need to display error messages to the user via a QMessageBox
the issue is that this will execute a Qt event loop that will handle the socket disconnection while the socket variable from the caller seems it will stay valid and alive
prevent that by not using a blocking method invocation such that life time mishandling about the socket listener is not possible