You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
When i try looking up something and go to the images tab when the results come in i get stuck in this forever loading loop where the loading symbol shows up but just spins forever, i have tried this on both mine and the official instance and on different devices and yet run into the same problem.
To Reproduce
Steps to reproduce the behavior:
Any current (2023-12-11) SearchTLD instance
Search anything that probably has a picture related to it
Click the images tab
See error
Expected behavior
A clear and concise description of what you expected to happen.
I expect the images to load as they should and have before.
I believe this is related to image provider being rate limited. I will try to see what is causing it and most likely use a fallback like in text results if this happens.
Figured out the issue, I'm currently working on the conversions update but will include the fix in the release. I used qwant lite for images but now it has been shut down so images don't work anymore.
Describe the bug
A clear and concise description of what the bug is.
When i try looking up something and go to the images tab when the results come in i get stuck in this forever loading loop where the loading symbol shows up but just spins forever, i have tried this on both mine and the official instance and on different devices and yet run into the same problem.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
I expect the images to load as they should and have before.
Screenshots
If applicable, add screenshots to help explain your problem.
https://i.imgur.com/CTy5fs3.png
Desktop (please complete the following information):
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: