-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser uncaught exception | error=Error: RangeError: Invalid array length #395
Comments
I have the same issue. It seems like adding a time zone to the render request url (eg tz=Asia%2FSeoul) makes the rendering work again, although the time zone itself has no effect on the time range (ie tz=Europe/Helsinki and tz=Asia/Tokyo will produce the same time range in the rendered image) The time zones UTC and GMT do not work at all, ie adding tz=GMT to the url will result in and empty image I tested downgrading from 3.6.3 to 3.6.1 and rendering without the tz url param works again, and tz=GMT works as well. There is a big difference in the CPU and memory consumption as well. And version 3.6.3 kept throwing error messages about the browser crashing
|
This appears to be a duplicate of grafana/grafana#59334 |
Indeed this is the same issue. With the workaround from grafana/grafana#59334 (comment) it works. In my eyes the issue is from the renderer and not Grafana, since adding the time zone to the environment variables of the renderer solved the problem. |
Hi @mr-manuel, thanks for sharing your thoughts. So, do you think the Image Renderer should just handle the case when there's no TZ defined and just pass Thanks! |
If it's working with |
Closing this issue as from this, it seems to be fixed with latest versions of the image renderer. Please reach out if you still face this issue. |
What happened:
After Grafana 9.2.4 and Grafana Image Renderer 3.6.2 the images for notifications stopped rendering in a Docker environment.
What you expected to happen:
That the images get rendered
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: