Added the code to handle panic while destroying the pubnub client in case pn.jobQueue is already closed #161
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.
Type of Change
Fixture to handle PubNub Client Destroy Gracefully in case JobQueue is already closed(non-breaking changes which adds functionality)
Description
Problem
I was implementing the reinitialize pubnub client mechanism in my application, So before reinitializing it, I was calling the inbuilt Destroy() func for cleaning all open requests, removing listeners, etc. It was throwing panic with the error mentioned below
Code In which it was panicking
p.client.Destroy()
lib code snapshot
panic Error
Solution
Tested
I was able to destroy the client connection gracefully and reinitialize the client connection in case of any pubnub system status events