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
Whenever I try to generate Icons (either by preset or by custom colours) wait won't show up. The same will sometimes happen to other shapes as well seemingly at random.
Looking up things in the console, these are the errors I am getting:
A 504 for GET https://bibata.vercel.app/api/svg/img:7039102c-89c6-4c66-b5ac-aaa2b5ed2611:1.0.0-alpha.0?color=...
Wow, I never expected an early users for this project. Thanks for the review.
Bibata is still in the early stages of development and is hosted on Vercel. I'm currently on the free tier on vercel, so the number of requests on the Redis and PostgreSQL databases is limited until I subscribe to Pro Account. Additionally, Next.js API functions defaults to timeouts after 10 seconds on 'nodejs' runtime. and /api/svg/[id] takes a while to fetch image URLs from Figma and process them, especially since the animation cursor has approximately 110 images, causing a delay in loading. I'll push some PRs to fix
this issue soon.
Also, the cursor package itself has some missing cursors, which I am currently redesigning. The hotspots are not correctly placed yet, and there are some issues with Windows cursors, such as ful1e5/Bibata_Cursor#154, which still exists because the build process is handled by clickgen, and the fix has not been pushed yet.
So, please be careful while playing and installing it until the stable version is released.
Whenever I try to generate Icons (either by preset or by custom colours)
wait
won't show up. The same will sometimes happen to other shapes as well seemingly at random.Looking up things in the console, these are the errors I am getting:
504
forGET https://bibata.vercel.app/api/svg/img:7039102c-89c6-4c66-b5ac-aaa2b5ed2611:1.0.0-alpha.0?color=...
Unable to fetch 'wait'
(thrown here: 472-88bd18eb4f2c84ee.js:1:3763)Browser: Firefox 120.0 and Chromium 119.0.6045.159 (both on Debian 12)
The text was updated successfully, but these errors were encountered: