Let the agent join the workflow's shared editing and execution session
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 14/100
- Tipo de issue
- Refactorización
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- scala
- Área
- backend, full-stack
Línea de trabajo
Read the agent service's current workflow loading path (the copy it takes when a chat starts) alongside the existing collaboration client the open canvas uses to join the editing room and subscribe to computing-unit execution events; that client is the model for the new shared session client. Then trace how the agent's chat loop consumes execution events and where it would instead apply edits to the shared workflow and summarize deltas for the model. Done means the agent edits the server-saved workflow and sees every execution's events regardless of who started it, verified with two clients (browser plus agent) on one workflow.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Task Summary
Today the agent works on its own copy of the workflow, loaded when the chat starts, and only hears about executions it starts itself. So the user's later edits can be lost, and the agent can't tell why the user's execution failed or came back empty.
Texera already shares edits and executions live: every open canvas joins the workflow's editing room and receives the computing unit's execution events. The agent is the only participant left out. The room has gaps of its own, though. Its server is the stock y-websocket server, which checks no one's access. It runs on Kubernetes and in local development, but single-node starts none, so shared editing does not work there. And every browser loads the workflow into the room when it opens it, and saves the whole workflow five seconds after a change.
This task makes the session the server's, in three parts:
- A session service. It replaces the y-websocket server in every deployment. It checks each person's token and access to the workflow (viewers get a read-only connection), loads the workflow from the Dashboard Service, and saves it shortly after edits stop. Browsers no longer load or save the workflow themselves. The live service of the Texera 2.0 prototype does this on Hocuspocus (MIT) and can be ported. The shared document keeps main's layout, so the Angular app, this service and later the React app read it the same way.
- Reads and edits from the server. The service lets the agent's tools read the workflow as it stands and apply a patch from #9481 as one change, tagged with the user and the chat, so review mode (#9075) can tell the agent's changes apart. The agent shows among the co-editors while it works.
- Executions. A new read of the workflow's current or last execution on its computing unit, whoever started it: its state, each operator's state and row counts, and its errors and console errors. This becomes the
get_executiontool. An execution the agent asks for does not end one that is still going (todaySyncExecutionResourceshuts the previous one down): the tool says who started it, and the agent asks the person first.
With them:
- The agent edits the shared workflow instead of a copy.
- It sees every execution, no matter who started it.
- Its model sees a short summary of what changed at each step.
- The server saves the workflow, so the agent's edits are kept even when no browser is open.
This also settles the open question in #9457 about which copy the agent edits, and makes the browser report in #9423 unnecessary.
Task Type
- Refactor / Cleanup
- DevOps / Deployment / CI
- Testing / QA
- Documentation
- Performance
- Other
- Lenguaje dominante
- Scala
- Estrellas
- 333
- Forks
- 202
- Merge medio
- 3 d 11 h
- PR fusionados (30 d)
- 185
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/texera
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
addOperator returns an error but still adds the operatorPosiblemente ocupada @sunny-kavixo la tomó hace 5 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
apache/texera#9121 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Failed tool calls are marked as succeeded (isError is always false)Posiblemente ocupada @oliarmak-web la tomó hace 14 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
apache/texera#9120 · 8 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
apache/texera#8682 · 5 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de apache/texera
Issues similares
-
? - Needs Triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
NVIDIA/cudf-spark#16937 ·
Los mantenedores suelen responder en 1 día
-
LFST not-issued-store count truncation can incorrectly clear strictShouldWaitPosiblemente ocupada @weidingliu la tomó hoy. Abiertomodule: memory type: bug/reported
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
OpenXiangShan/XiangShan#6974 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 3 días
-
bug indigo
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
PurpleKingdomGames/indigoengine#300 · 1 comentario ·
-
JavaReservoirSampleOperator returns the whole input when the dataset size is unknownPosiblemente ocupada @sasmith-14 la tomó hace 2 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
apache/wayang#884 · 3 comentarios ·
Los mantenedores suelen responder en 2 días
-
AI Generated CI/CD ⚒️ Flaky-tests 🐦 python 🐍
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
valkey-io/valkey-glide#7722 ·
Los mantenedores suelen responder en 1 día