notifications  

Messages by Thread

• • Re: [PR] fix(frontend): show validation errors on the Hugging Face field and drop two redundant guards [texera] via GitHub
  • Re: [PR] fix(frontend): show validation errors on the Hugging Face field and drop two redundant guards [texera] via GitHub
• [I] Hugging Face field never shows validation errors, plus two redundant template guards [texera] via GitHub
  • Re: [I] Hugging Face field never shows validation errors, plus two redundant template guards [texera] via GitHub
  • Re: [I] Hugging Face field never shows validation errors, plus two redundant template guards [texera] via GitHub
• [PR] chore(amber): remove unused actor helpers, an unreferenced RPC sentinel and four unreachable guards [texera] via GitHub
  • Re: [PR] chore(amber): remove unused actor helpers, an unreferenced RPC sentinel and four unreachable guards [texera] via GitHub
  • Re: [PR] chore(amber): remove unused actor helpers, an unreferenced RPC sentinel and four unreachable guards [texera] via GitHub
  • Re: [PR] chore(amber): remove unused actor helpers, an unreferenced RPC sentinel and four unreachable guards [texera] via GitHub
  • Re: [PR] chore(amber): remove unused actor helpers, an unreferenced RPC sentinel and four unreachable guards [texera] via GitHub
  • Re: [PR] chore(amber): remove unused actor helpers, an unreferenced RPC sentinel and four unreachable guards [texera] via GitHub
  • Re: [PR] refactor(amber): remove dead members and unreachable guards [texera] via GitHub
• [I] Unused actor helpers, an unreferenced RPC sentinel and four unreachable guards in amber [texera] via GitHub
  • Re: [I] Unused actor helpers, an unreferenced RPC sentinel and four unreachable guards in amber [texera] via GitHub
• [PR] chore(frontend, amber): remove the unreachable available-result event and orphaned list item [texera] via GitHub
  • Re: [PR] chore(frontend, amber): remove the unreachable available-result event and orphaned list item [texera] via GitHub
  • Re: [PR] chore(frontend, amber): remove the unreachable available-result event and orphaned list item [texera] via GitHub
  • Re: [PR] chore(frontend, amber): remove the unreachable available-result event and orphaned list item [texera] via GitHub
  • Re: [PR] chore(frontend, amber): remove the unreachable available-result event and orphaned list item [texera] via GitHub
• [I] Unreachable websocket event, orphaned dataset list-item component and unused schema helper [texera] via GitHub
  • Re: [I] Unreachable websocket event, orphaned dataset list-item component and unused schema helper [texera] via GitHub
  • Re: [I] Unreachable websocket event, orphaned dataset list-item component and unused schema helper [texera] via GitHub
  • Re: [I] Unreachable websocket event, orphaned dataset list-item component and unused schema helper [texera] via GitHub
• [PR] chore(amber): remove the unused ClosureRequest from ClientActor [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ClosureRequest from ClientActor [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ClosureRequest from ClientActor [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ClosureRequest from ClientActor [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ClosureRequest from ClientActor [texera] via GitHub
• [PR] chore(amber): remove the unused ReportCurrentProcessingTuple client event [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ReportCurrentProcessingTuple client event [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ReportCurrentProcessingTuple client event [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ReportCurrentProcessingTuple client event [texera] via GitHub
  • Re: [PR] chore(amber): remove the unused ReportCurrentProcessingTuple client event [texera] via GitHub
• [I] Remove the unused ReportCurrentProcessingTuple client event [texera] via GitHub
  • Re: [I] Remove the unused ReportCurrentProcessingTuple client event [texera] via GitHub
• [I] Remove the unused ClosureRequest message from ClientActor [texera] via GitHub
  • Re: [I] Remove the unused ClosureRequest message from ClientActor [texera] via GitHub
• [I] cover the remaining branches in ResultExportation, PresetService, WorkflowActionService, and ResultTableFrame [texera] via GitHub
• [PR] test(frontend): cover the operator label drag, computing-unit rows and menu clipboard [texera] via GitHub
  • Re: [PR] test(frontend): cover the operator label drag, computing-unit rows and menu clipboard [texera] via GitHub
  • Re: [PR] test(frontend): cover the operator label drag, computing-unit rows and menu clipboard [texera] via GitHub
  • Re: [PR] test(frontend): cover the operator label drag, computing-unit rows and menu clipboard [texera] via GitHub
• [I] Cover the operator label drag, the computing-unit rows and the menu clipboard [texera] via GitHub
  • Re: [I] Cover the operator label drag, the computing-unit rows and the menu clipboard [texera] via GitHub
• [PR] test(common): cover the java-source executor factory, aggregate close, file-scan helpers and operator versioning [texera] via GitHub
  • Re: [PR] test(common): cover the java-source executor factory, aggregate close, file-scan helpers and operator versioning [texera] via GitHub
  • Re: [PR] test(common): cover the java-source executor factory, aggregate close, file-scan helpers and operator versioning [texera] via GitHub
  • Re: [PR] test(common): cover the java-source executor factory, aggregate close, file-scan helpers and operator versioning [texera] via GitHub
  • Re: [PR] test(common): cover the java-source executor factory, aggregate close, file-scan helpers and operator versioning [texera] via GitHub
• [I] Cover the java-source executor factory, aggregate close, file-scan helpers and operator versioning [texera] via GitHub
  • Re: [I] Cover the java-source executor factory, aggregate close, file-scan helpers and operator versioning [texera] via GitHub
• [PR] test(frontend): render the small templates instead of calling their handlers [texera] via GitHub
  • Re: [PR] test(frontend): render the small templates instead of calling their handlers [texera] via GitHub
  • Re: [PR] test(frontend): render the small templates instead of calling their handlers [texera] via GitHub
  • Re: [PR] test(frontend): render the small templates instead of calling their handlers [texera] via GitHub
• [I] Render the small workspace and dashboard templates instead of calling their handlers [texera] via GitHub
  • Re: [I] Render the small workspace and dashboard templates instead of calling their handlers [texera] via GitHub
• [PR] test(amber): cover the promise handlers, metadata endpoint and actor-ref mapping [texera] via GitHub
  • Re: [PR] test(amber): cover the promise handlers, metadata endpoint and actor-ref mapping [texera] via GitHub
  • Re: [PR] test(amber): cover the promise handlers, metadata endpoint and actor-ref mapping [texera] via GitHub
  • Re: [PR] test(amber): cover the promise handlers, metadata endpoint and actor-ref mapping [texera] via GitHub
  • Re: [PR] test(amber): cover the promise handlers, metadata endpoint and actor-ref mapping [texera] via GitHub
• [I] Cover the promise handlers, the metadata endpoint and the actor-ref mapping service [texera] via GitHub
  • Re: [I] Cover the promise handlers, the metadata endpoint and the actor-ref mapping service [texera] via GitHub
• [PR] test(workflow-operator): guard visualization output schemas [texera] via GitHub
  • Re: [PR] test(workflow-operator): guard visualization output schemas [texera] via GitHub
  • Re: [PR] test(workflow-operator): guard visualization output schemas [texera] via GitHub
  • Re: [PR] test(workflow-operator): guard visualization output schemas [texera] via GitHub
  • Re: [PR] test(workflow-operator): guard visualization output schemas [texera] via GitHub
• [PR] test(workflow-operator): extend tests to cover the Projection drop mode [texera] via GitHub
  • Re: [PR] test(workflow-operator): extend tests to cover the Projection drop mode [texera] via GitHub
  • Re: [PR] test(workflow-operator): extend tests to cover the Projection drop mode [texera] via GitHub
  • Re: [PR] test(workflow-operator): extend tests to cover the Projection drop mode [texera] via GitHub
  • Re: [PR] test(workflow-operator): extend tests to cover the Projection drop mode [texera] via GitHub
• [I] guard visualization operators' getOutputSchemas with a single registry-wide sweep [texera] via GitHub
  • Re: [I] guard visualization operators' getOutputSchemas with a single registry-wide sweep [texera] via GitHub
• [I] cover the Projection operator's drop mode [texera] via GitHub
  • Re: [I] cover the Projection operator's drop mode [texera] via GitHub
• [PR] refactor(file-service): share one upload engine for versioned resources [texera] via GitHub
  • Re: [PR] refactor(file-service): share one upload engine for versioned resources [texera] via GitHub
  • Re: [PR] refactor(file-service): share one upload engine for versioned resources [texera] via GitHub
  • Re: [PR] refactor(file-service): share one upload engine for versioned resources [texera] via GitHub
  • Re: [PR] refactor(file-service): share one upload engine for versioned resources [texera] via GitHub
  • Re: [PR] refactor(file-service): share one upload engine for versioned resources [texera] via GitHub
  • Re: [PR] refactor(file-service): share one upload engine for versioned resources [texera] via GitHub
• [PR] refactor(file-service): extract the shared upload helpers [texera] via GitHub
  • Re: [PR] refactor(file-service): extract the shared upload helpers [texera] via GitHub
  • Re: [PR] refactor(file-service): extract the shared upload helpers [texera] via GitHub
  • Re: [PR] refactor(file-service): extract the shared upload helpers [texera] via GitHub
  • Re: [PR] refactor(file-service): extract the shared upload helpers [texera] via GitHub
  • Re: [PR] refactor(file-service): extract the shared upload helpers [texera] via GitHub
  • Re: [PR] refactor(file-service): extract the shared upload helpers [texera] via GitHub
  • Re: [PR] refactor(file-service): extract the shared upload helpers [texera] via GitHub
  • Re: [PR] refactor(file-service): extract the shared upload helpers [texera] via GitHub
• [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
  • 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

• Earlier messages
• Later messages