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
I replied in a similar issue but since it was closed due to inactivity and there was no response to my question I open this new issue.
I started having this issue when I tried upgrading from 12.3.0 to 13.6.0.
The screenshots that Gitlab CI produces are the same with the old ones but when I run it locally they have this issue.
I tried the different image versions including custom build that @mjhenkes suggested, but the issue persisted. I went through the factory directory history but I couldn't find anything that would point to this issue either. Would the new images use the fonts from the environment that they are build or something like this?
As a workaround, I still use 12.3.0 locally and 12.17.0 on CI as this is the first image that use Node 18+ which some of my dependencies (Vite plugins) require it. But since this is a temporary workaround and eventually I would need to use higher version of Node I would like to find a solution.
I asked my colleagues to test it and they had the same issue. We all have Macbook (Apple M1 - macOS 14.3).
Hey folks,
I replied in a similar issue but since it was closed due to inactivity and there was no response to my question I open this new issue.
I started having this issue when I tried upgrading from 12.3.0 to 13.6.0.
The screenshots that Gitlab CI produces are the same with the old ones but when I run it locally they have this issue.
I tried the different image versions including custom build that @mjhenkes suggested, but the issue persisted. I went through the
factory
directory history but I couldn't find anything that would point to this issue either. Would the new images use the fonts from the environment that they are build or something like this?As a workaround, I still use
12.3.0
locally and12.17.0
on CI as this is the first image that use Node 18+ which some of my dependencies (Vite plugins) require it. But since this is a temporary workaround and eventually I would need to use higher version of Node I would like to find a solution.I asked my colleagues to test it and they had the same issue. We all have Macbook (Apple M1 - macOS 14.3).
Originally posted by @sevilyilmaz in #885 (comment)
The text was updated successfully, but these errors were encountered: