There are core endpoints doing possibly long jobs, for example:
change of llm
change of embedder
plugin install/uninstall
plugin toggle
rabbithole file/url/memories
At the moment their behaviour is inconsistent, as some of them are sync (client gets response when job is finished) and some are async (client gets response immediately and gets a websocket notification when job is finished).
We should devise a common behaviour so clients (and first of all the admin) are offered a consistent interface.
After that we can align the admin so it auto refreshes its stores when such endpoints are finished with their job (e.g. no need to manually refresh after uploading a plugin or a memory)
This issue should be tackled after those endpoints are aligned in core, see here
There are core endpoints doing possibly long jobs, for example:
At the moment their behaviour is inconsistent, as some of them are sync (client gets response when job is finished) and some are async (client gets response immediately and gets a websocket notification when job is finished).
We should devise a common behaviour so clients (and first of all the admin) are offered a consistent interface. After that we can align the admin so it auto refreshes its stores when such endpoints are finished with their job (e.g. no need to manually refresh after uploading a plugin or a memory)
This issue should be tackled after those endpoints are aligned in core, see here