Sam Carré
Sam Carré
I'm currently working off a fork and I will see if it works - just installing it locally - the PR will be a little crude without testing but I...
I think either option 1 or 2 could be good. For people who haven't enabled queueing it will still run in sync, but for others it'll queue it. Option 2...
With option 1 you could even `Job::dispatchAfterResponse()` which would possibly reduce latency even further.
I think I figured it out - I believe it's caused by the `laravel-correlation-id` library installed from v3. I've been doing some debugging in the `CorrelationIdServiceProvider` and I have narrowed...
Hey @bilfeldt I had another look today and it turns out for us it's caused by the `Log::warning()` when the library has already loaded the macros. I believe this is...
So I believe the issue/behaviour is called with Parallel tests because this also baffled me once - I thought that the service providers were only loaded once and then kept...
> So my first question is what error you are getting? I'm getting a weird one:  However this could be caused by something else...
> My guess is that it is registered in the exact same file, but that is for some reason being called twice. Yes I believe it's just re-running the same...
Hey @bilfeldt I've just tested putting `Log::warning('test')` in my `AppServiceProvider` and it ran okay. This is a really odd one.
Hey @iaK apologies for the delay! I will take a look at this next week :)