-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to the task processing API #13115
Comments
@julien-nc we have a bit of a problem here. Translating chat messagesWe need OCS APIs as our mobile and desktop clients are calling it, and they should "respond" with it and not be delegated to a background job (No one will wait 5 minutes on the translation of a chat message). Transcription of call recordingsCan be done in a background job, should be fine (we do that now as well as far as I know) |
Also the API endpoints in https://github.com/nextcloud/server/blob/bc5c0262af3cd375620d6534353a3842149ad6ab/core/Controller/TranslationApiController.php are not marked as |
If the provider is an exApp, it will process tasks ASAP, no delay. If the provider is a Php app and Once the task is scheduled, the clients can poll it with |
So instead of getting a string returned the clients shall DOS the server. |
We can also keep the providers for the old APIs in integration_openai and the features in Talk are not broken. |
I will check with Andy next week what to do. |
Two things should make it more convenient:
All this is in stable30 already. The providers for the Translate API and the TaskProcessing API are implemented in different apps so you can keep using the Translate API as long as you want. |
Translation and SpeechToText backend APIs are deprecated. Those features are now included in the task processing API (since 30).
The old APIs will stay a few more NC major version. The old SpeechToText API can now use the new providers (for TaskProcessing) so there is no rush to migrate.
The providers for the Translate API and the translation providers for the TaskProcessing API can be installed side by side so there is no rush to migrate there either.
Translation
You can use the assistant's UI to run translation tasks in the UI. If the assistant app is enabled, the
OCA.Assistant.openAssistantForm
function should be available.The promise will resolve if the task succeeds, fails or is scheduled for later by the user. The promise result is the task object.
The
closeOnResult
parameter ofOCA.Assistant.openAssistantForm
decides if the assistant is closed when the task succeeds of fails. It can be false to stay close to the current behaviour of the translate modal in Talk. The user sees the result in the assistant and there is a "copy" button. The user can then close the assistant modal.SpeechToText
Transcription can be done with the
core:audio2text
task type of the taskProcessing API. More details on how to run such task in the backend in theTranscribe
section of nextcloud/assistant#114The text was updated successfully, but these errors were encountered: