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
If you deploy an altered config/project.yaml file, and then visit /admin you must first sync the changes. That page then internally calls /admin/actions/config-sync/apply-yaml-changes over XHR.
When said call fails (here due to a memory allocation error) the user is not notified of this failure. The page keeps on showing the spinner and the "Applying changes from the config file" text.
It's only when opening the dev tools that one can see the call has actually failed:
It'd be better that the page notifies the user of the failure of the call.
For reference, here's the full error from web.log:
Description
If you deploy an altered
config/project.yaml
file, and then visit/admin
you must first sync the changes. That page then internally calls/admin/actions/config-sync/apply-yaml-changes
over XHR.When said call fails (here due to a memory allocation error) the user is not notified of this failure. The page keeps on showing the spinner and the "Applying changes from the config file" text.
It's only when opening the dev tools that one can see the call has actually failed:
It'd be better that the page notifies the user of the failure of the call.
For reference, here's the full error from
web.log
:Additional info
The text was updated successfully, but these errors were encountered: