notifications  

Messages by Thread

• [PR] Add August 25, 2026 monthly meeting minutes [incubator-texera-site] via GitHub
  • Re: [PR] Add August 25, 2026 monthly meeting minutes [incubator-texera-site] via GitHub
  • Re: [PR] Add August 25, 2026 monthly meeting minutes [incubator-texera-site] via GitHub
• [PR] feat(frontend): check the attribute type rule on every column a property names [texera] via GitHub
  • Re: [PR] feat(frontend): check the attribute type rule on every column a property names [texera] via GitHub
  • Re: [PR] feat(frontend): check the attribute type rule on every column a property names [texera] via GitHub
  • Re: [PR] feat(frontend): check the attribute type rule on every column a property names [texera] via GitHub
  • Re: [PR] feat(frontend): check the attribute type rule on every column a property names [texera] via GitHub
  • Re: [PR] feat(frontend): check the attribute type rule on every column a property names [texera] via GitHub
• [I] attributeTypeRules is never checked on a property that takes several columns [texera] via GitHub
  • Re: [I] attributeTypeRules is never checked on a property that takes several columns [texera] via GitHub
  • Re: [I] attributeTypeRules is never checked on a property that takes several columns [texera] via GitHub
• [PR] feat(auth): Add email verification to user registration to verify email ownership. [texera] via GitHub
  • Re: [PR] feat(auth): Add email verification to user registration to verify email ownership. [texera] via GitHub
  • Re: [PR] feat(auth): Add email verification to user registration to verify email ownership. [texera] via GitHub
  • Re: [PR] feat(auth): Add email verification to user registration to verify email ownership. [texera] via GitHub
• [I] Add email verification for local login and non-verified account providers. [texera] via GitHub
  • Re: [I] Add email verification for local login and non-verified account providers. [texera] via GitHub
• [PR] ci(frontend): give the Vitest workers a heap limit that actually reaches them [texera] via GitHub
  • Re: [PR] ci(frontend): give the Vitest workers a heap limit that actually reaches them [texera] via GitHub
  • Re: [PR] ci(frontend): give the Vitest workers a heap limit that actually reaches them [texera] via GitHub
  • Re: [PR] ci(frontend): give the Vitest workers a heap limit that actually reaches them [texera] via GitHub
  • Re: [PR] ci(frontend): size the Vitest workers' heap, which the runner default under-provisions [texera] via GitHub
• [I] frontend: the macOS test leg dies on a V8 heap OOM — the configured 8 GB never reaches the Vitest workers [texera] via GitHub
  • Re: [I] frontend: the macOS test leg dies on a V8 heap OOM — the configured 8 GB never reaches the Vitest workers [texera] via GitHub
  • Re: [I] frontend: the macOS test leg dies on a V8 heap OOM — the Vitest workers' heap is never configured [texera] via GitHub
• [I] Waterfall Chart consumes the last data row as its total bar, so that row's value is never plotted [texera] via GitHub
  • Re: [I] Waterfall Chart consumes the last data row as its total bar, so that row's value is never plotted [texera] via GitHub
  • Re: [I] Waterfall Chart consumes the last data row as its total bar, so that row's value is never plotted [texera] via GitHub
• [PR] fix(sklearn): rename SVR shrinking parameter [texera] via GitHub
  • Re: [PR] fix(sklearn): rename SVR shrinking parameter [texera] via GitHub
  • Re: [PR] fix(sklearn): rename SVR shrinking parameter [texera] via GitHub
  • Re: [PR] fix(sklearn): rename SVR shrinking parameter [texera] via GitHub
  • Re: [PR] fix(sklearn): rename SVR shrinking parameter [texera] via GitHub
• [PR] test(frontend): close the result-table frame's stat-formatting gaps [texera] via GitHub
  • Re: [PR] test(frontend): close the result-table frame's stat-formatting gaps [texera] via GitHub
  • Re: [PR] test(frontend): close the result-table frame's stat-formatting gaps [texera] via GitHub
  • Re: [PR] test(frontend): close the result-table frame's stat-formatting gaps [texera] via GitHub
  • Re: [PR] test(frontend): close the result-table frame's stat-formatting gaps [texera] via GitHub
• [I] Close the result-table frame's remaining stat-formatting gaps [texera] via GitHub
  • Re: [I] Close the result-table frame's remaining stat-formatting gaps [texera] via GitHub
• [PR] feat(treeplot): declare igraph so the Tree Plot operator can run [texera] via GitHub
  • Re: [PR] feat(treeplot): declare igraph so the Tree Plot operator can run [texera] via GitHub
  • Re: [PR] feat(treeplot): declare igraph so the Tree Plot operator can run [texera] via GitHub
  • Re: [PR] feat(treeplot): declare igraph so the Tree Plot operator can run [texera] via GitHub
  • Re: [PR] feat(treeplot): declare igraph so the Tree Plot operator can run [texera] via GitHub
  • Re: [PR] feat(treeplot): declare igraph so the Tree Plot operator can run [texera] via GitHub
• [I] The Tree Plot operator can never run: igraph is not declared in any requirements file [texera] via GitHub
  • Re: [I] The Tree Plot operator can never run: igraph is not declared in any requirements file [texera] via GitHub
• [PR] test(frontend): drive the dashboard list item's controls from the DOM [texera] via GitHub
  • Re: [PR] test(frontend): drive the dashboard list item's controls from the DOM [texera] via GitHub
  • Re: [PR] test(frontend): drive the dashboard list item's controls from the DOM [texera] via GitHub
  • Re: [PR] test(frontend): drive the dashboard list item's controls from the DOM [texera] via GitHub
• [PR] test(frontend): render the login form's sign-up mode and provider flags [texera] via GitHub
  • Re: [PR] test(frontend): render the login form's sign-up mode and provider flags [texera] via GitHub
  • Re: [PR] test(frontend): render the login form's sign-up mode and provider flags [texera] via GitHub
  • Re: [PR] test(frontend): render the login form's sign-up mode and provider flags [texera] via GitHub
• [PR] test(frontend): render the execution-history table instead of calling its handlers [texera] via GitHub
  • Re: [PR] test(frontend): render the execution-history table instead of calling its handlers [texera] via GitHub
  • Re: [PR] test(frontend): render the execution-history table instead of calling its handlers [texera] via GitHub
  • Re: [PR] test(frontend): render the execution-history table instead of calling its handlers [texera] via GitHub
  • Re: [PR] test(frontend): render the execution-history table instead of calling its handlers [texera] via GitHub
  • Re: [PR] test(frontend): render the execution-history table instead of calling its handlers [texera] via GitHub
• [PR] test(agent-service): cover the full logical-plan branch of buildLogicalPlan [texera] via GitHub
  • Re: [PR] test(agent-service): cover the full logical-plan branch of buildLogicalPlan [texera] via GitHub
  • Re: [PR] test(agent-service): cover the full logical-plan branch of buildLogicalPlan [texera] via GitHub
  • Re: [PR] test(agent-service): cover the full logical-plan branch of buildLogicalPlan [texera] via GitHub
• [PR] chore(agent-service): remove the unreferenced workflow validation formatter [texera] via GitHub
  • Re: [PR] chore(agent-service): remove the unreferenced workflow validation formatter [texera] via GitHub
  • Re: [PR] chore(agent-service): remove the unreferenced workflow validation formatter [texera] via GitHub
  • Re: [PR] chore(agent-service): remove the unreferenced workflow validation formatter [texera] via GitHub
• [I] Render the login form's sign-up mode and provider flags [texera] via GitHub
  • Re: [I] Render the login form's sign-up mode and provider flags [texera] via GitHub
  • Re: [I] Render the login form's sign-up mode and provider flags [texera] via GitHub
• [I] Render the search filters and list-item controls from the DOM [texera] via GitHub
  • Re: [I] Render the dashboard list-item controls from the DOM [texera] via GitHub
  • Re: [I] Render the dashboard list-item controls from the DOM [texera] via GitHub
• [PR] test(frontend): cover the admin settings uploads and save guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the admin settings uploads and save guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the admin settings uploads and save guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the admin settings uploads and save guards [texera] via GitHub
• [I] Cover the workflow validation formatter and the full logical-plan branch [texera] via GitHub
  • Re: [I] Cover the workflow validation formatter and the full logical-plan branch [texera] via GitHub
• [I] Render the execution-history table instead of calling its handlers [texera] via GitHub
  • Re: [I] Render the execution-history table instead of calling its handlers [texera] via GitHub
• [PR] test(frontend): cover the dataset detail component's upload-progress paths [texera] via GitHub
  • Re: [PR] test(frontend): cover the dataset detail component's upload-progress paths [texera] via GitHub
  • Re: [PR] test(frontend): cover the dataset detail component's upload-progress paths [texera] via GitHub
  • Re: [PR] test(frontend): cover the dataset detail component's upload-progress paths [texera] via GitHub
• [PR] test(workflow-operator): close the AsterixDB source descriptor's branch arms [texera] via GitHub
  • Re: [PR] test(workflow-operator): close the AsterixDB source descriptor's branch arms [texera] via GitHub
  • Re: [PR] test(workflow-operator): close the AsterixDB source descriptor's branch arms [texera] via GitHub
  • Re: [PR] test(workflow-operator): close the AsterixDB source descriptor's branch arms [texera] via GitHub
  • Re: [PR] test(workflow-operator): close the AsterixDB source descriptor's branch arms [texera] via GitHub
  • Re: [PR] test(workflow-operator): close the AsterixDB source descriptor's branch arms [texera] via GitHub
• [I] Cover the dataset detail component's upload-progress paths [texera] via GitHub
  • Re: [I] Cover the dataset detail component's upload-progress paths [texera] via GitHub
• [I] Close the AsterixDB source descriptor's unpinned branch arms [texera] via GitHub
  • Re: [I] Close the AsterixDB source descriptor's unpinned branch arms [texera] via GitHub
• [PR] test(amber): cover the amber client and the async RPC server [texera] via GitHub
  • Re: [PR] test(amber): cover the amber client and the async RPC server [texera] via GitHub
  • Re: [PR] test(amber): cover the amber client and the async RPC server [texera] via GitHub
  • Re: [PR] test(amber): cover the amber client and the async RPC server [texera] via GitHub
  • Re: [PR] test(amber): cover the amber client and the async RPC server [texera] via GitHub
  • Re: [PR] test(amber): cover the amber client and the async RPC server [texera] via GitHub
• [I] Cover the amber client and the async RPC server [texera] via GitHub
  • Re: [I] Cover the amber client and the async RPC server [texera] via GitHub
• Re: [I] Add option to combine Filter operator predicates with AND instead of only OR [texera] via GitHub
• Re: [I] Add model management API [texera] via GitHub
• [I] An advanced trainer accepts the same hyperparameter twice and emits Python that will not compile [texera] via GitHub
  • Re: [I] An advanced trainer accepts the same hyperparameter twice and emits Python that will not compile [texera] via GitHub
• [PR] test(frontend): run the edge-intersection search against a real paper [texera] via GitHub
  • Re: [PR] test(frontend): run the edge-intersection search against a real paper [texera] via GitHub
  • Re: [PR] test(frontend): run the edge-intersection search against a real paper [texera] via GitHub
  • Re: [PR] test(frontend): run the edge-intersection search against a real paper [texera] via GitHub
  • Re: [PR] test(frontend): run the edge-intersection search against a real paper [texera] via GitHub
• [I] Run the edge-intersection search against a real paper [texera] via GitHub
  • Re: [I] Run the edge-intersection search against a real paper [texera] via GitHub
• [I] The SVM Regressor trainer offers a hyperparameter named `probability`, which sets `shrinking` instead [texera] via GitHub
  • Re: [I] The SVM Regressor trainer offers a hyperparameter named `probability`, which sets `shrinking` instead [texera] via GitHub
  • Re: [I] The SVM Regressor trainer offers a hyperparameter named `probability`, which sets `shrinking` instead [texera] via GitHub
• [PR] feat(frontend): let the upload drop zone grow with its content [texera] via GitHub
  • Re: [PR] feat(frontend): let the upload drop zone grow with its content [texera] via GitHub
  • Re: [PR] feat(frontend): let the upload drop zone grow with its content [texera] via GitHub
  • Re: [PR] feat(frontend): let the upload drop zone grow with its content [texera] via GitHub
  • Re: [PR] feat(frontend): let the upload drop zone grow with its content [texera] via GitHub
  • Re: [PR] feat(frontend): let the upload drop zone grow with its content [texera] via GitHub
• [I] Upload drop zone content overflows its border when the dataset side panel is narrowed [texera] via GitHub
  • Re: [I] Upload drop zone content overflows its border when the dataset side panel is narrowed [texera] via GitHub
  • Re: [I] Upload drop zone content overflows its border when the dataset side panel is narrowed [texera] via GitHub
• [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(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(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(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
• [I] The SVM trainers' gamma cannot be given the value scikit-learn defaults to [texera] via GitHub
  • Re: [I] The SVM trainers' gamma cannot be given the value scikit-learn defaults to [texera] via GitHub
  • Re: [I] The SVM trainers' gamma cannot be given the value scikit-learn defaults to [texera] via GitHub
  • Re: [I] The SVM trainers' gamma cannot be given the value scikit-learn defaults to [texera] via GitHub
• [PR] feat(computing-unit): surface failed/unhealthy computing units instead of an endless "Connecting" [texera] via GitHub
  • Re: [PR] feat(computing-unit): surface failed/unhealthy computing units instead of an endless "Connecting" [texera] via GitHub
  • Re: [PR] feat(computing-unit): surface failed/unhealthy computing units instead of an endless "Connecting" [texera] via GitHub
  • Re: [PR] feat(computing-unit): surface failed/unhealthy computing units instead of an endless "Connecting" [texera] via GitHub
  • Re: [PR] feat(computing-unit): surface failed/unhealthy computing units instead of an endless "Connecting" [texera] via GitHub
• [PR] feat(file-service): complete the model backend for sharing and the hub [texera] via GitHub
  • Re: [PR] feat(file-service): complete the model backend for sharing and the hub [texera] via GitHub
  • Re: [PR] feat(file-service): complete the model backend for sharing and the hub [texera] via GitHub
  • Re: [PR] feat(file-service): complete the model backend for sharing and the hub [texera] via GitHub
  • Re: [PR] feat(file-service): complete the model backend for sharing and the hub [texera] via GitHub
  • Re: [PR] feat(file-service): complete the model backend for sharing and the hub [texera] via GitHub
  • Re: [PR] feat(file-service): complete the model backend for sharing and the hub [texera] via GitHub
  • Re: [PR] feat(file-service): complete the model backend for sharing and the hub [texera] via GitHub
• [I] Frontend: mark the public version and open what a listing advertises [texera] via GitHub
  • Re: [I] Frontend: mark the public version and open what a listing advertises [texera] via GitHub
  • Re: [I] Frontend: mark the public version and open what a listing advertises [texera] via GitHub
• [I] Frontend: choose between following and pinning in the share dialog [texera] via GitHub
  • Re: [I] Frontend: choose between following and pinning in the share dialog [texera] via GitHub
  • Re: [I] Frontend: choose between following and pinning in the share dialog [texera] via GitHub
• [I] Mark the pinned version in the revision history [texera] via GitHub
  • Re: [I] Mark the pinned version in the revision history [texera] via GitHub
  • Re: [I] Mark the pinned version in the revision history [texera] via GitHub
• [I] Match search and listings against the copy on show [texera] via GitHub
  • Re: [I] Match search and listings against the copy on show [texera] via GitHub
  • Re: [I] Match search and listings against the copy on show [texera] via GitHub
• [I] Serve the pinned copy to public viewers [texera] via GitHub
  • Re: [I] Serve the pinned copy to public viewers [texera] via GitHub
  • Re: [I] Serve the pinned copy to public viewers [texera] via GitHub
• [I] Freeze a pinned version as the public copy [texera] via GitHub
  • Re: [I] Freeze a pinned version as the public copy [texera] via GitHub
  • Re: [I] Freeze a pinned version as the public copy [texera] via GitHub
• [PR] feat(python-notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(python-notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(python-notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(python-notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(python-notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(notebook-migration, single-node): deploy the notebook migration service and JupyterLab [texera] via GitHub
• [I] [Notebook Migration] Manage the notebook migration service and JupyterLab in the local dev tooling [texera] via GitHub
  • Re: [I] [Notebook Migration] Manage the notebook migration service and JupyterLab in the local dev tooling [texera] via GitHub
  • Re: [I] [Notebook Migration] Manage the notebook migration service and JupyterLab in the local dev tooling [texera] via GitHub
• [I] An advanced trainer's hyperparameter value is unconstrained and never required, so a wrong or missing one only fails once the run starts [texera] via GitHub
  • Re: [I] An advanced trainer's hyperparameter value is unconstrained and never required, so a wrong or missing one only fails once the run starts [texera] via GitHub
  • Re: [I] An advanced trainer's hyperparameter value is unconstrained and never required, so a wrong or missing one only fails once the run starts [texera] via GitHub
• [PR] feat(local-dev): keep the stored key prefix when refreshing the Lakekeeper warehouse [texera] via GitHub
  • Re: [PR] feat(local-dev): keep the stored key prefix when refreshing the Lakekeeper warehouse [texera] via GitHub
  • Re: [PR] feat(local-dev): keep the stored key prefix when refreshing the Lakekeeper warehouse [texera] via GitHub
  • Re: [PR] feat(local-dev): keep the stored key prefix when refreshing the Lakekeeper warehouse [texera] via GitHub
  • Re: [PR] feat(local-dev): keep the stored key prefix when refreshing the Lakekeeper warehouse [texera] via GitHub
  • Re: [PR] feat(local-dev): reuse the stored storage profile when refreshing the Lakekeeper warehouse [texera] via GitHub
  • Re: [PR] feat(local-dev): reuse the stored storage profile when refreshing the Lakekeeper warehouse [texera] via GitHub
  • Re: [PR] feat(local-dev): reuse the stored storage profile when refreshing the Lakekeeper warehouse [texera] via GitHub
• [PR] feat(notebook-migration, local-dev): manage the notebook migration service and JupyterLab [texera] via GitHub
  • Re: [PR] feat(notebook-migration, local-dev): manage the notebook migration service and JupyterLab [texera] via GitHub

• Earlier messages
• Later messages