Added a fix for JobWatchers when the job payload is encrypted #1089
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.
Hey guys.
I have opened this pr because i encountered a problem when using the JobEncryption feature for a given job.
Telescope assumes the Job is already ready to be unserialized and does not handle encryption
The logic have i stolen from here:
https://github.com/laravel/framework/blob/108385b4f98cacfc1ef1d6e323f57b1c2df3180f/src/Illuminate/Queue/CallQueuedHandler.php#L86-L105
Therefore i have not provided any tests sense the logic is exactly the same apart from the container not being present on the instance itself.