notifications  

Messages by Thread

• • Re: [I] bring DatasetDetailComponent's template and upload error paths to full coverage [texera] via GitHub
• [PR] test(amber): cover the executions resource's export, statistics and history paths [texera] via GitHub
  • Re: [PR] test(amber): cover the executions resource's export, statistics and history paths [texera] via GitHub
  • Re: [PR] test(amber): cover the executions resource's export, statistics and history paths [texera] via GitHub
  • Re: [PR] test(amber): cover the executions resource's export, statistics and history paths [texera] via GitHub
  • Re: [PR] test(amber): cover the executions resource's export, statistics and history paths [texera] via GitHub
  • Re: [PR] test(amber): cover the executions resource's export, statistics and history paths [texera] via GitHub
  • Re: [PR] test(amber): cover the executions resource's export, statistics and history paths [texera] via GitHub
• [I] Pin the executions resource's export, statistics and interaction-history paths [texera] via GitHub
  • Re: [I] Pin the executions resource's export, statistics and interaction-history paths [texera] via GitHub
• [PR] test(amber): cover the websocket handshake and session wiring [texera] via GitHub
  • Re: [PR] test(amber): cover the websocket handshake and session wiring [texera] via GitHub
  • Re: [PR] test(amber): cover the websocket handshake and session wiring [texera] via GitHub
  • Re: [PR] test(amber): cover the websocket handshake and session wiring [texera] via GitHub
  • Re: [PR] test(amber): cover the websocket handshake and session wiring [texera] via GitHub
• [I] Cover the websocket handshake configurator and the session wiring it feeds [texera] via GitHub
  • Re: [I] Cover the websocket handshake configurator and the session wiring it feeds [texera] via GitHub
• Re: [I] Remove the unused EmptyReplayLogger from the amber engine [texera] via GitHub
• [PR] refactor(amber): collapse the single-subclass ReplayLogger base into ReplayLoggerImpl [texera] via GitHub
  • Re: [PR] refactor(amber): collapse the single-subclass ReplayLogger base into ReplayLoggerImpl [texera] via GitHub
  • Re: [PR] refactor(amber): collapse the single-subclass ReplayLogger base into ReplayLoggerImpl [texera] via GitHub
  • Re: [PR] refactor(amber): collapse the single-subclass ReplayLogger base into ReplayLoggerImpl [texera] via GitHub
  • Re: [PR] refactor(amber): collapse the single-subclass ReplayLogger base into ReplayLoggerImpl [texera] via GitHub
  • Re: [PR] refactor(amber): collapse the single-subclass ReplayLogger hierarchy into one class [texera] via GitHub
  • Re: [PR] refactor(amber): collapse the single-subclass ReplayLogger hierarchy into one class [texera] via GitHub
  • Re: [PR] refactor(amber): collapse the single-subclass ReplayLogger hierarchy into one class [texera] via GitHub
• [I] Collapse the single-subclass ReplayLogger base into ReplayLoggerImpl [texera] via GitHub
  • Re: [I] Collapse the single-subclass ReplayLogger base into ReplayLoggerImpl [texera] via GitHub
  • Re: [I] Collapse the single-subclass ReplayLogger base into ReplayLoggerImpl [texera] via GitHub
• [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
  • Re: [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
  • Re: [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
  • Re: [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
  • Re: [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
  • Re: [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
  • Re: [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
  • Re: [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
  • Re: [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
  • Re: [PR] feat(arrow): store and read a timestamp as the wall clock it is [texera] via GitHub
• Re: [I] [Notebook Migration] Add an AI generate workflow entry point on the workflow dashboard [texera] via GitHub
• [I] [Notebook Migration] Upload notebooks under a per-workflow filename [texera] via GitHub
  • Re: [I] [Notebook Migration] Upload notebooks under a per-workflow filename [texera] via GitHub
  • Re: [I] [Notebook Migration] Upload notebooks under a per-workflow filename [texera] via GitHub
• Re: [I] [Notebook Migration] Refactor notebook-migration-service to be stateless [texera] via GitHub
• [I] Surface failed/unhealthy computing units instead of showing "Connecting" indefinitely [texera] via GitHub
  • Re: [I] Surface failed/unhealthy computing units instead of showing "Connecting" indefinitely [texera] via GitHub
• [PR] feat(workflow-operator): vectorize every named text column, not just one [texera] via GitHub
  • Re: [PR] feat(workflow-operator): vectorize every named text column, not just one [texera] via GitHub
  • Re: [PR] feat(workflow-operator): vectorize every named text column, not just one [texera] via GitHub
  • Re: [PR] feat(workflow-operator): vectorize every named text column, not just one [texera] via GitHub
  • Re: [PR] feat(workflow-operator): vectorize every named text column, not just one [texera] via GitHub
  • Re: [PR] feat(workflow-operator): vectorize every named text column, not just one [texera] via GitHub
  • Re: [PR] feat(workflow-operator): vectorize every named text column, not just one [texera] via GitHub
• [I] Sklearn operators vectorize one text column, so a dataset whose text spans several cannot be used [texera] via GitHub
  • Re: [I] Sklearn operators vectorize one text column, so a dataset whose text spans several cannot be used [texera] via GitHub
  • Re: [I] Sklearn operators vectorize one text column, so a dataset whose text spans several cannot be used [texera] via GitHub
• Re: [PR] feat: Added backend routes to export workflows + datasets to google drive [texera] via GitHub
  • Re: [PR] feat: Added backend routes to export workflows + datasets to google drive [texera] via GitHub
• [I] Arrow File Scan reads a timestamp in the server's timezone, so one file gives different values on different deployments [texera] via GitHub
  • Re: [I] Arrow File Scan reads a timestamp in the server's timezone, so one file gives different values on different deployments [texera] via GitHub
• [I] [Notebook Migration] Resolve Jupyter URL and token per user [texera] via GitHub
  • Re: [I] [Notebook Migration] Resolve Jupyter URL and token per user [texera] via GitHub
• [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
  • Re: [PR] feat(auth): Add ORCID Login [texera] via GitHub
• Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
  • Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
  • Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
  • Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
  • Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
  • Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
  • Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
  • Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
• Re: [I] Add model file storage and path resolution [texera] via GitHub
• [PR] feat(file-service): add model version upload [texera] via GitHub
  • Re: [PR] feat(file-service): add model version upload [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
  • Re: [PR] feat(file-service): add model file upload and version endpoints [texera] via GitHub
• Re: [I] WorkflowOperator can't run tests that execute generated Python, and spawns an interpreter per operator [texera] via GitHub
• [PR] test(amber): cover the runtime's serde bootstrap and worker startup [texera] via GitHub
  • Re: [PR] test(amber): cover the runtime's serde bootstrap and worker startup [texera] via GitHub
  • Re: [PR] test(amber): cover the runtime's serde bootstrap and worker startup [texera] via GitHub
  • Re: [PR] test(amber): cover the runtime's serde bootstrap and worker startup [texera] via GitHub
  • Re: [PR] test(amber): cover the runtime's serde bootstrap and worker startup [texera] via GitHub
• [I] Cover the runtime's serde bootstrap and worker startup [texera] via GitHub
  • Re: [I] Cover the runtime's serde bootstrap and worker startup [texera] via GitHub
• [PR] test(frontend): render the hub search result with its real children [texera] via GitHub
  • Re: [PR] test(frontend): render the hub search result with its real children [texera] via GitHub
  • Re: [PR] test(frontend): render the hub search result with its real children [texera] via GitHub
  • Re: [PR] test(frontend): render the hub search result with its real children [texera] via GitHub
• [I] Recover the hub search result template's coverage by rendering its real children [texera] via GitHub
  • Re: [I] Recover the hub search result template's coverage by rendering its real children [texera] via GitHub
• Re: [PR] ci: pull docs from apache/texera release branches at build time [incubator-texera-site] via GitHub
  • Re: [PR] ci: pull docs from apache/texera release branches at build time [incubator-texera-site] via GitHub
• Re: [PR] ci: drive website docs from release branches instead of pushing [texera] via GitHub
  • Re: [PR] ci: drive website docs from release branches instead of pushing [texera] via GitHub
• Re: [I] HuggingFace inference operator: inconsistent input validation, asserts vs a per-row ValueError that crashes the operator [texera] via GitHub
• [PR] ci: dispatch website rebuild on release-branch doc changes (drop push-based sync) [texera] via GitHub
  • Re: [PR] ci: dispatch website rebuild on release-branch doc changes (drop push-based sync) [texera] via GitHub
  • Re: [PR] ci: dispatch website rebuild on release-branch doc changes (drop push-based sync) [texera] via GitHub
  • Re: [PR] ci: dispatch website rebuild on release-branch doc changes (drop push-based sync) [texera] via GitHub
• [PR] ci: remove sync-docs-to-site workflow (superseded by build-time docs sync) [texera] via GitHub
  • Re: [PR] ci: remove sync-docs-to-site workflow (superseded by build-time docs sync) [texera] via GitHub
  • Re: [PR] ci: remove sync-docs-to-site workflow (superseded by build-time docs sync) [texera] via GitHub
  • Re: [PR] ci: remove sync-docs-to-site workflow (superseded by build-time docs sync) [texera] via GitHub
  • Re: [PR] ci: remove sync-docs-to-site workflow (superseded by build-time docs sync) [texera] via GitHub
  • Re: [PR] ci: remove sync-docs-to-site workflow (superseded by build-time docs sync) [texera] via GitHub
• [PR] test(frontend): bring four component templates to full coverage [texera] via GitHub
  • Re: [PR] test(frontend): bring four component templates to full coverage [texera] via GitHub
  • Re: [PR] test(frontend): bring four component templates to full coverage [texera] via GitHub
  • Re: [PR] test(frontend): bring four component templates to full coverage [texera] via GitHub
  • Re: [PR] test(frontend): bring four component templates to full coverage [texera] via GitHub
  • Re: [PR] test(frontend): bring four component templates to full coverage [texera] via GitHub
• [PR] test(amber): cover PveResource's duplicate-name conflict and empty-result paths [texera] via GitHub
  • Re: [PR] test(amber): cover PveResource's duplicate-name conflict and empty-result paths [texera] via GitHub
  • Re: [PR] test(amber): cover PveResource's duplicate-name conflict and empty-result paths [texera] via GitHub
  • Re: [PR] test(amber): cover PveResource's duplicate-name conflict and empty-result paths [texera] via GitHub
  • Re: [PR] test(amber): cover PveResource's duplicate-name conflict and empty-result paths [texera] via GitHub
  • Re: [PR] test(amber): cover PveResource's duplicate-name conflict and empty-result paths [texera] via GitHub
  • Re: [PR] test(amber): cover PveResource's duplicate-name conflict and empty-result paths [texera] via GitHub
• [PR] test(frontend): render the dataset filetree nodes and the admin-user table controls [texera] via GitHub
  • Re: [PR] test(frontend): render the dataset filetree nodes and the admin-user table controls [texera] via GitHub
  • Re: [PR] test(frontend): render the dataset filetree nodes and the admin-user table controls [texera] via GitHub
  • Re: [PR] test(frontend): render the dataset filetree nodes and the admin-user table controls [texera] via GitHub
  • Re: [PR] test(frontend): render the dataset filetree nodes and the admin-user table controls [texera] via GitHub
  • Re: [PR] test(frontend): render the dataset filetree nodes and the admin-user table controls [texera] via GitHub
  • Re: [PR] test(frontend): render the dataset filetree nodes and the admin-user table controls [texera] via GitHub
• [I] bring four small component templates to full coverage [texera] via GitHub
  • Re: [I] bring four small component templates to full coverage [texera] via GitHub
  • Re: [I] bring four small component templates to full coverage [texera] via GitHub
• Re: [I] Remove the orphaned SchemaPropagationResponse HTTP model [texera] via GitHub
• [I] cover PveResource's conflict and error branches [texera] via GitHub
  • Re: [I] cover PveResource's conflict and error branches [texera] via GitHub
  • Re: [I] cover PveResource's conflict and error branches [texera] via GitHub
• [PR] test(amber): add specs for GuestAuthFilter and UserResource [texera] via GitHub
  • Re: [PR] test(amber): add specs for GuestAuthFilter and UserResource [texera] via GitHub
  • Re: [PR] test(amber): add specs for GuestAuthFilter and UserResource [texera] via GitHub
  • Re: [PR] test(amber): add specs for GuestAuthFilter and UserResource [texera] via GitHub
  • Re: [PR] test(amber): add specs for GuestAuthFilter and UserResource [texera] via GitHub
• [I] bring the dataset filetree and admin-user search templates to full coverage [texera] via GitHub
  • Re: [I] bring the dataset filetree and admin-user search templates to full coverage [texera] via GitHub
• [I] cover GuestAuthFilter and UserResource [texera] via GitHub
  • Re: [I] cover GuestAuthFilter and UserResource [texera] via GitHub
• [PR] test(workflow-compiler): Extend WorkflowCompilerSpec to cover the Python code-generation error path [texera] via GitHub
  • Re: [PR] test(workflow-compiler): Extend WorkflowCompilerSpec to cover the Python code-generation error path [texera] via GitHub
  • Re: [PR] test(workflow-compiler): Extend WorkflowCompilerSpec to cover the Python code-generation error path [texera] via GitHub
  • Re: [PR] test(workflow-compiler): Extend WorkflowCompilerSpec to cover the Python code-generation error path [texera] via GitHub
  • Re: [PR] test(workflow-compiler): Extend WorkflowCompilerSpec to cover the Python code-generation error path [texera] via GitHub
• [PR] test(amber): cover AdvanceRegionExecutionsHandler [texera] via GitHub
  • Re: [PR] test(amber): cover AdvanceRegionExecutionsHandler [texera] via GitHub
  • Re: [PR] test(amber): cover AdvanceRegionExecutionsHandler [texera] via GitHub
  • Re: [PR] test(amber): cover AdvanceRegionExecutionsHandler [texera] via GitHub
  • Re: [PR] test(amber): cover AdvanceRegionExecutionsHandler [texera] via GitHub
• [I] add unit test coverage for the coordinator AdvanceRegionExecutionsHandler [texera] via GitHub
  • Re: [I] add unit test coverage for the coordinator AdvanceRegionExecutionsHandler [texera] via GitHub
• [I] extend WorkflowCompilerSpec to cover the Python code-generation error path [texera] via GitHub
  • Re: [I] extend WorkflowCompilerSpec to cover the Python code-generation error path [texera] via GitHub
• [PR] feat(gui): take the required marker from the schema's own condition [texera] via GitHub
  • Re: [PR] feat(gui): take the required marker from the schema's own condition [texera] via GitHub
  • Re: [PR] feat(gui): take the required marker from the schema's own condition [texera] via GitHub
  • Re: [PR] feat(gui): take the required marker from the schema's own condition [texera] via GitHub
  • Re: [PR] feat(gui): take the required marker from the schema's own condition [texera] via GitHub
  • Re: [PR] feat(gui): take the required marker from the schema's own condition [texera] via GitHub
• [PR] feat(workflow-operator): constrain the Sklearn text column, and drop what an estimator cannot fit [texera] via GitHub
  • Re: [PR] feat(workflow-operator): constrain the Sklearn text column, and drop what an estimator cannot fit [texera] via GitHub
  • Re: [PR] feat(workflow-operator): constrain the Sklearn text column, and drop what an estimator cannot fit [texera] via GitHub
  • Re: [PR] feat(workflow-operator): constrain the Sklearn text column, and drop what an estimator cannot fit [texera] via GitHub
  • Re: [PR] feat(workflow-operator): constrain the Sklearn text column, and drop what an estimator cannot fit [texera] via GitHub
  • Re: [PR] feat(workflow-operator): constrain the Sklearn text column, and drop what an estimator cannot fit [texera] via GitHub
  • Re: [PR] feat(workflow-operator): constrain the Sklearn text columns, and drop what an estimator cannot fit [texera] via GitHub
• [I] Sklearn operators end the run on two configurations they could refuse or handle [texera] via GitHub
  • Re: [I] Sklearn operators end the run on two configurations they could refuse or handle [texera] via GitHub

• Earlier messages
• Later messages