notifications  

Messages by Thread

• • Re: [PR] test(agent-service): drive sendMessage with a stand-in language model [texera] via GitHub
  • Re: [PR] test(agent-service): drive sendMessage with a stand-in language model [texera] via GitHub
• [I] Drive TexeraAgent.sendMessage with a stand-in language model [texera] via GitHub
  • Re: [I] Drive TexeraAgent.sendMessage with a stand-in language model [texera] via GitHub
  • Re: [I] Drive TexeraAgent.sendMessage with a stand-in language model [texera] via GitHub
• [I] A falsy throw from the model makes sendMessage reject instead of reporting an error step [texera] via GitHub
  • Re: [I] A falsy throw from the model makes sendMessage reject instead of reporting an error step [texera] via GitHub
  • Re: [I] A falsy throw from the model makes sendMessage reject instead of reporting an error step [texera] via GitHub
  • Re: [I] A falsy throw from the model makes sendMessage reject instead of reporting an error step [texera] via GitHub
• [I] maxSteps of 0 silently disables the agent's step cap [texera] via GitHub
  • Re: [I] maxSteps of 0 silently disables the agent's step cap [texera] via GitHub
  • Re: [I] maxSteps of 0 silently disables the agent's step cap [texera] via GitHub
• Re: [PR] chore(amber): remove the fully commented-out PythonWorkflowWorkerSpec [texera] via GitHub
  • Re: [PR] chore(amber): remove the fully commented-out PythonWorkflowWorkerSpec [texera] via GitHub
  • Re: [PR] chore(amber): remove the fully commented-out PythonWorkflowWorkerSpec [texera] via GitHub
• Re: [I] Bubble Chart's Color-Column is required even though it is only used when Enable Color is on [texera] via GitHub
• Re: [PR] feat(workflow-operator): stop forcing a color column on every Bubble Chart [texera] via GitHub
• [PR] chore(deps, pyright-language-service): update dependency ws to v8.21.3 [texera] via GitHub
  • Re: [PR] chore(deps, pyright-language-service): update dependency ws to v8.21.3 [texera] via GitHub
  • Re: [PR] chore(deps, pyright-language-service): update dependency ws to v8.21.3 [texera] via GitHub
  • Re: [PR] chore(deps, pyright-language-service): update dependency ws to v8.21.3 [texera] via GitHub
• [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
• Re: [I] Render the dataset list item's permission gates [texera] via GitHub
• Re: [I] Cover ExecutionConsoleService's console routing and debug commands [texera] via GitHub
• Re: [PR] test(amber): cover ExecutionConsoleService's console routing and debug commands [texera] via GitHub
• Re: [PR] test(frontend): render the dataset list item's permission gates [texera] via GitHub
  • Re: [PR] test(frontend): render the dataset list item's permission gates [texera] via GitHub
• Re: [I] add unit test coverage for CoordinatorTimerService [texera] via GitHub
• [PR] test(frontend): drive the virtual-environment socket [texera] via GitHub
  • Re: [PR] test(frontend): drive the virtual-environment socket [texera] via GitHub
  • Re: [PR] test(frontend): drive the virtual-environment socket [texera] via GitHub
  • Re: [PR] test(frontend): drive the virtual-environment socket [texera] via GitHub
• [PR] test(frontend): cover the link-breakpoint handlers in the workflow editor [texera] via GitHub
  • Re: [PR] test(frontend): cover the link-breakpoint handlers in the workflow editor [texera] via GitHub
  • Re: [PR] test(frontend): cover the link-breakpoint handlers in the workflow editor [texera] via GitHub
  • Re: [PR] test(frontend): cover the link-breakpoint handlers in the workflow editor [texera] via GitHub
• [PR] test(amber): pin the dataset search's access-control branches [texera] via GitHub
  • Re: [PR] test(amber): pin the dataset search's access-control branches [texera] via GitHub
  • Re: [PR] test(amber): pin the dataset search's access-control branches [texera] via GitHub
  • Re: [PR] test(amber): pin the dataset search's access-control branches [texera] via GitHub
  • Re: [PR] test(amber): pin the dataset search's access-control branches [texera] via GitHub
• [I] Drive the virtual-environment socket in the computing-unit selector [texera] via GitHub
  • Re: [I] Drive the virtual-environment socket in the computing-unit selector [texera] via GitHub
  • Re: [I] Drive the virtual-environment socket in the computing-unit selector [texera] via GitHub
• [I] Cover the link-breakpoint handlers in the workflow editor [texera] via GitHub
  • Re: [I] Cover the link-breakpoint handlers in the workflow editor [texera] via GitHub
  • Re: [I] Cover the link-breakpoint handlers in the workflow editor [texera] via GitHub
• [I] Pin the dataset search's access-control branches [texera] via GitHub
  • Re: [I] Pin the dataset search's access-control branches [texera] via GitHub
  • Re: [I] Pin the dataset search's access-control branches [texera] via GitHub
• Re: [PR] test(amber): add unit test coverage for CoordinatorTimerService [texera] via GitHub
  • Re: [PR] test(amber): add unit test coverage for CoordinatorTimerService [texera] via GitHub
• Re: [I] Feature Request: Try/Catch/Finally control blocks for workflows [texera] via GitHub
  • Re: [I] Feature Request: Try/Catch/Finally control blocks for workflows [texera] via GitHub
  • Re: [I] Feature Request: Try/Catch/Finally control blocks for workflows [texera] via GitHub
• Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
  • Re: [PR] feat(computing-unit): out-of-pod dataset mount infrastructure [texera] via GitHub
• [PR] fix(workflow-operator): accept single-segment HF model IDs and reject '..' in the model-id check [texera] via GitHub
  • Re: [PR] fix(workflow-operator): accept single-segment HF model IDs and reject '..' in the model-id check [texera] via GitHub
  • Re: [PR] fix(workflow-operator): accept single-segment HF model IDs and reject '..' in the model-id check [texera] via GitHub
  • Re: [PR] fix(workflow-operator): accept single-segment HF model IDs and reject '..' in the model-id check [texera] via GitHub
  • Re: [PR] fix(workflow-operator): accept single-segment HF model IDs and reject '..' in the model-id check [texera] via GitHub
  • Re: [PR] fix(workflow-operator): accept single-segment HF model IDs and reject '..' in the model-id check [texera] via GitHub
  • Re: [PR] fix(workflow-operator): accept single-segment HF model IDs and reject '..' in the model-id check [texera] via GitHub
• Re: [PR] fix(workflow-operator): report a clear error when a configured HF image/audio column is missing [texera] via GitHub
  • Re: [PR] fix(workflow-operator): report a clear error when a configured HF image/audio column is missing [texera] via GitHub
  • Re: [PR] fix(workflow-operator): report a clear error when a configured HF image/audio column is missing [texera] via GitHub
  • Re: [PR] fix(workflow-operator): report a clear error when a configured HF image/audio column is missing [texera] via GitHub
• Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
• Re: [I] Document PR title conventions for feat vs fix, tests, dependency bumps, and backports [texera] via GitHub
• Re: [PR] docs: define how to pick a PR title's type and scope [texera] via GitHub
  • Re: [PR] docs: define how to pick a PR title's type and scope [texera] via GitHub
  • Re: [PR] docs: define how to pick a PR title's type and scope [texera] via GitHub
  • Re: [PR] docs: define how to pick a PR title's type and scope [texera] via GitHub
• [I] extend DatasetFileSelectorComponent template coverage [texera] via GitHub
  • Re: [I] extend DatasetFileSelectorComponent template coverage [texera] via GitHub
• [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
  • Re: [PR] feat(storage): warehouse REST API, Lakekeeper client, and per-execution injection [texera] via GitHub
• [PR] test(frontend): extend DatasetFileSelectorComponent template coverage [texera] via GitHub
  • Re: [PR] test(frontend): extend DatasetFileSelectorComponent template coverage [texera] via GitHub
  • Re: [PR] test(frontend): extend DatasetFileSelectorComponent template coverage [texera] via GitHub
  • Re: [PR] test(frontend): extend DatasetFileSelectorComponent template coverage [texera] via GitHub
• [PR] test(frontend): extend TimeTravelComponent template coverage [texera] via GitHub
  • Re: [PR] test(frontend): extend TimeTravelComponent template coverage [texera] via GitHub
  • Re: [PR] test(frontend): extend TimeTravelComponent template coverage [texera] via GitHub
  • Re: [PR] test(frontend): extend TimeTravelComponent template coverage [texera] via GitHub
• [PR] test(frontend): render the TypeCastingDisplay schema table for coverage [texera] via GitHub
  • Re: [PR] test(frontend): render the TypeCastingDisplay schema table for coverage [texera] via GitHub
  • Re: [PR] test(frontend): render the TypeCastingDisplay schema table for coverage [texera] via GitHub
  • Re: [PR] test(frontend): render the TypeCastingDisplay schema table for coverage [texera] via GitHub
• [PR] test(frontend): cover HuggingFaceImageUploadComponent template preview and error states [texera] via GitHub
  • Re: [PR] test(frontend): cover HuggingFaceImageUploadComponent template preview and error states [texera] via GitHub
  • Re: [PR] test(frontend): cover HuggingFaceImageUploadComponent template preview and error states [texera] via GitHub
  • Re: [PR] test(frontend): cover HuggingFaceImageUploadComponent template preview and error states [texera] via GitHub
• [I] extend TimeTravelComponent template coverage [texera] via GitHub
  • Re: [I] extend TimeTravelComponent template coverage [texera] via GitHub
  • Re: [I] extend TimeTravelComponent template coverage [texera] via GitHub
• [I] extend TypeCastingDisplayComponent template coverage [texera] via GitHub
  • Re: [I] extend TypeCastingDisplayComponent template coverage [texera] via GitHub
• [I] extend HuggingFaceImageUploadComponent template coverage [texera] via GitHub
  • Re: [I] extend HuggingFaceImageUploadComponent template coverage [texera] via GitHub
• Re: [I] [BYO-S3] Schema: user_warehouse [texera] via GitHub
• Re: [I] Render the dataset explorer's toolbar and upload panel [texera] via GitHub
• Re: [PR] test(frontend): render the dataset explorer's toolbar and upload panel [texera] via GitHub
• Re: [I] Render the drag-and-drop repeat section's rows [texera] via GitHub
• Re: [PR] feat(storage): add the user_warehouse table schema [texera] via GitHub
  • Re: [PR] feat(storage): add the user_warehouse table schema [texera] via GitHub
  • Re: [PR] feat(storage): add the user_warehouse table schema [texera] via GitHub
• Re: [PR] test(frontend): render the drag-and-drop repeat section's rows [texera] via GitHub
• [PR] chore(amber): remove the deprecated project feature and its tables [texera] via GitHub
  • Re: [PR] chore(amber): remove the deprecated project feature and its tables [texera] via GitHub
  • Re: [PR] chore(amber): remove the deprecated project feature and its tables [texera] via GitHub
  • Re: [PR] chore(amber): remove the deprecated project feature and its tables [texera] via GitHub
  • Re: [PR] chore(amber): remove the deprecated project feature and its tables [texera] via GitHub
  • Re: [PR] chore(amber): remove the deprecated project feature and its tables [texera] via GitHub
  • Re: [PR] feat(amber): remove the deprecated project feature and its tables [texera] via GitHub
  • Re: [PR] feat(amber): remove the deprecated project feature and its tables [texera] via GitHub
  • Re: [PR] feat(amber): remove the deprecated project feature and its tables [texera] via GitHub
• [PR] chore(frontend): remove the deprecated project feature [texera] via GitHub
  • Re: [PR] chore(frontend): remove the deprecated project feature [texera] via GitHub
  • Re: [PR] chore(frontend): remove the deprecated project feature [texera] via GitHub
• [I] Browser-mode specs run without coverage, so ~75 tested lines report as uncovered [texera] via GitHub
  • Re: [I] Browser-mode specs run without coverage, so ~75 tested lines report as uncovered [texera] via GitHub
• [I] Remove the deprecated project feature from the backend and database schema [texera] via GitHub
  • Re: [I] Remove the deprecated project feature from the backend and database schema [texera] via GitHub
• [I] Remove the deprecated project feature from the frontend [texera] via GitHub
  • Re: [I] Remove the deprecated project feature from the frontend [texera] via GitHub
• [I] Template coverage does not register for components whose spec calls TestBed.overrideComponent [texera] via GitHub
  • Re: [I] Template coverage does not register for components whose spec calls TestBed.overrideComponent [texera] via GitHub
  • Re: [I] Template coverage does not register for components whose spec calls TestBed.overrideComponent [texera] via GitHub
• [I] Remove two pieces of unreachable code found by mutation testing [texera] via GitHub
  • Re: [I] Remove two pieces of unreachable code found by mutation testing [texera] via GitHub
  • Re: [I] Remove two pieces of unreachable code found by mutation testing [texera] via GitHub
  • Re: [I] Remove two pieces of unreachable code found by mutation testing [texera] via GitHub
• [I] ExecutionConsoleService leaks a non-daemon thread per execution [texera] via GitHub
  • Re: [I] ExecutionConsoleService leaks a non-daemon thread per execution [texera] via GitHub
  • Re: [I] ExecutionConsoleService leaks a non-daemon thread per execution [texera] via GitHub
• [I] SessionState registry is unsynchronized but iterated from cluster and scheduler threads [texera] via GitHub
  • Re: [I] SessionState registry is unsynchronized but iterated from cluster and scheduler threads [texera] via GitHub
  • Re: [I] SessionState registry is unsynchronized but iterated from cluster and scheduler threads [texera] via GitHub
• [I] Dropping a folder on the file uploader reports a file failure that did not happen [texera] via GitHub
  • Re: [I] Dropping a folder on the file uploader reports a file failure that did not happen [texera] via GitHub
  • Re: [I] Dropping a folder on the file uploader reports a file failure that did not happen [texera] via GitHub
• Re: [I] Remove the unused ElidableStatement from the amber engine [texera] via GitHub
• [I] Websocket runtime commands NPE instead of reporting an uninitialized execution [texera] via GitHub
  • Re: [I] Websocket runtime commands NPE instead of reporting an uninitialized execution [texera] via GitHub
  • Re: [I] Websocket runtime commands NPE instead of reporting an uninitialized execution [texera] via GitHub
• Re: [I] Remove the deprecated ExpansionGreedyScheduleGenerator from the amber engine [texera] via GitHub
  • Re: [I] Remove the deprecated ExpansionGreedyScheduleGenerator from the amber engine [texera] via GitHub
• [PR] chore(amber): remove the unused EmptyReplayLogger [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused EmptyReplayLogger [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused EmptyReplayLogger [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused EmptyReplayLogger [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused EmptyReplayLogger [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused EmptyReplayLogger [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused EmptyReplayLogger [texera] via GitHub
• [PR] chore(amber): remove the unused ElidableStatement [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ElidableStatement [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ElidableStatement [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ElidableStatement [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ElidableStatement [texera] via GitHub
• [PR] chore(amber): remove the unused SchemaPropagationResponse [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused SchemaPropagationResponse [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused SchemaPropagationResponse [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused SchemaPropagationResponse [texera] via GitHub

• Later messages