Closed kaiserkiwi closed 8 months ago
@kaiserkiwi Hm, that's weird. I cannot replicate it with your provided code though. 🤔😅
Maybe it's some kind of rate limiting on your side (which should be temporarily)?
I tried to find steps to reproduce the issue but it seems random. It still happens on a regular basis. Still not a single error log for this. I really have no idea how I could help here more.
Anything I could provide to narrow the problem down?
As I do not know what exactly is causing this issue and the response is completely empty it's very hard to determine where to start searching. What makes it even harder is the fact that I could not reproduce your behavior even once yet. What's even weirder is the fact that all unit tests for 4.1.0 are green as well which pushes the problem a bit towards IGDB. But that on the other hand does not play along the fact everything is working with 4.0.0 though.
Very strange problem we're facing here to be honest.
I will try again reproducing this behavior. I think that's the only thing we can do right now.
I'm afraid there's no direction I can push you in to provide any further information 🙈
As a workaround you may pin your version to 4.0.0 for now if the random empty responses are causing problems at your side.
@kaiserkiwi So, I've tried again reproducting this issue for half an hour. Without success. Even turning off the cache did not result in your described issue.
I have a really weird issue after the update to 4.1.0. A test with 4.0.0 shows that this issue doesn't exist on this version.
Sometimes I just don't get any output. No error, nothing. I have a script to update game info and this just gets the data via IGDB-IDs. Most of the time it works just fine but sometimes it doesn't. I tried to replicate this issue with Tinkerwell but I'm still not 100% sure what is happening. But at the end of the issue is a video that shows the issue.
I have an array with 431 IDs. Neither the number nor the exakt ID seems to be an issue, as I get this behavior with multiple configurations. Even when I only take 300 the error is there and is not if I delete the last one that shouldn't even be in the result. Also if I remove
involved_companies.company
from the included fields, it just works fine. If I remove everything butinvolved_companies.company
it also works. So it's probably not this. If I reduce the limit to 250 it also works.It's really really strange.
This is the exakt code I tried it with in the video, so you can try to replicate it.
Video
https://github.com/marcreichel/igdb-laravel/assets/8428551/981dc037-e371-4954-a5f6-e3c2c4ea8711