notifications  

Messages by Thread

• • Re: [I] JointJS papers are never disposed, so every remount leaves one listening to the shared graph [texera] via GitHub
  • Re: [I] JointJS papers are never disposed, so every remount leaves one listening to the shared graph [texera] via GitHub
• [I] How to input table API and output an object? [texera] via GitHub
  • Re: [I] How to input table API and output an object? [texera] via GitHub
• [PR] feat(amber): opt in to least-loaded routing on unconstrained links [texera] via GitHub
  • Re: [PR] feat(amber): opt in to least-loaded routing on unconstrained links [texera] via GitHub
• [I] Exported Sklearn Prediction script fails when the configured ground truth column is missing from the input [texera] via GitHub
  • Re: [I] Exported Sklearn Prediction script fails when the configured ground truth column is missing from the input [texera] via GitHub
  • Re: [I] Exported Sklearn Prediction script fails when the configured ground truth column is missing from the input [texera] via GitHub
  • Re: [I] Exported Sklearn Prediction script fails when the configured ground truth column is missing from the input [texera] via GitHub
• [PR] feat(amber): rank receivers by backlog and steer least-loaded senders [texera] via GitHub
  • Re: [PR] feat(amber): rank receivers by backlog and steer least-loaded senders [texera] via GitHub
• [PR] feat(amber): add least-loaded partitioner and worker backlog statistic [texera] via GitHub
  • Re: [PR] feat(amber): add least-loaded partitioner and worker backlog statistic [texera] via GitHub
• [I] Can the AI bot create a workflow from a script? [texera] via GitHub
• [I] How to output multiple products? [texera] via GitHub
• [I] How to update an environment on dknet-ai? [texera] via GitHub
• [I] Is there any way to import helper functions from a separate file? [texera] via GitHub
  • Re: [I] Is there any way to import helper functions from a separate file? [texera] via GitHub
• [I] Add least-loaded partitioning for links with no partitioning requirement [texera] via GitHub
  • Re: [I] Add least-loaded partitioning for links with no partitioning requirement [texera] via GitHub
• [I] a clean server-side websocket close leaves the workspace marked connected and never reconnects [texera] via GitHub
• [PR] fix(licensing, v1.2): restore the MIT notice on the vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing, v1.2): restore the MIT notice on the vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing, v1.2): restore the MIT notice on the vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing, v1.2): restore the MIT notice on the vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing, v1.2): restore the MIT notice on the vendored inner.py [texera] via GitHub
• [I] one failed request permanently stops the computing-unit list refresh and the selected-unit poll [texera] via GitHub
• [PR] fix(frontend): reconnect the workflow websocket after a clean server-side close [texera] via GitHub
  • Re: [PR] fix(frontend): reconnect the workflow websocket after a clean server-side close [texera] via GitHub
  • Re: [PR] fix(frontend): reconnect the workflow websocket after a clean server-side close [texera] via GitHub
  • Re: [PR] fix(frontend): reconnect the workflow websocket after a clean server-side close [texera] via GitHub
  • Re: [PR] fix(frontend): reconnect the workflow websocket after a clean server-side close [texera] via GitHub
  • Re: [PR] fix(frontend): reconnect the workflow websocket after a clean server-side close [texera] via GitHub
  • Re: [PR] fix(frontend): reconnect the workflow websocket after a clean server-side close [texera] via GitHub
  • Re: [PR] fix(frontend): reconnect the workflow websocket after a clean server-side close [texera] via GitHub
  • Re: [PR] fix(frontend): reconnect the workflow websocket after a clean server-side close [texera] via GitHub
• [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
  • Re: [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
  • Re: [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
  • Re: [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
  • Re: [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
  • Re: [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
  • Re: [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
  • Re: [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
  • Re: [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
  • Re: [PR] fix(frontend): keep the computing-unit refresh and poll alive after a failed request [texera] via GitHub
• [PR] fix(licensing, v1.3): restore the MIT notice on the vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing, v1.3): restore the MIT notice on the vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing, v1.3): restore the MIT notice on the vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing, v1.3): restore the MIT notice on the vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing, v1.3): restore the MIT notice on the vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing, v1.3): restore the MIT notice on the vendored inner.py [texera] via GitHub
• [PR] fix(licensing): use MIT notice on vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing): use MIT notice on vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing): use MIT notice on vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing): use MIT notice on vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing): use MIT notice on vendored inner.py [texera] via GitHub
  • Re: [PR] fix(licensing): use MIT notice on vendored inner.py [texera] via GitHub
• [PR] fix(frontend): hold the Python UDF parameter table's Name and Type cells locked when the panel enables its form group [texera] via GitHub
  • Re: [PR] fix(frontend): hold the Python UDF parameter table's Name and Type cells locked when the panel enables its form group [texera] via GitHub
  • Re: [PR] fix(frontend): hold the Python UDF parameter table's Name and Type cells locked when the panel enables its form group [texera] via GitHub
  • Re: [PR] fix(frontend): hold the Python UDF parameter table's Name and Type cells locked when the panel enables its form group [texera] via GitHub
  • Re: [PR] fix(frontend): hold the Python UDF parameter table's Name and Type cells locked when the panel enables its form group [texera] via GitHub
• [I] A Python UDF's Name and Type parameter cells come back editable on the operator property panel [texera] via GitHub
  • Re: [I] A Python UDF's Name and Type parameter cells come back editable on the operator property panel [texera] via GitHub
• [PR] feat(blog): add a post on ML model support [incubator-texera-site] via GitHub
  • Re: [PR] feat(blog): add a post on ML model support [incubator-texera-site] via GitHub
• [PR] fix(workflow-form): let ui-udf-parameters show the form's renames and hides in its columns, and add a parameter to the card's operator [texera] via GitHub
  • Re: [PR] fix(workflow-form): let ui-udf-parameters show the form's renames and hides in its columns, and add a parameter to the card's operator [texera] via GitHub
  • Re: [PR] fix(workflow-form): let ui-udf-parameters show the form's renames and hides in its columns, and add a parameter to the card's operator [texera] via GitHub
  • Re: [PR] fix(workflow-form): let ui-udf-parameters show the form's renames and hides in its columns, and add a parameter to the card's operator [texera] via GitHub
  • Re: [PR] fix(workflow-form): let ui-udf-parameters show the form's renames and hides in its columns, and add a parameter to the card's operator [texera] via GitHub
  • Re: [PR] fix(workflow-form): let ui-udf-parameters show the form's renames and hides in its columns, and add a parameter to the card's operator [texera] via GitHub
  • Re: [PR] fix(workflow-form): let ui-udf-parameters show the form's renames and hides in its columns, and add a parameter to the card's operator [texera] via GitHub
  • Re: [PR] fix(workflow-form): let ui-udf-parameters show the form's renames and hides in its columns, and add a parameter to the card's operator [texera] via GitHub
• Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
  • Re: [PR] feat(pyamber): hash epoch timestamps on Windows [texera] via GitHub
• Re: [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
  • [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
  • Re: [PR] feat(pyamber): reject non-string state keys [texera] via GitHub
• Re: [PR] feat(pyamber): truncate range double keys [texera] via GitHub
  • Re: [PR] feat(pyamber): truncate range double keys [texera] via GitHub
  • Re: [PR] feat(pyamber): truncate range double keys [texera] via GitHub
• Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
  • Re: [PR] feat(pyamber): keep peek side effect free [texera] via GitHub
• Re: [PR] feat(pyamber): hash binary bytes as signed [texera] via GitHub
  • Re: [PR] feat(pyamber): hash binary bytes as signed [texera] via GitHub
  • Re: [PR] feat(pyamber): hash binary bytes as signed [texera] via GitHub
• Re: [PR] feat(pyamber): validate materialization configuration [texera] via GitHub
  • Re: [PR] feat(pyamber): validate materialization configuration [texera] via GitHub
  • Re: [PR] feat(pyamber): validate materialization configuration [texera] via GitHub
• Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
  • Re: [PR] feat(pyamber): escape state marker collisions [texera] via GitHub
• Re: [PR] feat(pyamber): prevent tuple refinalization [texera] via GitHub
  • Re: [PR] feat(pyamber): prevent tuple refinalization [texera] via GitHub
  • Re: [PR] feat(pyamber): prevent tuple refinalization [texera] via GitHub
• Re: [PR] feat(pyamber): clear flushed shuffle batches [texera] via GitHub
  • Re: [PR] feat(pyamber): clear flushed shuffle batches [texera] via GitHub
  • Re: [PR] feat(pyamber): clear flushed shuffle batches [texera] via GitHub
• Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
  • Re: [PR] feat(pyamber): hash large binary tuples [texera] via GitHub
• Re: [PR] feat(pyamber): hash strings as UTF-16 [texera] via GitHub
  • Re: [PR] feat(pyamber): hash strings as UTF-16 [texera] via GitHub
  • Re: [PR] feat(pyamber): hash strings as UTF-16 [texera] via GitHub
• Re: [PR] feat(pyamber): route range shuffle by receivers [texera] via GitHub
  • Re: [PR] feat(pyamber): route range shuffle by receivers [texera] via GitHub
  • Re: [PR] feat(pyamber): route range shuffle by receivers [texera] via GitHub
• Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
  • Re: [PR] feat(pyamber): read Arrow rows across chunk boundaries [texera] via GitHub
• Re: [PR] ci: smoke-test the computing-unit cluster (master boot + worker join) [texera] via GitHub
  • Re: [PR] ci: smoke-test the computing-unit cluster (master boot + worker join) [texera] via GitHub
  • Re: [PR] ci: smoke-test the computing-unit cluster (master boot + worker join) [texera] via GitHub
• Re: [PR] feat(workflow-operator): validate pie chart name [texera] via GitHub
  • Re: [PR] feat(workflow-operator): validate pie chart name [texera] via GitHub
  • Re: [PR] feat(workflow-operator): validate pie chart name [texera] via GitHub
• Re: [PR] ci: add scala-build prebuild job to share compilation across Scala CI jobs [texera] via GitHub
  • Re: [PR] ci: add scala-build prebuild job to share compilation across Scala CI jobs [texera] via GitHub
• Re: [PR] refactor(sync-execution): migrate agent result contract [texera] via GitHub
  • Re: [PR] refactor(sync-execution): migrate agent result contract [texera] via GitHub
• [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
  • Re: [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
  • Re: [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
  • Re: [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
  • Re: [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
  • Re: [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
  • Re: [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
  • Re: [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
  • Re: [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
  • Re: [PR] fix(workflow-form): rebuild the cards on compilation only when it changed something they show [texera] via GitHub
• [I] fix(workflow-form): the Form View rebuilds every card on every compilation, redrawing its controls, dropping the focus and losing a click [texera] via GitHub
  • Re: [I] fix(workflow-form): the Form View rebuilds every card on every compilation, redrawing its controls, dropping the focus and losing a click [texera] via GitHub
  • Re: [I] fix(workflow-form): the Form View rebuilds every card on every compilation, redrawing its controls, dropping the focus and losing a click [texera] via GitHub
• [PR] feat(workflow-form): render Projection's drag-reorder list in the form, with the drag and a keyboard path [texera] via GitHub
  • Re: [PR] feat(workflow-form): render Projection's drag-reorder list in the form, with the drag and a keyboard path [texera] via GitHub
  • Re: [PR] feat(workflow-form): render Projection's drag-reorder list in the form, with the drag and a keyboard path [texera] via GitHub
  • Re: [PR] feat(workflow-form): render Projection's drag-reorder list in the form, with the drag [texera] via GitHub
  • Re: [PR] feat(workflow-form): render Projection's drag-reorder list in the form, with the drag [texera] via GitHub
  • Re: [PR] feat(workflow-form): render Projection's drag-reorder list in the form, with the drag [texera] via GitHub
  • Re: [PR] feat(workflow-form): render Projection's drag-reorder list in the form, with the drag [texera] via GitHub
  • Re: [PR] feat(workflow-form): render Projection's drag-reorder list in the form, with the drag [texera] via GitHub
  • Re: [PR] feat(workflow-form): render Projection's drag-reorder list in the form, with the drag [texera] via GitHub
• [I] fix(frontend): clicking a port that has no settings opens an empty Property panel [texera] via GitHub

• Earlier messages
• Later messages