notifications  

Messages by Thread

• • Re: [PR] fix(frontend, v1.2): remove the clear button from the dataset version picker [texera] via GitHub
  • Re: [PR] fix(frontend, v1.2): remove the clear button from the dataset version picker [texera] via GitHub
• [PR] fix(sklearn, v1.2): rename SVR shrinking parameter [texera] via GitHub
  • Re: [PR] fix(sklearn, v1.2): rename SVR shrinking parameter [texera] via GitHub
  • Re: [PR] fix(sklearn, v1.2): rename SVR shrinking parameter [texera] via GitHub
  • Re: [PR] fix(sklearn, v1.2): rename SVR shrinking parameter [texera] via GitHub
• Re: [I] The SVM Regressor trainer offers a hyperparameter named `probability`, which sets `shrinking` instead [texera] via GitHub
• [I] feat(workflow-form): render the exposed inputs and write values back [texera] via GitHub
  • Re: [I] feat(workflow-form): render the exposed inputs and write values back [texera] via GitHub
  • Re: [I] feat(workflow-form): render the exposed inputs and write values back [texera] via GitHub
  • Re: [I] feat(workflow-form): render the exposed inputs and write values back [texera] via GitHub
• [PR] test(verify): run the source operators, and report what is covered [texera] via GitHub
  • Re: [PR] test(verify): run the source operators, and report what is covered [texera] via GitHub
  • Re: [PR] test(verify): run the source operators, and report what is covered [texera] via GitHub
• [PR] feat(visualization): export the charts that draw over a table's columns [texera] via GitHub
  • Re: [PR] feat(visualization): export the charts that draw over a table's columns [texera] via GitHub
  • Re: [PR] feat(visualization): export the charts that draw over a table's columns [texera] via GitHub
  • Re: [PR] feat(visualization): export the charts that draw over a table's columns [texera] via GitHub
  • Re: [PR] feat(visualization): export the charts that draw over a table's columns [texera] via GitHub
  • Re: [PR] feat(visualization): export the charts that draw over a table's columns [texera] via GitHub
• [PR] test(verify): hand-write the configurations a schema cannot describe [texera] via GitHub
  • Re: [PR] test(verify): hand-write the configurations a schema cannot describe [texera] via GitHub
  • Re: [PR] test(verify): hand-write the configurations a schema cannot describe [texera] via GitHub
  • Re: [PR] test(verify): hand-write the configurations a schema cannot describe [texera] via GitHub
• [PR] feat(visualization): export the tables, ranges and embedded documents [texera] via GitHub
  • Re: [PR] feat(visualization): export the tables, ranges and embedded documents [texera] via GitHub
  • Re: [PR] feat(visualization): export the tables, ranges and embedded documents [texera] via GitHub
  • Re: [PR] feat(visualization): export the tables, ranges and embedded documents [texera] via GitHub
  • Re: [PR] feat(visualization): export the tables, ranges and embedded documents [texera] via GitHub
• [PR] test(verify): run the script the export produces [texera] via GitHub
  • Re: [PR] test(verify): run the script the export produces [texera] via GitHub
  • Re: [PR] test(verify): run the script the export produces [texera] via GitHub
  • Re: [PR] test(verify): run the script the export produces [texera] via GitHub
  • Re: [PR] test(verify): run the script the export produces [texera] via GitHub
  • Re: [PR] test(verify): run the script the export produces [texera] via GitHub
  • Re: [PR] test(verify): run the script the export produces [texera] via GitHub
  • Re: [PR] test(verify): run the script the export produces [texera] via GitHub
• [PR] feat(machine-learning): export the Machine Learning Scorer [texera] via GitHub
  • Re: [PR] feat(machine-learning): export the Machine Learning Scorer [texera] via GitHub
  • Re: [PR] feat(machine-learning): export the Machine Learning Scorer [texera] via GitHub
  • Re: [PR] feat(machine-learning): export the Machine Learning Scorer [texera] via GitHub
• [PR] test(verify): run a Python operator the way the engine runs it [texera] via GitHub
  • Re: [PR] test(verify): run a Python operator the way the engine runs it [texera] via GitHub
  • Re: [PR] test(verify): run a Python operator the way the engine runs it [texera] via GitHub
  • Re: [PR] test(verify): run a Python operator the way the engine runs it [texera] via GitHub
  • Re: [PR] test(verify): run a Python operator the way the engine runs it [texera] via GitHub
  • Re: [PR] test(verify): run a Python operator the way the engine runs it [texera] via GitHub
  • Re: [PR] test(verify): run a Python operator the way the engine runs it [texera] via GitHub
  • Re: [PR] test(verify): run a Python operator the way the engine runs it [texera] via GitHub
  • Re: [PR] test(verify): run a Python operator the way the engine runs it [texera] via GitHub
• [PR] test(verify): compare what the two paths produced [texera] via GitHub
  • Re: [PR] test(verify): compare what the two paths produced [texera] via GitHub
  • Re: [PR] test(verify): compare what the two paths produced [texera] via GitHub
  • Re: [PR] test(verify): compare what the two paths produced [texera] via GitHub
  • Re: [PR] test(verify): compare what the two paths produced [texera] via GitHub
  • Re: [PR] test(verify): compare what the two paths produced [texera] via GitHub
  • Re: [PR] test(verify): compare what the two paths produced [texera] via GitHub
  • Re: [PR] test(verify): compare what the two paths produced [texera] via GitHub
• [PR] feat(operator): export the estimators and the Hugging Face models [texera] via GitHub
  • Re: [PR] feat(operator): export the estimators and the Hugging Face models [texera] via GitHub
  • Re: [PR] feat(operator): export the estimators and the Hugging Face models [texera] via GitHub
  • Re: [PR] feat(operator): export the estimators and the Hugging Face models [texera] via GitHub
  • Re: [PR] feat(operator): export the estimators and the Hugging Face models [texera] via GitHub
  • Re: [PR] feat(operator): export the estimators and the Hugging Face models [texera] via GitHub
  • Re: [PR] feat(operator): export the estimators and the Hugging Face models [texera] via GitHub
  • Re: [PR] feat(operator): export the estimators and the Hugging Face models [texera] via GitHub
• [PR] test(verify): run every operator both ways and report what it did [texera] via GitHub
  • Re: [PR] test(verify): run every operator both ways and report what it did [texera] via GitHub
  • Re: [PR] test(verify): run every operator both ways and report what it did [texera] via GitHub
  • Re: [PR] test(verify): run every operator both ways and report what it did [texera] via GitHub
  • Re: [PR] test(verify): run every operator both ways and report what it did [texera] via GitHub
• [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
  • Re: [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
  • Re: [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
  • Re: [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
  • Re: [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
  • Re: [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
  • Re: [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
  • Re: [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
  • Re: [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
  • Re: [PR] test(verify): run an operator through the engine and keep what it wrote [texera] via GitHub
• [PR] build: read the fork options once, outside the grouping loop [texera] via GitHub
  • Re: [PR] build: read the fork options once, outside the grouping loop [texera] via GitHub
  • Re: [PR] build: read the fork options once, outside the grouping loop [texera] via GitHub
  • Re: [PR] build: read the fork options once, outside the grouping loop [texera] via GitHub
  • Re: [PR] build: read the fork options once, outside the grouping loop [texera] via GitHub
• [PR] test(verify): give every operator the same table to read [texera] via GitHub
  • Re: [PR] test(verify): give every operator the same table to read [texera] via GitHub
  • Re: [PR] test(verify): give every operator the same table to read [texera] via GitHub
  • Re: [PR] test(verify): give every operator the same table to read [texera] via GitHub
• [PR] test(verify): derive an operator's configuration from its schema [texera] via GitHub
  • Re: [PR] test(verify): derive an operator's configuration from its schema [texera] via GitHub
  • Re: [PR] test(verify): derive an operator's configuration from its schema [texera] via GitHub
  • Re: [PR] test(verify): derive an operator's configuration from its schema [texera] via GitHub
• Re: [I] Remove the deprecated project feature from the backend and database schema [texera] via GitHub
• [PR] ci: record the typing-extensions version that is actually installed [texera] via GitHub
  • Re: [PR] ci: record the typing-extensions version that is actually installed [texera] via GitHub
  • Re: [PR] ci: record the typing-extensions version that is actually installed [texera] via GitHub
  • Re: [PR] ci: record the typing-extensions version that is actually installed [texera] via GitHub
  • Re: [PR] ci: record the typing-extensions version that is actually installed [texera] via GitHub
  • Re: [PR] ci: record the typing-extensions version that is actually installed [texera] via GitHub
  • Re: [PR] ci: record the typing-extensions version that is actually installed [texera] via GitHub
  • Re: [PR] ci: record the typing-extensions version that is actually installed [texera] via GitHub
• [I] A version pinned in requirements.txt is not binding on the passes that follow it [texera] via GitHub
  • Re: [I] A version pinned in requirements.txt is not binding on the passes that follow it [texera] via GitHub
  • Re: [I] A version pinned in requirements.txt is not binding on the passes that follow it [texera] via GitHub
• [I] Dataset, model, and project revoke endpoints return HTTP 500 for an unregistered email [texera] via GitHub
  • Re: [I] Dataset, model, and project revoke endpoints return HTTP 500 for an unregistered email [texera] via GitHub
  • Re: [I] Dataset, model, and project revoke endpoints return HTTP 500 for an unregistered email [texera] via GitHub
• Re: [PR] feat(operator): give a trainer's hyperparameter value the constraint its parameter implies [texera] via GitHub
  • Re: [PR] feat(operator): give a trainer's hyperparameter value the constraint its parameter implies [texera] via GitHub
• Re: [PR] feat(treeplot): lay out the tree without igraph [texera] via GitHub
  • Re: [PR] feat(treeplot): lay out the tree without igraph [texera] via GitHub
• Re: [PR] feat(gui): gate workflow execution on the compilation state [texera] via GitHub
  • Re: [PR] feat(gui): gate workflow execution on the compilation state [texera] via GitHub
• Re: [PR] feat(workflow-operator): answer the filter on an empty cell instead of throwing [texera] via GitHub
  • Re: [PR] feat(workflow-operator): answer the filter on an empty cell instead of throwing [texera] via GitHub
• Re: [PR] feat(huggingface): keep the row on an empty petal measurement [texera] via GitHub
  • Re: [PR] feat(huggingface): keep the row on an empty petal measurement [texera] via GitHub
• Re: [PR] feat(sklearn): refuse the label column as an input column [texera] via GitHub
  • Re: [PR] feat(sklearn): refuse the label column as an input column [texera] via GitHub
• Re: [PR] feat(contour-plot): say what it cannot contour instead of ending the run [texera] via GitHub
  • Re: [PR] feat(contour-plot): say what it cannot contour instead of ending the run [texera] via GitHub
• [PR] Title: feat(frontend): gate the file tree's delete and cover controls on write access [texera] via GitHub
  • Re: [PR] Title: feat(frontend): gate the file tree's delete and cover controls on write access [texera] via GitHub
  • Re: [PR] feat(frontend): gate the file tree's delete and cover controls on write access [texera] via GitHub
  • Re: [PR] feat(frontend): gate the file tree's delete and cover controls on write access [texera] via GitHub
• [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
• Re: [PR] fix(workflow-operator): read chat-provider responses for the image question-answering tasks [texera] via GitHub
  • Re: [PR] fix(workflow-operator): read chat-provider responses for the image question-answering tasks [texera] via GitHub
  • Re: [PR] fix(workflow-operator): read chat-provider responses for the image question-answering tasks [texera] via GitHub
  • Re: [PR] fix(workflow-operator): read chat-provider responses for the image question-answering tasks [texera] via GitHub
  • Re: [PR] fix(workflow-operator): read chat-provider responses for the image question-answering tasks [texera] via GitHub
  • Re: [PR] fix(workflow-operator): read chat-provider responses for the image question-answering tasks [texera] via GitHub
• [PR] feat(gui): offer a workflow as a Python script [texera] via GitHub
  • Re: [PR] feat(gui): offer a workflow as a Python script [texera] via GitHub
  • Re: [PR] feat(gui): offer a workflow as a Python script [texera] via GitHub
  • Re: [PR] feat(gui): export a workflow as Python, and read the schema's constraints in the panel [texera] via GitHub
  • Re: [PR] feat(gui): export a workflow as Python, and read the schema's constraints in the panel [texera] via GitHub
  • Re: [PR] feat(gui): export a workflow as Python, and read the schema's constraints in the panel [texera] via GitHub
  • Re: [PR] feat(gui): export a workflow as Python, and read the schema's constraints in the panel [texera] via GitHub
  • Re: [PR] feat(gui): export a workflow as Python, and read the schema's constraints in the panel [texera] via GitHub
  • Re: [PR] feat(gui): export a workflow as Python, and read the schema's constraints in the panel [texera] via GitHub
  • Re: [PR] feat(gui): export a workflow as Python, and read the schema's constraints in the panel [texera] via GitHub
  • Re: [PR] feat(gui): export a workflow as Python, and read the schema's constraints in the panel [texera] via GitHub
• [I] READ-only collaborators are offered delete and "Set as cover" controls they cannot use [texera] via GitHub
  • Re: [I] READ-only collaborators are offered delete and "Set as cover" controls they cannot use [texera] via GitHub
  • Re: [I] READ-only collaborators are offered delete and "Set as cover" controls they cannot use [texera] via GitHub
• [PR] feat(operator): export the machine-learning operators as Python [texera] via GitHub
  • Re: [PR] feat(operator): export the machine-learning operators as Python [texera] via GitHub
  • Re: [PR] feat(operator): export the machine-learning operators as Python [texera] via GitHub
  • Re: [PR] feat(operator): export the machine-learning operators as Python [texera] via GitHub
  • Re: [PR] feat(machine-learning): export the four advanced trainers [texera] via GitHub
• [PR] fix(frontend): refresh a dataset's paths after a rename, and block re… [texera] via GitHub
  • Re: [PR] fix(frontend): refresh a dataset's paths after a rename, and block re… [texera] via GitHub
  • Re: [PR] fix(frontend): refresh a dataset's paths after a rename, and block re… [texera] via GitHub
  • Re: [PR] fix(frontend): refresh a dataset's paths after a rename, and block renaming mid-upload [texera] via GitHub
  • Re: [PR] fix(frontend): refresh a dataset's paths after a rename, and block renaming mid-upload [texera] via GitHub
  • Re: [PR] fix(frontend): refresh a dataset's paths after a rename, and block renaming mid-upload [texera] via GitHub
  • Re: [PR] fix(frontend): refresh a dataset's paths after a rename, and block renaming mid-upload [texera] via GitHub
• [PR] feat(visualization): export the coordinate-system and domain plots as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the coordinate-system and domain plots as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the coordinate-system and domain plots as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the coordinate-system and domain plots as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the coordinate-system and domain plots as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the coordinate-system and domain plots as Python [texera] via GitHub
• [I] Renaming a dataset leaves its file tree and Data Card pointing at the old name [texera] via GitHub
  • Re: [I] Renaming a dataset leaves its file tree and Data Card pointing at the old name [texera] via GitHub
  • Re: [I] Renaming a dataset leaves its file tree and Data Card pointing at the old name [texera] via GitHub
• [PR] feat(visualization): export the table and relation charts as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the table and relation charts as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the table and relation charts as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the table and relation charts as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the hierarchy and graph charts as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the hierarchy and graph charts as Python [texera] via GitHub
  • Re: [PR] feat(visualization): export the hierarchy and graph charts as Python [texera] via GitHub
• [PR] fix(frontend): remove the clear button from the dataset version picker [texera] via GitHub
  • Re: [PR] fix(frontend): remove the clear button from the dataset version picker [texera] via GitHub
  • Re: [PR] fix(frontend): remove the clear button from the dataset version picker [texera] via GitHub
  • Re: [PR] fix(frontend): remove the clear button from the dataset version picker [texera] via GitHub
  • Re: [PR] fix(frontend): remove the clear button from the dataset version picker [texera] via GitHub
  • Re: [PR] fix(frontend): remove the clear button from the dataset version picker [texera] via GitHub
  • Re: [PR] fix(frontend): remove the clear button from the dataset version picker [texera] via GitHub
• Re: [PR] fix(gui): only offer Hugging Face tasks the operator can run [texera] via GitHub
• Re: [I] HuggingFace inference operator: task dropdown offers tasks with no codegen, which silently fall back to text-gen and emit raw JSON [texera] via GitHub
• [I] Clearing the version selector on a dataset's detail page throws a TypeError [texera] via GitHub
  • Re: [I] Clearing the version selector on a dataset's detail page throws a TypeError [texera] via GitHub
  • Re: [I] Clearing the version selector on a dataset's detail page throws a TypeError [texera] via GitHub
• [PR] feat(workflow-operator): export the source operators as Python [texera] via GitHub
  • Re: [PR] feat(workflow-operator): export the source operators as Python [texera] via GitHub
  • Re: [PR] feat(workflow-operator): export the source operators as Python [texera] via GitHub
  • Re: [PR] feat(workflow-operator): export the source operators as Python [texera] via GitHub

• Earlier messages
• Later messages