notifications  

Messages by Thread

• • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
  • Re: [PR] refactor(file-service): make the file-tree builder resource-aware for model upload [texera] via GitHub
• [PR] chore(amber): the example JoinOperator raises TypeError on every match [texera] via GitHub
  • Re: [PR] chore(amber): the example JoinOperator raises TypeError on every match [texera] via GitHub
  • Re: [PR] chore(amber): the example JoinOperator raises TypeError on every match [texera] via GitHub
  • Re: [PR] chore(amber): the example JoinOperator raises TypeError on every match [texera] via GitHub
  • Re: [PR] chore(amber): the example JoinOperator raises TypeError on every match [texera] via GitHub
  • Re: [PR] chore(amber): the example JoinOperator raises TypeError on every match [texera] via GitHub
• [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
  • Re: [PR] refactor(file-service): share the dataset access and naming rules [texera] via GitHub
• [I] the example JoinOperator raises TypeError on every match — Tuple does not support `+` [texera] via GitHub
  • Re: [I] the example JoinOperator raises TypeError on every match — Tuple does not support `+` [texera] via GitHub
• [PR] feat(frontend): ask an account with no email address for one at sign-in [texera] via GitHub
  • Re: [PR] feat(frontend): ask an account with no email address for one at sign-in [texera] via GitHub
  • Re: [PR] feat(frontend): ask an account with no email address for one at sign-in [texera] via GitHub
  • Re: [PR] feat(frontend): ask an account with no email address for one at sign-in [texera] via GitHub
  • Re: [PR] feat(frontend): ask an account with no email address for one at sign-in [texera] via GitHub
  • Re: [PR] feat(frontend): ask an account with no email address for one at sign-in [texera] via GitHub
  • Re: [PR] feat(frontend): ask an account with no email address for one at sign-in [texera] via GitHub
  • Re: [PR] feat(frontend): ask an account with no email address for one at sign-in [texera] via GitHub
• [I] Add email modal for accounts without emails provided. [texera] via GitHub
  • Re: [I] Add email modal for accounts without emails provided. [texera] via GitHub
  • Re: [I] Add email modal for accounts without emails provided. [texera] via GitHub
• [I] Agent panel tab-selection test fails intermittently in CI [texera] via GitHub
  • Re: [I] Agent panel tab-selection test fails intermittently in CI [texera] via GitHub
• [PR] fix(test, frontend): stop the agent-panel tab test depending on nz-tabs click timing [texera] via GitHub
  • Re: [PR] fix(test, frontend): stop the agent-panel tab test depending on nz-tabs click timing [texera] via GitHub
  • Re: [PR] fix(test, frontend): stop the agent-panel tab test depending on nz-tabs click timing [texera] via GitHub
  • Re: [PR] fix(test, frontend): stop the agent-panel tab test depending on nz-tabs click timing [texera] via GitHub
• [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
  • Re: [PR] feat(amber): decouple the Lakekeeper catalog name from the user-facing name [texera] via GitHub
• [I] [BYO-S3] Decouple the Lakekeeper warehouse name from the user-facing name [texera] via GitHub
  • Re: [I] [BYO-S3] Decouple the Lakekeeper warehouse name from the user-facing name [texera] via GitHub
  • Re: [I] [BYO-S3] Decouple the Lakekeeper warehouse name from the user-facing name [texera] via GitHub
• [PR] feat: require a warehouse for every execution while the feature is enabled [texera] via GitHub
  • Re: [PR] feat: require a warehouse for every execution while the feature is enabled [texera] via GitHub
  • Re: [PR] feat: require a warehouse for every execution while the feature is enabled [texera] via GitHub
  • Re: [PR] feat: require a warehouse for every execution while the feature is enabled [texera] via GitHub
• [I] [BYO-S3] Require a warehouse for every execution while the feature is enabled [texera] via GitHub
  • Re: [I] [BYO-S3] Require a warehouse for every execution while the feature is enabled [texera] via GitHub
• [PR] test(pyamber): add unit test coverage for AddInputChannelHandler [texera] via GitHub
  • Re: [PR] test(pyamber): add unit test coverage for AddInputChannelHandler [texera] via GitHub
  • Re: [PR] test(pyamber): add unit test coverage for AddInputChannelHandler [texera] via GitHub
  • Re: [PR] test(pyamber): add unit test coverage for AddInputChannelHandler [texera] via GitHub
  • Re: [PR] test(pyamber): add unit test coverage for AddInputChannelHandler [texera] via GitHub
• [PR] test(pyamber): add test coverage for AsyncRPCHandlerInitializer [texera] via GitHub
  • Re: [PR] test(pyamber): add test coverage for AsyncRPCHandlerInitializer [texera] via GitHub
  • Re: [PR] test(pyamber): add test coverage for AsyncRPCHandlerInitializer [texera] via GitHub
  • Re: [PR] test(pyamber): add test coverage for AsyncRPCHandlerInitializer [texera] via GitHub
  • Re: [PR] test(pyamber): add test coverage for AsyncRPCHandlerInitializer [texera] via GitHub
  • Re: [PR] test(pyamber): add test coverage for AsyncRPCHandlerInitializer [texera] via GitHub
• [I] add unit test coverage for the Python AddInputChannelHandler [texera] via GitHub
  • Re: [I] add unit test coverage for the Python AddInputChannelHandler [texera] via GitHub
• [I] add unit test coverage for the Python AsyncRPCHandlerInitializer [texera] via GitHub
  • Re: [I] add unit test coverage for the Python AsyncRPCHandlerInitializer [texera] via GitHub
• [I] the Python worker's EvaluatePythonExpression reply is silently dropped: EvaluatedValue is not registered in ControlReturn's oneof [texera] via GitHub
  • Re: [I] the Python worker's EvaluatePythonExpression reply is silently dropped: EvaluatedValue is not registered in ControlReturn's oneof [texera] via GitHub
  • Re: [I] the Python worker's EvaluatePythonExpression reply is silently dropped: EvaluatedValue is not registered in ControlReturn's oneof [texera] via GitHub
• [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [PR] feat(amber): expose the warehouse owner in DashboardWarehouse [texera] via GitHub
• [PR] fix(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] fix(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] fix(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] feat(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] feat(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] feat(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] feat(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] feat(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] feat(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] feat(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] feat(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
  • Re: [PR] feat(amber): wait out Lakekeeper's asynchronous purge when deleting a warehouse [texera] via GitHub
• [I] [BYO-S3] Expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [I] [BYO-S3] Expose the warehouse owner in DashboardWarehouse [texera] via GitHub
  • Re: [I] [BYO-S3] Expose the warehouse owner in DashboardWarehouse [texera] via GitHub
• [I] Warehouse deletion should wait out Lakekeeper's asynchronous purge instead of failing with 409 [texera] via GitHub
  • Re: [I] Warehouse deletion should wait out Lakekeeper's asynchronous purge instead of failing with 409 [texera] via GitHub
  • Re: [I] [BYO-S3] Warehouse deletion should wait out Lakekeeper's asynchronous purge instead of failing with 409 [texera] via GitHub
• [PR] feat(notebook-migration): remove a workflow's notebook file from the Jupyter pod on delete [texera] via GitHub
  • Re: [PR] feat(notebook-migration): remove a workflow's notebook file from the Jupyter pod on delete [texera] via GitHub
  • Re: [PR] feat(notebook-migration): remove a workflow's notebook file from the Jupyter pod on delete [texera] via GitHub
  • Re: [PR] feat(notebook-migration): remove a workflow's notebook file from the Jupyter pod on delete [texera] via GitHub
  • Re: [PR] feat(notebook-migration): remove a workflow's notebook file from the Jupyter pod on delete [texera] via GitHub
  • Re: [PR] feat(notebook-migration): remove a workflow's notebook file from the Jupyter pod on delete [texera] via GitHub
  • Re: [PR] feat(notebook-migration): remove a workflow's notebook file from the Jupyter pod on delete [texera] via GitHub
  • Re: [PR] feat(notebook-migration): remove a workflow's notebook file from the Jupyter pod on delete [texera] via GitHub
• [PR] fix(deploy): give the default Iceberg warehouse its own key prefix [texera] via GitHub
  • Re: [PR] fix(deploy): give the default Iceberg warehouse its own key prefix [texera] via GitHub
  • Re: [PR] fix(deploy): give the default Iceberg warehouse its own key prefix [texera] via GitHub
  • Re: [PR] feat(storage): give the default Iceberg warehouse its own key prefix [texera] via GitHub
  • Re: [PR] feat(storage): give the default Iceberg warehouse its own key prefix [texera] via GitHub
  • Re: [PR] feat(storage): give the default Iceberg warehouse its own key prefix [texera] via GitHub
• [I] [BYO-S3] Per-user warehouse creation always fails: the default warehouse owns the bucket root [texera] via GitHub
  • Re: [I] [BYO-S3] Per-user warehouse creation always fails: the default warehouse owns the bucket root [texera] via GitHub
  • Re: [I] [BYO-S3] Per-user warehouse creation always fails: the default warehouse owns the bucket root [texera] via GitHub
• [PR] feat(notebook-migration, frontend): upload notebooks under a per-work… [texera] via GitHub
  • Re: [PR] feat(notebook-migration, frontend): upload notebooks under a per-work… [texera] via GitHub
  • Re: [PR] feat(notebook-migration, frontend): upload notebooks under a per-work… [texera] via GitHub
  • Re: [PR] feat(notebook-migration, frontend): upload notebooks under a per-work… [texera] via GitHub
  • Re: [PR] feat(notebook-migration, frontend): upload notebooks under a per-work… [texera] via GitHub
  • Re: [PR] feat(notebook-migration, frontend): upload notebooks under a per-work… [texera] via GitHub
  • Re: [PR] feat(notebook-migration, frontend): upload notebooks under a per-work… [texera] via GitHub
• [I] [Notebook Migration] Deleting a notebook leaves its .ipynb file in the Jupyter pod [texera] via GitHub
  • Re: [I] [Notebook Migration] Deleting a notebook leaves its .ipynb file in the Jupyter pod [texera] via GitHub
  • Re: [I] [Notebook Migration] Deleting a notebook leaves its .ipynb file in the Jupyter pod [texera] via GitHub
• [PR] fix(frontend, v1.2): give unit tests timeout headroom for loaded macOS runners [texera] via GitHub
  • Re: [PR] fix(frontend, v1.2): give unit tests timeout headroom for loaded macOS runners [texera] via GitHub
  • Re: [PR] fix(frontend, v1.2): give unit tests timeout headroom for loaded macOS runners [texera] via GitHub
  • Re: [PR] fix(frontend, v1.2): give unit tests timeout headroom for loaded macOS runners [texera] via GitHub
  • Re: [PR] fix(frontend, v1.2): give unit tests timeout headroom for loaded macOS runners [texera] via GitHub
• [PR] test(frontend): cover the code editor's genuinely untested half [texera] via GitHub
  • Re: [PR] test(frontend): cover the code editor's genuinely untested half [texera] via GitHub
  • Re: [PR] test(frontend): cover the code editor's genuinely untested half [texera] via GitHub
  • Re: [PR] test(frontend): cover the code editor's genuinely untested half [texera] via GitHub
• [I] Cover the code editor's genuinely untested half [texera] via GitHub
  • Re: [I] Cover the code editor's genuinely untested half [texera] via GitHub
• [PR] test(frontend): cover the console frame's controls and the preset guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the console frame's controls and the preset guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the console frame's controls and the preset guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the console frame's controls and the preset guards [texera] via GitHub
• [I] Cover the console frame's controls and the preset service's guards [texera] via GitHub
  • Re: [I] Cover the console frame's controls and the preset service's guards [texera] via GitHub
• [PR] test(amber): cover the materialization reader thread and the executor initializer [texera] via GitHub
  • Re: [PR] test(amber): cover the materialization reader thread and the executor initializer [texera] via GitHub
  • Re: [PR] test(amber): cover the materialization reader thread and the executor initializer [texera] via GitHub
  • Re: [PR] test(amber): cover the materialization reader thread and the executor initializer [texera] via GitHub
  • Re: [PR] test(amber): cover the materialization reader thread and the executor initializer [texera] via GitHub
• [I] Cover the input-port materialization reader thread and the executor initializer [texera] via GitHub
  • Re: [I] Cover the input-port materialization reader thread and the executor initializer [texera] via GitHub
• [PR] test(frontend): cover the compiling service and the search-results template [texera] via GitHub
  • Re: [PR] test(frontend): cover the compiling service and the search-results template [texera] via GitHub
  • Re: [PR] test(frontend): cover the compiling service and the search-results template [texera] via GitHub
  • Re: [PR] test(frontend): cover the compiling service and the search-results template [texera] via GitHub
• [I] Cover the compiling service and recover the search-results template's coverage [texera] via GitHub
  • Re: [I] Cover the compiling service and recover the search-results template's coverage [texera] via GitHub
• Re: [PR] chore(deps, frontend): update frontend patch updates [texera] via GitHub
  • Re: [PR] chore(deps, frontend): update frontend patch updates [texera] via GitHub
  • [PR] chore(deps, frontend): update frontend patch updates [texera] via GitHub
  • Re: [PR] chore(deps, frontend): update frontend patch updates [texera] via GitHub
  • Re: [PR] chore(deps, frontend): update frontend patch updates [texera] via GitHub
  • Re: [PR] chore(deps, frontend): update frontend patch updates [texera] via GitHub
  • [PR] chore(deps, frontend): update frontend patch updates [texera] via GitHub
  • Re: [PR] chore(deps, frontend): update frontend patch updates [texera] via GitHub
  • Re: [PR] chore(deps, frontend): update frontend patch updates [texera] via GitHub
• Re: [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • Re: [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • Re: [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • Re: [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • Re: [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • Re: [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • Re: [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • Re: [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
  • Re: [PR] chore(deps, amber): update sbt patch updates [texera] via GitHub
• [PR] chore(deps): update aws-java-sdk-v2 monorepo to v2.53.1 [texera] via GitHub
  • Re: [PR] chore(deps): update aws-java-sdk-v2 monorepo to v2.53.1 [texera] via GitHub
  • Re: [PR] chore(deps): update aws-java-sdk-v2 monorepo to v2.53.1 [texera] via GitHub

• Earlier messages
• Later messages