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
It looks like many duplicated requests to /api/foods and /api/units are made from the front end (when ingredient data is loaded) when you click into the recipe edit button on a recipe page. The first couple respond effectively instantly; the rest take 60 seconds/1 minute to either respond with 200 OK or 500 Internal Server Error.
However, any other actions (that need the server) on the page are blocked until these replies are received.
Steps to Reproduce
Go to the demo site
Make sure food and unit information is already populated
I thought it may have been my reverse proxy (Caddy), but since it's appearing on the demo site too it's unlikely this is a misconfiguration on my side. Browser Firefox 115.0.2 (64-bit) on Ubuntu.
The text was updated successfully, but these errors were encountered:
It looks like there's one pair of /api/units + /api/foods calls made per ingredient in the recipe editor. In the case of the recipe in the steps to reproduce, there's 13 ingredients so a total of 26 API calls.
First Check
What is the issue you are experiencing?
It looks like many duplicated requests to
/api/foods
and/api/units
are made from the front end (when ingredient data is loaded) when you click into the recipe edit button on a recipe page. The first couple respond effectively instantly; the rest take 60 seconds/1 minute to either respond with200 OK
or500 Internal Server Error
.However, any other actions (that need the server) on the page are blocked until these replies are received.
Steps to Reproduce
Please provide relevant logs
There aren't any relevant logs on my own install, and I don't have access to the logs from the demo site.
Mealie Version
Self-hosted: v1.3.2 / b54cdf6
Demo site: nightly / e84e5e2
Deployment
Docker (Linux)
Additional Deployment Details
I thought it may have been my reverse proxy (Caddy), but since it's appearing on the demo site too it's unlikely this is a misconfiguration on my side. Browser Firefox 115.0.2 (64-bit) on Ubuntu.
The text was updated successfully, but these errors were encountered: