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
Aftre installing the app from the appstore I only get the message "No flows found" and there are no workers running. Is there any configuration needed to get it running?
The text was updated successfully, but these errors were encountered:
We have a not very good situation, we did not think that we would ever change the model mapping storage format, because it was the same for all versions from the beginning, - and in the end we had to change it (we want to make feature so that the user can choose the models he wants automatically with the download)
Now in the original repo we have corrected this oversight and now the models for each version are stored separately, and such a situation will not happen in the future.
We will release a working release for Nextcloud next Monday or Tuesday, I will write in this issue after it.
Ok, I managed to update this ExApp locally to run, will update the repository with some optimizations today and the release is scheduled for tomorrow if nothing goes wrong.
The release has been published and should appear in the AppStore within the next 12 hours.
We upgraded the PostgreSQL version but forgot to change the database path and it's too late to re-release, so here's an important note from the changelog:
Please delete the docker volume named nc_app_visionatrix_data or uninstall the previous version of Visionatrix with the Delete data on uninstall flag checked.
If you already uninstalled Visionatrix without the flag checked, just install the latest version and if it gives you the pg_ctl: could not start server error, uninstall it with the flag checked and install it again and it should work.
Aftre installing the app from the appstore I only get the message "No flows found" and there are no workers running. Is there any configuration needed to get it running?
The text was updated successfully, but these errors were encountered: