ragulka

> I guess it's the `invoice.payment_succeeded` we need to check for this? We should be able to derive the subscribe for it and clear this metadata key on the subscription....

@driesvints sorry - somehow I did not see the notifications from this thread. I'd be up to submit a PR, I've just been rather tight with time.

I think the issue might be that the `originalnputs` array serves 2 different purposes: 1. A stored list of original data keys, so it's easier to reset the form data...

I also ran into this. It should not be too hard to add support for this, using callables: ```php it('works', function() { // test here... })->covers([MyClass::class, 'myMethod']); ``` Unfortunately, it...

I didn't notice this issue before I already opened a PR to add the 2nd reduced rate in #25.

FWIW, this seems to be caused by the fact that the Context is never hydrated on the `JobRetryRequested` event, it's only hydrated on `JobProcessing` event: https://github.com/laravel/framework/blob/5c986f2d33073d2eb260a911224490b72ff19656/src/Illuminate/Log/Context/ContextServiceProvider.php#L42-L45